>>> ansible: Building community/ansible 7.5.0-r0 (using abuild 3.11.0_rc13-r0) started Fri, 28 Apr 2023 05:57:12 +0000 >>> ansible: Checking sanity of /home/buildozer/aports/community/ansible/APKBUILD... >>> ansible: Analyzing dependencies... >>> ansible: Installing for build: build-base python3 ansible-core py3-gpep517 py3-setuptools py3-wheel (1/48) Installing libbz2 (1.0.8-r5) (2/48) Installing libffi (3.4.4-r2) (3/48) Installing gdbm (1.23-r1) (4/48) Installing xz-libs (5.4.2-r1) (5/48) Installing mpdecimal (2.5.1-r2) (6/48) Installing libpanelw (6.4_p20230401-r6) (7/48) Installing readline (8.2.1-r1) (8/48) Installing sqlite-libs (3.41.2-r2) (9/48) Installing python3 (3.11.3-r10) (10/48) Installing python3-pycache-pyc0 (3.11.3-r10) (11/48) Installing pyc (0.1-r0) (12/48) Installing python3-pyc (3.11.3-r10) (13/48) Installing py3-cparser (2.21-r2) (14/48) Installing py3-cparser-pyc (2.21-r2) (15/48) Installing py3-cffi (1.15.1-r3) (16/48) Installing py3-cffi-pyc (1.15.1-r3) (17/48) Installing py3-cryptography (40.0.2-r1) (18/48) Installing py3-cryptography-pyc (40.0.2-r1) (19/48) Installing py3-markupsafe (2.1.2-r1) (20/48) Installing py3-markupsafe-pyc (2.1.2-r1) (21/48) Installing py3-jinja2 (3.1.2-r2) (22/48) Installing py3-jinja2-pyc (3.1.2-r2) (23/48) Installing py3-parsing (3.0.9-r2) (24/48) Installing py3-parsing-pyc (3.0.9-r2) (25/48) Installing py3-packaging (23.1-r1) (26/48) Installing py3-packaging-pyc (23.1-r1) (27/48) Installing py3-bcrypt (4.0.1-r2) (28/48) Installing py3-bcrypt-pyc (4.0.1-r2) (29/48) Installing py3-pynacl (1.5.0-r4) (30/48) Installing py3-pynacl-pyc (1.5.0-r4) (31/48) Installing py3-paramiko (3.1.0-r1) (32/48) Installing py3-paramiko-pyc (3.1.0-r1) (33/48) Installing py3-resolvelib (0.9.0-r1) (34/48) Installing py3-resolvelib-pyc (0.9.0-r1) (35/48) Installing yaml (0.2.5-r1) (36/48) Installing py3-yaml (6.0-r3) (37/48) Installing py3-yaml-pyc (6.0-r3) (38/48) Installing ansible-core (2.14.5-r0) (39/48) Installing ansible-core-pyc (2.14.5-r0) (40/48) Installing py3-installer (0.7.0-r1) (41/48) Installing py3-installer-pyc (0.7.0-r1) (42/48) Installing py3-gpep517 (13-r2) (43/48) Installing py3-gpep517-pyc (13-r2) (44/48) Installing py3-setuptools (67.7.2-r0) (45/48) Installing py3-setuptools-pyc (67.7.2-r0) (46/48) Installing py3-wheel (0.40.0-r1) (47/48) Installing py3-wheel-pyc (0.40.0-r1) (48/48) Installing .makedepends-ansible (20230428.055714) Executing busybox-1.36.0-r8.trigger OK: 474 MiB in 146 packages >>> ansible: Cleaning up srcdir >>> ansible: Cleaning up pkgdir >>> ansible: Fetching https://distfiles.alpinelinux.org/distfiles/v3.18/ansible-7.5.0.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 88 35.9M 88 31.7M 0 0 42.0M 0 --:--:-- --:--:-- --:--:-- 42.0M 100 35.9M 100 35.9M 0 0 45.0M 0 --:--:-- --:--:-- --:--:-- 45.0M >>> ansible: Fetching https://distfiles.alpinelinux.org/distfiles/v3.18/ansible-7.5.0.tar.gz >>> ansible: Checking sha512sums... ansible-7.5.0.tar.gz: OK >>> ansible: Unpacking /var/cache/distfiles/v3.18/ansible-7.5.0.tar.gz... 2023-04-28 05:57:19,592 gpep517 INFO Building wheel via backend setuptools.build_meta 2023-04-28 05:57:19,638 root INFO running bdist_wheel 2023-04-28 05:57:19,657 root INFO running build 2023-04-28 05:57:19,657 root INFO running build_py 2023-04-28 05:57:19,662 root INFO creating build 2023-04-28 05:57:19,662 root INFO creating build/lib 2023-04-28 05:57:19,662 root INFO creating build/lib/ansible_collections 2023-04-28 05:57:19,662 root INFO copying ansible_collections/ansible_community.py -> build/lib/ansible_collections 2023-04-28 05:57:19,663 root INFO copying ansible_collections/ansible_release.py -> build/lib/ansible_collections 2023-04-28 05:57:19,663 root INFO running egg_info 2023-04-28 05:57:19,673 root INFO writing ansible.egg-info/PKG-INFO 2023-04-28 05:57:19,674 root INFO writing dependency_links to ansible.egg-info/dependency_links.txt 2023-04-28 05:57:19,674 root INFO writing entry points to ansible.egg-info/entry_points.txt 2023-04-28 05:57:19,674 root INFO writing requirements to ansible.egg-info/requires.txt 2023-04-28 05:57:19,675 root INFO writing top-level names to ansible.egg-info/top_level.txt 2023-04-28 05:57:19,730 root INFO reading manifest file 'ansible.egg-info/SOURCES.txt' 2023-04-28 05:57:20,074 root INFO reading manifest template 'MANIFEST.in' 2023-04-28 05:57:29,517 root INFO adding license file 'COPYING' 2023-04-28 05:57:34,070 root INFO writing manifest file 'ansible.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.autoscaling_group.roles.ec2_asg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.aws_az_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.aws_caller_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.callback_aws_resource_actions.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudformation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudtrail.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatch_metric_alarm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchevent_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.cloudwatchlogs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.vars' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_ami.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_eni.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_block_devices.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_checkmode_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_cpu_options.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_default_vpc_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_ebs_optimized.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_external_resource_attach.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_hibernation_options.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_iam_instance_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_minimal.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_multiple.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_instance_no_wait.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_metadata_options.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_security_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_state_config_updates.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_tags_and_vpc_settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_termination_protection.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_instance_uptime.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_metadata_facts.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_security_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_spot_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.vars' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_tag.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vol.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_dhcp_option.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_endpoint_service_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_igw.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_nat_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_net.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_route_table.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.ec2_vpc_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_application_lb.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.vars' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.elb_classic_lb.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_user' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.iam_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_ec2.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.inventory_aws_rds.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.kms_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.kms_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.kms_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.kms_key' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.kms_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.kms_key.roles.aws_kms.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_alias.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lambda_policy.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.legacy_missing_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_account_attribute.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_secret.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_service_ip_ranges.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.lookup_aws_ssm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_botocore_recorder' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_botocore_recorder' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_botocore_recorder' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_botocore_recorder' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_botocore_recorder' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.roles' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_core.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.library' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.module_utils_waiter.roles.get_waiter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.vars' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster.roles.rds_cluster.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.vars' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_cluster_snapshot.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_aurora.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_complex.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_modify.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_processor.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_replica.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_restore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_sgroups.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.vars' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_snapshot_mgmt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_states.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_tagging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_instance_upgrade.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_option_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_param_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.rds_subnet_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53.vars' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53_health_check.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.route53_zone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_bucket.roles.s3_bucket.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_object' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_object' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_object' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_object' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_object' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.templates' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.s3_object.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.handlers' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_botocore_pip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.defaults' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.handlers' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_ec2_instance_env.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.files' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.meta' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.integration.targets.setup_sshkey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.arn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.arn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.arn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.arn' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.arn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.botocore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.botocore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.botocore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.botocore' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.botocore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.cloud' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.elbv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.elbv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.elbv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.elbv2' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.elbv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.modules.ansible_aws_module' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.modules.ansible_aws_module' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.modules.ansible_aws_module' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.modules.ansible_aws_module' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.modules.ansible_aws_module' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.policy' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.retries' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.retries' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.retries' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.retries' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.retries' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.module_utils.transformation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.module_utils.transformation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.module_utils.transformation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.module_utils.transformation' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.module_utils.transformation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.ec2_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.ec2_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.ec2_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.ec2_instance' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.ec2_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures.certs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures.certs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures.certs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures.certs' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.fixtures.certs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.basic_s3_stack' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.basic_s3_stack' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.basic_s3_stack' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.basic_s3_stack' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.basic_s3_stack' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.client_request_token_s3_stack' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.client_request_token_s3_stack' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.client_request_token_s3_stack' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.client_request_token_s3_stack' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.client_request_token_s3_stack' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.delete_nonexistent_stack' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.delete_nonexistent_stack' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.delete_nonexistent_stack' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.delete_nonexistent_stack' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.delete_nonexistent_stack' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.get_nonexistent_stack' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.get_nonexistent_stack' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.get_nonexistent_stack' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.get_nonexistent_stack' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.get_nonexistent_stack' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.invalid_template_json' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.invalid_template_json' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.invalid_template_json' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.invalid_template_json' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.invalid_template_json' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_delete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_delete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_delete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_delete' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_delete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_do_nothing' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_do_nothing' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_do_nothing' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_do_nothing' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_do_nothing' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_rollback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_rollback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_rollback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_rollback' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.plugins.modules.placebo_recordings.cloudformation.on_create_failure_rollback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.amazon.aws.tests.unit.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.amazon.aws.tests.unit.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.amazon.aws.tests.unit.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.amazon.aws.tests.unit.utils' to be distributed and are already explicitly excluding 'ansible_collections.amazon.aws.tests.unit.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.docs' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.become' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.become' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.become' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.become' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.become' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.cache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.cache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.cache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.cache' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.cache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.cli_parser' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.cli_parser' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.cli_parser' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.cli_parser' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.cli_parser' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.cfg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.cfg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.cfg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.cfg' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.cfg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.facts' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.rm_base' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.rm_base' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.rm_base' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.rm_base' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.network.common.rm_base' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.network.grpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.network.grpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.network.grpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.network.grpc' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.network.grpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.network.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.network.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.network.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.network.netconf' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.network.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.network.restconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.network.restconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.network.restconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.network.restconf' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.network.restconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.module_utils.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.module_utils.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.module_utils.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.module_utils.utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.module_utils.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.netconf' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.sub_plugins.cli_parser' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.sub_plugins.cli_parser' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.sub_plugins.cli_parser' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.sub_plugins.cli_parser' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.sub_plugins.cli_parser' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.plugins.sub_plugins.grpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.plugins.sub_plugins.grpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.plugins.sub_plugins.grpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.plugins.sub_plugins.grpc' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.plugins.sub_plugins.grpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.cli_parse.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.tests.iosxr.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tests.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tests.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tests.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tests.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.grpc_get.tests.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.junos.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_config.tests.nxos.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.junos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.junos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.junos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.junos' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.junos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.sros' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.sros' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.sros' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.sros' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_get.tests.sros' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.junos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.junos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.junos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.junos' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.junos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.sros' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.sros' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.sros' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.sros' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.netconf_rpc.tests.sros' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxe_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxe_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxe_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxe_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxe_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_iosxr_tests.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_junos_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_junos_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_junos_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_junos_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_junos_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_nxos_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_nxos_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_nxos_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_nxos_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_nxos_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_sros_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_sros_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_sros_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_sros_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.prepare_sros_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tests.iosxe' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tests.iosxe' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tests.iosxe' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tests.iosxe' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_config.tests.iosxe' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tests.iosxe' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tests.iosxe' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tests.iosxe' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tests.iosxe' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.integration.targets.restconf_get.tests.iosxe' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network.common' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.module_utils.network.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.modules.network.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.modules.network.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.modules.network.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.modules.network.cli' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.modules.network.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins.action.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins.action.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins.action.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins.action.network' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins.action.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins.cli_parsers.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures.network' to be distributed and are already explicitly excluding 'ansible_collections.ansible.netcommon.tests.unit.plugins.filter.fixtures.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.docs' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.hacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.hacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.hacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.hacking' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.hacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.plugins.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.plugins.shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.plugins.shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.plugins.shell' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.plugins.shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.acl' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.at' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.at' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.at' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.at' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.at' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.at.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.at.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.at.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.at.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.at.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.at.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.at.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.at.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.at.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.at.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.authorized_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.firewalld' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.firewalld' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.firewalld' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.firewalld' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.firewalld' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.firewalld.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.firewalld_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.mount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.mount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.mount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.mount' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.mount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.mount.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.mount.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.mount.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.mount.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.mount.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.patch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.patch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.patch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.patch' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.patch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.patch.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.patch.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.patch.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.patch.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.patch.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.patch.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.patch.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.patch.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.patch.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.patch.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.patch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.patch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.patch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.patch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.patch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.prepare_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.prepare_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.prepare_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.prepare_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.prepare_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.seboolean' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.seboolean' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.seboolean' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.seboolean' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.seboolean' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.seboolean.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.seboolean.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.seboolean.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.seboolean.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.seboolean.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.selinux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.selinux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.selinux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.selinux' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.selinux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.selinux.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.selinux.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.selinux.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.selinux.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.selinux.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.setup_pkg_mgr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.setup_pkg_mgr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.setup_pkg_mgr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.setup_pkg_mgr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.setup_pkg_mgr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.synchronize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.synchronize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.synchronize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.synchronize' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.synchronize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.synchronize.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.sysctl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.sysctl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.sysctl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.sysctl' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.sysctl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.integration.targets.sysctl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.modules.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.modules.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.modules.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.modules.system' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.modules.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become_cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become_cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become_cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become_cli' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_become_cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_become_cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_become_cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_become_cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_become_cli' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_become_cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_sudo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_sudo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_sudo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_sudo' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_vagrant_sudo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_with_private_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_with_private_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_with_private_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_with_private_key' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.basic_with_private_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_play_context_private_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_play_context_private_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_play_context_private_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_play_context_private_key' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_play_context_private_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_su' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_su' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_su' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_su' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_su' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_with_private_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_with_private_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_with_private_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_with_private_key' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.unit.plugins.action.fixtures.synchronize.delegate_remote_with_private_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.posix.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.posix.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.posix.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.posix.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.ansible.posix.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.docs' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.module_utils.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.module_utils.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.module_utils.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.module_utils.common' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.module_utils.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.plugin_utils.base' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.plugin_utils.base' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.plugin_utils.base' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.plugin_utils.base' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.plugin_utils.base' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.sub_plugins.cli_parser' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.sub_plugins.cli_parser' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.sub_plugins.cli_parser' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.sub_plugins.cli_parser' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.sub_plugins.cli_parser' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.sub_plugins.fact_diff' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.sub_plugins.fact_diff' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.sub_plugins.fact_diff' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.sub_plugins.fact_diff' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.sub_plugins.fact_diff' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.sub_plugins.validate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.sub_plugins.validate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.sub_plugins.validate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.sub_plugins.validate' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.sub_plugins.validate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.plugins.test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.plugins.test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.plugins.test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.plugins.test' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.plugins.test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.output' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.output' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.output' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.output' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.output' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_cli_parse.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_consolidate.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_fact_diff.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_fact_diff.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_fact_diff.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_fact_diff.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_fact_diff.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_from_xml.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_from_xml.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_from_xml.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_from_xml.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_from_xml.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_get_path.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_get_path.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_get_path.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_get_path.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_get_path.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_index_of.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_index_of.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_index_of.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_index_of.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_index_of.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_ipaddr_filter.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_keep_keys.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_netaddr_test.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_param_list_compare.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_param_list_compare.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_param_list_compare.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_param_list_compare.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_param_list_compare.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_remove_keys.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_replace_keys.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_paths.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_paths.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_paths.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_paths.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_paths.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_to_xml.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_update_fact.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_update_fact.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_update_fact.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_update_fact.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_update_fact.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_usable_range.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.criteria' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.criteria' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.criteria' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.criteria' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.criteria' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.data' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.files.data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.config' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.jsonschema' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.jsonschema' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.jsonschema' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.jsonschema' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.tests.jsonschema' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.integration.targets.utils_validate.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.module_utils.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.module_utils.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.module_utils.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.module_utils.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.module_utils.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.action.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.action.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.action.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.action.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.action.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.cli_parsers.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.validate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.validate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.validate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.validate' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.sub_plugins.validate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.utils.tests.unit.plugins.test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.utils.tests.unit.plugins.test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.utils.tests.unit.plugins.test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.utils.tests.unit.plugins.test' to be distributed and are already explicitly excluding 'ansible_collections.ansible.utils.tests.unit.plugins.test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_Process.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_SCManager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.module_utils_WebRequest.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.handlers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_http_tests.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.handlers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_device.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.setup_win_printargv.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_acl' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_acl_inheritance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_certificate_store.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_command' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_command.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_command.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_command.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_command.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_command.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_command.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_command.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_command.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_command.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_command.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_copy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_copy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_copy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_copy' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_copy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2.subdir3.subdir4' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2.subdir3.subdir4' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2.subdir3.subdir4' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2.subdir3.subdir4' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.files.subdir.subdir2.subdir3.subdir4' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_copy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dns_client.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_domain_membership.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestClassDsc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestClassDsc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestClassDsc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestClassDsc' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestClassDsc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestCompositeDsc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestCompositeDsc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestCompositeDsc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestCompositeDsc' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestCompositeDsc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestDsc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestDsc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestDsc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestDsc' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.files.xTestDsc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_dsc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_environment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_environment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_environment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_environment' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_environment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_environment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_feature' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_feature' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_feature' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_feature' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_feature' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_feature.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_file' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_file' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_file' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_file' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_file' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar.directory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar.directory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar.directory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar.directory' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_file.files.foobar.directory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_file.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_file.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_file.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_file.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_file.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_file.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_file.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_file.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_file.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_file.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_find' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_find' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_find' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_find' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_find' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_find.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_find.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_find.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_find.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_find.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_find.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_find.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_find.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_find.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_find.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_find.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_find.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_find.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_find.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_find.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.anon' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.anon' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.anon' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.anon' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.anon' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.user' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.files.ftp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_get_url.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_group' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_group_membership.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_hostname.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_optional_feature.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_owner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_owner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_owner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_owner' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_owner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_owner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package.handlers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_package.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_package.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_package.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_package.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_package.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_path' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_path' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_path' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_path' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_path' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_path.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_path.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_path.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_path.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_path.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_ping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_ping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_ping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_ping' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_ping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_ping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_ping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_ping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_ping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_ping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_powershell.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reboot.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_reg_stat.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_regedit.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.handlers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_service_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_setup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_setup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_setup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_setup' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_setup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_setup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_share' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_share' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_share' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_share' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_share' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_share.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_share.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_share.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_share.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_share.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_share.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_share.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_share.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_share.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_share.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_shell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_shell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_shell' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_shell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_shell.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_shell.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_shell.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_shell.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_shell.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_slurp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_stat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_stat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_stat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_stat' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_stat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_stat.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_tempfile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_template' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_template.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_template.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_template.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_template.templates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_template.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_template.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_template.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_template.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_template.vars' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_template.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_updates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_updates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_updates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_updates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_updates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_updates.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_uri' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_uri' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_uri' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_uri' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_uri' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.meta' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_uri.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.library' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_user_right.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.files' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_wait_for.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.integration.targets.win_whoami.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.unit.test_data.win_updates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.unit.test_data.win_updates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.unit.test_data.win_updates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.unit.test_data.win_updates' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.unit.test_data.win_updates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ansible.windows.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ansible.windows.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ansible.windows.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ansible.windows.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.ansible.windows.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.docs' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acls' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.hostname' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.vlans' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.argspec.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acls' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.hostname' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.vlans' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.config.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acls' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.hostname' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.vlans' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.facts.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config.bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config.bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config.bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config.bgp' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.providers.cli.config.bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.rm_templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.rm_templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.rm_templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.rm_templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.rm_templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.module_utils.network.eos.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.module_utils.network.eos.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.module_utils.network.eos.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.module_utils.network.eos.utils' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.module_utils.network.eos.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acl_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_acls.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_banner.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_address_family.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_bgp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_command.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_command.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_command.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_command.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_command.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_command.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli_config' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.cli_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_config.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_eapi.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_facts.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_hostname.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l2_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_l3_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lacp_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lag_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_lldp_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_logging_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ntp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospf_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv2.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_ospfv3.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_prefix_lists.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_route_maps.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_smoke.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.templates' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_snmp_server.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_static_routes.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.eapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.eapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.eapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.eapi' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_system.tests.eapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_user.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.vars' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vlans.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.eos_vrf.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.integration.targets.prepare_eos_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.unit.modules.network.eos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.unit.modules.network.eos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.unit.modules.network.eos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.unit.modules.network.eos' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.unit.modules.network.eos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.arista.eos.tests.unit.modules.network.eos.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.arista.eos.tests.unit.modules.network.eos.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.arista.eos.tests.unit.modules.network.eos.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.arista.eos.tests.unit.modules.network.eos.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.arista.eos.tests.unit.modules.network.eos.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.images' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.meta' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.test.awx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.test.awx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.test.awx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.test.awx' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.test.awx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_cancel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_cancel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_cancel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_cancel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_cancel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_wait.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_wait.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_wait.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_wait.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.ad_hoc_command_wait.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.application.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.application.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.application.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.application.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.application.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.bulk_host_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.bulk_host_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.bulk_host_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.bulk_host_create' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.bulk_host_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.bulk_job_launch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.bulk_job_launch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.bulk_job_launch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.bulk_job_launch' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.bulk_job_launch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.credential.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.credential.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.credential.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.credential.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.credential.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.credential_input_source.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.credential_input_source.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.credential_input_source.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.credential_input_source.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.credential_input_source.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.credential_type.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.credential_type.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.credential_type.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.credential_type.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.credential_type.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.demo_data.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.demo_data.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.demo_data.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.demo_data.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.demo_data.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.execution_environment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.execution_environment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.execution_environment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.execution_environment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.execution_environment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.export' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.export' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.export' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.export' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.export' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.export.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.export.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.export.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.export.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.export.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.import' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.import' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.import' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.import' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.import' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.import.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.import.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.import.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.import.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.import.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.instance_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.instance_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.instance_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.instance_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.instance_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.inventory.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.inventory.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.inventory.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.inventory.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.inventory.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.inventory_source.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.inventory_source.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.inventory_source.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.inventory_source.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.inventory_source.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.inventory_source_update.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.inventory_source_update.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.inventory_source_update.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.inventory_source_update.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.inventory_source_update.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.job_cancel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.job_cancel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.job_cancel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.job_cancel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.job_cancel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.job_launch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.job_launch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.job_launch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.job_launch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.job_launch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.job_list.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.job_list.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.job_list.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.job_list.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.job_list.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.job_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.job_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.job_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.job_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.job_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.job_wait.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.job_wait.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.job_wait.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.job_wait.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.job_wait.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.label.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.label.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.label.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.label.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.label.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.lookup_api_plugin.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.lookup_api_plugin.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.lookup_api_plugin.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.lookup_api_plugin.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.lookup_api_plugin.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.lookup_rruleset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.lookup_rruleset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.lookup_rruleset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.lookup_rruleset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.lookup_rruleset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.notification_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.notification_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.notification_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.notification_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.notification_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.organization.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.organization.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.organization.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.organization.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.organization.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.project.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.project.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.project.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.project.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.project.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.project_manual.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.project_manual.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.project_manual.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.project_manual.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.project_manual.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.project_update.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.project_update.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.project_update.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.project_update.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.project_update.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.schedule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.schedule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.schedule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.schedule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.schedule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.schedule_rrule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.schedule_rrule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.schedule_rrule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.schedule_rrule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.schedule_rrule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.team.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.team.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.team.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.team.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.team.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.token.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.token.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.token.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.token.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.token.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.workflow_approval.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.workflow_approval.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.workflow_approval.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.workflow_approval.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.workflow_approval.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.workflow_job_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.workflow_job_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.workflow_job_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.workflow_job_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.workflow_job_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.integration.targets.workflow_launch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.integration.targets.workflow_launch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.integration.targets.workflow_launch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.integration.targets.workflow_launch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.integration.targets.workflow_launch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.awx.awx.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.awx.awx.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.awx.awx.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.awx.awx.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.awx.awx.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_account_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_acs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adapplication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adpassword.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_adserviceprincipal.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aduser.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aks.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_aksagentpool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagement.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_apimanagementservice.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.files' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appgateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_appserviceplan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationaccount.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_automationrunbook.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_autoscale.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_availabilityset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_azurefirewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backupazurevm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_backuppolicy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_bastionhost.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_batchaccount.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cdnprofile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cognitivesearch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerinstance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_containerregistrytag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_cosmosdbaccount.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datafactory.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_datalakestore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ddosprotectionplan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_deployment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.lookup_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.lookup_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.lookup_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.lookup_plugins' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.lookup_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_diskencryptionset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnsrecordset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_dnszone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_eventhub.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_expressroute.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_firewallpolicy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_functionapp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_gallery.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hdinsightcluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_hostgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_image.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_iothub.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_ipgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.lookup_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.lookup_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.lookup_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.lookup_plugins' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.lookup_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvault.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.lookup_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.lookup_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.lookup_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.lookup_plugins' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.lookup_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultkey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.lookup_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.lookup_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.lookup_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.lookup_plugins' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.lookup_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_keyvaultsecret.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loadbalancer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_loganalyticsworkspace.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_manageddisk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_managementgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mariadbserver.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitordiagnosticsetting.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_monitorlogprofile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.defaults' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.templates' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_multiplemanageddisks.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_mysqlserver.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_natgateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_networkinterface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_notificationhub.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_openshiftmanagedcluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_postgresqlserver.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednsrecordset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatednszonelink.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpoint.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privateendpointdnszonegroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_privatelinkservice.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_proximityplacementgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_publicipaddress.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_recoveryservicesvault.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_rediscache.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationassignment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_registrationdefinition.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resource.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_resourcegroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roleassignment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_roledefinition.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_routetable.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_securitygroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_servicebus.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlmanagedinstance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_sqlserver.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageaccount.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.files' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageblob.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_storageshare.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_subscription.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_trafficmanagerprofile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhub.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualhubconnection.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachine.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.files' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineextension.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachineimage_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinescaleset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualmachinesize_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetwork.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkgateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualnetworkpeering.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_virtualwan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vmbackuppolicy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_vpnsite.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webapp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappaccessrestriction.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_webappvnetconnection.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.meta' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.tasks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.azure_rm_workspace.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.templates' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.inventory_azure.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.integration.targets.setup_azure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.integration.targets.setup_azure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.integration.targets.setup_azure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.integration.targets.setup_azure' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.integration.targets.setup_azure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.utils.ado' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.utils.ado' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.utils.ado' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.utils.ado' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.utils.ado' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.azure.azcollection.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.azure.azcollection.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.azure.azcollection.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.azure.azcollection.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.azure.azcollection.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.meta' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.tests.units.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.tests.units.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.tests.units.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.tests.units.modules' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.tests.units.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.check_point.mgmt.tests.units.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.check_point.mgmt.tests.units.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.check_point.mgmt.tests.units.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.check_point.mgmt.tests.units.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.check_point.mgmt.tests.units.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.meta' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.plugins' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.defaults' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.files' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.setup_win_chocolatey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.defaults' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.files' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.meta' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.filter_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.filter_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.filter_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.filter_plugins' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.filter_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.tasks' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_feature.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.defaults' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.library' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.tasks' to be distributed and are already explicitly excluding 'ansible_collections.chocolatey.chocolatey.tests.integration.targets.win_chocolatey_source.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_custom_privilege.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.pki' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.pki' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.pki' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.pki' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.pki' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_ssh_auth.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.pki' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.pki' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.pki' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.pki' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.pki' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aaa_user_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_block_to_access_port.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_port_to_interface_policy_leaf_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_dst_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_span_filter_group_entry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_access_sub_port_block_to_access_port.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_aep_to_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_ap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_dhcp_label.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bd_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_asn.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bgp_rr_node.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_bulk_static_binding_to_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_aws_provider.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_aws_provider.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_aws_provider.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_aws_provider.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_aws_provider.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_bgp_asn.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_cidr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_ctx_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_epg_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_external_epg_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_provider.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_region.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_vpn_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_cloud_zone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_export_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_rollback.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_config_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_export.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_filter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_contract_subject_to_service_graph.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dhcp_relay_provider.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_dns_provider.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_encap_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_domain_to_vlan_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_encap_pool_range.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_contract_master.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_epg_to_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_contract_master.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_epg_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_ip_subnet_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_esg_tag_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_leaf_switch_assoc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_node.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_pod_policy_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_spine_switch_assoc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_block.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_fabric_switch_policy_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_filter_entry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_firmware_source.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_igmp_interface_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_blacklist.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_description.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_cdp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_breakout_port_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_policy_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_leaf_profile_fex_policy_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_link_level.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_ospf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_port_security.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_policy_spanning_tree.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_interface_selector_to_switch_policy_leaf_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_extepg_to_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_path.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_interface_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l2out_logical_node_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_bgp_peer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extepg_to_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_extsubnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_interface_secondary_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_profile_ospf_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_interface_vpc_member.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_logical_node_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_l3out_static_routes_nexthop.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_lookup_interface_range.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_node_mgmt_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_ntp_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.pki' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.pki' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.pki' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.pki' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.pki' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.xml_files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.xml_files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.xml_files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.xml_files' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_rest.tasks.xml_files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_client_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_community_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_snmp_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_binding_to_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_static_node_mgmt_address.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_leaf_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_leaf_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_switch_policy_vpc_protection_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_remote_dest.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_syslog_source.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_system' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_taboo_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_dst_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_src.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_tenant_span_src_group_to_dst_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vlan_pool_encap_block.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_controller.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_credential.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_uplink_container.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vmm_vswitch_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.integration.targets.aci_vzany_to_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.aci.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.aci.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.aci.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.aci.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.aci.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.docs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.ogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.ogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.ogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.ogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.argspec.ogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.ogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.ogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.ogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.ogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.config.ogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.ogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.ogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.ogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.ogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.facts.ogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.providers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.providers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.providers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.providers' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.providers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.rm_templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.rm_templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.rm_templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.rm_templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.rm_templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.module_utils.network.asa.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_acls.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.redirection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.redirection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.redirection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.redirection' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_config.tests.redirection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_ogs.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.integration.targets.asa_smoke.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.unit.modules.network.asa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.unit.modules.network.asa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.unit.modules.network.asa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.unit.modules.network.asa' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.unit.modules.network.asa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.asa.tests.unit.modules.network.asa.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.asa.tests.unit.modules.network.asa.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.asa.tests.unit.modules.network.asa.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.asa.tests.unit.modules.network.asa.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.asa.tests.unit.modules.network.asa.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.docs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.docs._gh_include' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.docs._gh_include' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.docs._gh_include' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.docs._gh_include' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.docs._gh_include' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.playbooks.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.playbooks.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.playbooks.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.playbooks.files' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.playbooks.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.plugins' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.tests.unit.modules.dnac' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.tests.unit.modules.dnac' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.tests.unit.modules.dnac' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.tests.unit.modules.dnac' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.tests.unit.modules.dnac' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.dnac.tests.unit.modules.dnac.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.dnac.tests.unit.modules.dnac.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.dnac.tests.unit.modules.dnac.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.dnac.tests.unit.modules.dnac.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.dnac.tests.unit.modules.dnac.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.misc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.misc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.misc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.misc' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.misc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.auto_support.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.auto_support.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.auto_support.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.auto_support.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.auto_support.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_storage.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_storage.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_storage.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_storage.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.cluster_storage.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.deploy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.deploy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.deploy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.deploy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.deploy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_storage.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_storage.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_storage.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_storage.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_cluster_storage.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_software_version.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_software_version.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_software_version.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_software_version.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.edge_software_version.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.fc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.fc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.fc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.fc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.fc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.intersight_org.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.intersight_org.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.intersight_org.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.intersight_org.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.intersight_org.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.iscsi.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.iscsi.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.iscsi.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.iscsi.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.iscsi.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.local_credential.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.local_credential.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.local_credential.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.local_credential.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.local_credential.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_profiles.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_profiles.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_profiles.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_profiles.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.node_profiles.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.software_version.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.software_version.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.software_version.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.software_version.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.software_version.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.sys_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.sys_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.sys_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.sys_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.sys_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.vcenter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.vcenter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.vcenter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.vcenter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.hyperflex_policies.vcenter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.policies.server_policies.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.policies.server_policies.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.policies.server_policies.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.policies.server_policies.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.policies.server_policies.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.playbooks.roles.servers.actions.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.playbooks.roles.servers.actions.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.playbooks.roles.servers.actions.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.playbooks.roles.servers.actions.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.playbooks.roles.servers.actions.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.plugins' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.intersight.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.intersight.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.intersight.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.intersight.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.intersight.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.docs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ping' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.ping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.vlans' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.argspec.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ping' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.ping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.vlans' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.config.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.vlans' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.facts.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config.bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config.bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config.bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config.bgp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.providers.cli.config.bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.rm_templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.rm_templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.rm_templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.rm_templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.rm_templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.module_utils.network.ios.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acl_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_acls.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_banner.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_address_family.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_bgp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_cliconf.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli_config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.cli_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.redirection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.redirection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.redirection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.redirection' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_config.tests.redirection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_hostname.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l2_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_l3_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lacp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lag_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_linkagg.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_lldp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_logging_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ntp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospf_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv2.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ospfv3.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_ping.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_prefix_lists.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_route_maps.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_smoke.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_snmp_server.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_static_routes.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_system.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.files' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_user.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.ios_vlans.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.integration.targets.prepare_ios_tests.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.modules.network.ios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.modules.network.ios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.modules.network.ios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.modules.network.ios' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.modules.network.ios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.modules.network.ios.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.modules.network.ios.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.modules.network.ios.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.modules.network.ios.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.modules.network.ios.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.ios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.ios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.ios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.ios' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.ios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.nos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.nos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.nos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.nos' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.nos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.slxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.slxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.slxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.slxos' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ios.tests.unit.plugins.cliconf.fixtures.slxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.docs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_neighbor_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_neighbor_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_neighbor_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_neighbor_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.bgp_neighbor_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ping' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.ping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.argspec.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_neighbor_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_neighbor_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_neighbor_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_neighbor_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.bgp_neighbor_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ping' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.ping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.config.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_neighbor_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_neighbor_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_neighbor_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_neighbor_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.bgp_neighbor_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.facts.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config.bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config.bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config.bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config.bgp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.providers.cli.config.bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.rm_templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.rm_templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.rm_templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.rm_templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.rm_templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.module_utils.network.iosxr.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.netconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc.pb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc.pb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc.pb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc.pb' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.sub_plugins.grpc.pb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acl_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_acls.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_banner.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_address_family.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_bgp_neighbor_address_family.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_cliconf.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli_config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.cli_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.redirection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.redirection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.redirection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.redirection' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_config.tests.redirection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_hostname.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l2_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_l3_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lacp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lag_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_lldp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_logging_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_netconf.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ntp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospf_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv2.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ospfv3.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_ping.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.tests.cli.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_prefix_lists.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_smoke.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_snmp_server.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_static_routes.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_system.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.files' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.iosxr_user.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.integration.targets.prepare_iosxr_tests.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf_ncs540.iosxr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf_ncs540.iosxr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf_ncs540.iosxr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf_ncs540.iosxr' to be distributed and are already explicitly excluding 'ansible_collections.cisco.iosxr.tests.unit.modules.network.iosxr.fixtures.cliconf_ncs540.iosxr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.docs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.docs._gh_include' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.docs._gh_include' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.docs._gh_include' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.docs._gh_include' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.docs._gh_include' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.playbooks.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.playbooks.group_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.playbooks.group_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.playbooks.group_vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.playbooks.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.playbooks.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.playbooks.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.playbooks.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.playbooks.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.playbooks.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.aws_deployment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.aws_deployment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.aws_deployment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.aws_deployment' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.aws_deployment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.aws_deployment.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.aws_deployment.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.aws_deployment.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.aws_deployment.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.aws_deployment.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.aws_deployment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.aws_deployment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.aws_deployment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.aws_deployment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.aws_deployment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.aws_deployment.tasks.aws' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.aws_deployment.tasks.aws' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.aws_deployment.tasks.aws' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.aws_deployment.tasks.aws' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.aws_deployment.tasks.aws' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.personas_deployment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.personas_deployment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.personas_deployment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.personas_deployment' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.personas_deployment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.personas_deployment.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.personas_deployment.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.personas_deployment.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.personas_deployment.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.personas_deployment.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.personas_deployment.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.personas_deployment.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.personas_deployment.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.personas_deployment.handlers' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.personas_deployment.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.personas_deployment.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.personas_deployment.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.personas_deployment.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.personas_deployment.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.personas_deployment.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.personas_deployment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.personas_deployment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.personas_deployment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.personas_deployment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.personas_deployment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.personas_deployment.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.personas_deployment.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.personas_deployment.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.personas_deployment.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.personas_deployment.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.roles.personas_deployment.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.roles.personas_deployment.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.roles.personas_deployment.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.roles.personas_deployment.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.roles.personas_deployment.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ise.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ise.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ise.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ise.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ise.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.plugins.module_utils.network.meraki' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.plugins.module_utils.network.meraki' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.plugins.module_utils.network.meraki' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.plugins.module_utils.network.meraki' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.plugins.module_utils.network.meraki' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.scripts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.scripts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.scripts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.scripts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.scripts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_action_batch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_admin.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_alert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_config_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_device.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_firewalled_services.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_management_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l3_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_l7_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_radio.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_rf_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mr_settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_list.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_policies.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_policies.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_policies.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_policies.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_access_policies.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_l3_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_l3_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_l3_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_l3_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_l3_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_link_aggregation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_ospf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_ospf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_ospf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_ospf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_ospf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack_l3_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack_l3_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack_l3_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack_l3_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_stack_l3_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_storm_control.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ms_switchport.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_content_filtering.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_intrusion_prevention.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l2_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l2_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l2_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l2_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l2_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l3_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_l7_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_malware.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_nat.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_network_vlan_settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_site_to_site_vpn.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_static_route.meraki_static_route.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_third_party_vpn_peers.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_uplink_bandwidth.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_mx_vlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_network_settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_organization.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_snmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_ssid.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_syslog.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.integration.targets.meraki_webhook_payload_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.meraki.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.meraki.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.meraki.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.meraki.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.meraki.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.plugins' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_backup_schedule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_option_policy_option.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_dhcp_relay_policy_provider.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_label' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_label' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_label' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_label' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_label' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_label.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_label.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_label.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_label.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_label.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.pki' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.pki' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.pki' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.pki' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.pki' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_remote_location.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_rest.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_role' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_clone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_bulk_staticport.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_anp_epg_staticport.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_l3out.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_bd_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_external_epg_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_l3out.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_service_graph.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_cidr_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_site_vrf_region_hub_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_anp_epg_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_dhcp_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_bd_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_clone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_filter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_contract_service_graph.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_deploy_status.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_selector.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_external_epg_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_filter_entry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_l3out.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_migrate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_service_graph.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_template_vrf_contract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_schema_validate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_service_node_type.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_site' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_site' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_site' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_site' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_site' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_site.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_site.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_site.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_site.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_site.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_tenant_site.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_user' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_version' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.mso_version.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.mso_version.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.mso_version.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.mso_version.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.mso_version.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.integration.targets.ndo_schema_template_deploy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.mso.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.mso.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.mso.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.mso.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.mso.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nso.tests.unit.plugins.modules.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nso.tests.unit.plugins.modules.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nso.tests.unit.plugins.modules.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nso.tests.unit.plugins.modules.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nso.tests.unit.plugins.modules.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.docs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bfd_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bfd_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bfd_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bfd_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bfd_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_neighbor_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_neighbor_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_neighbor_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_neighbor_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.bgp_neighbor_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hsrp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hsrp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hsrp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hsrp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.hsrp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.telemetry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.telemetry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.telemetry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.telemetry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.telemetry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.vlans' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.argspec.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref.telemetry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref.telemetry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref.telemetry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref.telemetry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.cmdref.telemetry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bfd_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bfd_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bfd_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bfd_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bfd_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_neighbor_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_neighbor_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_neighbor_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_neighbor_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.bgp_neighbor_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hsrp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hsrp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hsrp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hsrp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.hsrp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.telemetry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.telemetry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.telemetry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.telemetry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.telemetry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.vlans' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.config.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acls' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bfd_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bfd_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bfd_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bfd_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bfd_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_neighbor_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_neighbor_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_neighbor_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_neighbor_address_family' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.bgp_neighbor_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hostname' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hsrp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hsrp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hsrp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hsrp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.hsrp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.telemetry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.telemetry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.telemetry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.telemetry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.telemetry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.vlans' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.facts.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.rm_templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.rm_templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.rm_templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.rm_templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.rm_templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils.telemetry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils.telemetry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils.telemetry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils.telemetry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.module_utils.network.nxos.utils.telemetry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.modules.storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.modules.storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.modules.storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.modules.storage' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.modules.storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.netconf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_aaa_server_host.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acl_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_acls.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_banner.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bfd_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_address_family.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_af.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_address_family.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_bgp_neighbor_af.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.nxapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.nxapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.nxapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.nxapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_command.tests.nxapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli_config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.cli_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.nxapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.nxapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.nxapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.nxapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.nxapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_config.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_devicealias.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_evpn_vni.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_facts.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_feature.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.nxapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.nxapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.nxapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.nxapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_file_copy.tests.nxapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_gir_profile_management.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hostname.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_hsrp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_interface.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_igmp_snooping.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks.upgrade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks.upgrade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks.upgrade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks.upgrade' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tasks.upgrade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_install_os.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l2_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_l3_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lacp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lag_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_lldp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_logging_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_auth.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ntp_options.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.default' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n5k' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n5k' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n5k' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n5k' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n5k' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n7k' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n7k' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n7k' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n7k' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tasks.platform.n7k' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.nxapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.nxapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.nxapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.nxapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_nxapi.tests.nxapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospf_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv2.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_ospfv3.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks.platform.n7k' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks.platform.n7k' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks.platform.n7k' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks.platform.n7k' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tasks.platform.n7k' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_overlay_global.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_interface.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_pim_rp_address.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_prefix_lists.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_reboot.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rollback.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_route_maps.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_rpm.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_smoke.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snapshot.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_community.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_contact.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_host.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_location.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_server.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_traps.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_snmp_user.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_static_routes.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.nxapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.nxapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.nxapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.nxapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_system.tests.nxapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.templates' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.tests.common.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_telemetry.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_udld_interface.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_user.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vlans.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vpc_interface.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_af.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrf_interface.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vrrp.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vsan.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_domain.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_password.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vtp_version.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks.platform.n7k' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks.platform.n7k' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks.platform.n7k' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks.platform.n7k' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tasks.platform.n7k' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_vxlan_vtep_vni.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.vars' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.nxos_zone_zoneset.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.integration.targets.prepare_nxos_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.mds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.mds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.mds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.mds' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.mds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.nxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.nxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.nxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.nxos' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.cliconf.nxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bfd_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bfd_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bfd_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bfd_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bfd_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bgp' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_command' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_config' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_devicealias' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_devicealias' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_devicealias' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_devicealias' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_devicealias' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_evpn_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_evpn_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_evpn_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_evpn_global' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_evpn_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_feature' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_feature' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_feature' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_feature' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_feature' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface_ospf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface_ospf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface_ospf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface_ospf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_interface_ospf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_l3_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_l3_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_l3_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_l3_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_l3_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n3k' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n3k' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n3k' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n3k' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n3k' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n7k' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n7k' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n7k' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n7k' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_nxapi.n7k' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_rp_address' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_rp_address' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_rp_address' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_rp_address' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_pim_rp_address' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_switchport' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_switchport' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_switchport' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_switchport' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_switchport' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system.vrf_only' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system.vrf_only' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system.vrf_only' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system.vrf_only' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_system.vrf_only' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_telemetry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_telemetry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_telemetry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_telemetry' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_telemetry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlan' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlans' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc_interface' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vpc_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf_af' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf_af' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf_af' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf_af' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vrf_af' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vsan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vsan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vsan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vsan' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vsan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep_vni' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep_vni' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep_vni' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep_vni' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_vxlan_vtep_vni' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_zone_zoneset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_zone_zoneset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_zone_zoneset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_zone_zoneset' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.fixtures.nxos_zone_zoneset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.storage' to be distributed and are already explicitly excluding 'ansible_collections.cisco.nxos.tests.unit.modules.network.nxos.storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.meta' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.misc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.misc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.misc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.misc' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.misc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.playbooks.roles.servers.defaults.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.playbooks.roles.servers.defaults.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.playbooks.roles.servers.defaults.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.playbooks.roles.servers.defaults.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.playbooks.roles.servers.defaults.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profile_templates.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profile_templates.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profile_templates.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profile_templates.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profile_templates.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profiles.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profiles.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profiles.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profiles.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.playbooks.roles.servers.service_profiles.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.plugins' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cisco.ucs.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cisco.ucs.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cisco.ucs.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cisco.ucs.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cisco.ucs.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.plugins.module_utils.turbo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.plugins.module_utils.turbo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.plugins.module_utils.turbo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.plugins.module_utils.turbo' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.plugins.module_utils.turbo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.plugins.plugin_utils.turbo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.plugins.plugin_utils.turbo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.plugins.plugin_utils.turbo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.plugins.plugin_utils.turbo' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.plugins.plugin_utils.turbo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.integration.targets.turbo_fail.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.integration.targets.turbo_fail.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.integration.targets.turbo_fail.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.integration.targets.turbo_fail.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.integration.targets.turbo_fail.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.integration.targets.turbo_lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.integration.targets.turbo_lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.integration.targets.turbo_lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.integration.targets.turbo_lookup' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.integration.targets.turbo_lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode_parallel_exec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode_parallel_exec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode_parallel_exec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode_parallel_exec' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.integration.targets.turbo_mode_parallel_exec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloud.common.tests.unit.plugins.module_utils.turbo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloud.common.tests.unit.plugins.module_utils.turbo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloud.common.tests.unit.plugins.module_utils.turbo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloud.common.tests.unit.plugins.module_utils.turbo' to be distributed and are already explicitly excluding 'ansible_collections.cloud.common.tests.unit.plugins.module_utils.turbo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.common.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.custom_image.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.floating_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.objects_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.server_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.meta' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.integration.targets.volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cloudscale_ch.cloud.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cloudscale_ch.cloud.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cloudscale_ch.cloud.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cloudscale_ch.cloud.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cloudscale_ch.cloud.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws' to be distributed and are already explicitly excluding 'ansible_collections.community.aws' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.accessanalyzer_validate_policy_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.acm_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.acm_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.acm_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.acm_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.acm_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.acm_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.api_gateway_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_complete_lifecycle_action.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_instance_refresh.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_launch_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_lifecycle_hook.roles.ec2_asg_lifecycle_hook.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.autoscaling_scheduled_action.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.aws_region_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.aws_region_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.aws_region_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.aws_region_info' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.aws_region_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.aws_region_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_exports_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudformation_stack_set.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudfront_distribution.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.task' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.task' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.task' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.task' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.cloudfront_reponse_headers_policy.task' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codebuild_project' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codebuild_project' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codebuild_project' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codebuild_project' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codebuild_project' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codebuild_project.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codecommit_repository.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codepipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codepipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codepipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codepipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codepipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codepipeline.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codepipeline.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codepipeline.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codepipeline.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codepipeline.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codepipeline.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codepipeline.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codepipeline.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codepipeline.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codepipeline.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codepipeline.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codepipeline.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codepipeline.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codepipeline.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codepipeline.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.codepipeline.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.codepipeline.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.codepipeline.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.codepipeline.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.codepipeline.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.config' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.config.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.config.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.config.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.config.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.config.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.config.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.config.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_addressing.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_amazon.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_cross_region.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_encrypted_s3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_endpoint.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_fedora.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_profile.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ssm_document.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_ubuntu.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_vars.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.connection_aws_ssm_windows.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_endpoint.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dms_replication_subnet_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.dynamodb_table.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_launch_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_placement_group.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_transit_gateway_vpc_attachment.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_egress_igw.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_nacl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_peer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vgw.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ec2_vpc_vpn.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_ecr.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_tag' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ecs_tag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.efs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.efs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.efs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.efs' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.efs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.efs.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.efs.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.efs.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.efs.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.efs.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.efs.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.efs.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.efs.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.efs.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.efs.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.efs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.efs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.efs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.efs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.efs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_cluster' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_fargate_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.eks_nodegroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticache_subnet_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elasticbeanstalk_app.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_classic_lb_info.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_instance' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_instance.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_instance.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_instance.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_instance.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_instance.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_network_lb.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target_info' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.elb_target_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_connection.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_connection.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_connection.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_connection.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_connection.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_connection.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_connection.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_connection.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_connection.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_connection.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_crawler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_crawler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_crawler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_crawler' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_crawler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_crawler.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_job' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_job' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_job' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_job' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_job' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_job.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_job.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_job.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_job.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_job.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_job.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_job.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_job.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_job.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_job.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.glue_job.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.glue_job.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.glue_job.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.glue_job.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.glue_job.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_access_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_access_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_access_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_access_key' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_access_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_access_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_managed_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_password_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_role' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_role.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_role.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_role.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_role.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_role.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_role.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_role.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_role.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_role.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_role.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_saml_federation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.iam_server_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.inspector_target' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.inspector_target' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.inspector_target' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.inspector_target' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.inspector_target' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.inspector_target.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.inspector_target.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.inspector_target.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.inspector_target.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.inspector_target.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.inspector_target.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.inspector_target.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.inspector_target.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.inspector_target.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.inspector_target.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.inspector_target.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.inspector_target.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.inspector_target.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.inspector_target.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.inspector_target.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.kinesis_stream.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.legacy_missing_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.lightsail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.lightsail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.lightsail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.lightsail' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.lightsail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.lightsail.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.lightsail.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.lightsail.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.lightsail.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.lightsail.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.lightsail.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.lightsail.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.lightsail.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.lightsail.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.lightsail.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.lightsail.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.lightsail.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.lightsail.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.lightsail.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.lightsail.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.lightsail_static_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_cluster' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_config' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.msk_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.msk_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.msk_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.msk_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.msk_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.networkfirewall_rule_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.opensearch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.opensearch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.opensearch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.opensearch' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.opensearch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.opensearch.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.opensearch.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.opensearch.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.opensearch.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.opensearch.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.opensearch.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.opensearch.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.opensearch.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.opensearch.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.opensearch.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.opensearch.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.opensearch.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.opensearch.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.opensearch.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.opensearch.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.opensearch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.opensearch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.opensearch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.opensearch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.opensearch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.opensearch.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.opensearch.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.opensearch.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.opensearch.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.opensearch.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.redshift_subnet_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_bucket_notification.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_lifecycle.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_logging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_logging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_logging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_logging' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_logging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_metrics_configuration.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_sync' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_sync' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_sync' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_sync' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_sync' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_sync.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_sync.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_sync.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_sync.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_sync.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_sync.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_sync.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_sync.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_sync.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_sync.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_sync.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_sync.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_sync.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_sync.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_sync.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.s3_sync.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.s3_sync.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.s3_sync.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.s3_sync.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.s3_sync.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.secretsmanager_secret.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_identity_policy.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ses_rule_set.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_botocore_pip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_connection_aws_ssm.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_ec2_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.setup_sshkey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns_topic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns_topic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns_topic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns_topic' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns_topic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns_topic.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns_topic.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns_topic.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns_topic.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns_topic.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files.sns_topic_lambda' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files.sns_topic_lambda' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files.sns_topic_lambda' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files.sns_topic_lambda' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns_topic.files.sns_topic_lambda' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns_topic.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns_topic.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns_topic.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns_topic.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns_topic.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns_topic.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns_topic.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns_topic.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns_topic.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns_topic.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sns_topic.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sns_topic.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sns_topic.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sns_topic.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sns_topic.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sqs_queue' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sqs_queue' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sqs_queue' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sqs_queue' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sqs_queue' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sqs_queue.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.ssm_parameter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.files' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.stepfunctions_state_machine.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_assume_role.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_session_token' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_session_token' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_session_token' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_session_token' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_session_token' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.sts_session_token.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.waf_web_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_ip_set.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_rule_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.integration.targets.wafv2_web_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures.certs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures.certs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures.certs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures.certs' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.fixtures.certs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_pipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_pipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_pipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_pipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_pipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_without_population' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_without_population' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_without_population' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_without_population' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.activate_without_population' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_false' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_false' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_false' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_false' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_false' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_true' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_true' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_true' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_true' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_exists_true' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_status' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_status' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_status' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_status' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.check_dp_status' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_already_exists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_already_exists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_already_exists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_already_exists' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_already_exists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_with_tags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_with_tags' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_with_tags' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_with_tags' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.create_pipeline_with_tags' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.deactivate_pipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.deactivate_pipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.deactivate_pipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.deactivate_pipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.deactivate_pipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.define_pipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.define_pipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.define_pipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.define_pipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.define_pipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_nonexistent_pipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_nonexistent_pipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_nonexistent_pipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_nonexistent_pipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_nonexistent_pipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_pipeline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_pipeline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_pipeline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_pipeline' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.delete_pipeline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description_nonexistent' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description_nonexistent' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description_nonexistent' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description_nonexistent' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_description_nonexistent' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_field' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_field' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_field' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_field' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.data_pipeline.pipeline_field' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.associations_are_not_updated' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.associations_are_not_updated' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.associations_are_not_updated' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.associations_are_not_updated' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.associations_are_not_updated' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.changed_properties' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.changed_properties' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.changed_properties' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.changed_properties' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.changed_properties' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_does_not_exist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_does_not_exist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_does_not_exist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_does_not_exist' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_does_not_exist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_id' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_id' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_id' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_id' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_id' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_name' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_name' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_name' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_name' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_exists_by_name' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_status' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_status' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_status' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_status' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.connection_status' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.create_and_delete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.create_and_delete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.create_and_delete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.create_and_delete' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_connection.create_and_delete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections_without_force_delete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections_without_force_delete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections_without_force_delete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections_without_force_delete' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_lag_with_connections_without_force_delete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_nonexistent_lag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_nonexistent_lag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_nonexistent_lag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_nonexistent_lag' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.delete_nonexistent_lag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true_no' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true_no' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true_no' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true_no' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_changed_true_no' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists_using_name' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists_using_name' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists_using_name' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists_using_name' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_exists_using_name' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_status' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_status' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_status' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_status' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.lag_status' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_does_not_exist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_does_not_exist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_does_not_exist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_does_not_exist' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_does_not_exist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_status' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_status' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_status' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_status' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.nonexistent_lag_status' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.update_lag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.update_lag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.update_lag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.update_lag' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_link_aggregation_group.update_lag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_private_vi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_private_vi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_private_vi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_private_vi' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_private_vi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_public_vi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_public_vi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_public_vi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_public_vi' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.create_public_vi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.delete_vi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.delete_vi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.delete_vi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.delete_vi' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.delete_vi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_connection_id' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_connection_id' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_connection_id' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_connection_id' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_connection_id' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_name' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_name' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_name' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_name' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_name' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_vi_id' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_vi_id' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_vi_id' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_vi_id' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_by_vi_id' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_missing_for_vi_id' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_missing_for_vi_id' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_missing_for_vi_id' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_missing_for_vi_id' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_missing_for_vi_id' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_multiple' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_multiple' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_multiple' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_multiple' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.directconnect_virtual_interface.find_unique_vi_returns_multiple' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_routes' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_tags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_tags' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_tags' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_tags' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.add_tags' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_nonmodifiable_attr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_nonmodifiable_attr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_nonmodifiable_attr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_nonmodifiable_attr' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_nonmodifiable_attr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_tags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_tags' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_tags' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_tags' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.check_for_update_tags' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection_that_exists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection_that_exists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection_that_exists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection_that_exists' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.create_connection_that_exists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_nonexistent_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_nonexistent_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_nonexistent_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_nonexistent_connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.delete_nonexistent_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_filters' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_filters' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_filters' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_filters' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_filters' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_insufficient_filters' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_insufficient_filters' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_insufficient_filters' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_insufficient_filters' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_insufficient_filters' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_nonexistent' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_nonexistent' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_nonexistent' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_nonexistent' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_nonexistent' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_vpc_conn_id' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_vpc_conn_id' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_vpc_conn_id' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_vpc_conn_id' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.find_connection_vpc_conn_id' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.modify_deleted_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.modify_deleted_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.modify_deleted_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.modify_deleted_connection' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.modify_deleted_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.remove_tags' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.remove_tags' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.remove_tags' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.remove_tags' to be distributed and are already explicitly excluding 'ansible_collections.community.aws.tests.unit.plugins.modules.placebo_recordings.ec2_vpc_vpn.remove_tags' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure' to be distributed and are already explicitly excluding 'ansible_collections.community.azure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.azure.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.azure.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.azure.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.azure.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.azure.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure.tests.utils.ado' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure.tests.utils.ado' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure.tests.utils.ado' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure.tests.utils.ado' to be distributed and are already explicitly excluding 'ansible_collections.community.azure.tests.utils.ado' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.azure.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.azure.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.azure.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.azure.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.azure.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.ciscosmb.tests.unit.plugins.modules.ciscosmb.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.module_utils.acme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.module_utils.acme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.module_utils.acme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.module_utils.acme' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.module_utils.acme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.module_utils.crypto' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.module_utils.crypto' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.module_utils.crypto' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.module_utils.crypto' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.module_utils.crypto' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.module_utils.crypto.module_backends' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.module_utils.crypto.module_backends' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.module_utils.crypto.module_backends' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.module_utils.crypto.module_backends' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.module_utils.crypto.module_backends' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.module_utils.ecs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.module_utils.ecs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.module_utils.ecs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.module_utils.ecs' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.module_utils.ecs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.module_utils.openssh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.module_utils.openssh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.module_utils.openssh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.module_utils.openssh' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.module_utils.openssh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.module_utils.openssh.backends' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.module_utils.openssh.backends' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.module_utils.openssh.backends' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.module_utils.openssh.backends' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.module_utils.openssh.backends' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.crypto_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.crypto_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.crypto_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.crypto_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.crypto_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.luks_device.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.luks_device.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.luks_device.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.luks_device.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.luks_device.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.openssh_keypair.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.openssh_keypair.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.openssh_keypair.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.openssh_keypair.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.openssh_keypair.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.openssl_pkcs12.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.openssl_pkcs12.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.openssl_pkcs12.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.openssl_pkcs12.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.openssl_pkcs12.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.openssl_privatekey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.openssl_privatekey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.openssl_privatekey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.openssl_privatekey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.openssl_privatekey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.smoke.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.smoke.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.smoke.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.smoke.library' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.smoke.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.ee.roles.x509_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.ee.roles.x509_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.ee.roles.x509_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.ee.roles.x509_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.ee.roles.x509_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_account_info.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_certificate_revoke.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_challenge_cert_helper.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.acme_inspect.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files.roots' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files.roots' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files.roots' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files.roots' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.files.roots' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.certificate_complete_chain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.crypto_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.crypto_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.crypto_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.crypto_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.crypto_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.crypto_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_certificate.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.ecs_domain.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_csr_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_privatekey_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_openssl_publickey_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_split_pem.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_certificate_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.filter_x509_crl_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.get_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.get_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.get_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.get_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.get_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.files' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.get_certificate.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.luks_device' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.luks_device' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.luks_device' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.luks_device' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.luks_device' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.luks_device.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.luks_device.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.luks_device.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.luks_device.files' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.luks_device.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.luks_device.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.luks_device.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.luks_device.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.luks_device.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.luks_device.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.luks_device.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.luks_device.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.luks_device.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.luks_device.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.luks_device.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.luks_device.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_cert.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssh_keypair.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_csr_pipe.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_dhparam.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_pkcs12.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_convert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_privatekey_pipe.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_publickey_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.openssl_signature.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_http_tests.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.filter_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.filter_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.filter_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.filter_plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.filter_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.test_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.test_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.test_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.test_plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_jinja2_compat.test_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.prepare_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.prepare_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.prepare_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.prepare_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.prepare_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_acme.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_bcrypt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_openssl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_pkg_mgr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_pkg_mgr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_pkg_mgr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_pkg_mgr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_pkg_mgr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_pyopenssl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.filter_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.filter_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.filter_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.filter_plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.filter_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_python_info.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_constraints.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_agent.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.setup_ssh_keygen.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.files' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_certificate_pipe.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_crl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_crl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_crl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_crl' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_crl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.integration.targets.x509_crl.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.acme.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.crypto' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.crypto' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.crypto' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.crypto' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.crypto' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.openssh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.openssh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.openssh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.openssh' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.unit.plugins.module_utils.openssh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.crypto.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.crypto.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.crypto.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.crypto.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.crypto.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.scripts.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.scripts.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.scripts.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.scripts.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.scripts.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_account_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_balance_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_block_storage.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_cdn_endpoints_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_certificate_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_database_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_domain_record_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_droplet_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_firewall_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_floating_ip_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_image_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_kubernetes_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_load_balancer_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_monitoring_alerts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_project_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_region_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_size_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_snapshot_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_spaces_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_sshkey_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_tag_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_volume_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.integration.targets.digital_ocean_vpc_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.unit.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.unit.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.unit.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.unit.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.unit.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.digitalocean.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.digitalocean.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.digitalocean.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.digitalocean.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.digitalocean.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns' to be distributed and are already explicitly excluding 'ansible_collections.community.dns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.module_utils.conversion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.module_utils.conversion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.module_utils.conversion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.module_utils.conversion' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.module_utils.conversion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.module_utils.hetzner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.module_utils.hetzner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.module_utils.hetzner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.module_utils.hetzner' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.module_utils.hetzner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.module_utils.hosttech' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.module_utils.hosttech' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.module_utils.hosttech' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.module_utils.hosttech' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.module_utils.hosttech' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.module_utils.module' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.module_utils.module' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.module_utils.module' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.module_utils.module' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.module_utils.module' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.plugins.plugin_utils.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.plugins.plugin_utils.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.plugins.plugin_utils.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.plugins.plugin_utils.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.plugins.plugin_utils.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.ee' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.ee' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.ee' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.ee' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.ee' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.ee.roles.filter_domain_suffix.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.ee.roles.filter_domain_suffix.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.ee.roles.filter_domain_suffix.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.ee.roles.filter_domain_suffix.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.ee.roles.filter_domain_suffix.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.ee.roles.wait_for_txt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.ee.roles.wait_for_txt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.ee.roles.wait_for_txt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.ee.roles.wait_for_txt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.ee.roles.wait_for_txt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.filter_domain_suffix.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.hetzner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.hetzner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.hetzner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.hetzner' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.hetzner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.hetzner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.hetzner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.hetzner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.hetzner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.hetzner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.hosttech' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.hosttech' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.hosttech' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.hosttech' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.hosttech' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.hosttech.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.hosttech.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.hosttech.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.hosttech.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.hosttech.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.required_module_params' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.required_module_params' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.required_module_params' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.required_module_params' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.required_module_params' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.required_module_params.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.required_module_params.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.required_module_params.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.required_module_params.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.required_module_params.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.integration.targets.wait_for_txt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.module_utils.conversion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.module_utils.conversion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.module_utils.conversion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.module_utils.conversion' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.module_utils.conversion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hetzner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hetzner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hetzner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hetzner' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hetzner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hosttech' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hosttech' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hosttech' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hosttech' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.module_utils.hosttech' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.module_utils.module' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.module_utils.module' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.module_utils.module' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.module_utils.module' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.module_utils.module' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.dns.tests.unit.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.dns.tests.unit.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.dns.tests.unit.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.dns.tests.unit.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.dns.tests.unit.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker' to be distributed and are already explicitly excluding 'ansible_collections.community.docker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils._api' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils._api' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils._api' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils._api' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils._api' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils._api.api' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils._api.api' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils._api.api' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils._api.api' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils._api.api' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils._api.credentials' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils._api.credentials' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils._api.credentials' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils._api.credentials' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils._api.credentials' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils._api.transport' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils._api.transport' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils._api.transport' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils._api.transport' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils._api.transport' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils._api.types' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils._api.types' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils._api.types' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils._api.types' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils._api.types' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils._api.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils._api.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils._api.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils._api.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils._api.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.module_utils.module_container' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.module_utils.module_container' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.module_utils.module_container' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.module_utils.module_container' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.module_utils.module_container' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.ee' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.ee' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.ee' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.ee' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.ee' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.ee.roles.current_container_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.ee.roles.current_container_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.ee.roles.current_container_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.ee.roles.current_container_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.ee.roles.current_container_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.ee.roles.docker_plain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.ee.roles.docker_plain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.ee.roles.docker_plain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.ee.roles.docker_plain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.ee.roles.docker_plain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.ee.roles.docker_stack.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.ee.roles.docker_stack.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.ee.roles.docker_stack.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.ee.roles.docker_stack.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.ee.roles.docker_stack.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection_docker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection_docker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection_docker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection_docker' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection_docker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection_docker.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection_docker.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection_docker.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection_docker.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection_docker.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection_docker_api.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection_nsenter.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.connection_posix' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.connection_posix' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.connection_posix' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.connection_posix' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.connection_posix' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.current_container_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.current_container_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.current_container_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.current_container_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.current_container_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.current_container_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.current_container_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.current_container_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.current_container_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.current_container_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_compose' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_compose' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_compose' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_compose' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_compose' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_compose.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_compose.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_compose.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_compose.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_compose.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_compose.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_config' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container.files' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container.filter_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container.filter_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container.filter_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container.filter_plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container.filter_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_copy_into.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_exec.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_container_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_host_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_host_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_host_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_host_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_host_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_host_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image_load' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image_load' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image_load' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image_load' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image_load' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_image_load.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_login' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_login' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_login' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_login' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_login' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_login.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_login.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_login.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_login.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_login.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_login.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_network' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_network.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_network_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_network_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_network_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_network_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_network_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_network_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_node' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_node' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_node' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_node' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_node' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_node.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_node.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_node.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_node.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_node.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_node.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_node.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_node.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_node.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_node.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_node_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_node_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_node_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_node_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_node_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_node_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_plugin' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_plugin.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_prune' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_prune' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_prune' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_prune' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_prune' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_prune.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_prune.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_prune.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_prune.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_prune.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_prune.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_prune.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_prune.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_prune.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_prune.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_secret' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_secret' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_secret' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_secret' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_secret' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_secret.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_secret.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_secret.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_secret.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_secret.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_secret.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_secret.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_secret.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_secret.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_secret.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_info.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_stack_task_info.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.files' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_swarm_service_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_volume' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_volume' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_volume' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_volume' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_volume' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_volume.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_volume.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_volume.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_volume.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_volume.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_volume.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.docker_volume_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.files' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.filter_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.filter_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.filter_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.filter_plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.filter_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_connection_tests.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.generic_ssh_connection.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_containers.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_machine.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.inventory_docker_swarm.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_compose_v2.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.files' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_docker_registry.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_epel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_epel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_epel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_epel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_epel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_openssl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_paramiko.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_pkg_mgr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_pkg_mgr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_pkg_mgr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_pkg_mgr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_pkg_mgr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_remote_constraints.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.api' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.api' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.api' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.api' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.api' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.transport' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.transport' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.transport' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.transport' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.transport' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils.testdata.certs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils.testdata.certs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils.testdata.certs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils.testdata.certs' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.module_utils._api.utils.testdata.certs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.unit.plugins.test_support' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.unit.plugins.test_support' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.unit.plugins.test_support' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.unit.plugins.test_support' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.unit.plugins.test_support' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.docker.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.docker.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.docker.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.docker.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.docker.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.plugins.module_utils.fortianalyzer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.plugins.module_utils.fortianalyzer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.plugins.module_utils.fortianalyzer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.plugins.module_utils.fortianalyzer' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.plugins.module_utils.fortianalyzer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.fortios.tests.unit.plugins.modules.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.fortios.tests.unit.plugins.modules.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.fortios.tests.unit.plugins.modules.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.fortios.tests.unit.plugins.modules.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.fortios.tests.unit.plugins.modules.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general' to be distributed and are already explicitly excluding 'ansible_collections.community.general' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.general.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.general.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.general.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.general.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.docs.docsite.helper.lists_mergeby' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.docs.docsite.helper.lists_mergeby' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.docs.docsite.helper.lists_mergeby' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.docs.docsite.helper.lists_mergeby' to be distributed and are already explicitly excluding 'ansible_collections.community.general.docs.docsite.helper.lists_mergeby' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.general.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.become' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.become' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.become' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.become' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.become' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.cache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.cache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.cache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.cache' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.cache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.identity.keycloak' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.identity.keycloak' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.identity.keycloak' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.identity.keycloak' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.identity.keycloak' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.mh' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.mh' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.mh' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.mh' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.mh' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.mh.mixins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.mh.mixins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.mh.mixins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.mh.mixins' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.mh.mixins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.net_tools.pritunl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.net_tools.pritunl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.net_tools.pritunl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.net_tools.pritunl' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.net_tools.pritunl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.oracle' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.oracle' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.oracle' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.oracle' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.oracle' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.remote_management.lxca' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.remote_management.lxca' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.remote_management.lxca' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.remote_management.lxca' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.remote_management.lxca' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.source_control' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.source_control' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.source_control' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.source_control' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.source_control' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.storage.emc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.storage.emc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.storage.emc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.storage.emc' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.storage.emc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.module_utils.storage.hpe3par' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.module_utils.storage.hpe3par' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.module_utils.storage.hpe3par' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.module_utils.storage.hpe3par' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.module_utils.storage.hpe3par' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.plugins.test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.plugins.test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.plugins.test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.plugins.test' to be distributed and are already explicitly excluding 'ansible_collections.community.general.plugins.test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.aix_devices' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.aix_devices' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.aix_devices' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.aix_devices' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.aix_devices' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.aix_devices.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.aix_devices.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.aix_devices.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.aix_devices.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.aix_devices.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.aix_filesystem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.aix_filesystem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.aix_filesystem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.aix_filesystem' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.aix_filesystem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.aix_filesystem.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.aix_filesystem.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.aix_filesystem.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.aix_filesystem.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.aix_filesystem.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.alerta_customer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.alerta_customer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.alerta_customer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.alerta_customer' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.alerta_customer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.alerta_customer.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.alerta_customer.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.alerta_customer.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.alerta_customer.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.alerta_customer.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.alerta_customer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.alerta_customer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.alerta_customer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.alerta_customer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.alerta_customer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.alternatives' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.alternatives' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.alternatives' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.alternatives' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.alternatives' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.alternatives.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.alternatives.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.alternatives.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.alternatives.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.alternatives.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.alternatives.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.alternatives.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.alternatives.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.alternatives.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.alternatives.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.alternatives.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.alternatives.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.alternatives.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.alternatives.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.alternatives.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ansible_galaxy_install.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.apache2_module' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.apache2_module' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.apache2_module' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.apache2_module' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.apache2_module' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.apache2_module.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.apache2_module.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.apache2_module.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.apache2_module.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.apache2_module.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.archive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.archive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.archive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.archive' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.archive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.archive.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.archive.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.archive.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.archive.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.archive.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.archive.files.sub' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.archive.files.sub' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.archive.files.sub' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.archive.files.sub' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.archive.files.sub' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.archive.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.archive.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.archive.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.archive.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.archive.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.archive.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.archive.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.archive.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.archive.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.archive.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.archive.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.archive.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.archive.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.archive.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.archive.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.btrfs_subvolume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.callback' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.callback.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.callback.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.callback.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.callback.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.callback.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.callback_diy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.callback_diy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.callback_diy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.callback_diy' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.callback_diy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.callback_diy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.callback_diy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.callback_diy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.callback_diy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.callback_diy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.callback_log_plays' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.callback_log_plays' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.callback_log_plays' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.callback_log_plays' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.callback_log_plays' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.callback_yaml' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.callback_yaml' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.callback_yaml' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.callback_yaml' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.callback_yaml' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.callback_yaml.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.callback_yaml.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.callback_yaml.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.callback_yaml.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.callback_yaml.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cargo' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cargo' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cargo' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cargo' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cargo' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cargo.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cargo.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cargo.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cargo.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cargo.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cargo.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cargo.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cargo.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cargo.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cargo.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cloud_init_data_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cmd_runner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cmd_runner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cmd_runner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cmd_runner' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cmd_runner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cmd_runner.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cmd_runner.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cmd_runner.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cmd_runner.library' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cmd_runner.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cmd_runner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cmd_runner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cmd_runner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cmd_runner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cmd_runner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cmd_runner.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cmd_runner.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cmd_runner.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cmd_runner.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cmd_runner.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.connection_chroot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.connection_chroot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.connection_chroot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.connection_chroot' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.connection_chroot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.connection_jail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.connection_jail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.connection_jail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.connection_jail' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.connection_jail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.connection_lxc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.connection_lxc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.connection_lxc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.connection_lxc' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.connection_lxc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.connection_lxd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.connection_lxd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.connection_lxd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.connection_lxd' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.connection_lxd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.connection_posix' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.connection_posix' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.connection_posix' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.connection_posix' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.connection_posix' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.consul' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.consul' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.consul' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.consul' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.consul' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.consul.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.consul.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.consul.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.consul.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.consul.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.consul.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.consul.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.consul.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.consul.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.consul.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.consul.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.consul.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.consul.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.consul.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.consul.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.copr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.copr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.copr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.copr' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.copr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.copr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.copr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.copr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.copr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.copr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.copr.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.copr.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.copr.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.copr.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.copr.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cpanm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cpanm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cpanm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cpanm' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cpanm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cpanm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cpanm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cpanm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cpanm.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cpanm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cpanm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cpanm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cpanm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cpanm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cpanm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cronvar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cronvar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cronvar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cronvar' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cronvar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cronvar.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cronvar.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cronvar.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cronvar.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cronvar.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cronvar.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cronvar.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cronvar.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cronvar.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cronvar.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.cronvar.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.cronvar.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.cronvar.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.cronvar.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.cronvar.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.deploy_helper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.deploy_helper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.deploy_helper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.deploy_helper' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.deploy_helper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.deploy_helper.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.deploy_helper.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.deploy_helper.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.deploy_helper.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.deploy_helper.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.deploy_helper.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.deploy_helper.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.deploy_helper.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.deploy_helper.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.deploy_helper.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.discord' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.discord' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.discord' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.discord' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.discord' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.discord.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.discord.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.discord.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.discord.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.discord.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.discord.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.discord.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.discord.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.discord.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.discord.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.django_manage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.django_manage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.django_manage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.django_manage' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.django_manage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1.p1' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1.p1' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1.p1' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1.p1' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.simple_project.p1.p1' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.startproj' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.startproj' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.startproj' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.startproj' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.django_manage.files.base_test.startproj' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.django_manage.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.django_manage.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.django_manage.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.django_manage.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.django_manage.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.django_manage.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.django_manage.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.django_manage.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.django_manage.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.django_manage.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.dnf_versionlock.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.dpkg_divert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.dpkg_divert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.dpkg_divert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.dpkg_divert' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.dpkg_divert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.dpkg_divert.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.etcd3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.etcd3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.etcd3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.etcd3' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.etcd3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.etcd3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.etcd3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.etcd3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.etcd3.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.etcd3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.etcd3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.etcd3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.etcd3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.etcd3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.etcd3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesize' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesize.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesize.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesize.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesize.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesize.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesize.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesize.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesize.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesize.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesize.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesystem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesystem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesystem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesystem' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesystem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesystem.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesystem.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesystem.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesystem.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesystem.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesystem.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesystem.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesystem.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesystem.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesystem.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesystem.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesystem.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesystem.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesystem.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesystem.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filesystem.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filesystem.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filesystem.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filesystem.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filesystem.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_counter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_counter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_counter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_counter' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_counter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_counter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_counter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_counter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_counter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_counter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_dict' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_dict' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_dict' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_dict' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_dict' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_dict.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_dict.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_dict.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_dict.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_dict.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_dict_kv.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_from_csv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_from_csv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_from_csv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_from_csv' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_from_csv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_from_csv.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_groupby_as_dict.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_hashids' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_hashids' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_hashids' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_hashids' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_hashids' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_hashids.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_hashids.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_hashids.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_hashids.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_hashids.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_hashids.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_hashids.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_hashids.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_hashids.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_hashids.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_jc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_jc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_jc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_jc' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_jc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_jc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_jc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_jc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_jc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_jc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_json_query' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_json_query' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_json_query' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_json_query' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_json_query' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_json_query.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_json_query.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_json_query.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_json_query.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_json_query.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_json_query.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_json_query.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_json_query.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_json_query.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_json_query.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_lists_mergeby.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_path_join_shim.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_random_mac' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_random_mac' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_random_mac' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_random_mac' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_random_mac' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_random_mac.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_time' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_time' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_time' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_time' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_time' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_time.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_time.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_time.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_time.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_time.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_unicode_normalize.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_version_sort' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_version_sort' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_version_sort' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_version_sort' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_version_sort' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.filter_version_sort.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.filter_version_sort.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.filter_version_sort.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.filter_version_sort.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.filter_version_sort.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.flatpak' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.flatpak' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.flatpak' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.flatpak' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.flatpak' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.flatpak.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.flatpak.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.flatpak.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.flatpak.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.flatpak.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.flatpak.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.flatpak.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.flatpak.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.flatpak.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.flatpak.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.flatpak.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.flatpak.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.flatpak.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.flatpak.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.flatpak.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.flatpak_remote' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.flatpak_remote' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.flatpak_remote' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.flatpak_remote' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.flatpak_remote' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.flatpak_remote.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gandi_livedns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gandi_livedns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gandi_livedns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gandi_livedns' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gandi_livedns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gandi_livedns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gem' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gem' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gem' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gem' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gem' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gem.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gem.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gem.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gem.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gem.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gem.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gem.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gem.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gem.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gem.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gem.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gem.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gem.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gem.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gem.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.git_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.git_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.git_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.git_config' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.git_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.git_config.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.git_config.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.git_config.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.git_config.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.git_config.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.git_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.git_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.git_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.git_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.git_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.git_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.git_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.git_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.git_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.git_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.git_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.git_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.git_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.git_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.git_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.github_issue' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.github_issue' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.github_issue' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.github_issue' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.github_issue' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.github_issue.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.github_issue.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.github_issue.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.github_issue.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.github_issue.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.github_issue.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.github_issue.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.github_issue.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.github_issue.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.github_issue.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_branch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_branch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_branch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_branch' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_branch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_branch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_deploy_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group_members.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_group_variable.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_hook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_hook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_hook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_hook' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_hook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_hook.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_badge.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_members.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_project_variable.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_runner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_runner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_runner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_runner' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_runner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_runner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_user' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.gitlab_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.gitlab_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.gitlab_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.gitlab_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.gitlab_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hg' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hg.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hg.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hg.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hg.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hg.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.homebrew' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.homebrew' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.homebrew' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.homebrew' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.homebrew' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.homebrew.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.homebrew.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.homebrew.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.homebrew.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.homebrew.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.homebrew_cask' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.homebrew_cask' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.homebrew_cask' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.homebrew_cask' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.homebrew_cask' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.homebrew_cask.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.homectl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.homectl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.homectl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.homectl' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.homectl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.homectl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.homectl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.homectl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.homectl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.homectl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_ecs_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_evs_disk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_network_vpc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_smn_topic.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_eip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_peering_connect.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_port.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_private_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_route.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_security_group_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.hwc_vpc_subnet.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ilo_redfish_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.influxdb_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.influxdb_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.influxdb_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.influxdb_user' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.influxdb_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.influxdb_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.influxdb_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.influxdb_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.influxdb_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.influxdb_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.influxdb_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.influxdb_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.influxdb_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.influxdb_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.influxdb_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ini_file' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ini_file' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ini_file' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ini_file' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ini_file' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ini_file.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ini_file.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ini_file.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ini_file.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ini_file.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ini_file.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.interfaces_file' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.interfaces_file' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.interfaces_file' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.interfaces_file' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.interfaces_file' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.interfaces_file.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.interfaces_file.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.interfaces_file.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.interfaces_file.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.interfaces_file.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.interfaces_file.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.interfaces_file.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.interfaces_file.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.interfaces_file.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.interfaces_file.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.interfaces_file.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.interfaces_file.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.interfaces_file.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.interfaces_file.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.interfaces_file.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ipify_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ipify_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ipify_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ipify_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ipify_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ipify_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ipify_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ipify_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ipify_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ipify_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ipify_facts.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ipify_facts.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ipify_facts.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ipify_facts.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ipify_facts.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iptables_state' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iptables_state' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iptables_state' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iptables_state' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iptables_state' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iptables_state.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iptables_state.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iptables_state.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iptables_state.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iptables_state.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iptables_state.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ipwcli_dns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_create' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_create.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_create.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_create.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_create.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_create.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_create.files.test_dir' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_create.files.test_dir' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_create.files.test_dir' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_create.files.test_dir' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_create.files.test_dir' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_create.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_create.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_create.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_create.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_create.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_create.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_create.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_create.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_create.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_create.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_customize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_customize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_customize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_customize' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_customize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_customize.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_customize.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_customize.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_customize.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_customize.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_customize.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_customize.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_customize.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_customize.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_customize.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_extract' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_extract' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_extract' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_extract' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_extract' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_extract.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_extract.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_extract.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_extract.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_extract.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_extract.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_extract.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_extract.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_extract.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_extract.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_extract.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_extract.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_extract.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_extract.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_extract.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.iso_extract.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.iso_extract.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.iso_extract.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.iso_extract.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.iso_extract.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_cert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_cert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_cert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_cert' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_cert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_cert.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_cert.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_cert.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_cert.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_cert.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_cert.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_cert.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_cert.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_cert.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_cert.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_cert.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_cert.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_cert.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_cert.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_cert.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_cert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_cert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_cert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_cert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_cert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_keystore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_keystore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_keystore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_keystore' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_keystore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_keystore.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_keystore.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_keystore.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_keystore.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_keystore.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_keystore.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_keystore.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_keystore.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_keystore.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_keystore.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.java_keystore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.java_keystore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.java_keystore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.java_keystore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.java_keystore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.jboss' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.jboss' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.jboss' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.jboss' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.jboss' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.jboss.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.jboss.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.jboss.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.jboss.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.jboss.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.jboss.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.jboss.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.jboss.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.jboss.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.jboss.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.jira' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.jira' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.jira' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.jira' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.jira' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.jira.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.jira.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.jira.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.jira.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.jira.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.jira.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.jira.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.jira.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.jira.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.jira.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kdeconfig' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kdeconfig' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kdeconfig' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kdeconfig' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kdeconfig' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kdeconfig.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kdeconfig.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kdeconfig.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kdeconfig.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kdeconfig.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kdeconfig.tasks.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.kernel_blacklist.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_authz_authorization_scope.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_client' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_client' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_client' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_client' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_client' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_client.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_client.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_client.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_client.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_client.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_client.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_client.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_client.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_client.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_client.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientscope_type.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_info.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_clientsecret_regenerate.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_group' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_group.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_group.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_group.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_group.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_group.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_identity_provider.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_role' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_user_federation.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keycloak_user_rolemapping.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keyring' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keyring' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keyring' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keyring' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keyring' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keyring.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keyring.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keyring.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keyring.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keyring.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.keyring.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.keyring.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.keyring.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.keyring.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.keyring.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.launchd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.launchd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.launchd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.launchd' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.launchd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.launchd.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.launchd.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.launchd.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.launchd.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.launchd.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.launchd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.launchd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.launchd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.launchd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.launchd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.launchd.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.launchd.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.launchd.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.launchd.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.launchd.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.launchd.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.launchd.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.launchd.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.launchd.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.launchd.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.launchd.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.launchd.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.launchd.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.launchd.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.launchd.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ldap_search' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ldap_search' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ldap_search' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ldap_search' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ldap_search' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ldap_search.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ldap_search.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ldap_search.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ldap_search.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ldap_search.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ldap_search.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.listen_ports_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.locale_gen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.locale_gen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.locale_gen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.locale_gen' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.locale_gen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.locale_gen.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.locale_gen.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.locale_gen.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.locale_gen.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.locale_gen.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_cartesian.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_mf.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nothing.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nothing.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nothing.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nothing.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nothing.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.collections.ansible_collections.testns.testcoll_nv.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.library' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_collection_version.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_dependent' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_dependent' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_dependent' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_dependent' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_dependent' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_dependent.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_dependent.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_dependent.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_dependent.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_dependent.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_dig' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_dig' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_dig' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_dig' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_dig' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_dig.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_dig.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_dig.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_dig.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_dig.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_dig.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_dig.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_dig.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_dig.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_dig.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_etcd3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_flattened' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_flattened' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_flattened' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_flattened' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_flattened' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_flattened.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_flattened.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_flattened.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_flattened.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_flattened.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_lmdb_kv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_lmdb_kv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_lmdb_kv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_lmdb_kv' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_lmdb_kv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_merge_variables' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_merge_variables' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_merge_variables' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_merge_variables' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_merge_variables' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_passwordstore.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_random_pet' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_random_pet' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_random_pet' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_random_pet' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_random_pet' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_random_string' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_random_string' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_random_string' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_random_string' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_random_string' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lookup_random_words' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lookup_random_words' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lookup_random_words' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lookup_random_words' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lookup_random_words' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lvg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lvg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lvg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lvg' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lvg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lvg.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lvg.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lvg.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lvg.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lvg.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lvg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lvg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lvg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lvg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lvg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lxd_project' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lxd_project' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lxd_project' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lxd_project' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lxd_project' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.lxd_project.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.lxd_project.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.lxd_project.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.lxd_project.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.lxd_project.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mail' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mail' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mail' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mail' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mail' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mail.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mail.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mail.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mail.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mail.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mail.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mail.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mail.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mail.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mail.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mail.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mail.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mail.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mail.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mail.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mas' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mas' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mas' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mas' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mas' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mas.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mas.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mas.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mas.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mas.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_dns_reload.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_memstore_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_server_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_server_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_server_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_server_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_server_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_server_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_server_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_server_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_server_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_server_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_server_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_server_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_server_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_server_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_server_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_domain.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_record' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.memset_zone_record.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.module_helper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.module_helper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.module_helper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.module_helper' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.module_helper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.module_helper.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.module_helper.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.module_helper.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.module_helper.library' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.module_helper.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.module_helper.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.module_helper.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.module_helper.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.module_helper.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.module_helper.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.monit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.monit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.monit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.monit' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.monit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.monit.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.monit.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.monit.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.monit.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.monit.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.monit.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.monit.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.monit.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.monit.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.monit.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.monit.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.monit.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.monit.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.monit.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.monit.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.monit.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.monit.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.monit.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.monit.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.monit.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.monit.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.monit.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.monit.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.monit.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.monit.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.monit.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.monit.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.monit.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.monit.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.monit.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mqtt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mqtt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mqtt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mqtt' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mqtt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mqtt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mqtt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mqtt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mqtt.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mqtt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mqtt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mqtt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mqtt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mqtt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mqtt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mssql_script' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mssql_script' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mssql_script' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mssql_script' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mssql_script' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mssql_script.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mssql_script.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mssql_script.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mssql_script.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mssql_script.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.mssql_script.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.mssql_script.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.mssql_script.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.mssql_script.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.mssql_script.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.nomad' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.nomad' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.nomad' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.nomad' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.nomad' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.nomad.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.nomad.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.nomad.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.nomad.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.nomad.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.nomad.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.nomad.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.nomad.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.nomad.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.nomad.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.nomad.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.nomad.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.nomad.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.nomad.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.nomad.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.npm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.npm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.npm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.npm' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.npm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.npm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.npm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.npm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.npm.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.npm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.npm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.npm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.npm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.npm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.npm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.odbc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.odbc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.odbc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.odbc' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.odbc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.odbc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.odbc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.odbc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.odbc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.odbc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.odbc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.odbc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.odbc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.odbc.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.odbc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.odbc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.odbc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.odbc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.odbc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.odbc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_host' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_host' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_host' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_host' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_host' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_host.files.testhost.tmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_host.files.testhost.tmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_host.files.testhost.tmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_host.files.testhost.tmp' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_host.files.testhost.tmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_host.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_host.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_host.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_host.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_host.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_template' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_template.files.testhost.tmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_template.files.testhost.tmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_template.files.testhost.tmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_template.files.testhost.tmp' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_template.files.testhost.tmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.one_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.one_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.one_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.one_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.one_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.osx_defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.osx_defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.osx_defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.osx_defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.osx_defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.osx_defaults.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.osx_defaults.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.osx_defaults.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.osx_defaults.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.osx_defaults.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pacman' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pacman' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pacman' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pacman' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pacman' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pacman.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pacman.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pacman.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pacman.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pacman.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pacman.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pacman.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pacman.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pacman.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pacman.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pagerduty_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pagerduty_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pagerduty_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pagerduty_user' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pagerduty_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pagerduty_user.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pam_limits' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pam_limits' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pam_limits' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pam_limits' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pam_limits' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pam_limits.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pam_limits.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pam_limits.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pam_limits.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pam_limits.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pam_limits.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pam_limits.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pam_limits.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pam_limits.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pam_limits.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pamd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pamd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pamd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pamd' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pamd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pamd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pamd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pamd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pamd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pamd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.parted' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.parted' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.parted' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.parted' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.parted' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.parted.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.parted.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.parted.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.parted.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.parted.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.parted.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.parted.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.parted.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.parted.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.parted.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pids' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pids' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pids' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pids' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pids' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pids.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pids.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pids.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pids.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pids.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pids.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pids.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pids.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pids.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pids.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pids.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pids.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pids.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pids.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pids.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pids.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pids.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pids.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pids.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pids.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pipx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pipx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pipx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pipx' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pipx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pipx.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pipx.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pipx.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pipx.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pipx.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pipx_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pipx_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pipx_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pipx_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pipx_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pipx_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pipx_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pipx_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pipx_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pipx_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pkgng' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pkgng' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pkgng' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pkgng' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pkgng' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pkgng.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pkgng.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pkgng.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pkgng.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pkgng.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pkgng.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pkgng.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pkgng.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pkgng.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pkgng.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pkgng.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pkgng.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pkgng.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pkgng.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pkgng.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pkgutil' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pkgutil' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pkgutil' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pkgutil' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pkgutil' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.pkgutil.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.pkgutil.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.pkgutil.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.pkgutil.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.pkgutil.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.proxmox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.proxmox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.proxmox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.proxmox' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.proxmox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.proxmox.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.proxmox.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.proxmox.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.proxmox.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.proxmox.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.python_requirements_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.python_requirements_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.python_requirements_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.python_requirements_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.python_requirements_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.python_requirements_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.python_requirements_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.python_requirements_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.python_requirements_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.python_requirements_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.read_csv' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.read_csv' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.read_csv' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.read_csv' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.read_csv' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.read_csv.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.read_csv.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.read_csv.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.read_csv.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.read_csv.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.redis_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.redis_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.redis_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.redis_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.redis_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.redis_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.redis_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.redis_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.redis_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.redis_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.redis_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.redis_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.redis_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.redis_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.redis_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.redis_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.redis_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.redis_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.redis_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.redis_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.rundeck' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.rundeck' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.rundeck' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.rundeck' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.rundeck' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.rundeck.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.rundeck.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.rundeck.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.rundeck.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.rundeck.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.rundeck.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.rundeck.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.rundeck.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.rundeck.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.rundeck.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.rundeck.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.rundeck.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.rundeck.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.rundeck.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.rundeck.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.rundeck.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.rundeck.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.rundeck.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.rundeck.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.rundeck.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_compute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_compute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_compute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_compute' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_compute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_compute.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_namespace_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_container_registry_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_database_backup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_function_namespace_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_image_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_ip' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_ip_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_lb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_lb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_lb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_lb' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_lb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_lb.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_organization_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_security_group_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_server_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_snapshot_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_sshkey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_user_data.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_volume' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_volume' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_volume' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_volume' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_volume' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.scaleway_volume_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sefcontext' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sefcontext' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sefcontext' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sefcontext' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sefcontext' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sefcontext.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sefcontext.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sefcontext.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sefcontext.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sefcontext.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sefcontext.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sefcontext.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sefcontext.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sefcontext.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sefcontext.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sensu_client' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sensu_client' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sensu_client' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sensu_client' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sensu_client' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sensu_client.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sensu_client.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sensu_client.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sensu_client.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sensu_client.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sensu_handler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sensu_handler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sensu_handler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sensu_handler' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sensu_handler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sensu_handler.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sensu_handler.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sensu_handler.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sensu_handler.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sensu_handler.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_cron.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_cron.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_cron.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_cron.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_cron.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_cron.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_cron.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_cron.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_cron.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_cron.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_cron.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_cron.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_cron.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_cron.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_cron.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_cron.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_cron.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_cron.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_cron.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_cron.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_epel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_epel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_epel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_epel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_epel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_etcd3.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_flatpak_remote.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_gnutar.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_influxdb.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_influxdb.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_influxdb.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_influxdb.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_influxdb.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_java_keytool.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_mosquitto.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_openldap.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_openldap.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_openldap.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_openldap.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_openldap.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_openldap.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_openldap.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_openldap.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_openldap.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_openldap.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_openldap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_openldap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_openldap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_openldap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_openldap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_openldap.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_openldap.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_openldap.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_openldap.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_openldap.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_opennebula.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_openssl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_openssl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_openssl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_openssl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_openssl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_openssl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_openssl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_openssl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_openssl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_openssl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_openssl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_openssl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_openssl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_openssl.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_openssl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_pkg_mgr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_pkg_mgr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_pkg_mgr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_pkg_mgr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_pkg_mgr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_postgresql_db.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_redis_replication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_remote_constraints.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_remote_tmp_dir_outside_tmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_rundeck.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_snap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_snap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_snap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_snap' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_snap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_snap.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_snap.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_snap.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_snap.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_snap.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_snap.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_snap.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_snap.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_snap.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_snap.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_snap.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_snap.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_snap.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_snap.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_snap.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_snap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_snap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_snap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_snap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_snap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_tls.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_tls.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_tls.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_tls.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_tls.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_tls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_tls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_tls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_tls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_tls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.setup_wildfly_server.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.shutdown' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.shutdown' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.shutdown' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.shutdown' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.shutdown' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.shutdown.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.shutdown.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.shutdown.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.shutdown.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.shutdown.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.snap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.snap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.snap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.snap' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.snap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.snap.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.snap.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.snap.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.snap.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.snap.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.snap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.snap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.snap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.snap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.snap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.snap_alias' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.snap_alias' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.snap_alias' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.snap_alias' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.snap_alias' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.snap_alias.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.snap_alias.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.snap_alias.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.snap_alias.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.snap_alias.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.snap_alias.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.snap_alias.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.snap_alias.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.snap_alias.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.snap_alias.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.spectrum_model_attrs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ssh_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ssh_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ssh_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ssh_config' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ssh_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ssh_config.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ssh_config.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ssh_config.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ssh_config.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ssh_config.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ssh_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ssh_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ssh_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ssh_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ssh_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ssh_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ssh_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ssh_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ssh_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ssh_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sudoers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sudoers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sudoers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sudoers' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sudoers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sudoers.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sudoers.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sudoers.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sudoers.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sudoers.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.supervisorctl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.supervisorctl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.supervisorctl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.supervisorctl' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.supervisorctl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.supervisorctl.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.supervisorctl.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.supervisorctl.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.supervisorctl.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.supervisorctl.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.supervisorctl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.supervisorctl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.supervisorctl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.supervisorctl.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.supervisorctl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.supervisorctl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.supervisorctl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.supervisorctl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.supervisorctl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.supervisorctl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.supervisorctl.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.supervisorctl.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.supervisorctl.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.supervisorctl.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.supervisorctl.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.supervisorctl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.supervisorctl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.supervisorctl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.supervisorctl.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.supervisorctl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sysrc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sysrc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sysrc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sysrc' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sysrc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.sysrc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.sysrc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.sysrc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.sysrc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.sysrc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.terraform' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.terraform' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.terraform' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.terraform' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.terraform' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.terraform.files.complex_variables' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.terraform.files.complex_variables' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.terraform.files.complex_variables' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.terraform.files.complex_variables' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.terraform.files.complex_variables' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.terraform.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.terraform.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.terraform.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.terraform.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.terraform.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.terraform.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.terraform.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.terraform.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.terraform.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.terraform.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.terraform.templates.provider_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.terraform.templates.provider_test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.terraform.templates.provider_test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.terraform.templates.provider_test' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.terraform.templates.provider_test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.terraform.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.terraform.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.terraform.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.terraform.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.terraform.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.test_a_module' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.test_a_module' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.test_a_module' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.test_a_module' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.test_a_module' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.test_a_module.collections.ansible_collections.testns.testcoll.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.test_a_module.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.test_a_module.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.test_a_module.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.test_a_module.library' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.test_a_module.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.timezone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.timezone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.timezone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.timezone' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.timezone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.timezone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.timezone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.timezone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.timezone.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.timezone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.timezone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.timezone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.timezone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.timezone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.timezone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ufw' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ufw' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ufw' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ufw' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ufw' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ufw.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ufw.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ufw.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ufw.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ufw.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ufw.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ufw.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ufw.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ufw.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ufw.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.ufw.tasks.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.ufw.tasks.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.ufw.tasks.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.ufw.tasks.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.ufw.tasks.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.wakeonlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.wakeonlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.wakeonlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.wakeonlan' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.wakeonlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.wakeonlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.wakeonlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.wakeonlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.wakeonlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.wakeonlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xattr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xattr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xattr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xattr' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xattr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xattr.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xattr.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xattr.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xattr.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xattr.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xattr.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xattr.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xattr.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xattr.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xattr.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xattr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xattr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xattr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xattr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xattr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xfs_quota' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xfs_quota' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xfs_quota' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xfs_quota' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xfs_quota' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xfs_quota.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xfs_quota.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xfs_quota.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xfs_quota.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xfs_quota.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xfs_quota.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xfs_quota.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xfs_quota.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xfs_quota.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xfs_quota.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xfs_quota.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xfs_quota.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xfs_quota.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xfs_quota.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xfs_quota.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xml' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xml' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xml' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xml' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xml' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xml.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xml.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xml.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xml.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xml.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xml.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xml.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xml.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xml.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xml.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xml.results' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xml.results' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xml.results' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xml.results' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xml.results' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xml.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xml.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xml.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xml.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xml.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.xml.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.xml.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.xml.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.xml.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.xml.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.yarn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.yarn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.yarn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.yarn' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.yarn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.yarn.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.yarn.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.yarn.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.yarn.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.yarn.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.yarn.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.yarn.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.yarn.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.yarn.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.yarn.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.yarn.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.yarn.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.yarn.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.yarn.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.yarn.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.yum_versionlock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.yum_versionlock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.yum_versionlock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.yum_versionlock' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.yum_versionlock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.yum_versionlock.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.yum_versionlock.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.yum_versionlock.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.yum_versionlock.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.yum_versionlock.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper_repository' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper_repository' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper_repository' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper_repository' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper_repository' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper_repository.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper_repository.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper_repository.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper_repository.files' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper_repository.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper_repository.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper_repository.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper_repository.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper_repository.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper_repository.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.integration.targets.zypper_repository.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.integration.targets.zypper_repository.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.integration.targets.zypper_repository.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.integration.targets.zypper_repository.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.integration.targets.zypper_repository.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.become' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.become' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.become' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.become' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.become' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.cache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.cache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.cache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.cache' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.cache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.inventory.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.inventory.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.inventory.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.inventory.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.inventory.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.lookup.onepassword_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.lookup.onepassword_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.lookup.onepassword_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.lookup.onepassword_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.lookup.onepassword_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.module_utils.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.module_utils.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.module_utils.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.module_utils.cloud' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.module_utils.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.module_utils.hwc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.module_utils.hwc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.module_utils.hwc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.module_utils.hwc' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.module_utils.hwc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.module_utils.identity.keycloak' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.module_utils.identity.keycloak' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.module_utils.identity.keycloak' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.module_utils.identity.keycloak' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.module_utils.identity.keycloak' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.module_utils.net_tools.pritunl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.module_utils.net_tools.pritunl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.module_utils.net_tools.pritunl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.module_utils.net_tools.pritunl' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.module_utils.net_tools.pritunl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.module_utils.xenserver.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.golden_output' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.golden_output' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.golden_output' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.golden_output' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.golden_output' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.input' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.input' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.input' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.input' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.unit.plugins.modules.interfaces_file.interfaces_file_fixtures.input' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.general.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.general.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.general.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.general.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.general.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google' to be distributed and are already explicitly excluding 'ansible_collections.community.google' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.google.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.google.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.google.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.google.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.google.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.google.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.google.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.scripts.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.scripts.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.scripts.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.scripts.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.google.scripts.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.google.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.google.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.google.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.google.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.google.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.google.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.google.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.google.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.google.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.hacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.hacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.hacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.hacking' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.hacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.files' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_dashboard.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_datasource.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_folder.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_notification_channel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_organization.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_team.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.integration.targets.grafana_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_datasource' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_datasource' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_datasource' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_datasource' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_datasource' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_plugin' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_team' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_team' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_team' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_team' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_team' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_user' to be distributed and are already explicitly excluding 'ansible_collections.community.grafana.tests.unit.modules.grafana.grafana_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.docs.preview' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.docs.preview' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.docs.preview' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.docs.preview' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.docs.preview' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.docs.preview.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.docs.preview.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.docs.preview.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.docs.preview.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.docs.preview.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_approle.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_aws_iam.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_azure.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.files' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_cert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.files' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_jwt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_ldap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_none.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_token.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.auth_userpass.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.connection_options.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.filter_vault_login_token.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_hashi_vault.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_ansible_settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv1_get.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_kv2_get.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_list.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_login.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_read.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_token_create.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.lookup_vault_write.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv1_get.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_delete.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_get.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_kv2_write.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_list.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_login.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_pki_generate_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_read.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_token_create.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.module_vault_write.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.files' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_cert_content.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.requirements' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.requirements' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.requirements' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.requirements' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.files.requirements' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates.mmock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates.mmock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates.mmock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates.mmock' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.templates.mmock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_docker.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.files.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_localenv_gha.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_configure_engine_pki.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_server_cert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.library' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.lookup_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.lookup_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.lookup_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.lookup_plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.lookup_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.integration.targets.setup_vault_test_plugins.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.authentication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.authentication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.authentication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.authentication' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.authentication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.option_adapter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.option_adapter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.option_adapter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.option_adapter' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.module_utils.option_adapter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.authentication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.authentication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.authentication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.authentication' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.authentication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.base' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.base' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.base' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.base' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.base' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.option_adapter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.option_adapter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.option_adapter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.option_adapter' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.unit.plugins.plugin_utils.option_adapter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hashi_vault.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hashi_vault.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hashi_vault.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hashi_vault.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.hashi_vault.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.ee' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.ee' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.ee' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.ee' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.ee' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.ee.roles.smoke.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.ee.roles.smoke.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.ee.roles.smoke.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.ee.roles.smoke.library' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.ee.roles.smoke.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.ee.roles.smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.ee.roles.smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.ee.roles.smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.ee.roles.smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.ee.roles.smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.unit.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.unit.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.unit.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.unit.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.unit.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.hrobot.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.hrobot.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.hrobot.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.hrobot.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.hrobot.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_lxc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_lxc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_lxc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_lxc' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_lxc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_qemu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_qemu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_qemu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_qemu' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.connection_libvirt_qemu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.inventory_libvirt.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_net' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_net' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_net' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_net' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_net' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.files' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_net.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.integration.targets.virt_pool.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.unit.modules.cloud.misc.virt_net' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.unit.modules.cloud.misc.virt_net' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.unit.modules.cloud.misc.virt_net' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.unit.modules.cloud.misc.virt_net' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.unit.modules.cloud.misc.virt_net' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.libvirt.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.libvirt.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.libvirt.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.libvirt.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.libvirt.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.plugins.cache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.plugins.cache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.plugins.cache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.plugins.cache' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.plugins.cache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_auth.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_auth.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_auth.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_auth.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_auth.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.custom_db_path.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.files' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_hold_packages.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.mongodb_nohold_packages.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.specific_mongodb_version.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_install.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_install.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_install.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_install.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_install.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.files' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_linux.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_linux.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_linux.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_linux.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_linux.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.custom_db_path.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.multiple_bind_ip.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongod.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongod.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongod.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongod.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongod.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_mongos.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_mongos.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_mongos.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_mongos.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_mongos.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_repository.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_repository.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_repository.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_repository.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_repository.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.files' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.molecule.virtualbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mongodb.roles.mongodb_selinux.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mongodb.roles.mongodb_selinux.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mongodb.roles.mongodb_selinux.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mongodb.roles.mongodb_selinux.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.mongodb.roles.mongodb_selinux.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.plugins.module_utils.implementations.mariadb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.plugins.module_utils.implementations.mariadb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.plugins.module_utils.implementations.mariadb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.plugins.module_utils.implementations.mariadb' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.plugins.module_utils.implementations.mariadb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.plugins.module_utils.implementations.mysql' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.plugins.module_utils.implementations.mysql' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.plugins.module_utils.implementations.mysql' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.plugins.module_utils.implementations.mysql' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.plugins.module_utils.implementations.mysql' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.old_mariadb_replication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.setup_mysql.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_db.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_info.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_query.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_replication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.files' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.integration.targets.test_mysql_variables.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.mysql.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.mysql.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.mysql.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.mysql.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.mysql.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network' to be distributed and are already explicitly excluding 'ansible_collections.community.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.network.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.network.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.become' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.become' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.become' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.become' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.become' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.cache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.cache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.cache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.cache' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.cache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.a10' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.a10' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.a10' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.a10' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.a10' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.aireos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.aireos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.aireos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.aireos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.aireos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.aos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.aos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.aos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.aos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.aos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.apconos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.apconos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.apconos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.apconos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.apconos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.aruba' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.aruba' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.aruba' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.aruba' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.aruba' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.avi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.avi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.avi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.avi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.avi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.bigswitch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.bigswitch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.bigswitch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.bigswitch' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.bigswitch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.cloudengine' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.cloudengine' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.cloudengine' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.cloudengine' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.cloudengine' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.cnos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.cnos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.cnos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.cnos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.cnos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.edgeos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.edgeos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.edgeos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.edgeos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.edgeos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.edgeswitch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.edgeswitch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.edgeswitch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.edgeswitch' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.edgeswitch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.enos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.enos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.enos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.enos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.enos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.eric_eccli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.eric_eccli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.eric_eccli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.eric_eccli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.eric_eccli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.vlans' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.argspec.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.config' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.config.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.config.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.config.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.config.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.config.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.config.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.config.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.config.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.config.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.config.vlans' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.config.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.facts' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.vlans' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.facts.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.exos.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.exos.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.exos.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.exos.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.exos.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.ftd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.ftd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.ftd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.ftd' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.ftd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.icx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.icx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.icx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.icx' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.icx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.ingate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.ingate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.ingate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.ingate' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.ingate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.ironware' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.ironware' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.ironware' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.ironware' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.ironware' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.netscaler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.netscaler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.netscaler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.netscaler' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.netscaler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.netvisor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.netvisor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.netvisor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.netvisor' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.netvisor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.nos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.nos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.nos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.nos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.nos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.ordnance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.ordnance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.ordnance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.ordnance' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.ordnance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.slxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.slxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.slxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.slxos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.slxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.sros' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.sros' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.sros' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.sros' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.sros' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.module_utils.network.voss' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.module_utils.network.voss' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.module_utils.network.voss' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.module_utils.network.voss' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.module_utils.network.voss' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.community.network.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_instance.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_interface.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_is_is_view.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lacp' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lacp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lacp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lacp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lacp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lacp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lacp.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_lldp_interface.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_mdn_interface.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_global.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_multicast_igmp_enable.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.ce_static_route_bfd.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_backup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_backup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_backup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_backup' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_backup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_backup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_backup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_backup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_backup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_backup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_backup.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_backup.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_backup.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_backup.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_backup.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_banner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_banner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_banner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_banner' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_banner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_banner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_banner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_banner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_banner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_banner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_banner.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_banner.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_banner.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_banner.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_banner.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_banner.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_bgp' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_bgp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_command' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_command.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_conditional_template.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_config' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_config.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_image' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_image' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_image' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_image' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_image' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_image.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_image.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_image.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_image.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_image.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_image.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_image.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_image.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_image.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_image.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_interface.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_interface.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_interface.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_interface.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_interface.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_interface.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l2_interface.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_l3_interface.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_linkagg.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_lldp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_lldp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_lldp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_lldp' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_lldp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_lldp.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_logging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_logging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_logging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_logging' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_logging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_logging.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_rollback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_rollback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_rollback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_rollback' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_rollback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_rollback.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_save' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_save' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_save' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_save' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_save' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_save.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_save.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_save.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_save.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_save.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_save.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_save.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_save.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_save.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_save.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_showrun' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_showrun' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_showrun' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_showrun' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_showrun' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_showrun.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_static_route' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_static_route' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_static_route' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_static_route' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_static_route' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_static_route.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_system' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_system.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_template' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_template.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_template.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_template.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_template.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_template.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_template.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_template.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_template.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_template.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_template.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_user' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_user.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_user.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_user.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_user.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_user.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlag' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlag.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlan' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vlan.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vrf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vrf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vrf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vrf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vrf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.cnos_vrf.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_command' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_command.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_command.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_command.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_command.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_command.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_config' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_config.templates.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.enos_facts.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.enos_facts.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.enos_facts.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.enos_facts.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.enos_facts.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_command' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_command.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_command.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_command.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_command.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_command.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_config' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_config.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_config.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_config.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_config.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_config.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_config.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_facts.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_facts.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_facts.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_facts.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_facts.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tests.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tests.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tests.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tests.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.tests.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_l2_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tests.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tests.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tests.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tests.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.tests.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tests.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tests.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tests.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tests.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.tests.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_lldp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_vlans' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_vlans.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_vlans.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_vlans.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_vlans.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_vlans.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tests.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tests.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tests.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tests.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_vlans.tests.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.exos_vlans.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.exos_vlans.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.exos_vlans.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.exos_vlans.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.exos_vlans.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.nuage_vspk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.nuage_vspk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.nuage_vspk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.nuage_vspk' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.nuage_vspk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.nuage_vspk.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.integration.targets.prepare_nuage_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.integration.targets.prepare_nuage_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.integration.targets.prepare_nuage_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.integration.targets.prepare_nuage_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.integration.targets.prepare_nuage_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.ios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.ios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.ios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.ios' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.ios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.nos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.nos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.nos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.nos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.nos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.slxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.slxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.slxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.slxos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.slxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.weos4' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.weos4' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.weos4' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.weos4' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.cliconf.fixtures.weos4' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.lookup.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.lookup.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.lookup.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.lookup.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.lookup.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.avi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.avi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.avi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.avi' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.avi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.common' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd.test_data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd.test_data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd.test_data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd.test_data' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.ftd.test_data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.netscaler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.netscaler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.netscaler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.netscaler' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.netscaler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.nos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.nos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.nos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.nos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.nos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.slxos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.slxos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.slxos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.slxos' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.module_utils.network.slxos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.aireos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.aireos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.aireos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.aireos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.aireos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.apconos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.apconos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.apconos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.apconos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.apconos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.aruba_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.aruba_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.aruba_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.aruba_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.aruba_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.avi_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.avi_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.avi_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.avi_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.avi_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_instance' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_view' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_view' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_view' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_view' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_is_is_view' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lacp' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_lldp_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_mdn_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_mdn_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_mdn_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_mdn_interface' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_mdn_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_global' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_igmp_enable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_igmp_enable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_igmp_enable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_igmp_enable' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_multicast_igmp_enable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_static_route_bfd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_static_route_bfd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_static_route_bfd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_static_route_bfd' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ce_fixtures.ce_static_route_bfd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.cnos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.cnos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.cnos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.cnos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.cnos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.eccli_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.eccli_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.eccli_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.eccli_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.eccli_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.edgeos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.edgeos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.edgeos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.edgeos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.edgeos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.edgeswitch_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.edgeswitch_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.edgeswitch_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.edgeswitch_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.edgeswitch_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.enos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.enos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.enos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.enos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.enos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.exos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.exos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.exos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.exos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.exos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.icx_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.icx_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.icx_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.icx_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.icx_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ingate_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ingate_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ingate_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ingate_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ingate_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.ironware_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.ironware_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.ironware_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.ironware_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.ironware_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.nos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.nos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.nos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.nos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.nos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.opx_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.opx_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.opx_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.opx_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.opx_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.slxos_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.slxos_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.slxos_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.slxos_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.slxos_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.modules.voss_fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.modules.voss_fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.modules.voss_fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.modules.voss_fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.modules.voss_fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.unit.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.unit.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.unit.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.unit.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.unit.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.network.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.network.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.network.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.network.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.network.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd' to be distributed and are already explicitly excluding 'ansible_collections.community.okd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.ci' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.ci' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.ci' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.ci' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.ci' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.docs' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.files' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.library' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.ad' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.ad' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.ad' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.ad' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.ad' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.rfc2307' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.rfc2307' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.rfc2307' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.rfc2307' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.roles.openshift_adm_groups.templates.rfc2307' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.molecule.default.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.molecule.default.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.molecule.default.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.molecule.default.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.molecule.default.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.okd.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.okd.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.okd.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.okd.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.okd.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_copy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_db.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ext.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_idx.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_lang.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_membership.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_owner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_pg_hba.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_ping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_privs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_publication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.files' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_query.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_schema.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.files' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_script.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_sequence.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_set.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_slot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_subscription.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_table.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_tablespace.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.postgresql_user_obj_stat_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_pkg_mgr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_pkg_mgr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_pkg_mgr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_pkg_mgr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_pkg_mgr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.files' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_db.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.integration.targets.setup_postgresql_replication.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.postgresql.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.postgresql.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.postgresql.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.postgresql.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.postgresql.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.roles.proxysql.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.roles.proxysql.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.roles.proxysql.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.roles.proxysql.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.roles.proxysql.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.setup_proxysql.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_backend_servers.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_global_variables.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_mysql_users.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_query_rules_fast_routing.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_replication_hostgroups.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.integration.targets.test_proxysql_scheduler.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.proxysql.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.proxysql.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.proxysql.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.proxysql.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.proxysql.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.lookup_rabbitmq.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_binding.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_exchange.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_feature_flag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_global_parameter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_plugin.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.files' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_publish.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_queue.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_upgrade.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_user_limits.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.rabbitmq_vhost_limits.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.files' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_rabbitmq.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.files' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.integration.targets.setup_tls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.rabbitmq.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.rabbitmq.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.rabbitmq.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.rabbitmq.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.rabbitmq.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.ee' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.ee' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.ee' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.ee' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.ee' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.ee.roles.filter_quoting.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.ee.roles.smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.ee.roles.smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.ee.roles.smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.ee.roles.smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.ee.roles.smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.integration.targets.filter_quoting.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures.facts' to be distributed and are already explicitly excluding 'ansible_collections.community.routeros.tests.unit.plugins.modules.fixtures.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap' to be distributed and are already explicitly excluding 'ansible_collections.community.sap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.plugins.modules.database.saphana' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.plugins.modules.database.saphana' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.plugins.modules.database.saphana' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.plugins.modules.database.saphana' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.plugins.modules.database.saphana' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.plugins.modules.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.plugins.modules.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.plugins.modules.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.plugins.modules.files' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.plugins.modules.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.plugins.modules.identity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.plugins.modules.identity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.plugins.modules.identity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.plugins.modules.identity' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.plugins.modules.identity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.plugins.modules.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.plugins.modules.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.plugins.modules.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.plugins.modules.system' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.plugins.modules.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.plugins.modules.database' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.plugins.modules.database' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.plugins.modules.database' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.plugins.modules.database' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.plugins.modules.database' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.plugins.modules.database.saphana' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.plugins.modules.database.saphana' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.plugins.modules.database.saphana' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.plugins.modules.database.saphana' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.plugins.modules.database.saphana' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.plugins.modules.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.plugins.modules.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.plugins.modules.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.plugins.modules.files' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.plugins.modules.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.plugins.modules.identity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.plugins.modules.identity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.plugins.modules.identity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.plugins.modules.identity' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.plugins.modules.identity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap.tests.unit.plugins.modules.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap.tests.unit.plugins.modules.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap.tests.unit.plugins.modules.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap.tests.unit.plugins.modules.system' to be distributed and are already explicitly excluding 'ansible_collections.community.sap.tests.unit.plugins.modules.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sap_libs.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sap_libs.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sap_libs.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sap_libs.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.sap_libs.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.plugins.module_utils.network.skydive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.plugins.module_utils.network.skydive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.plugins.module_utils.network.skydive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.plugins.module_utils.network.skydive' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.plugins.module_utils.network.skydive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.skydive.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.skydive.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.skydive.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.skydive.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.skydive.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops' to be distributed and are already explicitly excluding 'ansible_collections.community.sops' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.plugins.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.plugins.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.plugins.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.plugins.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.plugins.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles._install_age' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles._install_age' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles._install_age' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles._install_age' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles._install_age' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles._install_age.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles._install_age.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles._install_age.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles._install_age.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles._install_age.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles._install_age.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles._install_age.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles._install_age.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles._install_age.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles._install_age.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles._install_age.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles._install_age.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles._install_age.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles._install_age.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles._install_age.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles._install_age.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles._install_age.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles._install_age.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles._install_age.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles._install_age.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles.install' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles.install' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles.install' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles.install' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles.install' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles.install.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles.install.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles.install.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles.install.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles.install.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles.install.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles.install.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles.install.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles.install.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles.install.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles.install.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles.install.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles.install.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles.install.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles.install.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.roles.install.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.roles.install.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.roles.install.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.roles.install.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.roles.install.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.ee' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.ee' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.ee' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.ee' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.ee' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.files' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.ee.roles.lookup_sops.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.age' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.age' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.age' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.age' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.age' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.age.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.age.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.age.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.age.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.age.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.age.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.age.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.age.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.age.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.age.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.files' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.filter_decrypt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.load_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.load_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.load_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.load_vars' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.load_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.load_vars.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.load_vars.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.load_vars.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.load_vars.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.load_vars.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.load_vars.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.load_vars.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.load_vars.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.load_vars.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.load_vars.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.load_vars.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.load_vars.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.load_vars.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.load_vars.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.load_vars.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.lookup_sops' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.lookup_sops' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.lookup_sops' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.lookup_sops' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.lookup_sops' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.files' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.lookup_sops.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.role_install_latest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.role_install_latest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.role_install_latest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.role_install_latest' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.role_install_latest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.role_install_latest.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.role_install_latest.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.role_install_latest.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.role_install_latest.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.role_install_latest.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.role_install_localhost_remote.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.role_install_version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.role_install_version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.role_install_version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.role_install_version' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.role_install_version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.role_install_version.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.role_install_version.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.role_install_version.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.role_install_version.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.role_install_version.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.setup_sops.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.setup_sops.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.setup_sops.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.setup_sops.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.setup_sops.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.files' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.sops_encrypt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.var_sops' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.var_sops' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.var_sops' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.var_sops' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.var_sops' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.integration.targets.var_sops.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.integration.targets.var_sops.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.integration.targets.var_sops.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.integration.targets.var_sops.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.integration.targets.var_sops.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.sops.tests.sanity.extra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.sops.tests.sanity.extra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.sops.tests.sanity.extra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.sops.tests.sanity.extra' to be distributed and are already explicitly excluding 'ansible_collections.community.sops.tests.sanity.extra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.LICENSES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.LICENSES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.LICENSES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.LICENSES' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.LICENSES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.docs' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.docs.docsite.rst.vmware_scenarios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.docs.docsite.rst.vmware_scenarios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.docs.docsite.rst.vmware_scenarios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.docs.docsite.rst.vmware_scenarios' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.docs.docsite.rst.vmware_scenarios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.scripts.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.scripts.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.scripts.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.scripts.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.scripts.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory.playbook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory.playbook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory.playbook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory.playbook' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_host_inventory.playbook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory.playbook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory.playbook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory.playbook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory.playbook' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.inventory_vmware_vm_inventory.playbook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.prepare_vmware_tests.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.script_inventory_vmware_inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.script_inventory_vmware_inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.script_inventory_vmware_inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.script_inventory_vmware_inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.script_inventory_vmware_inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_domain_user_group_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_extension_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_folder.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vcenter_license.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_about_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_category' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_category' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_category' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_category' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_category' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_category.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_category.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_category.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_category.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_category.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cfg_backup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_dpm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_drs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_ha.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_cluster_vsan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_deploy_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_content_library_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_custom_attribute_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datacenter_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_cluster_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_datastore_maintenancemode.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_group_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_drs_rule_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_find.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvs_portgroup_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_nioc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_pvlans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_dvswitch_uplink_pg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_evc_mode.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_export_ovf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_first_class_disk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_folder_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_boot_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_controller.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_cross_vc_clone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attribute_defs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_custom_attributes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_customization_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_disk_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_find.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_instant_clone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_move.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_powerstate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_register_operation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_screenshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_sendkey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_serial_port.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_snapshot_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_storage_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_guest_tools_wait.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_acceptance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_active_directory.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_auto_start.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_capability_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_config_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_custom_attributes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_datastore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_disk_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_dns_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_feature_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_firewall_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_hyperthreading.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ipv6.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_iscsi_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_kernel_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_lockdown_exceptions.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_logbundle_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ntp_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_package_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_passthrough.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powermgmt_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_powerstate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scanhba.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_scsidisk_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_service_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_snmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_sriov.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_ssl_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_tcpip_stacks.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_user_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmhba_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_host_vmnic_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_role_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_local_user_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_maintenancemode.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_migrate_vmk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_custom_attributes_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_rename.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_object_role_permission_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_portgroup_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_recommended_datastore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_resource_pool_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_tag_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_target_canonical_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vc_infraprofile_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_settings_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vcenter_statistics.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_config_option.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_host_drs_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_storage_policy_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vm_vm_drs_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmkernel_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vmotion.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vsan_health_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vspan_session.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vmware_vswitch_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.integration.targets.vsphere_file.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit.modules.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit.modules.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit.modules.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit.modules.cloud' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit.modules.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware.test_data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware.test_data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware.test_data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware.test_data' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tests.unit.modules.cloud.vmware.test_data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.vmware.tools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.vmware.tools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.vmware.tools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.vmware.tools' to be distributed and are already explicitly excluding 'ansible_collections.community.vmware.tools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows' to be distributed and are already explicitly excluding 'ansible_collections.community.windows' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.psexec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.psexec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.psexec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.psexec' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.psexec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.psexec.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.psexec.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.psexec.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.psexec.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.psexec.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_domain_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_domain_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_domain_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_domain_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_domain_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_http_tests.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_remote_tmp_dir.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_win_device.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.setup_win_psget.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_audit_policy_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_audit_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_auto_logon.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_certificate_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_computer_description' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_computer_description' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_computer_description' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_computer_description' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_computer_description' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_computer_description.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_credential' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_credential' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_credential' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_credential' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_credential' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_credential.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_credential.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_credential.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_credential.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_credential.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_credential.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_credential.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_credential.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_credential.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_credential.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_credential.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_credential.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_credential.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_credential.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_credential.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_credential.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_credential.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_credential.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_credential.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_credential.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_credential.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_credential.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_credential.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_credential.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_credential.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_data_deduplication.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dhcp_lease.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_disk_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dns_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dns_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dns_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dns_record' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dns_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dns_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dns_zone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_computer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_group' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_object_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_ou.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_user' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_domain_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_dotnet_ngen.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_eventlog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_eventlog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_eventlog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_eventlog' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_eventlog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_eventlog.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_eventlog.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_eventlog.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_eventlog.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_eventlog.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_eventlog_entry.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_feature_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_feature_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_feature_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_feature_info' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_feature_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_feature_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_file_compression' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_file_compression' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_file_compression' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_file_compression' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_file_compression' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_file_compression.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_firewall' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_firewall_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_format' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_format' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_format' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_format' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_format' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_format.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_format.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_format.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_format.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_format.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_format.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_format.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_format.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_format.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_format.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_format.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_format.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_format.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_format.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_format.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_hosts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_hosts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_hosts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_hosts' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_hosts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_hosts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_hosts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_hosts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_hosts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_hosts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_hosts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_hosts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_hosts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_hosts.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_hosts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_hosts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_hosts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_hosts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_hosts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_hosts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_hotfix' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_hotfix' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_hotfix' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_hotfix' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_hotfix' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_hotfix.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_http_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_virtualdirectory.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapplication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webapppool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_iis_webbinding.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_inet_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_initialize_disk.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files.expectations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files.expectations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files.expectations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files.expectations' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.files.expectations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_lineinfile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_listen_ports_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_mapped_drive.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_msg' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_msg' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_msg' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_msg' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_msg' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_msg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_msg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_msg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_msg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_msg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_net_adapter_feature.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_netbios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_netbios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_netbios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_netbios' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_netbios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_netbios.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_netbios.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_netbios.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_netbios.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_netbios.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_netbios.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_netbios.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_netbios.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_netbios.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_netbios.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_nssm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_nssm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_nssm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_nssm' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_nssm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_nssm.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_nssm.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_nssm.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_nssm.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_nssm.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_nssm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_nssm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_nssm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_nssm.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_nssm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_nssm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_nssm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_nssm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_nssm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_nssm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pagefile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pagefile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pagefile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pagefile' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pagefile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pagefile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pagefile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pagefile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pagefile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pagefile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_partition' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_partition' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_partition' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_partition' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_partition' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_partition.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_partition.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_partition.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_partition.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_partition.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_partition.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_partition.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_partition.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_partition.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_partition.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_partition.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_partition.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_partition.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_partition.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_partition.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_partition.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_partition.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_partition.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_partition.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_partition.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pester' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pester' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pester' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pester' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pester' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pester.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pester.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pester.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pester.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pester.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pester.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pester.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pester.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pester.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pester.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pester.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pester.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pester.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pester.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pester.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_power_plan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_power_plan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_power_plan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_power_plan' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_power_plan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_power_plan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_power_plan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_power_plan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_power_plan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_power_plan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_product_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_product_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_product_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_product_facts' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_product_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_product_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_product_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_product_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_product_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_product_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psexec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psexec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psexec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psexec' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psexec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psexec.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psexec.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psexec.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psexec.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psexec.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psexec.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psexec.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psexec.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psexec.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psexec.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files.module' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files.module' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files.module' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files.module' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.files.module' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psmodule_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_copy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psrepository_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_psscript_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_pssession_configuration.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_rabbitmq_plugin.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_rds' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_rds' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_rds' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_rds' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_rds' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_rds.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_rds.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_rds.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_rds.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_rds.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_rds.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_rds.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_rds.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_rds.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_rds.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_rds.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_rds.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_rds.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_rds.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_rds.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_rds.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_rds.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_rds.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_rds.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_rds.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_region' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_region' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_region' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_region' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_region' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_region.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_region.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_region.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_region.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_region.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_regmerge' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_regmerge' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_regmerge' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_regmerge' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_regmerge' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_regmerge.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_route' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_route' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_route' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_route' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_route' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_route.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_route.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_route.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_route.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_route.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_route.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_route.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_route.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_route.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_route.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_say' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_say' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_say' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_say' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_say' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_say.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_say.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_say.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_say.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_say.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scheduled_task_stat.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scoop' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scoop' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scoop' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scoop' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scoop' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scoop.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scoop.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scoop.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scoop.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scoop.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scoop.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scoop.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scoop.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scoop.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scoop.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_scoop_bucket.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_security_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_security_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_security_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_security_policy' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_security_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.library' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_security_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_shortcut' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_shortcut' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_shortcut' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_shortcut' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_shortcut' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_shortcut.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_shortcut.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_shortcut.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_shortcut.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_shortcut.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_snmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_snmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_snmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_snmp' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_snmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_snmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_snmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_snmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_snmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_snmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_snmp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_snmp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_snmp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_snmp.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_snmp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_timezone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_timezone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_timezone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_timezone' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_timezone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_timezone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_timezone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_timezone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_timezone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_timezone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_toast' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_toast' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_toast' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_toast' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_toast' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_toast.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_toast.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_toast.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_toast.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_toast.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_unzip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_unzip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_unzip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_unzip' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_unzip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_unzip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_unzip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_unzip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_unzip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_unzip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_unzip.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_unzip.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_unzip.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_unzip.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_unzip.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_unzip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_unzip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_unzip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_unzip.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_unzip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_unzip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_unzip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_unzip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_unzip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_unzip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_user_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_user_profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_user_profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_user_profile' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_user_profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_user_profile.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_user_profile.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_user_profile.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_user_profile.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_user_profile.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_wait_for_process.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_wakeonlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_xml' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_xml' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_xml' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_xml' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_xml' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_xml.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_xml.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_xml.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_xml.files' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_xml.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_xml.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_xml.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_xml.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_xml.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_xml.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_xml.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_xml.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_xml.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_xml.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_xml.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_zip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_zip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_zip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_zip' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_zip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_zip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_zip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_zip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_zip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_zip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_zip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_zip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_zip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_zip.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_zip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.integration.targets.win_zip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.integration.targets.win_zip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.integration.targets.win_zip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.integration.targets.win_zip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.integration.targets.win_zip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.unit.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.unit.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.unit.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.unit.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.unit.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.unit.plugins.lookup.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.unit.plugins.lookup.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.unit.plugins.lookup.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.unit.plugins.lookup.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.unit.plugins.lookup.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.windows.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.windows.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.windows.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.windows.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.community.windows.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.docs' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.agent2_common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.agent2_common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.agent2_common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.agent2_common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.agent2_common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.autopsk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.autopsk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.autopsk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.autopsk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.autopsk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.no_auto_psk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.no_auto_psk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.no_auto_psk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.no_auto_psk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.common.tests.no_auto_psk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.agent2_common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.agent2_common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.agent2_common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.agent2_common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.agent2_common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.no_auto_psk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.no_auto_psk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.no_auto_psk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.no_auto_psk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2.tests.no_auto_psk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.agent2_common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.agent2_common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.agent2_common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.agent2_common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.agent2_common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.autopsk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.autopsk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.autopsk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.autopsk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.autopsk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.agent2autopsk.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.autopsk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.autopsk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.autopsk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.autopsk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.autopsk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.autopsk.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.common' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.no_auto_psk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.no_auto_psk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.no_auto_psk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.no_auto_psk' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_agent_tests.molecule.default.tests.no_auto_psk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_javagateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_javagateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_javagateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_javagateway' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_javagateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_javagateway.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_javagateway.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_javagateway.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_javagateway.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_javagateway.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_proxy' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_proxy.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_proxy.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_proxy.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_proxy.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_proxy.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_server' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_server.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_server.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_server.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_server.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_server.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_web' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_web' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_web' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_web' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_web' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.molecule.zabbix_web.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.molecule.zabbix_web.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.molecule.zabbix_web.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.molecule.zabbix_web.tests' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.molecule.zabbix_web.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.files' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.files.win_sample' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.files.win_sample' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.files.win_sample' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.files.win_sample' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.files.win_sample' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.molecule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.molecule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.molecule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.molecule' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.molecule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.templates.userparameters' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.templates.userparameters' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.templates.userparameters' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.templates.userparameters' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.templates.userparameters' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_agent.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_agent.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_agent.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_agent.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_agent.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway.files' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_javagateway.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_javagateway.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_javagateway.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_javagateway.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_javagateway.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy.files' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_proxy.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_proxy.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_proxy.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_proxy.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_proxy.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server.files' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_server.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_server.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_server.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_server.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_server.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_web' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_web' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_web' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_web' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_web' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_web.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_web.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_web.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_web.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_web.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_web.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_web.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_web.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_web.handlers' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_web.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_web.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_web.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_web.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_web.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_web.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_web.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_web.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_web.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_web.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_web.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_web.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_web.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_web.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_web.templates' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_web.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.roles.zabbix_web.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.roles.zabbix_web.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.roles.zabbix_web.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.roles.zabbix_web.vars' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.roles.zabbix_web.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.scripts.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.scripts.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.scripts.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.scripts.inventory' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.scripts.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.setup_zabbix.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_action.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_authentication.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_autoregister.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_discovery_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_globalmacro.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_group_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_host_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_hostmacro.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_housekeeping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_maintenance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_mediatype.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_module_defaults_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_proxy_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_screen.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_script.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_service.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.files' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_template_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_directory.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_user_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.integration.targets.test_zabbix_usergroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.community.zabbix.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.community.zabbix.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.community.zabbix.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.community.zabbix.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.community.zabbix.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.docs' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.docs._static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.docs._static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.docs._static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.docs._static' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.docs._static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.meta' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.plugins.become' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.plugins.become' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.plugins.become' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.plugins.become' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.plugins.become' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.plugins.module_utils.podman' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.plugins.module_utils.podman' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.plugins.module_utils.podman' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.plugins.module_utils.podman' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.plugins.module_utils.podman' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.connection' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.connection_buildah' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.connection_buildah' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.connection_buildah' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.connection_buildah' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.connection_buildah' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.connection_podman' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.connection_podman' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.connection_podman' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.connection_podman' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.connection_podman' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_container.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_container.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_container.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_container.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_container.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.files' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_container_idempotency.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_container_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_container_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_container_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_container_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_container_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_containers.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_containers.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_containers.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_containers.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_containers.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_export.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_export.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_export.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_export.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_export.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_generate_systemd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_generate_systemd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_generate_systemd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_generate_systemd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_generate_systemd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_image.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_image.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_image.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_image.files' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_image.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_image.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_image.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_image.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_image.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_image.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_image_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_image_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_image_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_image_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_image_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_import.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_import.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_import.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_import.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_import.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_load.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_load.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_load.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_load.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_load.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_login.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_login.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_login.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_login.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_login.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_login_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_login_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_login_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_login_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_login_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_logout.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_logout.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_logout.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_logout.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_logout.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_network_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_network_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_network_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_network_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_network_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks.files' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_play.tasks.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_pod.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_pod.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_pod.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_pod.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_pod.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_pod_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_pod_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_pod_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_pod_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_pod_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_save.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_save.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_save.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_save.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_save.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_secret.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_secret.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_secret.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_secret.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_secret.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_tag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_tag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_tag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_tag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_tag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.integration.targets.podman_volume_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.integration.targets.podman_volume_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.integration.targets.podman_volume_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.integration.targets.podman_volume_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.integration.targets.podman_volume_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.containers.podman.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.containers.podman.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.containers.podman.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.containers.podman.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.containers.podman.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.ci' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.ci' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.ci' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.ci' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.ci' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.dev' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.dev' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.dev' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.dev' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.dev' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.dev.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.dev.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.dev.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.dev.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.dev.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.dev.policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.dev.policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.dev.policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.dev.policy' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.dev.policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.dev.proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.dev.proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.dev.proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.dev.proxy' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.dev.proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.dev.test_app_centos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.dev.test_app_centos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.dev.test_app_centos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.dev.test_app_centos' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.dev.test_app_centos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.dev.test_app_ubuntu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.dev.test_app_ubuntu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.dev.test_app_ubuntu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.dev.test_app_ubuntu' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.dev.test_app_ubuntu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.examples' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.meta' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.meta' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.templates' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.junit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.junit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.junit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.junit' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.junit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.policy' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.proxy' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_centos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_centos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_centos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_centos' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_centos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_ubuntu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_ubuntu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_ubuntu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_ubuntu' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_app_ubuntu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_cases' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_cases' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_cases' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_cases' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.roles.conjur_host_identity.tests.test_cases' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.conjur_variable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.conjur_variable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.conjur_variable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.conjur_variable' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.conjur_variable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.conjur_variable.junit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.conjur_variable.junit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.conjur_variable.junit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.conjur_variable.junit' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.conjur_variable.junit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.conjur_variable.policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.conjur_variable.policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.conjur_variable.policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.conjur_variable.policy' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.conjur_variable.policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.conjur_variable.proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.conjur_variable.proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.conjur_variable.proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.conjur_variable.proxy' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.conjur_variable.proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.conjur_variable.test_cases' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.conjur_variable.test_cases' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.conjur_variable.test_cases' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.conjur_variable.test_cases' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.conjur_variable.test_cases' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.conjur.tests.unit.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.conjur.tests.unit.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.conjur.tests.unit.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.conjur.tests.unit.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.conjur.tests.unit.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.docs' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.docs.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.docs.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.docs.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.docs.images' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.docs.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.meta' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.roles.aimprovider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.roles.aimprovider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.roles.aimprovider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.roles.aimprovider' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.roles.aimprovider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.roles.aimprovider.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.roles.aimprovider.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.roles.aimprovider.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.roles.aimprovider.defaults' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.roles.aimprovider.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.roles.aimprovider.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.roles.aimprovider.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.roles.aimprovider.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.roles.aimprovider.tasks' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.roles.aimprovider.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.cyberark.pas.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.cyberark.pas.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.cyberark.pas.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.cyberark.pas.tests' to be distributed and are already explicitly excluding 'ansible_collections.cyberark.pas.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.changelogs.archive_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.changelogs.archive_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.changelogs.archive_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.changelogs.archive_fragments' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.changelogs.archive_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.group_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.group_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.group_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.playbooks.bgp_l3_fabric.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.playbooks.common_examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.playbooks.common_examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.playbooks.common_examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.playbooks.common_examples' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.playbooks.common_examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.aaa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.aaa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.aaa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.aaa' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.aaa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_af' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_af' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_af' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_af' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_af' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_as_paths' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_as_paths' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_as_paths' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_as_paths' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_as_paths' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_communities' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_communities' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_communities' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_communities' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_communities' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_ext_communities' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_ext_communities' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_ext_communities' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_ext_communities' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_ext_communities' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors_af' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors_af' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors_af' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors_af' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.bgp_neighbors_af' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.mclag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.mclag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.mclag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.mclag' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.mclag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.ntp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.ntp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.ntp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.ntp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.ntp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.port_breakout' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.port_breakout' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.port_breakout' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.port_breakout' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.port_breakout' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.radius_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.radius_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.radius_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.radius_server' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.radius_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.system' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.tacacs_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.tacacs_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.tacacs_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.tacacs_server' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.tacacs_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.users' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vlans' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vrfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vrfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vrfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vrfs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vrfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vxlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vxlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vxlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vxlans' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.argspec.vxlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.aaa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.aaa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.aaa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.aaa' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.aaa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_af' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_af' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_af' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_af' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_af' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_as_paths' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_as_paths' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_as_paths' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_as_paths' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_as_paths' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_communities' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_communities' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_communities' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_communities' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_communities' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_ext_communities' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_ext_communities' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_ext_communities' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_ext_communities' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_ext_communities' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors_af' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors_af' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors_af' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors_af' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.bgp_neighbors_af' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.mclag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.mclag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.mclag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.mclag' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.mclag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.ntp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.ntp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.ntp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.ntp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.ntp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.port_breakout' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.port_breakout' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.port_breakout' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.port_breakout' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.port_breakout' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.radius_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.radius_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.radius_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.radius_server' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.radius_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.system' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.tacacs_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.tacacs_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.tacacs_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.tacacs_server' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.tacacs_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.users' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vlans' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vrfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vrfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vrfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vrfs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vrfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vxlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vxlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vxlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vxlans' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.config.vxlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.aaa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.aaa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.aaa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.aaa' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.aaa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_af' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_af' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_af' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_af' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_af' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_as_paths' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_as_paths' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_as_paths' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_as_paths' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_as_paths' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_communities' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_communities' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_communities' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_communities' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_communities' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_ext_communities' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_ext_communities' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_ext_communities' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_ext_communities' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_ext_communities' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors_af' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors_af' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors_af' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors_af' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.bgp_neighbors_af' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.mclag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.mclag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.mclag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.mclag' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.mclag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.ntp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.ntp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.ntp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.ntp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.ntp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.port_breakout' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.port_breakout' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.port_breakout' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.port_breakout' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.port_breakout' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.radius_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.radius_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.radius_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.radius_server' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.radius_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.system' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.tacacs_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.tacacs_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.tacacs_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.tacacs_server' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.tacacs_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.users' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vlans' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vrfs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vrfs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vrfs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vrfs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vrfs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vxlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vxlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vxlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vxlans' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.facts.vxlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.module_utils.network.sonic.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.common.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_aaa.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_api.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_af.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_as_paths.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_communities.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_ext_communities.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_bgp_neighbors_af.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l2_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_l3_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_lag_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_mclag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_port_breakout.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_prefix_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_radius_server.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_tacacs_server.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_users.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vlans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vrfs.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.sonic_vxlan.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.regression.roles.test_reports.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.enterprise_sonic.tests.unit.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.enterprise_sonic.tests.unit.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.enterprise_sonic.tests.unit.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.enterprise_sonic.tests.unit.utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.enterprise_sonic.tests.unit.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.docs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.docs.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.docs.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.docs.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.docs.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.docs.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.idrac' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.idrac' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.idrac' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.idrac' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.idrac' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.idrac.deprecated' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.idrac.deprecated' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.idrac.deprecated' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.idrac.deprecated' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.idrac.deprecated' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.application' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.application' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.application' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.application' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.application' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.compliance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.compliance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.compliance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.compliance' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.compliance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline.component_reports_filtering' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline.component_reports_filtering' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline.component_reports_filtering' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline.component_reports_filtering' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.baseline.component_reports_filtering' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.catalog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.catalog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.catalog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.catalog' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.firmware.catalog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.powerstate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.powerstate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.powerstate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.powerstate' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.powerstate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.profile' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.profile' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.profile' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.profile' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.template' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.ome.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.ome.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.ome.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.ome.user' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.ome.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.redfish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.redfish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.redfish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.redfish' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.redfish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.redfish.firmware' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.redfish.firmware' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.redfish.firmware' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.redfish.firmware' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.redfish.firmware' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.playbooks.redfish.storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.playbooks.redfish.storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.playbooks.redfish.storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.playbooks.redfish.storage' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.playbooks.redfish.storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.plugins' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.openmanage.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.openmanage.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.openmanage.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.openmanage.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.openmanage.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.docs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.group_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.group_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.group_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.host_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.host_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.host_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.host_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.playbooks.clos_fabric_ebgp.host_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn.host_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn.host_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn.host_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn.host_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.playbooks.vxlan_evpn.host_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_aaa.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_aaa.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_aaa.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_aaa.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_aaa.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_acl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_acl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_acl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_acl.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_acl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bfd.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bfd.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bfd.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bfd.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bfd.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_bgp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_bgp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_bgp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_bgp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_bgp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_copy_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_copy_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_copy_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_copy_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_copy_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_dns.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_dns.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_dns.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_dns.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_dns.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ecmp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ecmp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ecmp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ecmp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ecmp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_fabric_summary' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_fabric_summary' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_fabric_summary' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_fabric_summary' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_fabric_summary' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests.host_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests.host_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests.host_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests.host_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_fabric_summary.tests.host_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_flow_monitor.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_image_upgrade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_image_upgrade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_image_upgrade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_image_upgrade' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_image_upgrade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_image_upgrade.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_interface.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_interface.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_interface.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_interface.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_interface.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lag.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lag.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lag.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lag.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lag.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_lldp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_lldp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_lldp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_lldp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_lldp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_logging.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_logging.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_logging.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_logging.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_logging.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_network_validation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_network_validation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_network_validation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_network_validation' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_network_validation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_network_validation.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_network_validation.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_network_validation.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_network_validation.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_network_validation.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_network_validation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_network_validation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_network_validation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_network_validation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_network_validation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.group_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.group_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.group_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.host_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.host_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.host_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.host_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_network_validation.tests.host_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_ntp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_ntp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_ntp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_ntp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_ntp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_prefix_list.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_prefix_list.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_prefix_list.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_prefix_list.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_prefix_list.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_qos.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_qos.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_qos.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_qos.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_qos.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_raguard.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_raguard.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_raguard.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_raguard.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_raguard.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_route_map.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_route_map.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_route_map.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_route_map.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_route_map.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_snmp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_snmp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_snmp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_snmp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_snmp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_system.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_system.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_system.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_system.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_system.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_template' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_template.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_template.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_template.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_template.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_template.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_template.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_template.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_template.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_template.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_template.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_template.tests.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_template.tests.group_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_template.tests.group_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_template.tests.group_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_template.tests.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_uplink.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_uplink.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_uplink.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_uplink.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_uplink.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_users.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_users.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_users.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_users.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_users.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlan.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlan.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlan.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlan.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlan.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vlt.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vlt.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vlt.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vlt.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vlt.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrf.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrf.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrf.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrf.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrf.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vrrp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vrrp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vrrp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vrrp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vrrp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_vxlan.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_vxlan.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_vxlan.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_vxlan.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_vxlan.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.roles.os10_xstp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.roles.os10_xstp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.roles.os10_xstp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.roles.os10_xstp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.roles.os10_xstp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.templates.aaa_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.templates.aaa_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.templates.aaa_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.templates.aaa_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.templates.aaa_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_aaa_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.templates.acl_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.templates.acl_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.templates.acl_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.templates.acl_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.templates.acl_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_acl_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.templates.bgp_vrf.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.templates.bgp_vrf.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.templates.bgp_vrf.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.templates.bgp_vrf.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.templates.bgp_vrf.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_bgp_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.templates.ecmp_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.templates.ecmp_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.templates.ecmp_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.templates.ecmp_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.templates.ecmp_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ecmp_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.templates.flow_monitor_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.templates.flow_monitor_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.templates.flow_monitor_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.templates.flow_monitor_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.templates.flow_monitor_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_flow_monitor_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.templates.interface_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.templates.interface_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.templates.interface_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.templates.interface_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.templates.interface_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_interface_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.templates.lag_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.templates.lag_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.templates.lag_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.templates.lag_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.templates.lag_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lag_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.templates.lldp_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.templates.lldp_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.templates.lldp_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.templates.lldp_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.templates.lldp_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_lldp_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.templates.logging_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.templates.logging_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.templates.logging_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.templates.logging_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.templates.logging_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_logging_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.templates.ntp_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.templates.ntp_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.templates.ntp_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.templates.ntp_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.templates.ntp_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_ntp_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.templates.prefix_list_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.templates.prefix_list_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.templates.prefix_list_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.templates.prefix_list_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.templates.prefix_list_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_prefix_list_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.templates.qos_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.templates.qos_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.templates.qos_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.templates.qos_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.templates.qos_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_qos_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.templates.route_map_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.templates.route_map_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.templates.route_map_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.templates.route_map_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.templates.route_map_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_route_map_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.templates.snmp_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.templates.snmp_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.templates.snmp_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.templates.snmp_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.templates.snmp_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_snmp_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.templates.system_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.templates.system_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.templates.system_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.templates.system_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.templates.system_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_system_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.templates.uplink_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.templates.uplink_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.templates.uplink_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.templates.uplink_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.templates.uplink_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_uplink_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks_old' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks_old' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks_old' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks_old' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tasks_old' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.templates.users_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.templates.users_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.templates.users_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.templates.users_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.templates.users_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_users_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.templates.vlan_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.templates.vlan_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.templates.vlan_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.templates.vlan_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.templates.vlan_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlan_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.templates.vlt_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.templates.vlt_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.templates.vlt_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.templates.vlt_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.templates.vlt_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vlt_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.templates.vrrp_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.templates.vrrp_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.templates.vrrp_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.templates.vrrp_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.templates.vrrp_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_vrrp_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.templates.xstp_basic.steps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.templates.xstp_basic.steps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.templates.xstp_basic.steps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.templates.xstp_basic.steps' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.templates.xstp_basic.steps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.os10_xstp_role.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks.testcase' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks.testcase' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks.testcase' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks.testcase' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.integration.targets.role_test.tasks.testcase' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os10.tests.unit.modules.network.os10.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.docs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.playbooks.ibgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.playbooks.ibgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.playbooks.ibgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.playbooks.ibgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.playbooks.ibgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.playbooks.ibgp.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.playbooks.ibgp.group_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.playbooks.ibgp.group_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.playbooks.ibgp.group_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.playbooks.ibgp.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.playbooks.ibgp.host_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.playbooks.ibgp.host_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.playbooks.ibgp.host_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.playbooks.ibgp.host_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.playbooks.ibgp.host_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_aaa.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_aaa.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_aaa.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_aaa.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_aaa.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_acl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_acl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_acl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_acl.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_acl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_bgp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_bgp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_bgp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_bgp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_bgp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_interface.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_interface.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_interface.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_interface.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_interface.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lag.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lag.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lag.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lag.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lag.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_lldp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_lldp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_lldp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_lldp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_lldp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_logging.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_logging.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_logging.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_logging.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_logging.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_ntp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_ntp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_ntp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_ntp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_ntp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_qos.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_qos.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_qos.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_qos.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_qos.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_snmp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_snmp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_snmp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_snmp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_snmp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_system.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_system.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_system.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_system.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_system.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_users.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_users.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_users.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_users.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_users.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vlan.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vlan.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vlan.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vlan.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vlan.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_vrrp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_vrrp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_vrrp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_vrrp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_vrrp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.roles.os6_xstp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.roles.os6_xstp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.roles.os6_xstp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.roles.os6_xstp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.roles.os6_xstp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_command.os6_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_config.os6_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.integration.targets.os6_facts.os6_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os6.tests.unit.modules.network.os6.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.docs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.group_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.group_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.group_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.host_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.host_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.host_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.host_vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.playbooks.clos_fabric_ebgp.host_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_aaa.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_aaa.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_aaa.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_aaa.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_aaa.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_acl.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_acl.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_acl.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_acl.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_acl.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_bgp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_bgp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_bgp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_bgp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_bgp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_copy_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_copy_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_copy_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_copy_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_copy_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dcb.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dcb.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dcb.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dcb.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dcb.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_dns.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_dns.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_dns.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_dns.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_dns.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ecmp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ecmp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ecmp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ecmp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ecmp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_interface.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_interface.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_interface.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_interface.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_interface.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lag.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lag.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lag.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lag.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lag.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_lldp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_lldp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_lldp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_lldp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_lldp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_logging.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_logging.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_logging.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_logging.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_logging.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_ntp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_ntp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_ntp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_ntp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_ntp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_prefix_list.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_prefix_list.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_prefix_list.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_prefix_list.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_prefix_list.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_sflow.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_sflow.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_sflow.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_sflow.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_sflow.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_snmp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_snmp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_snmp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_snmp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_snmp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_system.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_system.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_system.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_system.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_system.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_users.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_users.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_users.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_users.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_users.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlan.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlan.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlan.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlan.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlan.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vlt.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vlt.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vlt.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vlt.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vlt.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrf.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrf.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrf.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrf.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrf.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_vrrp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_vrrp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_vrrp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_vrrp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_vrrp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp.handlers' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp.templates' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.roles.os9_xstp.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.roles.os9_xstp.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.roles.os9_xstp.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.roles.os9_xstp.vars' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.roles.os9_xstp.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_command.os9_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_config.os9_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.integration.targets.os9_facts.os9_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.os9.tests.unit.modules.network.os9.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.docs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.docs.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.docs.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.docs.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.docs.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.docs.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.plugins.module_utils.storage.dell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.plugins.module_utils.storage.dell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.plugins.module_utils.storage.dell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.plugins.module_utils.storage.dell' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.plugins.module_utils.storage.dell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.powerflex.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.powerflex.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.powerflex.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.powerflex.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.powerflex.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.docs' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.docs.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.docs.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.docs.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.docs.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.docs.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.meta' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.plugins.module_utils.storage.dell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.plugins.module_utils.storage.dell' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.plugins.module_utils.storage.dell' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.plugins.module_utils.storage.dell' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.plugins.module_utils.storage.dell' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.tests' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.dellemc.unity.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.dellemc.unity.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.dellemc.unity.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.dellemc.unity.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.dellemc.unity.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.docs' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.meta' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit.module_utils.network.f5' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit.module_utils.network.f5' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit.module_utils.network.f5' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit.module_utils.network.f5' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit.module_utils.network.f5' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.f5networks.f5_modules.tests.unit.modules.network.f5.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager.meta' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager.plugins' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortimanager.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortimanager.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortimanager.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortimanager.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortimanager.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.examples' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.examples.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.examples.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.examples.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.examples.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.examples.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.examples.httpapi.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.examples.httpapi.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.examples.httpapi.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.examples.httpapi.inventory' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.examples.httpapi.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.meta' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.common' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.fortimanager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.fortimanager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.fortimanager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.fortimanager' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.fortimanager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.system' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.argspec.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts.system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts.system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts.system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts.system' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.module_utils.fortios.facts.system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.fortinet.fortios.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.fortinet.fortios.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.fortinet.fortios.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.fortinet.fortios.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.fortinet.fortios.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.docs' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.meta' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.module_utils.network.frr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.module_utils.network.frr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.module_utils.network.frr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.module_utils.network.frr' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.module_utils.network.frr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config.bgp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config.bgp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config.bgp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config.bgp' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.module_utils.network.frr.providers.cli.config.bgp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.unit.modules.network.frr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.unit.modules.network.frr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.unit.modules.network.frr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.unit.modules.network.frr' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.unit.modules.network.frr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.frr.frr.tests.unit.modules.network.frr.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.frr.frr.tests.unit.modules.network.frr.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.frr.frr.tests.unit.modules.network.frr.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.frr.frr.tests.unit.modules.network.frr.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.frr.frr.tests.unit.modules.network.frr.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.gluster.gluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.gluster.gluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.gluster.gluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.gluster.gluster' to be distributed and are already explicitly excluding 'ansible_collections.gluster.gluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.gluster.gluster.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.gluster.gluster.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.gluster.gluster.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.gluster.gluster.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.gluster.gluster.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.gluster.gluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.gluster.gluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.gluster.gluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.gluster.gluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.gluster.gluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.gluster.gluster.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.gluster.gluster.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.gluster.gluster.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.gluster.gluster.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.gluster.gluster.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.gluster.gluster.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.gluster.gluster.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.gluster.gluster.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.gluster.gluster.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.gluster.gluster.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.molecule.gcloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.molecule.gcloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.molecule.gcloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.molecule.gcloud' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.molecule.gcloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.molecule.gcloud.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.molecule.gcloud.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.molecule.gcloud.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.molecule.gcloud.files' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.molecule.gcloud.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.molecule.gcloud.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.molecule.gcloud.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.molecule.gcloud.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.molecule.gcloud.tests' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.molecule.gcloud.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.molecule.gcsfuse' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.molecule.gcsfuse' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.molecule.gcsfuse' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.molecule.gcsfuse' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.molecule.gcsfuse' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.molecule.gcsfuse.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.molecule.gcsfuse.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.molecule.gcsfuse.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.molecule.gcsfuse.files' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.molecule.gcsfuse.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.molecule.gcsfuse.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.molecule.gcsfuse.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.molecule.gcsfuse.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.molecule.gcsfuse.tests' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.molecule.gcsfuse.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.plugins' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcloud' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcloud.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcloud.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcloud.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcloud.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcloud.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcloud.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcloud.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcloud.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcloud.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcloud.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcloud.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcloud.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcloud.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcloud.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcloud.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcloud.tasks.archive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcloud.tasks.archive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcloud.tasks.archive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcloud.tasks.archive' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcloud.tasks.archive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcloud.tasks.package' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcloud.tasks.package' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcloud.tasks.package' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcloud.tasks.package' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcloud.tasks.package' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcloud.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcloud.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcloud.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcloud.vars' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcloud.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcp_http_lb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcp_http_lb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcp_http_lb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcp_http_lb' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcp_http_lb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcp_http_lb.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcp_http_lb.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcp_http_lb.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcp_http_lb.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcp_http_lb.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcp_http_lb.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcp_http_lb.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcp_http_lb.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcp_http_lb.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcp_http_lb.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcp_http_lb.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcp_http_lb.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcp_http_lb.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcp_http_lb.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcp_http_lb.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcp_http_lb.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcp_http_lb.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcp_http_lb.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcp_http_lb.tests' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcp_http_lb.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcp_http_lb.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcp_http_lb.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcp_http_lb.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcp_http_lb.vars' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcp_http_lb.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcsfuse' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcsfuse' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcsfuse' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcsfuse' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcsfuse' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcsfuse.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcsfuse.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcsfuse.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcsfuse.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcsfuse.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcsfuse.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcsfuse.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcsfuse.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcsfuse.handlers' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcsfuse.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcsfuse.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcsfuse.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcsfuse.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcsfuse.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcsfuse.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcsfuse.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcsfuse.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcsfuse.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcsfuse.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcsfuse.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.roles.gcsfuse.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.roles.gcsfuse.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.roles.gcsfuse.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.roles.gcsfuse.vars' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.roles.gcsfuse.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.scripts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.scripts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.scripts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.scripts' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.scripts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_appengine_firewall_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_dataset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigquery_table.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_bigtable_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudbuild_trigger.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudfunctions_cloud_function.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudscheduler_job.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_cloudtasks_queue.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_address.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_autoscaler.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_bucket.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_backend_service.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_disk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_external_vpn_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_forwarding_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_address.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_global_forwarding_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_health_check.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_http_health_check.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_https_health_check.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_image.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_group_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_instance_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_interconnect_attachment.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_managed_ssl_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_network_endpoint_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_node_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_autoscaler.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_backend_service.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_disk.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_health_check.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_instance_group_manager.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_http_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_target_https_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_region_url_map.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_reservation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_resource_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_route.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_router.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_ssl_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_subnetwork.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_http_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_https_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_ssl_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_tcp_proxy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_target_vpn_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_url_map.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_compute_vpn_tunnel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_container_node_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_managed_zone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_dns_resource_record_set.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_filestore_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_iam_service_account_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_crypto_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_kms_key_ring.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_logging_metric.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_model.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_mlengine_version.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_subscription.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_pubsub_topic.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_redis_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_resourcemanager_project.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_runtimeconfig_variable.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_serviceusage_service.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sourcerepo_repository.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_database.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_spanner_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_database.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_ssl_cert.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_sql_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_bucket_access_control.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_default_object_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_storage_object.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.defaults' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.meta' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.tasks' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.integration.targets.gcp_tpu_node.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.google.cloud.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.google.cloud.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.google.cloud.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.google.cloud.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.google.cloud.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.meta' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.roles.grafana_agent' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.roles.grafana_agent' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.roles.grafana_agent' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.roles.grafana_agent' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.roles.grafana_agent' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.roles.grafana_agent.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.roles.grafana_agent.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.roles.grafana_agent.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.roles.grafana_agent.defaults' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.roles.grafana_agent.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.roles.grafana_agent.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.roles.grafana_agent.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.roles.grafana_agent.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.roles.grafana_agent.meta' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.roles.grafana_agent.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.roles.grafana_agent.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.roles.grafana_agent.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.roles.grafana_agent.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.roles.grafana_agent.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.roles.grafana_agent.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.alert_contact_point.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.alert_contact_point.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.alert_contact_point.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.alert_contact_point.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.alert_contact_point.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.alert_notification_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.alert_notification_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.alert_notification_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.alert_notification_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.alert_notification_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_api_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_api_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_api_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_api_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_api_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_plugin.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_plugin.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_plugin.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_plugin.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_plugin.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_stack.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_stack.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_stack.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_stack.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.cloud_stack.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.dashboard.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.dashboard.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.dashboard.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.dashboard.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.dashboard.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.datasource.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.datasource.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.datasource.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.datasource.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.datasource.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.grafana.grafana.tests.integration.targets.folder.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.grafana.grafana.tests.integration.targets.folder.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.grafana.grafana.tests.integration.targets.folder.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.grafana.grafana.tests.integration.targets.folder.tasks' to be distributed and are already explicitly excluding 'ansible_collections.grafana.grafana.tests.integration.targets.folder.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_certificate_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_datacenter_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_floating_ip_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_image_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_service.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_target.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_load_balancer_type_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_location_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_network_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_placement_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_primary_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_rdns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_route.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_server_type_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_ssh_key_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_subnetwork.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.hcloud_volume_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_selfsigned_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_selfsigned_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_selfsigned_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_selfsigned_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_selfsigned_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_sshkey.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_sshkey.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_sshkey.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_sshkey.tasks' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.integration.targets.setup_sshkey.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.utils.gitlab' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.utils.gitlab' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.utils.gitlab' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.utils.gitlab' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.utils.gitlab' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hetzner.hcloud.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hetzner.hcloud.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hetzner.hcloud.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hetzner.hcloud.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.hetzner.hcloud.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hpe.nimble' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hpe.nimble' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hpe.nimble' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hpe.nimble' to be distributed and are already explicitly excluding 'ansible_collections.hpe.nimble' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hpe.nimble.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hpe.nimble.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hpe.nimble.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hpe.nimble.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.hpe.nimble.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hpe.nimble.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hpe.nimble.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hpe.nimble.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hpe.nimble.meta' to be distributed and are already explicitly excluding 'ansible_collections.hpe.nimble.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hpe.nimble.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hpe.nimble.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hpe.nimble.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hpe.nimble.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.hpe.nimble.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hpe.nimble.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hpe.nimble.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hpe.nimble.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hpe.nimble.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.hpe.nimble.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hpe.nimble.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hpe.nimble.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hpe.nimble.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hpe.nimble.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.hpe.nimble.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.hpe.nimble.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.hpe.nimble.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.hpe.nimble.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.hpe.nimble.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.hpe.nimble.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.docs' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.meta' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.deploy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.deploy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.deploy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.deploy' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.deploy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.deploy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.deploy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.deploy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.deploy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.deploy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.log_source_management.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.offense' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.offense' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.offense' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.offense' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.offense' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.offense.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.offense.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.offense.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.offense.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.offense.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_deploy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_deploy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_deploy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_deploy' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_deploy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_source_management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_source_management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_source_management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_source_management' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_source_management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.meta' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.vars' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_log_sources_management.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_offense' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_offense' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_offense' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_offense' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_offense' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_rule' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.qradar_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.rule' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.integration.targets.rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.integration.targets.rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.integration.targets.rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.integration.targets.rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.integration.targets.rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.unit.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.unit.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.unit.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.unit.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.unit.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.qradar.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.qradar.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.qradar.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.qradar.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ibm.qradar.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.docs' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.meta' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.plugins' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.roles' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ibm.spectrum_virtualize.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.docs' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.ibox_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.ibox_vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.ibox_vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.ibox_vars' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.ibox_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.meta' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.tests.hacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.tests.hacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.tests.hacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.tests.hacking' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.tests.hacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infinidat.infinibox.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infinidat.infinibox.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infinidat.infinibox.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infinidat.infinibox.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.infinidat.infinibox.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.plugins' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_a_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_aaaa_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_cname_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_dns_view.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_host_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_mx_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_naptr_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_network_view.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_ptr_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_srv_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_txt_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.defaults' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.meta' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.nios_zone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.integration.targets.prepare_nios_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.integration.targets.prepare_nios_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.integration.targets.prepare_nios_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.integration.targets.prepare_nios_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.integration.targets.prepare_nios_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.infoblox.nios_modules.tests.unit.plugins.modules.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim.docs' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim.meta' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.ispim.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.ispim.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.ispim.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.ispim.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.inspur.ispim.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.docs' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.meta' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.playbooks.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.playbooks.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.playbooks.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.playbooks.modules' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.playbooks.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.playbooks.modules.overall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.playbooks.modules.overall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.playbooks.modules.overall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.playbooks.modules.overall' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.playbooks.modules.overall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.inspur.sm.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.inspur.sm.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.inspur.sm.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.inspur.sm.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.inspur.sm.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.docs' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acls' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.hostname' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_instances' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_instances' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_instances' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_instances' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_instances' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_options' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_options' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_options' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_options' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.routing_options' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_policies_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_zones' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_zones' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_zones' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_zones' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.security_zones' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.vlans' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.argspec.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acls' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.hostname' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_instances' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_instances' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_instances' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_instances' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_instances' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_options' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_options' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_options' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_options' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.routing_options' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_policies_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_zones' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_zones' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_zones' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_zones' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.security_zones' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.vlans' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.config.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acl_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acl_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acl_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acl_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acl_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acls' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acls' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acls' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acls' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.acls' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.hostname' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l2_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l2_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l2_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l2_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l2_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lacp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_instances' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_instances' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_instances' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_instances' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_instances' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_options' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_options' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_options' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_options' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.routing_options' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies_global' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_policies_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_zones' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_zones' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_zones' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_zones' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.security_zones' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.vlans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.vlans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.vlans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.vlans' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.facts.vlans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.utils' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.module_utils.network.junos.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acl_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_acls.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_banner.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_address_family.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_bgp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_json' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_json' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_json' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_json' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_json' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_text' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_text' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_text' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_text' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_text' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_xml' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_xml' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_xml' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_xml' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_command.tests.netconf_xml' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.templates.basic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.templates.basic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.templates.basic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.templates.basic' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.templates.basic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.cli_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.cli_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.cli_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.cli_config' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.cli_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.redirection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.redirection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.redirection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.redirection' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_config.tests.redirection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_facts.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_hostname.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_interfaces.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l2_interfaces.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_l3_interfaces.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lacp_interfaces.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lag_interfaces.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_global.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_lldp_interfaces.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.backups' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.backups' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.backups' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.backups' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.backups' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_logging_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_netconf.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.backups' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.backups' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.backups' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.backups' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.backups' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ntp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospf_interfaces.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_ospfv3.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_prefix_lists.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_instances.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_routing_options.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_rpc.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_policies_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_security_zones.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_smoke.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.backups' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.backups' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.backups' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.backups' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.backups' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.vars' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_snmp_server.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_static_routes.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_system.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_user.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vlans.tests.netconf.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.defaults' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tests.netconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tests.netconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tests.netconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tests.netconf' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.junos_vrf.tests.netconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.integration.targets.prepare_junos_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.modules.network.junos.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.junipernetworks.junos.tests.unit.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.junipernetworks.junos.tests.unit.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.junipernetworks.junos.tests.unit.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.junipernetworks.junos.tests.unit.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.junipernetworks.junos.tests.unit.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.docs' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.docs.docsite.rst.kubernetes_scenarios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.docs.docsite.rst.kubernetes_scenarios' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.docs.docsite.rst.kubernetes_scenarios' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.docs.docsite.rst.kubernetes_scenarios' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.docs.docsite.rst.kubernetes_scenarios' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.connection' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.module_utils.client' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.module_utils.client' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.module_utils.client' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.module_utils.client' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.module_utils.client' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.module_utils.k8s' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.module_utils.k8s' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.module_utils.k8s' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.module_utils.k8s' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.module_utils.k8s' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm.files' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm.library' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks.tests_chart' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks.tests_chart' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks.tests_chart' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks.tests_chart' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm.tasks.tests_chart' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.files' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_diff.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_kubeconfig.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.files.sample_plugin' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.files.sample_plugin' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.files.sample_plugin' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.files.sample_plugin' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.files.sample_plugin' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_plugin.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_pull.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_repository.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.helm_set_values.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.install_helm.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks.vars' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.inventory_k8s.playbooks.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_access_review.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_append_hash.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_apply.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_check_mode.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_cluster_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.ansible' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.ansible' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.ansible' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.ansible' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.ansible' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.teams' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.teams' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.teams' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.teams' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.files.data.teams' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.library' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.templates' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_copy.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.files' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_crd.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_delete.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.templates' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_diff.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_drain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_exec.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_full.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_gc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_generate_name.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_json_patch.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_label_selectors.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_log.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_manifest_url.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_merge_type.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_patched.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_rollback.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.files' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_scale.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_taint.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.templates' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_template.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_user_impersonation.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_validate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.k8s_waiter.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_k8s.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.meta' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.lookup_kustomize.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.remove_namespace.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.library' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.setup_kubeconfig.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.defaults' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.tasks' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.integration.targets.setup_namespace.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.unit.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.unit.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.unit.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.unit.action' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.unit.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.unit.module_utils.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.unit.module_utils.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.unit.module_utils.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.unit.module_utils.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.unit.module_utils.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.kubernetes.core.tests.unit.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.kubernetes.core.tests.unit.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.kubernetes.core.tests.unit.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.kubernetes.core.tests.unit.utils' to be distributed and are already explicitly excluding 'ansible_collections.kubernetes.core.tests.unit.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.docs' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_category.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_schedule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.agent_job_step.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.backup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.credential.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.database.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.dba_multitool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.first_responder_kit.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.files' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.install_script.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.instance_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.login.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.maintenance_solution.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.memory.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.nonquery.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.resource_governor.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_resource_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.rg_workload_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sa.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.defaults' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.vars' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.connection_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.connection_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.connection_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.connection_plugins' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.connection_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.shell_plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.shell_plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.shell_plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.shell_plugins' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.shell_plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.vars' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_sqlserver_test_plugins.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.vars' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.setup_win_sqlserver.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_configure.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.sp_whoisactive.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.traceflag.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_listener.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_ag_replica.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_category.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_schedule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_agent_job_step.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_availability_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_backup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_credential.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_database.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_dba_multitool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_first_responder_kit.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_hadr.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.files' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_install_script.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_instance_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_login.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_maintenance_solution.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_memory.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_nonquery.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_resource_governor.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_restore.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_resource_pool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_rg_workload_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sa.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_configure.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_sp_whoisactive.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_spn.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.tasks' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_tcp_port.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_traceflag.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.lowlydba.sqlserver.tests.integration.targets.win_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.plugins.module_utils.network.onyx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.plugins.module_utils.network.onyx' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.plugins.module_utils.network.onyx' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.plugins.module_utils.network.onyx' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.plugins.module_utils.network.onyx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.mellanox.onyx.tests.unit.modules.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.mellanox.onyx.tests.unit.modules.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.mellanox.onyx.tests.unit.modules.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.mellanox.onyx.tests.unit.modules.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.mellanox.onyx.tests.unit.modules.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.computer' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.computer' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.computer' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.computer' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.computer' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.computer.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.computer.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.computer.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.computer.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.computer.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.computer.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.computer.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.computer.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.computer.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.computer.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.domain' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.domain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.domain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.domain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.domain.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.domain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.domain_controller.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.group' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.group.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.membership' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.membership' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.membership' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.membership' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.membership' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.membership.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.membership.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.membership.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.membership.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.membership.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object.defaults' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object_info' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.handlers' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.object_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.offline_join.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.ou' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.ou' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.ou' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.ou' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.ou' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.ou.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.ou.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.ou.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.ou.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.ou.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.ou.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.ou.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.ou.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.ou.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.ou.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.setup_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.user' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.user.meta' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.integration.targets.user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.integration.targets.user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.integration.targets.user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.integration.targets.user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.integration.targets.user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit.plugins' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.unit.test_data.win_updates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.unit.test_data.win_updates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.unit.test_data.win_updates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.unit.test_data.win_updates' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.unit.test_data.win_updates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.microsoft.ad.tests.utils.shippable' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.microsoft.ad.tests.utils.shippable' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.microsoft.ad.tests.utils.shippable' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.microsoft.ad.tests.utils.shippable' to be distributed and are already explicitly excluding 'ansible_collections.microsoft.ad.tests.utils.shippable' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.aws.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.aws.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.aws.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.aws.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.aws.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_account.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_capacity_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.integration.targets.azure_rm_netapp_volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.runner.requirements' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.runner.requirements' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.runner.requirements' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.runner.requirements' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.runner.requirements' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.azure.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.azure.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.azure.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.azure.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.azure.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.execution_environments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.execution_environments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.execution_environments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.execution_environments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.execution_environments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.execution_environments.from_galaxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.execution_environments.from_galaxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.execution_environments.from_galaxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.execution_environments.from_galaxy' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.execution_environments.from_galaxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.execution_environments.from_github' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.execution_environments.from_github' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.execution_environments.from_github' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.execution_environments.from_github' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.execution_environments.from_github' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.plugins' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.cloudmanager.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.elementsw.tests.unit.plugins.modules_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.execution_environments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.execution_environments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.execution_environments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.execution_environments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.execution_environments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.execution_environments.from_galaxy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.execution_environments.from_galaxy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.execution_environments.from_galaxy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.execution_environments.from_galaxy' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.execution_environments.from_galaxy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.execution_environments.from_github' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.execution_environments.from_github' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.execution_environments.from_github' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.execution_environments.from_github' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.execution_environments.from_github' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.playbooks.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.playbooks.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.playbooks.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.playbooks.examples' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.playbooks.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.playbooks.examples.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.playbooks.examples.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.playbooks.examples.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.playbooks.examples.filter' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.playbooks.examples.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.playbooks.examples.json_query' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.playbooks.examples.json_query' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.playbooks.examples.json_query' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.playbooks.examples.json_query' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.playbooks.examples.json_query' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.playbooks.examples.rest_apis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.playbooks.examples.rest_apis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.playbooks.examples.rest_apis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.playbooks.examples.rest_apis' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.playbooks.examples.rest_apis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.playbooks.examples.support' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.playbooks.examples.support' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.playbooks.examples.support' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.playbooks.examples.support' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.playbooks.examples.support' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.handlers' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tests' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.vars' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_cluster_config.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.handlers' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tests' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.vars' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_nas_create.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_san_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_san_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_san_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_san_create' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_san_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.handlers' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tests' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.vars' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_san_create.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.handlers' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tests' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.vars' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_snapmirror_create.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.handlers' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tests' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.vars' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_create.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.handlers' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tests' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.vars' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.roles.na_ontap_vserver_delete.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.tests.unit.framework' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.tests.unit.framework' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.tests.unit.framework' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.tests.unit.framework' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.tests.unit.framework' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.ontap.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.ontap.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.ontap.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.ontap.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.ontap.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.storagegrid.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.storagegrid.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.storagegrid.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.storagegrid.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.storagegrid.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp.um_info.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp.um_info.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp.um_info.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp.um_info.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp.um_info.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks.collect_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks.collect_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks.collect_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks.collect_facts' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_common.tasks.collect_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.interface' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.snapshot' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.tasks.snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.templates' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_host.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.defaults' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.meta' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.roles.nar_santricity_management.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts_syslog.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts_syslog.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts_syslog.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts_syslog.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_alerts_syslog.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_asup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_asup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_asup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_asup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_asup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auditlog.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auditlog.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auditlog.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auditlog.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auditlog.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auth.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auth.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auth.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auth.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_auth.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_client_certificate.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_client_certificate.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_client_certificate.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_client_certificate.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_client_certificate.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_discover.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_discover.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_discover.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_discover.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_discover.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_drive_firmware.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_drive_firmware.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_drive_firmware.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_drive_firmware.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_drive_firmware.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_firmware.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_firmware.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_firmware.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_firmware.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_firmware.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_hostgroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_hostgroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_hostgroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_hostgroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_hostgroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ib_iser_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ib_iser_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ib_iser_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ib_iser_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ib_iser_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_target.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_target.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_target.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_target.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_iscsi_target.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ldap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ldap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ldap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ldap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_ldap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_lun_mapping.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_lun_mapping.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_lun_mapping.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_lun_mapping.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_lun_mapping.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_mgmt_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_mgmt_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_mgmt_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_mgmt_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_mgmt_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_nvme_interface.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_nvme_interface.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_nvme_interface.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_nvme_interface.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_nvme_interface.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_drive_firmware_upload.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_drive_firmware_upload.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_drive_firmware_upload.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_drive_firmware_upload.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_drive_firmware_upload.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_firmware_upload.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_firmware_upload.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_firmware_upload.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_firmware_upload.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_firmware_upload.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_systems.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_systems.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_systems.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_systems.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_proxy_systems.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_storagepool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_storagepool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_storagepool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_storagepool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_storagepool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_syslog.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_syslog.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_syslog.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_syslog.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_syslog.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.integration.targets.na_santricity_volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netapp_eseries.santricity.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netapp_eseries.santricity.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netapp_eseries.santricity.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netapp_eseries.santricity.vars' to be distributed and are already explicitly excluding 'ansible_collections.netapp_eseries.santricity.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs._extensions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs._extensions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs._extensions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs._extensions' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs._extensions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs._static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs._static' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs._static' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs._static' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs._static' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.changelog' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.changelog' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.changelog' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.changelog' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.changelog' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.getting_started' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.getting_started' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.getting_started' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.getting_started' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.getting_started' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.getting_started.contributing' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.getting_started.contributing' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.getting_started.contributing' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.getting_started.contributing' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.getting_started.contributing' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.getting_started.contributing.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.getting_started.contributing.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.getting_started.contributing.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.getting_started.contributing.inventory' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.getting_started.contributing.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules.media' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules.media' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules.media' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules.media' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.getting_started.contributing.modules.media' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.js.ansible' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.js.ansible' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.js.ansible' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.js.ansible' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.js.ansible' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.media' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.media' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.media' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.media' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.media' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_circuits' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_circuits' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_circuits' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_circuits' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_circuits' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_dcim' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_dcim' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_dcim' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_dcim' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_dcim' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_extras' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_extras' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_extras' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_extras' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_extras' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_ipam' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_ipam' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_ipam' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_ipam' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_ipam' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_secrets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_secrets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_secrets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_secrets' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_secrets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_tenancy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_tenancy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_tenancy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_tenancy' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_tenancy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_utils' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.module_utils.netbox_virtualization' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.module_utils.netbox_virtualization' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.module_utils.netbox_virtualization' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.module_utils.netbox_virtualization' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.module_utils.netbox_virtualization' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.docs.plugins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.docs.plugins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.docs.plugins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.docs.plugins' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.docs.plugins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.hacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.hacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.hacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.hacking' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.hacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.meta' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.inventory' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.filter_query_parameters' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.filter_query_parameters' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.filter_query_parameters' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.filter_query_parameters' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.filter_query_parameters' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.get_resource_list_chunked' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.get_resource_list_chunked' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.get_resource_list_chunked' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.get_resource_list_chunked' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.get_resource_list_chunked' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.group_extractors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.group_extractors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.group_extractors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.group_extractors' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.group_extractors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.refresh_url' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.refresh_url' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.refresh_url' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.refresh_url' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.refresh_url' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.validate_query_parameter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.validate_query_parameter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.validate_query_parameter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.validate_query_parameter' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.inventory.test_data.validate_query_parameter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.fixtures.choices' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.fixtures.choices' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.fixtures.choices' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.fixtures.choices' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.fixtures.choices' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.arg_spec_default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.arg_spec_default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.arg_spec_default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.arg_spec_default' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.arg_spec_default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_child' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_child' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_child' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_child' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_child' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_no_child' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_no_child' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_no_child' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_no_child' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_no_child' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_user_query_params' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_user_query_params' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_user_query_params' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_user_query_params' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.build_query_params_user_query_params' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.choices_id' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.choices_id' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.choices_id' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.choices_id' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.choices_id' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.find_app' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.find_app' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.find_app' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.find_app' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.find_app' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.normalize_data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.normalize_data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.normalize_data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.normalize_data' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.normalize_data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.slug' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.slug' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.slug' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.slug' to be distributed and are already explicitly excluding 'ansible_collections.netbox.netbox.tests.unit.module_utils.test_data.slug' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.scripts.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.scripts.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.scripts.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.scripts.inventory' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.scripts.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_account.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_affinitygroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_cluster.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_common.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_configuration.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_disk_offering.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_firewall.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_host.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_image_store.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_nic_secondaryip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instance_password_reset.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_instancegroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_ip_address.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.vars' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_iso.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_loadbalancer_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_acl_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_network_offering.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_physical_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_pod.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_portforward.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_project.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_region.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_resourcelimit.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_role_permission.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_router.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_securitygroup_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_service_offering.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_snapshot_policy.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_sshkeypair.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_storage_pool.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_traffic_type.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vlan_ip_range.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vmsnapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_volume.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpc_offering.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_connection.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_customer_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_vpn_gateway.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.cs_zone_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.templates' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.vars' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.integration.targets.inventory_instance.playbooks.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.cloudstack.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.cloudstack.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.cloudstack.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.cloudstack.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.cloudstack.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.tests.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.tests.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.tests.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.tests.legacy' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.tests.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.exoscale.tests.legacy.roles.test_exoscale_dns.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.meta' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_account_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_block_storage_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_domain_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_dns_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_group_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_firewall_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_network_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_os_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_baremetal_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_plan_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_region_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_baremetal.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_server_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_ssh_key_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_startup_script_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.integration.targets.vultr_user_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ngine_io.vultr.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ngine_io.vultr.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ngine_io.vultr.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ngine_io.vultr.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.ngine_io.vultr.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud.docs' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud.meta' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openstack.cloud.scripts.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openstack.cloud.scripts.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openstack.cloud.scripts.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openstack.cloud.scripts.inventory' to be distributed and are already explicitly excluding 'ansible_collections.openstack.cloud.scripts.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.docs' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.meta' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.defaults' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.meta' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tasks' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tests' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_bridge.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.defaults' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.meta' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tasks' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tests' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.openvswitch_db.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.prepare_ovs_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.prepare_ovs_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.prepare_ovs_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.prepare_ovs_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.integration.targets.prepare_ovs_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.openvswitch.openvswitch.tests.unit.modules.network.ovs.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.automation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.automation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.automation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.automation' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.automation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.examples.filters' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.examples.filters' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.examples.filters' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.examples.filters' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.examples.filters' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.licenses' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.licenses' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.licenses' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.licenses' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.licenses' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.meta' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.plugins.test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.plugins.test' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.plugins.test' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.plugins.test' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.plugins.test' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.cluster_upgrade.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.disaster_recovery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.disaster_recovery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.disaster_recovery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.disaster_recovery' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.disaster_recovery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.files' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.clean' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.clean' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.clean' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.clean' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.clean' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.recover' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.recover' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.recover' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.recover' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.disaster_recovery.tasks.recover' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.engine_setup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.engine_setup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.engine_setup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.engine_setup' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.engine_setup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.engine_setup.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.engine_setup.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.engine_setup.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.engine_setup.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.engine_setup.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.engine_setup.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.engine_setup.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.engine_setup.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.engine_setup.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.engine_setup.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.engine_setup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.engine_setup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.engine_setup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.engine_setup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.engine_setup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.engine_setup.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.engine_setup.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.engine_setup.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.engine_setup.templates' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.engine_setup.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.engine_setup.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.engine_setup.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.engine_setup.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.engine_setup.tests' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.engine_setup.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.engine_setup.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.engine_setup.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.engine_setup.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.engine_setup.vars' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.engine_setup.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.files' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_add_host' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_add_host' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_add_host' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_add_host' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_add_host' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_setup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_setup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_setup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_setup' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.after_setup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_after_engine_setup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_after_engine_setup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_after_engine_setup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_after_engine_setup' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_after_engine_setup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_before_engine_setup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_before_engine_setup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_before_engine_setup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_before_engine_setup' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.hooks.enginevm_before_engine_setup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.bootstrap_local_vm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.bootstrap_local_vm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.bootstrap_local_vm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.bootstrap_local_vm' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.bootstrap_local_vm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.create_target_vm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.create_target_vm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.create_target_vm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.create_target_vm' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.create_target_vm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.pre_checks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.pre_checks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.pre_checks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.pre_checks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.tasks.pre_checks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.templates' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.hosted_engine_setup.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.image_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.image_template' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.image_template' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.image_template' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.image_template' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.image_template.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.image_template.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.image_template.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.image_template.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.image_template.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.image_template.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.image_template.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.image_template.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.image_template.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.image_template.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.image_template.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.image_template.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.image_template.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.image_template.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.image_template.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.image_template.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.image_template.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.image_template.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.image_template.vars' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.image_template.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.examples.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.examples.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.examples.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.examples.vars' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.examples.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.aaa_jdbc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.vars' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.clusters.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenter_cleanup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.datacenters.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.external_providers.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.hosts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.mac_pools.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.networks.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.permissions.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.roles.storages.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.infra.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.infra.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.infra.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.infra.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.infra.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.remove_stale_lun.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.repositories' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.repositories' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.repositories' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.repositories' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.repositories' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.repositories.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.repositories.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.repositories.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.repositories.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.repositories.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.repositories.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.repositories.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.repositories.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.repositories.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.repositories.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.repositories.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.repositories.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.repositories.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.repositories.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.repositories.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.repositories.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.repositories.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.repositories.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.repositories.vars' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.repositories.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.shutdown_env' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.shutdown_env' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.shutdown_env' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.shutdown_env' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.shutdown_env' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.shutdown_env.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.shutdown_env.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.shutdown_env.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.shutdown_env.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.shutdown_env.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.shutdown_env.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.shutdown_env.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.shutdown_env.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.shutdown_env.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.shutdown_env.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.shutdown_env.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.shutdown_env.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.shutdown_env.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.shutdown_env.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.shutdown_env.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.vm_infra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.vm_infra' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.vm_infra' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.vm_infra' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.vm_infra' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.vm_infra.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.vm_infra.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.vm_infra.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.vm_infra.defaults' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.vm_infra.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.vm_infra.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.vm_infra.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.vm_infra.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.vm_infra.examples' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.vm_infra.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.roles.vm_infra.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.roles.vm_infra.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.roles.vm_infra.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.roles.vm_infra.tasks' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.roles.vm_infra.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.tests' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.ovirt.ovirt.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.ovirt.ovirt.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.ovirt.ovirt.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.ovirt.ovirt.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.ovirt.ovirt.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.meta' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.playbooks.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.playbooks.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.playbooks.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.playbooks.files' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.playbooks.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.playbooks.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.playbooks.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.playbooks.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.playbooks.roles' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.playbooks.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.playbooks.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.playbooks.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.playbooks.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.playbooks.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.playbooks.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.playbooks.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.playbooks.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.playbooks.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.playbooks.templates' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.playbooks.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.playbooks.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.playbooks.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.playbooks.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.playbooks.vars' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.playbooks.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.roles' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flasharray.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flasharray.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flasharray.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flasharray.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flasharray.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.meta' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.playbooks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.playbooks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.playbooks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.playbooks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.playbooks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.playbooks.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.playbooks.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.playbooks.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.playbooks.files' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.playbooks.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.playbooks.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.playbooks.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.playbooks.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.playbooks.roles' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.playbooks.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.playbooks.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.playbooks.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.playbooks.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.playbooks.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.playbooks.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.playbooks.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.playbooks.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.playbooks.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.playbooks.templates' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.playbooks.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.playbooks.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.playbooks.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.playbooks.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.playbooks.vars' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.playbooks.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.roles' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.flashblade.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.flashblade.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.flashblade.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.flashblade.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.flashblade.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.meta' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.playbooks.simple' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.playbooks.simple' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.playbooks.simple' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.playbooks.simple' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.playbooks.simple' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.playbooks.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.playbooks.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.playbooks.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.playbooks.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.playbooks.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.playbooks.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.playbooks.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.playbooks.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.playbooks.templates' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.playbooks.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.playbooks.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.playbooks.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.playbooks.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.playbooks.vars' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.playbooks.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_az.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_az.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_az.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_az.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_az.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_hap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_hap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_hap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_hap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_hap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ni.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ni.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ni.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ni.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ni.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_nig.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_nig.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_nig.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_nig.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_nig.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pg.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pg.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pg.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pg.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pg.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pp.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pp.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pp.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_pp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_region.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_region.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_region.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_region.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_region.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_sc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_sc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_sc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_sc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_sc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_se.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_se.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_se.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_se.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_se.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ss.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ss.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ss.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ss.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ss.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_tenant.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_tenant.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_tenant.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_tenant.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_tenant.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.integration.targets.fusion_ts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.unit.mocks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.unit.mocks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.unit.mocks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.unit.mocks' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.unit.mocks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.unit.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.unit.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.unit.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.unit.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.unit.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.purestorage.fusion.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.purestorage.fusion.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.purestorage.fusion.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.purestorage.fusion.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.purestorage.fusion.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docker' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docker' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docker' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docker' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docker' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs.examples.installation' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs.examples.installation' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs.examples.installation' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs.examples.installation' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs.examples.installation' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs.examples.quickstart' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs.examples.quickstart' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs.examples.quickstart' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs.examples.quickstart' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs.examples.quickstart' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs.examples.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs.examples.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs.examples.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs.examples.roles' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs.examples.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs.source' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs.source' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs.source' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs.source' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs.source' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs.source.hacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs.source.hacking' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs.source.hacking' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs.source.hacking' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs.source.hacking' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs.source.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs.source.roles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs.source.roles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs.source.roles' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs.source.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.docs.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.docs.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.docs.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.docs.templates' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.docs.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.meta' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.defaults' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.handlers' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.meta' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.tasks' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.tasks.linux' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.tasks.linux' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.tasks.linux' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.tasks.linux' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.tasks.linux' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.tasks.windows' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.tasks.windows' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.tasks.windows' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.tasks.windows' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.tasks.windows' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.templates' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.agent.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.agent.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.agent.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.agent.vars' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.agent.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.backend' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.backend' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.backend' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.backend' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.backend' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.backend.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.backend.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.backend.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.backend.defaults' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.backend.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.backend.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.backend.handlers' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.backend.handlers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.backend.handlers' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.backend.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.backend.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.backend.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.backend.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.backend.meta' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.backend.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.backend.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.backend.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.backend.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.backend.tasks' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.backend.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.backend.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.backend.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.backend.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.backend.templates' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.backend.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.backend.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.backend.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.backend.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.backend.vars' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.backend.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.defaults' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.meta' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.tasks' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.tasks.apt' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.tasks.apt' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.tasks.apt' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.tasks.apt' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.tasks.apt' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.tasks.dnf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.tasks.dnf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.tasks.dnf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.tasks.dnf' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.tasks.dnf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.tasks.msi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.tasks.msi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.tasks.msi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.tasks.msi' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.tasks.msi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.tasks.yum' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.tasks.yum' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.tasks.yum' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.tasks.yum' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.tasks.yum' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.roles.install.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.roles.install.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.roles.install.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.roles.install.vars' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.roles.install.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.action_bonsai_asset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.action_bonsai_asset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.action_bonsai_asset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.action_bonsai_asset' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.action_bonsai_asset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_authentication' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_authentication' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_authentication' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_authentication' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_authentication' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert.files' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.misc_api_cert.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ad_auth_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ad_auth_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ad_auth_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ad_auth_provider' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ad_auth_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_asset' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_asset' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_asset' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_asset' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_asset' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_check' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_check' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_check' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_check' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_check' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role_binding' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role_binding' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role_binding' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role_binding' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_cluster_role_binding' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_datastore' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_datastore' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_datastore' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_datastore' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_datastore' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_entity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_entity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_entity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_entity' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_entity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_etcd_replicator' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_etcd_replicator' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_etcd_replicator' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_etcd_replicator' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_etcd_replicator' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_event' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_event' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_event' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_event' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_event' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_filter' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_handler_set' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_handler_set' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_handler_set' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_handler_set' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_handler_set' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_hook' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_hook' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_hook' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_hook' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_hook' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ldap_auth_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ldap_auth_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ldap_auth_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ldap_auth_provider' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_ldap_auth_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_mutator' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_mutator' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_mutator' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_mutator' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_mutator' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_namespace' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_namespace' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_namespace' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_namespace' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_namespace' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_oidc_auth_provider' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_oidc_auth_provider' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_oidc_auth_provider' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_oidc_auth_provider' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_oidc_auth_provider' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_pipe_handler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_pipe_handler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_pipe_handler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_pipe_handler' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_pipe_handler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role_binding' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role_binding' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role_binding' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role_binding' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_role_binding' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secret' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secret' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secret' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secret' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secret' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_env' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_env' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_env' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_env' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_env' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault.files' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_secrets_provider_vault.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_silence' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_silence' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_silence' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_silence' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_silence' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_socket_handler' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_socket_handler' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_socket_handler' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_socket_handler' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_socket_handler' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_tessen' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_tessen' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_tessen' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_tessen' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_tessen' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_user' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.module_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_config' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_default' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured.files' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_agent_secured.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_config' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_default' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured.files' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured.files' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured.files' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_backend_secured.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_build' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_build' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_build' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_build' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_build' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_version' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_version' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_version' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_version' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_custom_version' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_deb' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_deb' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_deb' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_deb' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_deb' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_rpm' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_rpm' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_rpm' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_rpm' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_default_rpm' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_downgrade' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_downgrade' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_downgrade' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_downgrade' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.integration.molecule.role_install_downgrade' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.unit.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.unit.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.unit.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.unit.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.unit.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.unit.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.unit.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.unit.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.unit.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.unit.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.unit.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.unit.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.unit.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.unit.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.unit.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules.common' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tests.unit.plugins.modules.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.tools' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.tools' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.tools' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.tools' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.tools' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.sensu.sensu_go.vagrant.windows' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.sensu.sensu_go.vagrant.windows' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.sensu.sensu_go.vagrant.windows' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.sensu.sensu_go.vagrant.windows' to be distributed and are already explicitly excluding 'ansible_collections.sensu.sensu_go.vagrant.windows' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.docs' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.meta' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.plugins.httpapi' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.plugins.httpapi' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.plugins.httpapi' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.plugins.httpapi' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.plugins.httpapi' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.adaptive_response_notable_event.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.correlation_search_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.data_input_monitor.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.data_input_network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.data_input_network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.data_input_network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.data_input_network' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.data_input_network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.data_input_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.data_input_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.data_input_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.data_input_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.data_input_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_event.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.defaults' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.meta' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tests' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.vars' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_adaptive_response_notable_events.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_correlation_searches.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_correlation_searches.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_correlation_searches.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_correlation_searches.tests' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_correlation_searches.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.defaults' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.meta' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tests' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.vars' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_monitor.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.defaults' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.meta' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tasks' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tests' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.vars' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.integration.targets.splunk_data_inputs_network.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.unit.compat' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.unit.compat' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.unit.compat' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.unit.compat' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.unit.compat' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.unit.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.unit.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.unit.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.unit.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.unit.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.splunk.es.tests.unit.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.splunk.es.tests.unit.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.splunk.es.tests.unit.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.splunk.es.tests.unit.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.splunk.es.tests.unit.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.docs' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.examples' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.examples' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.examples' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.examples' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.examples' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.meta' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.defaults' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.meta' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.tasks' to be distributed and are already explicitly excluding 'ansible_collections.t_systems_mms.icinga_director.roles.ansible_icinga.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.meta' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.plugins.callback' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.plugins.callback' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.plugins.callback' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.plugins.callback' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.plugins.callback' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.activation_keys' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.activation_keys' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.activation_keys' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.activation_keys' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.activation_keys' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.activation_keys.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.activation_keys.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.activation_keys.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.activation_keys.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.activation_keys.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.auth_sources_ldap.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.compute_profiles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.compute_profiles' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.compute_profiles' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.compute_profiles' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.compute_profiles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.compute_profiles.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.compute_profiles.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.compute_profiles.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.compute_profiles.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.compute_profiles.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.compute_resources' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.compute_resources' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.compute_resources' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.compute_resources' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.compute_resources' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.compute_resources.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.compute_resources.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.compute_resources.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.compute_resources.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.compute_resources.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_credentials' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_credentials' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_credentials' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_credentials' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_credentials' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_credentials.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_credentials.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_credentials.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_credentials.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_credentials.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_rhel' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_rhel' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_rhel' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_rhel' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_rhel' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_rhel.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_rhel.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_rhel.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_rhel.defaults' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_rhel.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_rhel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_rhel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_rhel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_rhel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_rhel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_view_publish' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_view_publish' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_view_publish' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_view_publish' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_view_publish' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_view_publish.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_view_publish.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_view_publish.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_view_publish.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_view_publish.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_view_version_cleanup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_views' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_views' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_views' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_views' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_views' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.content_views.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.content_views.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.content_views.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.content_views.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.content_views.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.convert2rhel' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.convert2rhel' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.convert2rhel' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.convert2rhel' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.convert2rhel' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.convert2rhel.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.convert2rhel.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.convert2rhel.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.convert2rhel.defaults' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.convert2rhel.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.convert2rhel.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.convert2rhel.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.convert2rhel.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.convert2rhel.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.convert2rhel.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.domains' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.domains' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.domains' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.domains' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.domains' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.domains.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.domains.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.domains.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.domains.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.domains.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.hostgroups' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.hostgroups' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.hostgroups' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.hostgroups' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.hostgroups' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.hostgroups.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.hostgroups.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.hostgroups.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.hostgroups.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.hostgroups.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.lifecycle_environments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.lifecycle_environments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.lifecycle_environments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.lifecycle_environments' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.lifecycle_environments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.lifecycle_environments.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.lifecycle_environments.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.lifecycle_environments.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.lifecycle_environments.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.lifecycle_environments.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.manifest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.manifest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.manifest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.manifest' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.manifest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.manifest.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.manifest.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.manifest.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.manifest.defaults' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.manifest.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.manifest.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.manifest.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.manifest.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.manifest.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.manifest.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.operatingsystems' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.operatingsystems' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.operatingsystems' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.operatingsystems' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.operatingsystems' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.operatingsystems.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.operatingsystems.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.operatingsystems.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.operatingsystems.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.operatingsystems.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.organizations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.organizations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.organizations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.organizations' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.organizations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.organizations.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.organizations.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.organizations.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.organizations.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.organizations.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.provisioning_templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.provisioning_templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.provisioning_templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.provisioning_templates' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.provisioning_templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.provisioning_templates.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.provisioning_templates.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.provisioning_templates.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.provisioning_templates.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.provisioning_templates.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.repositories' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.repositories' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.repositories' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.repositories' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.repositories' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.repositories.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.repositories.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.repositories.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.repositories.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.repositories.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.settings' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.settings' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.settings' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.settings' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.settings' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.settings.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.settings.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.settings.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.settings.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.settings.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.subnets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.subnets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.subnets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.subnets' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.subnets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.subnets.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.subnets.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.subnets.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.subnets.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.subnets.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.sync_plans' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.sync_plans' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.sync_plans' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.sync_plans' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.sync_plans' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.theforeman.foreman.roles.sync_plans.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.theforeman.foreman.roles.sync_plans.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.theforeman.foreman.roles.sync_plans.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.theforeman.foreman.roles.sync_plans.tasks' to be distributed and are already explicitly excluding 'ansible_collections.theforeman.foreman.roles.sync_plans.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.docs' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.docs.docsite' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.docs.docsite' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.docs.docsite' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.docs.docsite' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.docs.docsite' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.docs.docsite.rst' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.docs.docsite.rst' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.docs.docsite.rst' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.docs.docsite.rst' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.docs.docsite.rst' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.appliance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.appliance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.appliance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.appliance' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.appliance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter_vm_customize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter_vm_customize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter_vm_customize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter_vm_customize' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.docs.docsite.rst.vmware_rest_scenarios.vcenter_vm_customize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.manual.source' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.manual.source' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.manual.source' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.manual.source' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.manual.source' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.appliance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.appliance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.appliance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.appliance' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.appliance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.vcenter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.vcenter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.vcenter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.vcenter' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.manual.source.vmware_rest_scenarios.vcenter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.meta' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.plugins.plugin_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.plugins.plugin_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.plugins.plugin_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.plugins.plugin_utils' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.plugins.plugin_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.meta' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.appliance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.prepare_lab.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.prepare_lab.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.prepare_lab.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.prepare_lab.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.prepare_lab.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.meta' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_library_and_ovf_clone.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.meta' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_clone_on_library.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.meta' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_cloning.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.meta' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_customize.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.meta' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.integration.targets.vcenter_vm_scenario1.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vmware.vmware_rest.tests.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vmware.vmware_rest.tests.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vmware.vmware_rest.tests.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vmware.vmware_rest.tests.utils' to be distributed and are already explicitly excluding 'ansible_collections.vmware.vmware_rest.tests.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.account_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.account_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.account_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.account_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.account_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.account_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.account_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.account_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.account_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.account_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.block_storage_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.cleanup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.common' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.common' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.common' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.common' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.common' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.common.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.common.default' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.common.default' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.common.default' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.common.default' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_domain_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.dns_record.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_group_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.firewall_rule_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.instance_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.os_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.os_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.os_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.os_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.os_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.os_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.os_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.os_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.os_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.os_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.plan_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.plan_metal_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.region_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.region_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.region_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.region_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.region_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.region_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.region_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.region_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.region_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.region_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.reserved_ip.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.snapshot_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.ssh_key_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.startup_script_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.user_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.meta' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.integration.targets.vpc_info.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.vultr.cloud.tests.unit.plugins.inventory.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.changelogs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.changelogs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.changelogs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.changelogs' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.changelogs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.changelogs.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.changelogs.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.changelogs.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.changelogs.fragments' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.changelogs.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.docs' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.action' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.action' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.action' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.action' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.action' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.cliconf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.cliconf' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.cliconf' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.cliconf' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.cliconf' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.doc_fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.doc_fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.doc_fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.doc_fragments' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.doc_fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.filter' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.filter' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.filter' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.filter' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.filter' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.inventory' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.inventory' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.inventory' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.inventory' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.inventory' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.facts' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_rules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_rules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_rules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_rules' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.firewall_rules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.hostname' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.argspec.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_rules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_rules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_rules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_rules' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.firewall_rules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.hostname' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.config.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_address_family' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_address_family' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_address_family' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_address_family' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_address_family' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.bgp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_rules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_rules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_rules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_rules' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.firewall_rules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.hostname' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.l3_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.l3_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.l3_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.l3_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.l3_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lag_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lag_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lag_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lag_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lag_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.legacy' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.legacy' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.legacy' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.legacy' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.legacy' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.logging_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.logging_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.logging_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.logging_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.logging_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ntp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ntp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ntp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ntp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ntp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospf_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospf_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospf_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospf_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospf_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv2' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv2' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv3' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv3' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv3' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.ospfv3' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.prefix_lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.prefix_lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.prefix_lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.prefix_lists' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.prefix_lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.route_maps' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.route_maps' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.route_maps' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.route_maps' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.route_maps' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.snmp_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.snmp_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.snmp_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.snmp_server' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.snmp_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.static_routes' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.facts.static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.rm_templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.rm_templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.rm_templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.rm_templates' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.rm_templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.utils' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.utils' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.utils' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.utils' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.module_utils.network.vyos.utils' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.plugins.terminal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.plugins.terminal' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.plugins.terminal' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.plugins.terminal' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.plugins.terminal' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.prepare_vyos_tests.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_banner.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_address_family.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_bgp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_command.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.templates' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli_config' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.cli_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_config.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_facts.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_firewall_rules.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_hostname.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_l3_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lag_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_lldp_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_logging_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ntp_global.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospf_interfaces.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv2.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_ospfv3.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_prefix_lists.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_route_maps.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_smoke.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_snmp_server.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.meta' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.redirection.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.redirection.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.redirection.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.redirection.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.tests.redirection.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.vars' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.vars' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.vars' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_static_routes.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_system.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_user.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.defaults' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.defaults' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.defaults' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tasks' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tasks' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tasks' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tests.cli' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tests.cli' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tests.cli' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tests.cli' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.integration.targets.vyos_vlan.tests.cli' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.sanity' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.sanity' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.sanity' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.sanity' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.sanity' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.unit' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.unit' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.unit' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.unit' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.unit' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.unit.mock' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.unit.mock' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.unit.mock' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.unit.mock' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.unit.mock' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.unit.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.unit.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.unit.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.unit.modules' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.unit.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.unit.modules.network' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.unit.modules.network' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.unit.modules.network' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.unit.modules.network' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.unit.modules.network' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos.fixtures' to be distributed and are already explicitly excluding 'ansible_collections.vyos.vyos.tests.unit.modules.network.vyos.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.docs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.docs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.docs' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.docs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.meta' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.meta' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.meta' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_config' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_config' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_config' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_config' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_firmwareupdate' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_firmwareupdate' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_firmwareupdate' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_firmwareupdate' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_firmwareupdate' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_hostname' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_hostname' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_hostname' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_hostname' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_hostname' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_interface' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_interface' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_interface' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_interface' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_interface' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_iptables' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_iptables' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_iptables' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_iptables' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_iptables' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_plugconfig' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_plugconfig' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_plugconfig' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_plugconfig' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_plugconfig' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_plugcontrol' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_plugcontrol' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_plugcontrol' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_plugcontrol' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_plugcontrol' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_serial_ports' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_serial_ports' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_serial_ports' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_serial_ports' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_serial_ports' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_snmp' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_snmp' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_snmp' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_snmp' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_snmp' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_status' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_status' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_status' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_status' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_status' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_syslog_client' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_syslog_client' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_syslog_client' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_syslog_client' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_syslog_client' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_syslog_server' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_syslog_server' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_syslog_server' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_syslog_server' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_syslog_server' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_time_date' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_time_date' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_time_date' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_time_date' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_time_date' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.playbooks.cpm_user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.playbooks.cpm_user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.playbooks.cpm_user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.playbooks.cpm_user' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.playbooks.cpm_user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.plugins.lookup' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.plugins.lookup' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.plugins.lookup' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.plugins.lookup' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.plugins.lookup' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'ansible_collections.wti.remote.plugins.modules' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'ansible_collections.wti.remote.plugins.modules' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'ansible_collections.wti.remote.plugins.modules' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'ansible_collections.wti.remote.plugins.modules' to be distributed and are already explicitly excluding 'ansible_collections.wti.remote.plugins.modules' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) 2023-04-28 05:57:40,033 root INFO creating build/lib/ansible_collections/amazon 2023-04-28 05:57:40,033 root INFO creating build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,033 root INFO copying ansible_collections/amazon/aws/CHANGELOG.rst -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,034 root INFO copying ansible_collections/amazon/aws/CONTRIBUTING.md -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,034 root INFO copying ansible_collections/amazon/aws/COPYING -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,035 root INFO copying ansible_collections/amazon/aws/FILES.json -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,035 root INFO copying ansible_collections/amazon/aws/MANIFEST.json -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,036 root INFO copying ansible_collections/amazon/aws/PSF-license.txt -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,036 root INFO copying ansible_collections/amazon/aws/README.md -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,036 root INFO copying ansible_collections/amazon/aws/bindep.txt -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,037 root INFO copying ansible_collections/amazon/aws/requirements.txt -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,037 root INFO copying ansible_collections/amazon/aws/test-requirements.txt -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,037 root INFO copying ansible_collections/amazon/aws/tox.ini -> build/lib/ansible_collections/amazon/aws 2023-04-28 05:57:40,037 root INFO creating build/lib/ansible_collections/amazon/aws/changelogs 2023-04-28 05:57:40,037 root INFO copying ansible_collections/amazon/aws/changelogs/changelog.yaml -> build/lib/ansible_collections/amazon/aws/changelogs 2023-04-28 05:57:40,038 root INFO copying ansible_collections/amazon/aws/changelogs/config.yaml -> build/lib/ansible_collections/amazon/aws/changelogs 2023-04-28 05:57:40,038 root INFO creating build/lib/ansible_collections/amazon/aws/changelogs/fragments 2023-04-28 05:57:40,038 root INFO copying ansible_collections/amazon/aws/changelogs/fragments/.keep -> build/lib/ansible_collections/amazon/aws/changelogs/fragments 2023-04-28 05:57:40,039 root INFO creating build/lib/ansible_collections/amazon/aws/meta 2023-04-28 05:57:40,039 root INFO copying ansible_collections/amazon/aws/meta/runtime.yml -> build/lib/ansible_collections/amazon/aws/meta 2023-04-28 05:57:40,039 root INFO creating build/lib/ansible_collections/amazon/aws/plugins 2023-04-28 05:57:40,039 root INFO creating build/lib/ansible_collections/amazon/aws/plugins/action 2023-04-28 05:57:40,039 root INFO copying ansible_collections/amazon/aws/plugins/action/s3_object.py -> build/lib/ansible_collections/amazon/aws/plugins/action 2023-04-28 05:57:40,039 root INFO creating build/lib/ansible_collections/amazon/aws/plugins/callback 2023-04-28 05:57:40,040 root INFO copying ansible_collections/amazon/aws/plugins/callback/aws_resource_actions.py -> build/lib/ansible_collections/amazon/aws/plugins/callback 2023-04-28 05:57:40,040 root INFO creating build/lib/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:40,040 root INFO copying ansible_collections/amazon/aws/plugins/doc_fragments/aws.py -> build/lib/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:40,040 root INFO copying ansible_collections/amazon/aws/plugins/doc_fragments/aws_credentials.py -> build/lib/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:40,041 root INFO copying ansible_collections/amazon/aws/plugins/doc_fragments/aws_region.py -> build/lib/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:40,041 root INFO copying ansible_collections/amazon/aws/plugins/doc_fragments/boto3.py -> build/lib/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:40,041 root INFO copying ansible_collections/amazon/aws/plugins/doc_fragments/ec2.py -> build/lib/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:40,041 root INFO copying ansible_collections/amazon/aws/plugins/doc_fragments/tags.py -> build/lib/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:40,042 root INFO creating build/lib/ansible_collections/amazon/aws/plugins/inventory 2023-04-28 05:57:40,042 root INFO copying ansible_collections/amazon/aws/plugins/inventory/aws_ec2.py -> build/lib/ansible_collections/amazon/aws/plugins/inventory 2023-04-28 05:57:40,042 root INFO copying ansible_collections/amazon/aws/plugins/inventory/aws_rds.py -> build/lib/ansible_collections/amazon/aws/plugins/inventory 2023-04-28 05:57:40,042 root INFO creating build/lib/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:40,042 root INFO copying ansible_collections/amazon/aws/plugins/lookup/aws_account_attribute.py -> build/lib/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:40,043 root INFO copying ansible_collections/amazon/aws/plugins/lookup/aws_secret.py -> build/lib/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:40,043 root INFO copying ansible_collections/amazon/aws/plugins/lookup/aws_service_ip_ranges.py -> build/lib/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:40,043 root INFO copying ansible_collections/amazon/aws/plugins/lookup/aws_ssm.py -> build/lib/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:40,044 root INFO creating build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,044 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/_version.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,044 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/acm.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,044 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/arn.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,044 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/batch.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,045 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/botocore.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,045 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/cloud.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,045 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/cloudfront_facts.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,046 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/core.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,046 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/direct_connect.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,046 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/ec2.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,046 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/elb_utils.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,046 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/elbv2.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,047 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/iam.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,047 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/modules.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,047 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/policy.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,047 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/rds.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,048 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/retries.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,048 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/route53.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,048 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/s3.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,048 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/tagging.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,049 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/tower.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,049 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/transformation.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,049 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/urls.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,049 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/version.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,049 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/waf.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,050 root INFO copying ansible_collections/amazon/aws/plugins/module_utils/waiters.py -> build/lib/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:40,050 root INFO creating build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,050 root INFO copying ansible_collections/amazon/aws/plugins/modules/autoscaling_group.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,050 root INFO copying ansible_collections/amazon/aws/plugins/modules/autoscaling_group_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,051 root INFO copying ansible_collections/amazon/aws/plugins/modules/aws_az_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,051 root INFO copying ansible_collections/amazon/aws/plugins/modules/aws_caller_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,051 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudformation.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,051 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudformation_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,052 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudtrail.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,052 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudtrail_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,052 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudwatch_metric_alarm.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,052 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudwatch_metric_alarm_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,053 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudwatchevent_rule.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,053 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,053 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,053 root INFO copying ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group_metric_filter.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,054 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_ami.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,054 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_ami_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,054 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_eip.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,054 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_eip_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,055 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_eni.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,055 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_eni_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,055 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_instance.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,055 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_instance_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,056 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_key.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,056 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_metadata_facts.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,056 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_security_group.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,057 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_security_group_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,057 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_snapshot.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,057 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_snapshot_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,057 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_spot_instance.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,058 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_spot_instance_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,058 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_tag.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,058 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_tag_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,058 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vol.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,059 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vol_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,059 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_dhcp_option.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,059 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_dhcp_option_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,059 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,059 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,060 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint_service_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,060 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_igw.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,060 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_igw_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,060 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_nat_gateway.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,061 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_nat_gateway_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,061 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_net.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,061 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_net_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,062 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_route_table.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,062 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_route_table_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,062 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_subnet.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,062 root INFO copying ansible_collections/amazon/aws/plugins/modules/ec2_vpc_subnet_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,063 root INFO copying ansible_collections/amazon/aws/plugins/modules/elb_application_lb.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,063 root INFO copying ansible_collections/amazon/aws/plugins/modules/elb_application_lb_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,063 root INFO copying ansible_collections/amazon/aws/plugins/modules/elb_classic_lb.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,063 root INFO copying ansible_collections/amazon/aws/plugins/modules/iam_policy.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,064 root INFO copying ansible_collections/amazon/aws/plugins/modules/iam_policy_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,064 root INFO copying ansible_collections/amazon/aws/plugins/modules/iam_user.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,064 root INFO copying ansible_collections/amazon/aws/plugins/modules/iam_user_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,064 root INFO copying ansible_collections/amazon/aws/plugins/modules/kms_key.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,065 root INFO copying ansible_collections/amazon/aws/plugins/modules/kms_key_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,065 root INFO copying ansible_collections/amazon/aws/plugins/modules/lambda.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,065 root INFO copying ansible_collections/amazon/aws/plugins/modules/lambda_alias.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,065 root INFO copying ansible_collections/amazon/aws/plugins/modules/lambda_event.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,066 root INFO copying ansible_collections/amazon/aws/plugins/modules/lambda_execute.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,066 root INFO copying ansible_collections/amazon/aws/plugins/modules/lambda_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,066 root INFO copying ansible_collections/amazon/aws/plugins/modules/lambda_policy.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,066 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_cluster.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,067 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_cluster_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,067 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_cluster_snapshot.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,067 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_instance.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,068 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_instance_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,068 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_instance_snapshot.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,068 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_option_group.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,068 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_option_group_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,069 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_param_group.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,069 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_snapshot_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,069 root INFO copying ansible_collections/amazon/aws/plugins/modules/rds_subnet_group.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,069 root INFO copying ansible_collections/amazon/aws/plugins/modules/route53.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,070 root INFO copying ansible_collections/amazon/aws/plugins/modules/route53_health_check.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,070 root INFO copying ansible_collections/amazon/aws/plugins/modules/route53_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,070 root INFO copying ansible_collections/amazon/aws/plugins/modules/route53_zone.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,070 root INFO copying ansible_collections/amazon/aws/plugins/modules/s3_bucket.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,071 root INFO copying ansible_collections/amazon/aws/plugins/modules/s3_object.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,071 root INFO copying ansible_collections/amazon/aws/plugins/modules/s3_object_info.py -> build/lib/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:40,071 root INFO creating build/lib/ansible_collections/ansible 2023-04-28 05:57:40,071 root INFO creating build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,072 root INFO copying ansible_collections/ansible/netcommon/CHANGELOG.rst -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,072 root INFO copying ansible_collections/ansible/netcommon/FILES.json -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,072 root INFO copying ansible_collections/ansible/netcommon/LICENSE -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,072 root INFO copying ansible_collections/ansible/netcommon/MANIFEST.json -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,073 root INFO copying ansible_collections/ansible/netcommon/README.md -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,073 root INFO copying ansible_collections/ansible/netcommon/bindep.txt -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,073 root INFO copying ansible_collections/ansible/netcommon/pyproject.toml -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,073 root INFO copying ansible_collections/ansible/netcommon/requirements.txt -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,074 root INFO copying ansible_collections/ansible/netcommon/test-requirements.txt -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,074 root INFO copying ansible_collections/ansible/netcommon/tox.ini -> build/lib/ansible_collections/ansible/netcommon 2023-04-28 05:57:40,074 root INFO creating build/lib/ansible_collections/ansible/netcommon/LICENSES 2023-04-28 05:57:40,074 root INFO copying ansible_collections/ansible/netcommon/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/ansible/netcommon/LICENSES 2023-04-28 05:57:40,074 root INFO copying ansible_collections/ansible/netcommon/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/ansible/netcommon/LICENSES 2023-04-28 05:57:40,075 root INFO creating build/lib/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:40,075 root INFO copying ansible_collections/ansible/netcommon/changelogs/CHANGELOG.rst -> build/lib/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:40,075 root INFO copying ansible_collections/ansible/netcommon/changelogs/changelog.yaml -> build/lib/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:40,075 root INFO copying ansible_collections/ansible/netcommon/changelogs/config.yaml -> build/lib/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:40,075 root INFO creating build/lib/ansible_collections/ansible/netcommon/changelogs/fragments 2023-04-28 05:57:40,076 root INFO copying ansible_collections/ansible/netcommon/changelogs/fragments/.keep -> build/lib/ansible_collections/ansible/netcommon/changelogs/fragments 2023-04-28 05:57:40,076 root INFO creating build/lib/ansible_collections/ansible/netcommon/meta 2023-04-28 05:57:40,076 root INFO copying ansible_collections/ansible/netcommon/meta/runtime.yml -> build/lib/ansible_collections/ansible/netcommon/meta 2023-04-28 05:57:40,076 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins 2023-04-28 05:57:40,076 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,076 root INFO copying ansible_collections/ansible/netcommon/plugins/action/cli_command.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,077 root INFO copying ansible_collections/ansible/netcommon/plugins/action/cli_config.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,077 root INFO copying ansible_collections/ansible/netcommon/plugins/action/grpc.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,077 root INFO copying ansible_collections/ansible/netcommon/plugins/action/net_get.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,077 root INFO copying ansible_collections/ansible/netcommon/plugins/action/net_ping.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,078 root INFO copying ansible_collections/ansible/netcommon/plugins/action/net_put.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,078 root INFO copying ansible_collections/ansible/netcommon/plugins/action/netconf.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,078 root INFO copying ansible_collections/ansible/netcommon/plugins/action/network.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,078 root INFO copying ansible_collections/ansible/netcommon/plugins/action/network_resource.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,079 root INFO copying ansible_collections/ansible/netcommon/plugins/action/telnet.py -> build/lib/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:40,079 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/become 2023-04-28 05:57:40,079 root INFO copying ansible_collections/ansible/netcommon/plugins/become/enable.py -> build/lib/ansible_collections/ansible/netcommon/plugins/become 2023-04-28 05:57:40,079 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/cache 2023-04-28 05:57:40,079 root INFO copying ansible_collections/ansible/netcommon/plugins/cache/memory.py -> build/lib/ansible_collections/ansible/netcommon/plugins/cache 2023-04-28 05:57:40,079 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:40,080 root INFO copying ansible_collections/ansible/netcommon/plugins/connection/grpc.py -> build/lib/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:40,080 root INFO copying ansible_collections/ansible/netcommon/plugins/connection/httpapi.py -> build/lib/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:40,080 root INFO copying ansible_collections/ansible/netcommon/plugins/connection/libssh.py -> build/lib/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:40,080 root INFO copying ansible_collections/ansible/netcommon/plugins/connection/netconf.py -> build/lib/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:40,081 root INFO copying ansible_collections/ansible/netcommon/plugins/connection/network_cli.py -> build/lib/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:40,081 root INFO copying ansible_collections/ansible/netcommon/plugins/connection/persistent.py -> build/lib/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:40,081 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/doc_fragments 2023-04-28 05:57:40,081 root INFO copying ansible_collections/ansible/netcommon/plugins/doc_fragments/connection_persistent.py -> build/lib/ansible_collections/ansible/netcommon/plugins/doc_fragments 2023-04-28 05:57:40,082 root INFO copying ansible_collections/ansible/netcommon/plugins/doc_fragments/network_agnostic.py -> build/lib/ansible_collections/ansible/netcommon/plugins/doc_fragments 2023-04-28 05:57:40,082 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/filter 2023-04-28 05:57:40,082 root INFO copying ansible_collections/ansible/netcommon/plugins/filter/network.py -> build/lib/ansible_collections/ansible/netcommon/plugins/filter 2023-04-28 05:57:40,082 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/httpapi 2023-04-28 05:57:40,082 root INFO copying ansible_collections/ansible/netcommon/plugins/httpapi/restconf.py -> build/lib/ansible_collections/ansible/netcommon/plugins/httpapi 2023-04-28 05:57:40,082 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils 2023-04-28 05:57:40,083 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser 2023-04-28 05:57:40,083 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/cli_parserbase.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser 2023-04-28 05:57:40,083 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/cli_parsertemplate.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser 2023-04-28 05:57:40,083 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network 2023-04-28 05:57:40,083 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,083 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/config.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,084 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/netconf.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,084 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,084 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network_template.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,084 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/parsing.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,085 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/resource_module.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,085 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/utils.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:40,085 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg 2023-04-28 05:57:40,085 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg/base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg 2023-04-28 05:57:40,085 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts 2023-04-28 05:57:40,086 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts/facts.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts 2023-04-28 05:57:40,086 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:40,086 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/network_template.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:40,086 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/resource_module.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:40,086 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/resource_module_base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:40,087 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc 2023-04-28 05:57:40,087 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc/grpc.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc 2023-04-28 05:57:40,087 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf 2023-04-28 05:57:40,087 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf/netconf.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf 2023-04-28 05:57:40,087 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf 2023-04-28 05:57:40,088 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf/restconf.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf 2023-04-28 05:57:40,088 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/utils 2023-04-28 05:57:40,088 root INFO copying ansible_collections/ansible/netcommon/plugins/module_utils/utils/data.py -> build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/utils 2023-04-28 05:57:40,088 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,088 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/cli_command.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,088 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/cli_config.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,089 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/grpc_config.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,089 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/grpc_get.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,089 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/net_get.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,089 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/net_ping.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,090 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/net_put.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,090 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/netconf_config.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,090 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/netconf_get.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,090 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/netconf_rpc.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,091 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/network_resource.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,091 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/restconf_config.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,091 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/restconf_get.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,091 root INFO copying ansible_collections/ansible/netcommon/plugins/modules/telnet.py -> build/lib/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:40,092 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/netconf 2023-04-28 05:57:40,092 root INFO copying ansible_collections/ansible/netcommon/plugins/netconf/default.py -> build/lib/ansible_collections/ansible/netcommon/plugins/netconf 2023-04-28 05:57:40,092 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:40,092 root INFO copying ansible_collections/ansible/netcommon/plugins/plugin_utils/cliconf_base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:40,092 root INFO copying ansible_collections/ansible/netcommon/plugins/plugin_utils/connection_base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:40,093 root INFO copying ansible_collections/ansible/netcommon/plugins/plugin_utils/httpapi_base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:40,093 root INFO copying ansible_collections/ansible/netcommon/plugins/plugin_utils/netconf_base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:40,093 root INFO copying ansible_collections/ansible/netcommon/plugins/plugin_utils/terminal_base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:40,093 root INFO copying ansible_collections/ansible/netcommon/plugins/plugin_utils/version.py -> build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:40,093 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins 2023-04-28 05:57:40,094 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,094 root INFO copying ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/content_templates_parser.py -> build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,094 root INFO copying ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/native_parser.py -> build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,094 root INFO copying ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/ntc_templates_parser.py -> build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,094 root INFO copying ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/pyats_parser.py -> build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,095 root INFO creating build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc 2023-04-28 05:57:40,095 root INFO copying ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc/base.py -> build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc 2023-04-28 05:57:40,095 root INFO creating build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,095 root INFO copying ansible_collections/ansible/posix/CHANGELOG.rst -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,095 root INFO copying ansible_collections/ansible/posix/COPYING -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,096 root INFO copying ansible_collections/ansible/posix/FILES.json -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,096 root INFO copying ansible_collections/ansible/posix/MANIFEST.json -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,096 root INFO copying ansible_collections/ansible/posix/PSF-license.txt -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,096 root INFO copying ansible_collections/ansible/posix/README.md -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,097 root INFO copying ansible_collections/ansible/posix/bindep.txt -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,097 root INFO copying ansible_collections/ansible/posix/codecov.yml -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,097 root INFO copying ansible_collections/ansible/posix/requirements.txt -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,097 root INFO copying ansible_collections/ansible/posix/shippable.yml -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,098 root INFO copying ansible_collections/ansible/posix/test-requirements.txt -> build/lib/ansible_collections/ansible/posix 2023-04-28 05:57:40,098 root INFO creating build/lib/ansible_collections/ansible/posix/changelogs 2023-04-28 05:57:40,098 root INFO copying ansible_collections/ansible/posix/changelogs/changelog.yaml -> build/lib/ansible_collections/ansible/posix/changelogs 2023-04-28 05:57:40,098 root INFO copying ansible_collections/ansible/posix/changelogs/config.yaml -> build/lib/ansible_collections/ansible/posix/changelogs 2023-04-28 05:57:40,098 root INFO creating build/lib/ansible_collections/ansible/posix/changelogs/fragments 2023-04-28 05:57:40,098 root INFO copying ansible_collections/ansible/posix/changelogs/fragments/.keep -> build/lib/ansible_collections/ansible/posix/changelogs/fragments 2023-04-28 05:57:40,099 root INFO creating build/lib/ansible_collections/ansible/posix/hacking 2023-04-28 05:57:40,099 root INFO copying ansible_collections/ansible/posix/hacking/cgroup_perf_recap_graph.py -> build/lib/ansible_collections/ansible/posix/hacking 2023-04-28 05:57:40,099 root INFO creating build/lib/ansible_collections/ansible/posix/meta 2023-04-28 05:57:40,099 root INFO copying ansible_collections/ansible/posix/meta/runtime.yml -> build/lib/ansible_collections/ansible/posix/meta 2023-04-28 05:57:40,099 root INFO creating build/lib/ansible_collections/ansible/posix/plugins 2023-04-28 05:57:40,099 root INFO creating build/lib/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:40,100 root INFO copying ansible_collections/ansible/posix/plugins/action/__init__.py -> build/lib/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:40,100 root INFO copying ansible_collections/ansible/posix/plugins/action/patch.py -> build/lib/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:40,100 root INFO copying ansible_collections/ansible/posix/plugins/action/synchronize.py -> build/lib/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:40,100 root INFO creating build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,100 root INFO copying ansible_collections/ansible/posix/plugins/callback/__init__.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,101 root INFO copying ansible_collections/ansible/posix/plugins/callback/cgroup_perf_recap.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,101 root INFO copying ansible_collections/ansible/posix/plugins/callback/debug.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,101 root INFO copying ansible_collections/ansible/posix/plugins/callback/json.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,101 root INFO copying ansible_collections/ansible/posix/plugins/callback/jsonl.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,102 root INFO copying ansible_collections/ansible/posix/plugins/callback/profile_roles.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,102 root INFO copying ansible_collections/ansible/posix/plugins/callback/profile_tasks.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,102 root INFO copying ansible_collections/ansible/posix/plugins/callback/skippy.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,102 root INFO copying ansible_collections/ansible/posix/plugins/callback/timer.py -> build/lib/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:40,103 root INFO creating build/lib/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:40,103 root INFO copying ansible_collections/ansible/posix/plugins/module_utils/__init__.py -> build/lib/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:40,103 root INFO copying ansible_collections/ansible/posix/plugins/module_utils/_version.py -> build/lib/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:40,103 root INFO copying ansible_collections/ansible/posix/plugins/module_utils/firewalld.py -> build/lib/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:40,103 root INFO copying ansible_collections/ansible/posix/plugins/module_utils/mount.py -> build/lib/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:40,104 root INFO copying ansible_collections/ansible/posix/plugins/module_utils/version.py -> build/lib/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:40,104 root INFO creating build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,104 root INFO copying ansible_collections/ansible/posix/plugins/modules/__init__.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,104 root INFO copying ansible_collections/ansible/posix/plugins/modules/acl.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,104 root INFO copying ansible_collections/ansible/posix/plugins/modules/at.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,105 root INFO copying ansible_collections/ansible/posix/plugins/modules/authorized_key.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,105 root INFO copying ansible_collections/ansible/posix/plugins/modules/firewalld.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,105 root INFO copying ansible_collections/ansible/posix/plugins/modules/firewalld_info.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,105 root INFO copying ansible_collections/ansible/posix/plugins/modules/mount.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,106 root INFO copying ansible_collections/ansible/posix/plugins/modules/patch.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,106 root INFO copying ansible_collections/ansible/posix/plugins/modules/rhel_facts.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,106 root INFO copying ansible_collections/ansible/posix/plugins/modules/rhel_rpm_ostree.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,106 root INFO copying ansible_collections/ansible/posix/plugins/modules/rpm_ostree_upgrade.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,107 root INFO copying ansible_collections/ansible/posix/plugins/modules/seboolean.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,107 root INFO copying ansible_collections/ansible/posix/plugins/modules/selinux.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,107 root INFO copying ansible_collections/ansible/posix/plugins/modules/synchronize.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,107 root INFO copying ansible_collections/ansible/posix/plugins/modules/sysctl.py -> build/lib/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:40,108 root INFO creating build/lib/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:40,108 root INFO copying ansible_collections/ansible/posix/plugins/shell/__init__.py -> build/lib/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:40,108 root INFO copying ansible_collections/ansible/posix/plugins/shell/csh.py -> build/lib/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:40,108 root INFO copying ansible_collections/ansible/posix/plugins/shell/fish.py -> build/lib/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:40,108 root INFO creating build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,109 root INFO copying ansible_collections/ansible/utils/CHANGELOG.rst -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,109 root INFO copying ansible_collections/ansible/utils/FILES.json -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,109 root INFO copying ansible_collections/ansible/utils/LICENSE -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,109 root INFO copying ansible_collections/ansible/utils/MANIFEST.json -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,110 root INFO copying ansible_collections/ansible/utils/README.md -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,110 root INFO copying ansible_collections/ansible/utils/bindep.txt -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,110 root INFO copying ansible_collections/ansible/utils/pyproject.toml -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,110 root INFO copying ansible_collections/ansible/utils/requirements.txt -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,111 root INFO copying ansible_collections/ansible/utils/test-requirements.txt -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,111 root INFO copying ansible_collections/ansible/utils/tox.ini -> build/lib/ansible_collections/ansible/utils 2023-04-28 05:57:40,111 root INFO creating build/lib/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:40,111 root INFO copying ansible_collections/ansible/utils/changelogs/changelog.yaml -> build/lib/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:40,111 root INFO copying ansible_collections/ansible/utils/changelogs/cli_parse_fix.yaml -> build/lib/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:40,112 root INFO copying ansible_collections/ansible/utils/changelogs/config.yaml -> build/lib/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:40,112 root INFO creating build/lib/ansible_collections/ansible/utils/changelogs/fragments 2023-04-28 05:57:40,112 root INFO copying ansible_collections/ansible/utils/changelogs/fragments/.keep -> build/lib/ansible_collections/ansible/utils/changelogs/fragments 2023-04-28 05:57:40,112 root INFO creating build/lib/ansible_collections/ansible/utils/meta 2023-04-28 05:57:40,112 root INFO copying ansible_collections/ansible/utils/meta/runtime.yml -> build/lib/ansible_collections/ansible/utils/meta 2023-04-28 05:57:40,113 root INFO creating build/lib/ansible_collections/ansible/utils/plugins 2023-04-28 05:57:40,113 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:40,113 root INFO copying ansible_collections/ansible/utils/plugins/action/cli_parse.py -> build/lib/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:40,113 root INFO copying ansible_collections/ansible/utils/plugins/action/fact_diff.py -> build/lib/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:40,113 root INFO copying ansible_collections/ansible/utils/plugins/action/update_fact.py -> build/lib/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:40,113 root INFO copying ansible_collections/ansible/utils/plugins/action/validate.py -> build/lib/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:40,114 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,114 root INFO copying ansible_collections/ansible/utils/plugins/filter/cidr_merge.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,114 root INFO copying ansible_collections/ansible/utils/plugins/filter/consolidate.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,114 root INFO copying ansible_collections/ansible/utils/plugins/filter/from_xml.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,115 root INFO copying ansible_collections/ansible/utils/plugins/filter/get_path.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,115 root INFO copying ansible_collections/ansible/utils/plugins/filter/hwaddr.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,115 root INFO copying ansible_collections/ansible/utils/plugins/filter/index_of.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,115 root INFO copying ansible_collections/ansible/utils/plugins/filter/ip4_hex.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,116 root INFO copying ansible_collections/ansible/utils/plugins/filter/ipaddr.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,116 root INFO copying ansible_collections/ansible/utils/plugins/filter/ipmath.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,116 root INFO copying ansible_collections/ansible/utils/plugins/filter/ipsubnet.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,116 root INFO copying ansible_collections/ansible/utils/plugins/filter/ipv4.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,116 root INFO copying ansible_collections/ansible/utils/plugins/filter/ipv6.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,117 root INFO copying ansible_collections/ansible/utils/plugins/filter/ipwrap.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,117 root INFO copying ansible_collections/ansible/utils/plugins/filter/keep_keys.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,117 root INFO copying ansible_collections/ansible/utils/plugins/filter/macaddr.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,117 root INFO copying ansible_collections/ansible/utils/plugins/filter/network_in_network.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,118 root INFO copying ansible_collections/ansible/utils/plugins/filter/network_in_usable.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,118 root INFO copying ansible_collections/ansible/utils/plugins/filter/next_nth_usable.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,118 root INFO copying ansible_collections/ansible/utils/plugins/filter/nthhost.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,118 root INFO copying ansible_collections/ansible/utils/plugins/filter/param_list_compare.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,119 root INFO copying ansible_collections/ansible/utils/plugins/filter/previous_nth_usable.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,119 root INFO copying ansible_collections/ansible/utils/plugins/filter/reduce_on_network.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,119 root INFO copying ansible_collections/ansible/utils/plugins/filter/remove_keys.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,119 root INFO copying ansible_collections/ansible/utils/plugins/filter/replace_keys.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,120 root INFO copying ansible_collections/ansible/utils/plugins/filter/slaac.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,120 root INFO copying ansible_collections/ansible/utils/plugins/filter/to_paths.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,120 root INFO copying ansible_collections/ansible/utils/plugins/filter/to_xml.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,120 root INFO copying ansible_collections/ansible/utils/plugins/filter/usable_range.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,120 root INFO copying ansible_collections/ansible/utils/plugins/filter/validate.py -> build/lib/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:40,121 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:40,121 root INFO copying ansible_collections/ansible/utils/plugins/lookup/get_path.py -> build/lib/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:40,121 root INFO copying ansible_collections/ansible/utils/plugins/lookup/index_of.py -> build/lib/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:40,121 root INFO copying ansible_collections/ansible/utils/plugins/lookup/to_paths.py -> build/lib/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:40,122 root INFO copying ansible_collections/ansible/utils/plugins/lookup/validate.py -> build/lib/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:40,122 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/module_utils 2023-04-28 05:57:40,122 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:40,122 root INFO copying ansible_collections/ansible/utils/plugins/module_utils/common/argspec_validate.py -> build/lib/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:40,122 root INFO copying ansible_collections/ansible/utils/plugins/module_utils/common/get_path.py -> build/lib/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:40,122 root INFO copying ansible_collections/ansible/utils/plugins/module_utils/common/to_paths.py -> build/lib/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:40,123 root INFO copying ansible_collections/ansible/utils/plugins/module_utils/common/utils.py -> build/lib/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:40,123 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:40,123 root INFO copying ansible_collections/ansible/utils/plugins/modules/cli_parse.py -> build/lib/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:40,123 root INFO copying ansible_collections/ansible/utils/plugins/modules/fact_diff.py -> build/lib/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:40,124 root INFO copying ansible_collections/ansible/utils/plugins/modules/update_fact.py -> build/lib/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:40,124 root INFO copying ansible_collections/ansible/utils/plugins/modules/validate.py -> build/lib/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:40,124 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,124 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/connection_base.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,124 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/consolidate.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,125 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/from_xml.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,125 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/index_of.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,125 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/keep_keys.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,125 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/remove_keys.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,126 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/replace_keys.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,126 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/to_xml.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:40,126 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:40,126 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/base/cli_parser.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:40,126 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/base/fact_diff.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:40,127 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/base/ipaddr_utils.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:40,127 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/base/ipaddress_utils.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:40,127 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/base/utils.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:40,127 root INFO copying ansible_collections/ansible/utils/plugins/plugin_utils/base/validate.py -> build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:40,128 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/sub_plugins 2023-04-28 05:57:40,128 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,128 root INFO copying ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/json_parser.py -> build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,128 root INFO copying ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/textfsm_parser.py -> build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,128 root INFO copying ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/ttp_parser.py -> build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,128 root INFO copying ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/xml_parser.py -> build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:40,129 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff 2023-04-28 05:57:40,129 root INFO copying ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff/native.py -> build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff 2023-04-28 05:57:40,129 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/validate 2023-04-28 05:57:40,130 root INFO copying ansible_collections/ansible/utils/plugins/sub_plugins/validate/config.py -> build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/validate 2023-04-28 05:57:40,130 root INFO copying ansible_collections/ansible/utils/plugins/sub_plugins/validate/jsonschema.py -> build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/validate 2023-04-28 05:57:40,130 root INFO creating build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,130 root INFO copying ansible_collections/ansible/utils/plugins/test/in_any_network.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,130 root INFO copying ansible_collections/ansible/utils/plugins/test/in_network.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,131 root INFO copying ansible_collections/ansible/utils/plugins/test/in_one_network.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,131 root INFO copying ansible_collections/ansible/utils/plugins/test/ip.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,131 root INFO copying ansible_collections/ansible/utils/plugins/test/ip_address.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,131 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv4.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,131 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv4_address.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,132 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv4_hostmask.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,132 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv4_netmask.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,132 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv6.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,132 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv6_address.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,133 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv6_ipv4_mapped.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,133 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv6_sixtofour.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,133 root INFO copying ansible_collections/ansible/utils/plugins/test/ipv6_teredo.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,133 root INFO copying ansible_collections/ansible/utils/plugins/test/loopback.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,133 root INFO copying ansible_collections/ansible/utils/plugins/test/mac.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,134 root INFO copying ansible_collections/ansible/utils/plugins/test/multicast.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,134 root INFO copying ansible_collections/ansible/utils/plugins/test/private.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,134 root INFO copying ansible_collections/ansible/utils/plugins/test/public.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,134 root INFO copying ansible_collections/ansible/utils/plugins/test/reserved.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,135 root INFO copying ansible_collections/ansible/utils/plugins/test/resolvable.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,135 root INFO copying ansible_collections/ansible/utils/plugins/test/subnet_of.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,135 root INFO copying ansible_collections/ansible/utils/plugins/test/supernet_of.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,135 root INFO copying ansible_collections/ansible/utils/plugins/test/unspecified.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,135 root INFO copying ansible_collections/ansible/utils/plugins/test/validate.py -> build/lib/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:40,136 root INFO creating build/lib/ansible_collections/ansible/windows 2023-04-28 05:57:40,136 root INFO copying ansible_collections/ansible/windows/CHANGELOG.rst -> build/lib/ansible_collections/ansible/windows 2023-04-28 05:57:40,136 root INFO copying ansible_collections/ansible/windows/COPYING -> build/lib/ansible_collections/ansible/windows 2023-04-28 05:57:40,136 root INFO copying ansible_collections/ansible/windows/FILES.json -> build/lib/ansible_collections/ansible/windows 2023-04-28 05:57:40,137 root INFO copying ansible_collections/ansible/windows/MANIFEST.json -> build/lib/ansible_collections/ansible/windows 2023-04-28 05:57:40,137 root INFO copying ansible_collections/ansible/windows/README.md -> build/lib/ansible_collections/ansible/windows 2023-04-28 05:57:40,137 root INFO creating build/lib/ansible_collections/ansible/windows/changelogs 2023-04-28 05:57:40,137 root INFO copying ansible_collections/ansible/windows/changelogs/changelog.yaml -> build/lib/ansible_collections/ansible/windows/changelogs 2023-04-28 05:57:40,138 root INFO copying ansible_collections/ansible/windows/changelogs/config.yaml -> build/lib/ansible_collections/ansible/windows/changelogs 2023-04-28 05:57:40,138 root INFO creating build/lib/ansible_collections/ansible/windows/changelogs/fragments 2023-04-28 05:57:40,138 root INFO copying ansible_collections/ansible/windows/changelogs/fragments/.keep -> build/lib/ansible_collections/ansible/windows/changelogs/fragments 2023-04-28 05:57:40,138 root INFO creating build/lib/ansible_collections/ansible/windows/meta 2023-04-28 05:57:40,138 root INFO copying ansible_collections/ansible/windows/meta/runtime.yml -> build/lib/ansible_collections/ansible/windows/meta 2023-04-28 05:57:40,139 root INFO creating build/lib/ansible_collections/ansible/windows/plugins 2023-04-28 05:57:40,139 root INFO creating build/lib/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:40,139 root INFO copying ansible_collections/ansible/windows/plugins/action/__init__.py -> build/lib/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:40,139 root INFO copying ansible_collections/ansible/windows/plugins/action/win_copy.py -> build/lib/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:40,139 root INFO copying ansible_collections/ansible/windows/plugins/action/win_reboot.py -> build/lib/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:40,139 root INFO copying ansible_collections/ansible/windows/plugins/action/win_template.py -> build/lib/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:40,140 root INFO copying ansible_collections/ansible/windows/plugins/action/win_updates.py -> build/lib/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:40,140 root INFO creating build/lib/ansible_collections/ansible/windows/plugins/doc_fragments 2023-04-28 05:57:40,140 root INFO copying ansible_collections/ansible/windows/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/ansible/windows/plugins/doc_fragments 2023-04-28 05:57:40,140 root INFO copying ansible_collections/ansible/windows/plugins/doc_fragments/web_request.py -> build/lib/ansible_collections/ansible/windows/plugins/doc_fragments 2023-04-28 05:57:40,141 root INFO creating build/lib/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:40,141 root INFO copying ansible_collections/ansible/windows/plugins/filter/__init__.py -> build/lib/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:40,141 root INFO copying ansible_collections/ansible/windows/plugins/filter/quote.py -> build/lib/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:40,141 root INFO copying ansible_collections/ansible/windows/plugins/filter/quote.yml -> build/lib/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:40,141 root INFO creating build/lib/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:40,142 root INFO copying ansible_collections/ansible/windows/plugins/module_utils/Process.cs -> build/lib/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:40,142 root INFO copying ansible_collections/ansible/windows/plugins/module_utils/Process.psm1 -> build/lib/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:40,142 root INFO copying ansible_collections/ansible/windows/plugins/module_utils/SCManager.cs -> build/lib/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:40,142 root INFO copying ansible_collections/ansible/windows/plugins/module_utils/WebRequest.psm1 -> build/lib/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:40,143 root INFO copying ansible_collections/ansible/windows/plugins/module_utils/__init__.py -> build/lib/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:40,143 root INFO creating build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,143 root INFO copying ansible_collections/ansible/windows/plugins/modules/__init__.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,143 root INFO copying ansible_collections/ansible/windows/plugins/modules/async_status.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,143 root INFO copying ansible_collections/ansible/windows/plugins/modules/async_status.yml -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,144 root INFO copying ansible_collections/ansible/windows/plugins/modules/setup.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,144 root INFO copying ansible_collections/ansible/windows/plugins/modules/setup.yml -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,144 root INFO copying ansible_collections/ansible/windows/plugins/modules/slurp.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,144 root INFO copying ansible_collections/ansible/windows/plugins/modules/slurp.yml -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,145 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_acl.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,145 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_acl.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,145 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_acl_inheritance.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,145 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_acl_inheritance.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,146 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_certificate_store.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,146 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_certificate_store.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,146 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_command.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,146 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_command.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,147 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_copy.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,147 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_copy.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,147 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_dns_client.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,147 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_dns_client.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,147 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_domain.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,148 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_domain.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,148 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_domain_controller.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,148 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_domain_controller.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,148 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_domain_membership.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,149 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_domain_membership.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,149 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_dsc.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,149 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_dsc.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,149 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_environment.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,150 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_environment.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,150 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_feature.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,150 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_feature.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,150 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_file.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,151 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_file.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,151 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_find.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,151 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_find.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,151 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_get_url.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,152 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_get_url.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,152 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_group.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,152 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_group.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,152 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_group_membership.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,152 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_group_membership.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,153 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_hostname.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,153 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_hostname.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,153 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_optional_feature.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,153 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_optional_feature.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,154 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_owner.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,154 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_owner.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,154 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_package.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,154 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_package.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,155 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_path.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,155 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_path.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,155 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_ping.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,155 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_ping.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,156 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_powershell.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,156 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_powershell.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,156 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_reboot.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,156 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_reg_stat.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,157 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_reg_stat.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,157 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_regedit.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,157 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_regedit.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,157 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_service.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,158 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_service.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,158 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_service_info.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,158 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_service_info.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,158 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_share.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,159 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_share.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,159 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_shell.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,159 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_shell.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,159 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_stat.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,159 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_stat.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,160 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_tempfile.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,160 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_tempfile.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,160 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_template.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,160 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_updates.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,161 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_updates.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,161 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_uri.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,161 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_uri.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,161 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_user.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,162 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_user.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,162 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_user_right.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,162 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_user_right.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,162 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_wait_for.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,163 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_wait_for.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,163 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_whoami.ps1 -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,163 root INFO copying ansible_collections/ansible/windows/plugins/modules/win_whoami.py -> build/lib/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:40,163 root INFO creating build/lib/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:40,164 root INFO copying ansible_collections/ansible/windows/plugins/plugin_utils/__init__.py -> build/lib/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:40,164 root INFO copying ansible_collections/ansible/windows/plugins/plugin_utils/_quote.py -> build/lib/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:40,164 root INFO copying ansible_collections/ansible/windows/plugins/plugin_utils/_reboot.py -> build/lib/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:40,164 root INFO creating build/lib/ansible_collections/arista 2023-04-28 05:57:40,164 root INFO creating build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,164 root INFO copying ansible_collections/arista/eos/CHANGELOG.rst -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,165 root INFO copying ansible_collections/arista/eos/FILES.json -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,165 root INFO copying ansible_collections/arista/eos/LICENSE -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,166 root INFO copying ansible_collections/arista/eos/MANIFEST.json -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,166 root INFO copying ansible_collections/arista/eos/README.md -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,166 root INFO copying ansible_collections/arista/eos/bindep.txt -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,166 root INFO copying ansible_collections/arista/eos/ignore-2.9.txt -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,167 root INFO copying ansible_collections/arista/eos/pyproject.toml -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,167 root INFO copying ansible_collections/arista/eos/requirements.txt -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,167 root INFO copying ansible_collections/arista/eos/test-requirements.txt -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,167 root INFO copying ansible_collections/arista/eos/tox.ini -> build/lib/ansible_collections/arista/eos 2023-04-28 05:57:40,168 root INFO creating build/lib/ansible_collections/arista/eos/changelogs 2023-04-28 05:57:40,168 root INFO copying ansible_collections/arista/eos/changelogs/changelog.yaml -> build/lib/ansible_collections/arista/eos/changelogs 2023-04-28 05:57:40,168 root INFO copying ansible_collections/arista/eos/changelogs/config.yaml -> build/lib/ansible_collections/arista/eos/changelogs 2023-04-28 05:57:40,168 root INFO creating build/lib/ansible_collections/arista/eos/changelogs/fragments 2023-04-28 05:57:40,168 root INFO copying ansible_collections/arista/eos/changelogs/fragments/.keep -> build/lib/ansible_collections/arista/eos/changelogs/fragments 2023-04-28 05:57:40,169 root INFO creating build/lib/ansible_collections/arista/eos/meta 2023-04-28 05:57:40,169 root INFO copying ansible_collections/arista/eos/meta/runtime.yml -> build/lib/ansible_collections/arista/eos/meta 2023-04-28 05:57:40,169 root INFO creating build/lib/ansible_collections/arista/eos/plugins 2023-04-28 05:57:40,169 root INFO creating build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,169 root INFO copying ansible_collections/arista/eos/plugins/action/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,169 root INFO copying ansible_collections/arista/eos/plugins/action/acl_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,170 root INFO copying ansible_collections/arista/eos/plugins/action/acls.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,170 root INFO copying ansible_collections/arista/eos/plugins/action/banner.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,170 root INFO copying ansible_collections/arista/eos/plugins/action/bgp.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,170 root INFO copying ansible_collections/arista/eos/plugins/action/bgp_address_family.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,171 root INFO copying ansible_collections/arista/eos/plugins/action/bgp_global.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,171 root INFO copying ansible_collections/arista/eos/plugins/action/command.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,171 root INFO copying ansible_collections/arista/eos/plugins/action/config.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,171 root INFO copying ansible_collections/arista/eos/plugins/action/eapi.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,171 root INFO copying ansible_collections/arista/eos/plugins/action/eos.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,172 root INFO copying ansible_collections/arista/eos/plugins/action/facts.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,172 root INFO copying ansible_collections/arista/eos/plugins/action/hostname.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,172 root INFO copying ansible_collections/arista/eos/plugins/action/interface.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,172 root INFO copying ansible_collections/arista/eos/plugins/action/interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,172 root INFO copying ansible_collections/arista/eos/plugins/action/l2_interface.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,173 root INFO copying ansible_collections/arista/eos/plugins/action/l2_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,173 root INFO copying ansible_collections/arista/eos/plugins/action/l3_interface.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,173 root INFO copying ansible_collections/arista/eos/plugins/action/l3_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,173 root INFO copying ansible_collections/arista/eos/plugins/action/lacp.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,174 root INFO copying ansible_collections/arista/eos/plugins/action/lacp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,174 root INFO copying ansible_collections/arista/eos/plugins/action/lag_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,174 root INFO copying ansible_collections/arista/eos/plugins/action/linkagg.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,174 root INFO copying ansible_collections/arista/eos/plugins/action/lldp.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,174 root INFO copying ansible_collections/arista/eos/plugins/action/lldp_global.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,175 root INFO copying ansible_collections/arista/eos/plugins/action/lldp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,175 root INFO copying ansible_collections/arista/eos/plugins/action/logging.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,175 root INFO copying ansible_collections/arista/eos/plugins/action/logging_global.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,175 root INFO copying ansible_collections/arista/eos/plugins/action/ntp_global.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,176 root INFO copying ansible_collections/arista/eos/plugins/action/ospf_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,176 root INFO copying ansible_collections/arista/eos/plugins/action/ospfv2.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,176 root INFO copying ansible_collections/arista/eos/plugins/action/ospfv3.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,176 root INFO copying ansible_collections/arista/eos/plugins/action/prefix_lists.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,176 root INFO copying ansible_collections/arista/eos/plugins/action/route_maps.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,177 root INFO copying ansible_collections/arista/eos/plugins/action/snmp_server.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,177 root INFO copying ansible_collections/arista/eos/plugins/action/static_route.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,177 root INFO copying ansible_collections/arista/eos/plugins/action/static_routes.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,177 root INFO copying ansible_collections/arista/eos/plugins/action/system.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,178 root INFO copying ansible_collections/arista/eos/plugins/action/user.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,178 root INFO copying ansible_collections/arista/eos/plugins/action/vlan.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,178 root INFO copying ansible_collections/arista/eos/plugins/action/vlans.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,178 root INFO copying ansible_collections/arista/eos/plugins/action/vrf.py -> build/lib/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:40,178 root INFO creating build/lib/ansible_collections/arista/eos/plugins/cliconf 2023-04-28 05:57:40,179 root INFO copying ansible_collections/arista/eos/plugins/cliconf/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/cliconf 2023-04-28 05:57:40,179 root INFO copying ansible_collections/arista/eos/plugins/cliconf/eos.py -> build/lib/ansible_collections/arista/eos/plugins/cliconf 2023-04-28 05:57:40,179 root INFO creating build/lib/ansible_collections/arista/eos/plugins/filter 2023-04-28 05:57:40,179 root INFO copying ansible_collections/arista/eos/plugins/filter/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/filter 2023-04-28 05:57:40,179 root INFO creating build/lib/ansible_collections/arista/eos/plugins/httpapi 2023-04-28 05:57:40,179 root INFO copying ansible_collections/arista/eos/plugins/httpapi/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/httpapi 2023-04-28 05:57:40,180 root INFO copying ansible_collections/arista/eos/plugins/httpapi/eos.py -> build/lib/ansible_collections/arista/eos/plugins/httpapi 2023-04-28 05:57:40,180 root INFO creating build/lib/ansible_collections/arista/eos/plugins/inventory 2023-04-28 05:57:40,180 root INFO copying ansible_collections/arista/eos/plugins/inventory/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/inventory 2023-04-28 05:57:40,180 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils 2023-04-28 05:57:40,180 root INFO copying ansible_collections/arista/eos/plugins/module_utils/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils 2023-04-28 05:57:40,181 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network 2023-04-28 05:57:40,181 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network 2023-04-28 05:57:40,181 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos 2023-04-28 05:57:40,181 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos 2023-04-28 05:57:40,181 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/eos.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos 2023-04-28 05:57:40,181 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec 2023-04-28 05:57:40,182 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec 2023-04-28 05:57:40,182 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces 2023-04-28 05:57:40,182 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces 2023-04-28 05:57:40,182 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces 2023-04-28 05:57:40,182 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls 2023-04-28 05:57:40,183 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls 2023-04-28 05:57:40,183 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/acls.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls 2023-04-28 05:57:40,183 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family 2023-04-28 05:57:40,183 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family 2023-04-28 05:57:40,183 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family 2023-04-28 05:57:40,184 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global 2023-04-28 05:57:40,184 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global 2023-04-28 05:57:40,184 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/bgp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global 2023-04-28 05:57:40,184 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts 2023-04-28 05:57:40,184 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts 2023-04-28 05:57:40,185 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/facts.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts 2023-04-28 05:57:40,185 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname 2023-04-28 05:57:40,185 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname 2023-04-28 05:57:40,185 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/hostname.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname 2023-04-28 05:57:40,185 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces 2023-04-28 05:57:40,186 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces 2023-04-28 05:57:40,186 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces 2023-04-28 05:57:40,186 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces 2023-04-28 05:57:40,186 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces 2023-04-28 05:57:40,186 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces 2023-04-28 05:57:40,187 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces 2023-04-28 05:57:40,187 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces 2023-04-28 05:57:40,187 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces 2023-04-28 05:57:40,187 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp 2023-04-28 05:57:40,187 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp 2023-04-28 05:57:40,187 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/lacp.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp 2023-04-28 05:57:40,188 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces 2023-04-28 05:57:40,188 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces 2023-04-28 05:57:40,188 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces 2023-04-28 05:57:40,188 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces 2023-04-28 05:57:40,188 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces 2023-04-28 05:57:40,189 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces 2023-04-28 05:57:40,189 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global 2023-04-28 05:57:40,189 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global 2023-04-28 05:57:40,189 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/lldp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global 2023-04-28 05:57:40,189 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces 2023-04-28 05:57:40,189 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces 2023-04-28 05:57:40,190 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces 2023-04-28 05:57:40,190 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global 2023-04-28 05:57:40,190 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global 2023-04-28 05:57:40,190 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/logging_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global 2023-04-28 05:57:40,191 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global 2023-04-28 05:57:40,191 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global 2023-04-28 05:57:40,191 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/ntp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global 2023-04-28 05:57:40,191 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces 2023-04-28 05:57:40,191 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces 2023-04-28 05:57:40,191 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces 2023-04-28 05:57:40,192 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2 2023-04-28 05:57:40,192 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2 2023-04-28 05:57:40,192 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/ospfv2.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2 2023-04-28 05:57:40,192 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3 2023-04-28 05:57:40,192 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3 2023-04-28 05:57:40,193 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/ospfv3.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3 2023-04-28 05:57:40,193 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists 2023-04-28 05:57:40,193 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists 2023-04-28 05:57:40,193 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists 2023-04-28 05:57:40,193 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps 2023-04-28 05:57:40,194 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps 2023-04-28 05:57:40,194 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/route_maps.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps 2023-04-28 05:57:40,194 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server 2023-04-28 05:57:40,194 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server 2023-04-28 05:57:40,194 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/snmp_server.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server 2023-04-28 05:57:40,195 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes 2023-04-28 05:57:40,195 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes 2023-04-28 05:57:40,195 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/static_routes.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes 2023-04-28 05:57:40,195 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans 2023-04-28 05:57:40,195 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans 2023-04-28 05:57:40,196 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/vlans.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans 2023-04-28 05:57:40,196 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config 2023-04-28 05:57:40,196 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config 2023-04-28 05:57:40,196 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces 2023-04-28 05:57:40,196 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces 2023-04-28 05:57:40,196 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces 2023-04-28 05:57:40,197 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls 2023-04-28 05:57:40,197 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls 2023-04-28 05:57:40,197 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/acls.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls 2023-04-28 05:57:40,197 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family 2023-04-28 05:57:40,198 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family 2023-04-28 05:57:40,198 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family 2023-04-28 05:57:40,198 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global 2023-04-28 05:57:40,198 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global 2023-04-28 05:57:40,198 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/bgp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global 2023-04-28 05:57:40,199 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname 2023-04-28 05:57:40,199 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname 2023-04-28 05:57:40,199 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/hostname.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname 2023-04-28 05:57:40,199 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces 2023-04-28 05:57:40,199 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces 2023-04-28 05:57:40,199 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces 2023-04-28 05:57:40,200 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces 2023-04-28 05:57:40,200 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces 2023-04-28 05:57:40,200 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces 2023-04-28 05:57:40,200 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces 2023-04-28 05:57:40,200 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces 2023-04-28 05:57:40,201 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces 2023-04-28 05:57:40,201 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp 2023-04-28 05:57:40,201 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp 2023-04-28 05:57:40,201 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/lacp.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp 2023-04-28 05:57:40,202 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces 2023-04-28 05:57:40,202 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces 2023-04-28 05:57:40,202 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces 2023-04-28 05:57:40,202 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces 2023-04-28 05:57:40,202 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces 2023-04-28 05:57:40,202 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces 2023-04-28 05:57:40,203 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global 2023-04-28 05:57:40,203 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global 2023-04-28 05:57:40,203 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/lldp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global 2023-04-28 05:57:40,203 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces 2023-04-28 05:57:40,203 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces 2023-04-28 05:57:40,204 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces 2023-04-28 05:57:40,204 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global 2023-04-28 05:57:40,204 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global 2023-04-28 05:57:40,204 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/logging_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global 2023-04-28 05:57:40,204 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global 2023-04-28 05:57:40,205 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global 2023-04-28 05:57:40,205 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/ntp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global 2023-04-28 05:57:40,205 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces 2023-04-28 05:57:40,205 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces 2023-04-28 05:57:40,205 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces 2023-04-28 05:57:40,206 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2 2023-04-28 05:57:40,206 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2 2023-04-28 05:57:40,206 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/ospfv2.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2 2023-04-28 05:57:40,206 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3 2023-04-28 05:57:40,206 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3 2023-04-28 05:57:40,207 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/ospfv3.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3 2023-04-28 05:57:40,207 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists 2023-04-28 05:57:40,207 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists 2023-04-28 05:57:40,207 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists 2023-04-28 05:57:40,207 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps 2023-04-28 05:57:40,208 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps 2023-04-28 05:57:40,208 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/route_maps.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps 2023-04-28 05:57:40,208 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server 2023-04-28 05:57:40,208 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server 2023-04-28 05:57:40,208 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/snmp_server.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server 2023-04-28 05:57:40,209 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes 2023-04-28 05:57:40,209 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes 2023-04-28 05:57:40,209 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/static_routes.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes 2023-04-28 05:57:40,209 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans 2023-04-28 05:57:40,209 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans 2023-04-28 05:57:40,210 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/vlans.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans 2023-04-28 05:57:40,210 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts 2023-04-28 05:57:40,210 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts 2023-04-28 05:57:40,210 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/facts.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts 2023-04-28 05:57:40,210 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces 2023-04-28 05:57:40,210 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces 2023-04-28 05:57:40,211 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces 2023-04-28 05:57:40,211 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls 2023-04-28 05:57:40,211 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls 2023-04-28 05:57:40,211 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/acls.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls 2023-04-28 05:57:40,211 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family 2023-04-28 05:57:40,212 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family 2023-04-28 05:57:40,212 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family 2023-04-28 05:57:40,212 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global 2023-04-28 05:57:40,212 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global 2023-04-28 05:57:40,212 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/bgp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global 2023-04-28 05:57:40,213 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname 2023-04-28 05:57:40,213 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname 2023-04-28 05:57:40,213 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/hostname.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname 2023-04-28 05:57:40,213 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces 2023-04-28 05:57:40,213 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces 2023-04-28 05:57:40,214 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces 2023-04-28 05:57:40,214 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces 2023-04-28 05:57:40,214 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces 2023-04-28 05:57:40,214 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces 2023-04-28 05:57:40,214 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces 2023-04-28 05:57:40,215 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces 2023-04-28 05:57:40,215 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces 2023-04-28 05:57:40,215 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp 2023-04-28 05:57:40,215 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp 2023-04-28 05:57:40,215 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/lacp.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp 2023-04-28 05:57:40,215 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces 2023-04-28 05:57:40,216 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces 2023-04-28 05:57:40,216 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces 2023-04-28 05:57:40,216 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces 2023-04-28 05:57:40,216 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces 2023-04-28 05:57:40,216 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces 2023-04-28 05:57:40,217 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy 2023-04-28 05:57:40,217 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy 2023-04-28 05:57:40,217 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/base.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy 2023-04-28 05:57:40,217 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global 2023-04-28 05:57:40,217 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global 2023-04-28 05:57:40,218 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/lldp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global 2023-04-28 05:57:40,218 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces 2023-04-28 05:57:40,218 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces 2023-04-28 05:57:40,218 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces 2023-04-28 05:57:40,218 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global 2023-04-28 05:57:40,218 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global 2023-04-28 05:57:40,219 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/logging_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global 2023-04-28 05:57:40,219 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global 2023-04-28 05:57:40,219 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global 2023-04-28 05:57:40,219 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/ntp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global 2023-04-28 05:57:40,219 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces 2023-04-28 05:57:40,220 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces 2023-04-28 05:57:40,220 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces 2023-04-28 05:57:40,220 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2 2023-04-28 05:57:40,220 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2 2023-04-28 05:57:40,220 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/ospfv2.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2 2023-04-28 05:57:40,221 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3 2023-04-28 05:57:40,221 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3 2023-04-28 05:57:40,221 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/ospfv3.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3 2023-04-28 05:57:40,221 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists 2023-04-28 05:57:40,221 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists 2023-04-28 05:57:40,222 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists 2023-04-28 05:57:40,222 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps 2023-04-28 05:57:40,222 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps 2023-04-28 05:57:40,222 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/route_maps.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps 2023-04-28 05:57:40,222 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server 2023-04-28 05:57:40,223 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server 2023-04-28 05:57:40,223 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/snmp_server.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server 2023-04-28 05:57:40,223 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes 2023-04-28 05:57:40,223 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes 2023-04-28 05:57:40,223 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/static_routes.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes 2023-04-28 05:57:40,224 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans 2023-04-28 05:57:40,224 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans 2023-04-28 05:57:40,224 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/vlans.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans 2023-04-28 05:57:40,224 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:40,224 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:40,225 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/module.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:40,225 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/providers.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:40,225 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli 2023-04-28 05:57:40,225 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli 2023-04-28 05:57:40,225 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config 2023-04-28 05:57:40,225 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config 2023-04-28 05:57:40,226 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:40,226 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:40,226 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/address_family.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:40,226 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/neighbors.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:40,226 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/process.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:40,227 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,227 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,227 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/bgp_address_family.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,227 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/bgp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,228 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/hostname.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,228 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/logging_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,228 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ntp_global.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,228 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ospf_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,229 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ospfv3.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,229 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/prefix_lists.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,229 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/route_maps.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,230 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/snmp_server.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:40,230 root INFO creating build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils 2023-04-28 05:57:40,230 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils 2023-04-28 05:57:40,230 root INFO copying ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/utils.py -> build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils 2023-04-28 05:57:40,230 root INFO creating build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,231 root INFO copying ansible_collections/arista/eos/plugins/modules/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,231 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_acl_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,231 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_acls.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,231 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_banner.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,232 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_bgp.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,232 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_bgp_address_family.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,232 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_bgp_global.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,232 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_command.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,233 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_config.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,233 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_eapi.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,233 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_facts.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,233 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_hostname.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,234 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,234 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_l2_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,234 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_l3_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,234 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_lacp.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,235 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_lacp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,235 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_lag_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,235 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_lldp.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,235 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_lldp_global.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,235 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_lldp_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,236 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_logging.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,236 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_logging_global.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,236 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_ntp_global.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,237 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_ospf_interfaces.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,237 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_ospfv2.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,237 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_ospfv3.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,237 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_prefix_lists.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,238 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_route_maps.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,238 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_snmp_server.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,238 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_static_routes.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,239 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_system.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,239 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_user.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,239 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_vlans.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,239 root INFO copying ansible_collections/arista/eos/plugins/modules/eos_vrf.py -> build/lib/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:40,240 root INFO creating build/lib/ansible_collections/arista/eos/plugins/terminal 2023-04-28 05:57:40,240 root INFO copying ansible_collections/arista/eos/plugins/terminal/__init__.py -> build/lib/ansible_collections/arista/eos/plugins/terminal 2023-04-28 05:57:40,240 root INFO copying ansible_collections/arista/eos/plugins/terminal/eos.py -> build/lib/ansible_collections/arista/eos/plugins/terminal 2023-04-28 05:57:40,240 root INFO creating build/lib/ansible_collections/awx 2023-04-28 05:57:40,240 root INFO creating build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,240 root INFO copying ansible_collections/awx/awx/COPYING -> build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,241 root INFO copying ansible_collections/awx/awx/FILES.json -> build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,241 root INFO copying ansible_collections/awx/awx/MANIFEST.json -> build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,241 root INFO copying ansible_collections/awx/awx/README.md -> build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,241 root INFO copying ansible_collections/awx/awx/TESTING.md -> build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,242 root INFO copying ansible_collections/awx/awx/bindep.txt -> build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,242 root INFO copying ansible_collections/awx/awx/requirements.txt -> build/lib/ansible_collections/awx/awx 2023-04-28 05:57:40,242 root INFO creating build/lib/ansible_collections/awx/awx/images 2023-04-28 05:57:40,242 root INFO copying ansible_collections/awx/awx/images/completeness_test_output.png -> build/lib/ansible_collections/awx/awx/images 2023-04-28 05:57:40,243 root INFO creating build/lib/ansible_collections/awx/awx/meta 2023-04-28 05:57:40,243 root INFO copying ansible_collections/awx/awx/meta/runtime.yml -> build/lib/ansible_collections/awx/awx/meta 2023-04-28 05:57:40,243 root INFO creating build/lib/ansible_collections/awx/awx/plugins 2023-04-28 05:57:40,244 root INFO creating build/lib/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:40,244 root INFO copying ansible_collections/awx/awx/plugins/doc_fragments/auth.py -> build/lib/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:40,244 root INFO copying ansible_collections/awx/awx/plugins/doc_fragments/auth_legacy.py -> build/lib/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:40,244 root INFO copying ansible_collections/awx/awx/plugins/doc_fragments/auth_plugin.py -> build/lib/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:40,244 root INFO creating build/lib/ansible_collections/awx/awx/plugins/inventory 2023-04-28 05:57:40,244 root INFO copying ansible_collections/awx/awx/plugins/inventory/controller.py -> build/lib/ansible_collections/awx/awx/plugins/inventory 2023-04-28 05:57:40,245 root INFO creating build/lib/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:40,245 root INFO copying ansible_collections/awx/awx/plugins/lookup/controller_api.py -> build/lib/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:40,245 root INFO copying ansible_collections/awx/awx/plugins/lookup/schedule_rrule.py -> build/lib/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:40,245 root INFO copying ansible_collections/awx/awx/plugins/lookup/schedule_rruleset.py -> build/lib/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:40,246 root INFO creating build/lib/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:40,246 root INFO copying ansible_collections/awx/awx/plugins/module_utils/awxkit.py -> build/lib/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:40,246 root INFO copying ansible_collections/awx/awx/plugins/module_utils/controller_api.py -> build/lib/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:40,246 root INFO copying ansible_collections/awx/awx/plugins/module_utils/tower_legacy.py -> build/lib/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:40,246 root INFO creating build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,247 root INFO copying ansible_collections/awx/awx/plugins/modules/__init__.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,247 root INFO copying ansible_collections/awx/awx/plugins/modules/ad_hoc_command.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,247 root INFO copying ansible_collections/awx/awx/plugins/modules/ad_hoc_command_cancel.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,247 root INFO copying ansible_collections/awx/awx/plugins/modules/ad_hoc_command_wait.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,247 root INFO copying ansible_collections/awx/awx/plugins/modules/application.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,248 root INFO copying ansible_collections/awx/awx/plugins/modules/bulk_host_create.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,248 root INFO copying ansible_collections/awx/awx/plugins/modules/bulk_job_launch.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,248 root INFO copying ansible_collections/awx/awx/plugins/modules/controller_meta.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,248 root INFO copying ansible_collections/awx/awx/plugins/modules/credential.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,249 root INFO copying ansible_collections/awx/awx/plugins/modules/credential_input_source.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,249 root INFO copying ansible_collections/awx/awx/plugins/modules/credential_type.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,249 root INFO copying ansible_collections/awx/awx/plugins/modules/execution_environment.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,249 root INFO copying ansible_collections/awx/awx/plugins/modules/export.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,249 root INFO copying ansible_collections/awx/awx/plugins/modules/group.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,250 root INFO copying ansible_collections/awx/awx/plugins/modules/host.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,250 root INFO copying ansible_collections/awx/awx/plugins/modules/import.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,250 root INFO copying ansible_collections/awx/awx/plugins/modules/instance.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,250 root INFO copying ansible_collections/awx/awx/plugins/modules/instance_group.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,251 root INFO copying ansible_collections/awx/awx/plugins/modules/inventory.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,251 root INFO copying ansible_collections/awx/awx/plugins/modules/inventory_source.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,251 root INFO copying ansible_collections/awx/awx/plugins/modules/inventory_source_update.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,251 root INFO copying ansible_collections/awx/awx/plugins/modules/job_cancel.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,252 root INFO copying ansible_collections/awx/awx/plugins/modules/job_launch.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,252 root INFO copying ansible_collections/awx/awx/plugins/modules/job_list.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,252 root INFO copying ansible_collections/awx/awx/plugins/modules/job_template.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,252 root INFO copying ansible_collections/awx/awx/plugins/modules/job_wait.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,252 root INFO copying ansible_collections/awx/awx/plugins/modules/label.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,253 root INFO copying ansible_collections/awx/awx/plugins/modules/license.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,253 root INFO copying ansible_collections/awx/awx/plugins/modules/notification_template.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,253 root INFO copying ansible_collections/awx/awx/plugins/modules/organization.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,253 root INFO copying ansible_collections/awx/awx/plugins/modules/project.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,254 root INFO copying ansible_collections/awx/awx/plugins/modules/project_update.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,254 root INFO copying ansible_collections/awx/awx/plugins/modules/role.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,254 root INFO copying ansible_collections/awx/awx/plugins/modules/schedule.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,255 root INFO copying ansible_collections/awx/awx/plugins/modules/settings.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,255 root INFO copying ansible_collections/awx/awx/plugins/modules/subscriptions.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,255 root INFO copying ansible_collections/awx/awx/plugins/modules/team.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,255 root INFO copying ansible_collections/awx/awx/plugins/modules/token.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,256 root INFO copying ansible_collections/awx/awx/plugins/modules/user.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,256 root INFO copying ansible_collections/awx/awx/plugins/modules/workflow_approval.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,256 root INFO copying ansible_collections/awx/awx/plugins/modules/workflow_job_template.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,256 root INFO copying ansible_collections/awx/awx/plugins/modules/workflow_job_template_node.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,257 root INFO copying ansible_collections/awx/awx/plugins/modules/workflow_launch.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,257 root INFO copying ansible_collections/awx/awx/plugins/modules/workflow_node_wait.py -> build/lib/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:40,257 root INFO creating build/lib/ansible_collections/awx/awx/test 2023-04-28 05:57:40,257 root INFO creating build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,257 root INFO copying ansible_collections/awx/awx/test/awx/conftest.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,258 root INFO copying ansible_collections/awx/awx/test/awx/test_ad_hoc_wait.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,258 root INFO copying ansible_collections/awx/awx/test/awx/test_application.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,258 root INFO copying ansible_collections/awx/awx/test/awx/test_bulk.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,258 root INFO copying ansible_collections/awx/awx/test/awx/test_completeness.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,259 root INFO copying ansible_collections/awx/awx/test/awx/test_credential.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,259 root INFO copying ansible_collections/awx/awx/test/awx/test_credential_input_source.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,259 root INFO copying ansible_collections/awx/awx/test/awx/test_credential_type.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,259 root INFO copying ansible_collections/awx/awx/test/awx/test_group.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,259 root INFO copying ansible_collections/awx/awx/test/awx/test_instance_group.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,260 root INFO copying ansible_collections/awx/awx/test/awx/test_inventory.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,260 root INFO copying ansible_collections/awx/awx/test/awx/test_inventory_source.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,260 root INFO copying ansible_collections/awx/awx/test/awx/test_job.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,260 root INFO copying ansible_collections/awx/awx/test/awx/test_job_template.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,261 root INFO copying ansible_collections/awx/awx/test/awx/test_label.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,261 root INFO copying ansible_collections/awx/awx/test/awx/test_module_utils.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,261 root INFO copying ansible_collections/awx/awx/test/awx/test_notification_template.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,261 root INFO copying ansible_collections/awx/awx/test/awx/test_organization.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,261 root INFO copying ansible_collections/awx/awx/test/awx/test_project.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,262 root INFO copying ansible_collections/awx/awx/test/awx/test_role.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,262 root INFO copying ansible_collections/awx/awx/test/awx/test_schedule.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,262 root INFO copying ansible_collections/awx/awx/test/awx/test_settings.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,262 root INFO copying ansible_collections/awx/awx/test/awx/test_team.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,263 root INFO copying ansible_collections/awx/awx/test/awx/test_token.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,263 root INFO copying ansible_collections/awx/awx/test/awx/test_user.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,263 root INFO copying ansible_collections/awx/awx/test/awx/test_workflow_job_template.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,263 root INFO copying ansible_collections/awx/awx/test/awx/test_workflow_job_template_node.py -> build/lib/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:40,263 root INFO creating build/lib/ansible_collections/azure 2023-04-28 05:57:40,264 root INFO creating build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,264 root INFO copying ansible_collections/azure/azcollection/CHANGELOG.md -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,264 root INFO copying ansible_collections/azure/azcollection/CONTRIBUTING.md -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,264 root INFO copying ansible_collections/azure/azcollection/CredScanSuppressions.json -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,264 root INFO copying ansible_collections/azure/azcollection/FILES.json -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,265 root INFO copying ansible_collections/azure/azcollection/LICENSE -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,265 root INFO copying ansible_collections/azure/azcollection/MANIFEST.json -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,266 root INFO copying ansible_collections/azure/azcollection/README.md -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,266 root INFO copying ansible_collections/azure/azcollection/ansible.cfg -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,266 root INFO copying ansible_collections/azure/azcollection/azure-pipelines.yml -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,266 root INFO copying ansible_collections/azure/azcollection/pr-pipelines.yml -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,267 root INFO copying ansible_collections/azure/azcollection/release-pipelines.yml -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,267 root INFO copying ansible_collections/azure/azcollection/requirements-azure.txt -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,267 root INFO copying ansible_collections/azure/azcollection/sanity-requirements-azure.txt -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,267 root INFO copying ansible_collections/azure/azcollection/shippable.yml -> build/lib/ansible_collections/azure/azcollection 2023-04-28 05:57:40,267 root INFO creating build/lib/ansible_collections/azure/azcollection/meta 2023-04-28 05:57:40,268 root INFO copying ansible_collections/azure/azcollection/meta/execution-environment.yml -> build/lib/ansible_collections/azure/azcollection/meta 2023-04-28 05:57:40,268 root INFO copying ansible_collections/azure/azcollection/meta/runtime.yml -> build/lib/ansible_collections/azure/azcollection/meta 2023-04-28 05:57:40,268 root INFO creating build/lib/ansible_collections/azure/azcollection/plugins 2023-04-28 05:57:40,268 root INFO creating build/lib/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:40,268 root INFO copying ansible_collections/azure/azcollection/plugins/doc_fragments/azure.py -> build/lib/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:40,268 root INFO copying ansible_collections/azure/azcollection/plugins/doc_fragments/azure_rm.py -> build/lib/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:40,269 root INFO copying ansible_collections/azure/azcollection/plugins/doc_fragments/azure_tags.py -> build/lib/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:40,269 root INFO creating build/lib/ansible_collections/azure/azcollection/plugins/inventory 2023-04-28 05:57:40,269 root INFO copying ansible_collections/azure/azcollection/plugins/inventory/azure_rm.py -> build/lib/ansible_collections/azure/azcollection/plugins/inventory 2023-04-28 05:57:40,269 root INFO creating build/lib/ansible_collections/azure/azcollection/plugins/lookup 2023-04-28 05:57:40,269 root INFO copying ansible_collections/azure/azcollection/plugins/lookup/azure_keyvault_secret.py -> build/lib/ansible_collections/azure/azcollection/plugins/lookup 2023-04-28 05:57:40,270 root INFO creating build/lib/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:40,270 root INFO copying ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common.py -> build/lib/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:40,270 root INFO copying ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common_ext.py -> build/lib/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:40,270 root INFO copying ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common_rest.py -> build/lib/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:40,271 root INFO creating build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,271 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_account_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,271 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adapplication.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,271 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adapplication_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,271 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adgroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,272 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adgroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,272 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adpassword.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,272 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adpassword_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,272 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adserviceprincipal.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,273 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_adserviceprincipal_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,273 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aduser.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,273 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aduser_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,273 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aks.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,274 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aks_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,274 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpool.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,274 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpool_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,274 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpoolversion_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,275 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksupgrade_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,275 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksversion_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,275 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagement.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,275 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagement_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,276 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagementservice.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,276 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagementservice_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,276 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_appgateway.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,276 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_appgateway_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,277 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_applicationsecuritygroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,277 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_applicationsecuritygroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,277 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_appserviceplan.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,277 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_appserviceplan_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,278 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationaccount.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,278 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationaccount_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,278 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationrunbook.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,278 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationrunbook_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,279 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_autoscale.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,279 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_autoscale_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,279 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_availabilityset.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,279 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_availabilityset_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,280 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_azurefirewall.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,280 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_azurefirewall_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,280 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_backupazurevm.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,280 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_backupazurevm_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,281 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_backuppolicy.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,281 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_backuppolicy_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,281 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_bastionhost.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,281 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_bastionhost_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,282 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_batchaccount.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,282 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnendpoint.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,282 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnendpoint_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,282 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnprofile.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,283 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnprofile_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,283 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cognitivesearch.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,283 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cognitivesearch_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,283 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerinstance.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,284 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerinstance_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,284 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistry.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,284 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistry_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,284 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistryreplication.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,285 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistryreplication_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,285 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrytag.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,285 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrytag_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,285 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrywebhook.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,286 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrywebhook_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,286 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cosmosdbaccount.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,286 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_cosmosdbaccount_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,286 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_datafactory.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,287 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_datafactory_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,287 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_datalakestore.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,287 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_datalakestore_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,287 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_ddosprotectionplan.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,288 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_ddosprotectionplan_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,288 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_deployment.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,288 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_deployment_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,288 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlab.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,289 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlab_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,289 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabarmtemplate_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,289 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifact_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,289 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifactsource.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,290 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifactsource_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,290 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabcustomimage.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,290 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabcustomimage_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,290 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabenvironment.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,291 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabenvironment_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,291 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabpolicy.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,291 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabpolicy_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,291 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabschedule.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,291 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabschedule_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,292 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualmachine.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,292 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualmachine_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,292 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualnetwork.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,292 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualnetwork_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,293 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_diskencryptionset.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,293 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_diskencryptionset_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,293 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnsrecordset.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,293 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnsrecordset_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,294 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnszone.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,294 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnszone_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,294 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_eventhub.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,294 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_eventhub_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,295 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_expressroute.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,295 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_expressroute_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,295 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_firewallpolicy.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,295 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_firewallpolicy_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,296 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_functionapp.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,296 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_functionapp_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,296 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_gallery.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,296 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_gallery_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,297 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimage.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,297 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimage_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,297 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimageversion.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,297 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimageversion_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,298 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_hdinsightcluster.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,298 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_hdinsightcluster_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,298 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_hostgroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,298 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_hostgroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,299 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_image.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,299 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_image_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,299 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevice.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,299 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevice_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,300 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevicemodule.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,300 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothub.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,300 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothub_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,301 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothubconsumergroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,301 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_ipgroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,301 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_ipgroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,301 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvault.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,301 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvault_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,302 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultkey.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,302 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultkey_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,302 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultsecret.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,302 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultsecret_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,303 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_loadbalancer.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,303 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_loadbalancer_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,303 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_lock.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,303 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_lock_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,304 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_loganalyticsworkspace.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,304 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_loganalyticsworkspace_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,304 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_manageddisk.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,304 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_manageddisk_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,305 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_managementgroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,305 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_managementgroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,305 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbconfiguration.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,305 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbconfiguration_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,306 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbdatabase.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,306 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbdatabase_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,306 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbfirewallrule.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,306 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbfirewallrule_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,307 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbserver.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,307 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbserver_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,307 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitordiagnosticsetting.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,307 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitordiagnosticsetting_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,308 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitorlogprofile.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,308 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_multiplemanageddisks.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,308 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlconfiguration.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,308 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlconfiguration_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,309 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqldatabase.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,309 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqldatabase_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,309 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlfirewallrule.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,309 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlfirewallrule_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,310 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlserver.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,310 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlserver_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,310 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_natgateway.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,310 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_natgateway_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,311 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_networkinterface.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,311 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_networkinterface_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,311 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_notificationhub.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,311 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_notificationhub_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,312 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_openshiftmanagedcluster.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,312 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_openshiftmanagedcluster_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,312 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlconfiguration.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,312 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlconfiguration_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,313 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqldatabase.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,313 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqldatabase_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,313 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlfirewallrule.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,313 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlfirewallrule_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,314 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlserver.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,314 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlserver_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,314 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednsrecordset.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,314 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednsrecordset_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,315 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszone.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,315 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszone_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,315 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszonelink.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,315 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszonelink_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,316 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpoint.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,316 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpoint_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,316 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointconnection.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,316 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointconnection_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,317 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointdnszonegroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,317 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointdnszonegroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,317 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatelinkservice.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,317 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatelinkservice_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,318 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_proximityplacementgroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,318 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_proximityplacementgroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,318 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_publicipaddress.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,318 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_publicipaddress_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,319 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_recoveryservicesvault.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,319 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_recoveryservicesvault_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,319 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscache.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,319 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscache_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,320 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscachefirewallrule.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,320 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationassignment.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,320 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationassignment_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,320 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationdefinition.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,321 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationdefinition_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,321 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_resource.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,321 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_resource_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,321 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_resourcegroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,322 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_resourcegroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,322 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_roleassignment.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,322 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_roleassignment_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,322 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_roledefinition.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,323 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_roledefinition_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,323 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_route.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,323 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_route_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,323 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_routetable.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,324 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_routetable_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,324 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_securitygroup.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,324 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_securitygroup_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,324 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebus.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,325 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebus_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,325 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebusqueue.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,325 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebussaspolicy.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,325 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebustopic.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,326 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebustopicsubscription.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,326 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_snapshot.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,326 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqldatabase.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,326 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqldatabase_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,327 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlelasticpool.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,327 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlelasticpool_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,327 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlfirewallrule.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,327 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlfirewallrule_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,328 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlmanagedinstance.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,328 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlmanagedinstance_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,328 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlserver.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,328 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlserver_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,329 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageaccount.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,329 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageaccount_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,329 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageblob.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,329 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageshare.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,330 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageshare_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,330 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_subnet.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,330 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_subnet_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,331 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_subscription_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,331 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanager.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,331 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerendpoint.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,331 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerendpoint_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,332 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerprofile.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,332 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerprofile_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,332 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhub.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,332 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhub_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,333 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhubconnection.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,333 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhubconnection_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,333 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachine.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,334 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachine_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,334 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineextension.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,334 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineextension_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,334 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineimage_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,335 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescaleset.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,335 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescaleset_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,335 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetextension.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,335 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetextension_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,336 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetinstance.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,336 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetinstance_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,336 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinesize_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,336 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,337 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,337 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkgateway.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,337 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkpeering.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,337 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkpeering_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,338 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualwan.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,338 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualwan_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,338 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_vmbackuppolicy.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,338 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_vmbackuppolicy_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,339 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsite.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,339 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsite_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,339 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsitelink_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,339 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_webapp.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,340 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_webapp_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,340 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappaccessrestriction.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,340 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappaccessrestriction_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,340 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappslot.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,341 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappvnetconnection.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,341 root INFO copying ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappvnetconnection_info.py -> build/lib/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:40,341 root INFO creating build/lib/ansible_collections/check_point 2023-04-28 05:57:40,341 root INFO creating build/lib/ansible_collections/check_point/mgmt 2023-04-28 05:57:40,341 root INFO copying ansible_collections/check_point/mgmt/CHANGELOG.rst -> build/lib/ansible_collections/check_point/mgmt 2023-04-28 05:57:40,342 root INFO copying ansible_collections/check_point/mgmt/FILES.json -> build/lib/ansible_collections/check_point/mgmt 2023-04-28 05:57:40,342 root INFO copying ansible_collections/check_point/mgmt/MANIFEST.json -> build/lib/ansible_collections/check_point/mgmt 2023-04-28 05:57:40,342 root INFO copying ansible_collections/check_point/mgmt/README.md -> build/lib/ansible_collections/check_point/mgmt 2023-04-28 05:57:40,342 root INFO creating build/lib/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:40,342 root INFO copying ansible_collections/check_point/mgmt/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:40,343 root INFO copying ansible_collections/check_point/mgmt/changelogs/changelog.yaml -> build/lib/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:40,343 root INFO copying ansible_collections/check_point/mgmt/changelogs/config.yaml -> build/lib/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:40,343 root INFO creating build/lib/ansible_collections/check_point/mgmt/meta 2023-04-28 05:57:40,343 root INFO copying ansible_collections/check_point/mgmt/meta/execution-environment.yml -> build/lib/ansible_collections/check_point/mgmt/meta 2023-04-28 05:57:40,344 root INFO copying ansible_collections/check_point/mgmt/meta/runtime.yml -> build/lib/ansible_collections/check_point/mgmt/meta 2023-04-28 05:57:40,344 root INFO creating build/lib/ansible_collections/check_point/mgmt/plugins 2023-04-28 05:57:40,344 root INFO creating build/lib/ansible_collections/check_point/mgmt/plugins/action 2023-04-28 05:57:40,344 root INFO copying ansible_collections/check_point/mgmt/plugins/action/cp_mgmt_access_rules.py -> build/lib/ansible_collections/check_point/mgmt/plugins/action 2023-04-28 05:57:40,344 root INFO creating build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:40,344 root INFO copying ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_commands.py -> build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:40,345 root INFO copying ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:40,345 root INFO copying ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_objects.py -> build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:40,345 root INFO copying ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_objects_action_module.py -> build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:40,345 root INFO creating build/lib/ansible_collections/check_point/mgmt/plugins/httpapi 2023-04-28 05:57:40,345 root INFO copying ansible_collections/check_point/mgmt/plugins/httpapi/checkpoint.py -> build/lib/ansible_collections/check_point/mgmt/plugins/httpapi 2023-04-28 05:57:40,346 root INFO creating build/lib/ansible_collections/check_point/mgmt/plugins/module_utils 2023-04-28 05:57:40,346 root INFO copying ansible_collections/check_point/mgmt/plugins/module_utils/checkpoint.py -> build/lib/ansible_collections/check_point/mgmt/plugins/module_utils 2023-04-28 05:57:40,346 root INFO creating build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,346 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_layer.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,346 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_layer_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,347 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_role.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,347 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_role_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,347 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rule.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,347 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rule_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,348 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rules.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,348 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_section.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,348 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_api_key.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,348 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_data_center_object.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,348 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_domain.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,349 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_nat_rule.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,349 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_rules_batch.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,349 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_address_range.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,349 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_address_range_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,350 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_administrator.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,350 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_administrator_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,350 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,350 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_category.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,350 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_category_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,351 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,351 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_group.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,351 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_group_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,351 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_approve_session.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,352 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_assign_global_assignment.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,352 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_check_network_feed.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,352 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_check_threat_ioc_feed.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,352 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_cluster_members_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,352 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_connect_cloud_services.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,353 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_data_center_object_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,353 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_api_key.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,353 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_data_center_object.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,353 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_domain.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,354 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_nat_rule.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,354 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_rules_batch.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,354 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_discard.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,354 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_disconnect_cloud_services.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,355 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dns_domain.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,355 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dns_domain_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,355 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,355 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_permissions_profile.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,355 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_permissions_profile_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,356 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dynamic_object.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,356 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dynamic_object_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,356 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_exception_group.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,356 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_exception_group_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,357 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_get_platform.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,357 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_global_assignment.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,357 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_global_assignment_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,357 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,358 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,358 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_with_exclusion.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,358 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_with_exclusion_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,358 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_host.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,358 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_host_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,359 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_https_section.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,359 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_identity_tag.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,359 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_identity_tag_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,359 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_administrator_group.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,360 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_administrator_group_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,360 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_to_domain_assignment_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,360 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_database.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,360 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_lsm_policy.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,360 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_lsm_settings.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,361 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_policy.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,361 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_software_package.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,361 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_interoperable_device.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,361 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_interoperable_device_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,362 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,362 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,362 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster_profile_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,362 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,363 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,363 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway_profile_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,363 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_run_script.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,363 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_md_permissions_profile.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,364 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_md_permissions_profile_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,364 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_mds.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,364 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_mds_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,364 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_multicast_address_range.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,364 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_multicast_address_range_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,365 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_nat_rule_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,365 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_nat_section.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,365 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,365 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,366 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_feed.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,366 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_feed_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,366 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_objects_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,366 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_package.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,367 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_package_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,367 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_provisioning_profile_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,367 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_publish.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,367 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_put_file.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,367 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_reject_session.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,368 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_repository_script.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,368 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_repository_script_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,368 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_reset_sic.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,368 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_run_ips_update.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,369 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_run_script.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,369 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_security_zone.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,369 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_security_zone_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,369 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_dce_rpc.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,369 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_dce_rpc_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,370 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_group.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,370 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_group_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,370 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,370 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp6.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,371 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp6_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,371 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,371 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_other.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,371 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_other_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,372 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_rpc.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,372 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_rpc_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,372 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_sctp.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,372 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_sctp_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,373 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_tcp.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,373 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_tcp_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,373 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_udp.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,373 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_udp_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,374 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_session_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,374 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_domain.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,374 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_global_properties.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,374 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_idp_default_assignment.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,375 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_idp_to_domain_assignment.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,375 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_nat_rule.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,375 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_session.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,375 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_threat_advanced_settings.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,376 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_access_section.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,376 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_cloud_services.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,376 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_global_properties.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,376 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_https_section.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,376 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_idp_default_assignment.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,377 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_logs.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,377 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_nat_section.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,377 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_servers_and_processes.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,377 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_software_package_details.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,378 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_task.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,378 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_tasks.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,378 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_threat_advanced_settings.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,378 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_cluster.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,379 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_cluster_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,379 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_gateway.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,379 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_gateway_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,380 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_smtp_server.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,380 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_smtp_server_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,380 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_submit_session.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,380 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_tag.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,381 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_tag_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,381 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_test_sic_status.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,381 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_exception.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,381 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_exception_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,381 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_indicator.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,382 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_indicator_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,382 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_layer.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,382 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_layer_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,382 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_profile.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,383 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_profile_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,383 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_protection_override.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,383 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_rule.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,383 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_rule_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,384 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_time.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,384 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_time_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,384 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_trusted_client.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,384 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_trusted_client_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,385 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_uninstall_software_package.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,385 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_update_provisioned_satellites.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,385 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_verify_policy.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,385 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_verify_software_package.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,385 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_meshed.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,386 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_meshed_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,386 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_star.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,386 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_star_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,386 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_wildcard.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,387 root INFO copying ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_wildcard_facts.py -> build/lib/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:40,387 root INFO creating build/lib/ansible_collections/chocolatey 2023-04-28 05:57:40,387 root INFO creating build/lib/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:40,387 root INFO copying ansible_collections/chocolatey/chocolatey/FILES.json -> build/lib/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:40,387 root INFO copying ansible_collections/chocolatey/chocolatey/LICENSE -> build/lib/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:40,388 root INFO copying ansible_collections/chocolatey/chocolatey/MANIFEST.json -> build/lib/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:40,388 root INFO copying ansible_collections/chocolatey/chocolatey/README.md -> build/lib/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:40,388 root INFO copying ansible_collections/chocolatey/chocolatey/requirements.txt -> build/lib/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:40,388 root INFO creating build/lib/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:40,388 root INFO copying ansible_collections/chocolatey/chocolatey/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:40,389 root INFO copying ansible_collections/chocolatey/chocolatey/changelogs/changelog.yaml -> build/lib/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:40,389 root INFO copying ansible_collections/chocolatey/chocolatey/changelogs/config.yaml -> build/lib/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:40,389 root INFO creating build/lib/ansible_collections/chocolatey/chocolatey/meta 2023-04-28 05:57:40,389 root INFO copying ansible_collections/chocolatey/chocolatey/meta/runtime.yml -> build/lib/ansible_collections/chocolatey/chocolatey/meta 2023-04-28 05:57:40,390 root INFO creating build/lib/ansible_collections/chocolatey/chocolatey/plugins 2023-04-28 05:57:40,390 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/README.md -> build/lib/ansible_collections/chocolatey/chocolatey/plugins 2023-04-28 05:57:40,390 root INFO creating build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:40,390 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/module_utils/Common.psm1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:40,390 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/module_utils/Config.psm1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:40,391 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/module_utils/Features.psm1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:40,391 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/module_utils/Packages.psm1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:40,391 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/module_utils/Sources.psm1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:40,391 root INFO creating build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,391 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey.ps1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,392 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey.py -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,392 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_config.ps1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,392 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_config.py -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,392 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_facts.ps1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,393 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_facts.py -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,393 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_feature.ps1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,393 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_feature.py -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,393 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_source.ps1 -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,394 root INFO copying ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_source.py -> build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:40,394 root INFO creating build/lib/ansible_collections/cisco 2023-04-28 05:57:40,394 root INFO creating build/lib/ansible_collections/cisco/aci 2023-04-28 05:57:40,394 root INFO copying ansible_collections/cisco/aci/CHANGELOG.rst -> build/lib/ansible_collections/cisco/aci 2023-04-28 05:57:40,394 root INFO copying ansible_collections/cisco/aci/FILES.json -> build/lib/ansible_collections/cisco/aci 2023-04-28 05:57:40,395 root INFO copying ansible_collections/cisco/aci/LICENSE -> build/lib/ansible_collections/cisco/aci 2023-04-28 05:57:40,395 root INFO copying ansible_collections/cisco/aci/MANIFEST.json -> build/lib/ansible_collections/cisco/aci 2023-04-28 05:57:40,395 root INFO copying ansible_collections/cisco/aci/README.md -> build/lib/ansible_collections/cisco/aci 2023-04-28 05:57:40,395 root INFO copying ansible_collections/cisco/aci/requirements.txt -> build/lib/ansible_collections/cisco/aci 2023-04-28 05:57:40,396 root INFO creating build/lib/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:40,396 root INFO copying ansible_collections/cisco/aci/changelogs/.gitignore -> build/lib/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:40,396 root INFO copying ansible_collections/cisco/aci/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:40,396 root INFO copying ansible_collections/cisco/aci/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:40,397 root INFO copying ansible_collections/cisco/aci/changelogs/config.yaml -> build/lib/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:40,397 root INFO creating build/lib/ansible_collections/cisco/aci/meta 2023-04-28 05:57:40,397 root INFO copying ansible_collections/cisco/aci/meta/runtime.yml -> build/lib/ansible_collections/cisco/aci/meta 2023-04-28 05:57:40,397 root INFO creating build/lib/ansible_collections/cisco/aci/plugins 2023-04-28 05:57:40,397 root INFO creating build/lib/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:40,397 root INFO copying ansible_collections/cisco/aci/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:40,398 root INFO copying ansible_collections/cisco/aci/plugins/doc_fragments/aci.py -> build/lib/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:40,398 root INFO copying ansible_collections/cisco/aci/plugins/doc_fragments/annotation.py -> build/lib/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:40,398 root INFO copying ansible_collections/cisco/aci/plugins/doc_fragments/owner.py -> build/lib/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:40,398 root INFO creating build/lib/ansible_collections/cisco/aci/plugins/lookup 2023-04-28 05:57:40,398 root INFO copying ansible_collections/cisco/aci/plugins/lookup/__init__.py -> build/lib/ansible_collections/cisco/aci/plugins/lookup 2023-04-28 05:57:40,399 root INFO copying ansible_collections/cisco/aci/plugins/lookup/interface_range.py -> build/lib/ansible_collections/cisco/aci/plugins/lookup 2023-04-28 05:57:40,399 root INFO creating build/lib/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:40,399 root INFO copying ansible_collections/cisco/aci/plugins/module_utils/__init__.py -> build/lib/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:40,399 root INFO copying ansible_collections/cisco/aci/plugins/module_utils/aci.py -> build/lib/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:40,399 root INFO copying ansible_collections/cisco/aci/plugins/module_utils/constants.py -> build/lib/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:40,400 root INFO creating build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,400 root INFO copying ansible_collections/cisco/aci/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,400 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_custom_privilege.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,400 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_domain.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,401 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_role.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,401 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_ssh_auth.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,401 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_user.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,401 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_certificate.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,401 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_domain.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,402 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_role.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,402 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_access_port_block_to_access_port.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,402 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_access_port_to_interface_policy_leaf_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,402 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_access_span_dst_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,403 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_access_span_filter_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,403 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_access_span_filter_group_entry.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,403 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_access_sub_port_block_to_access_port.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,403 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aep.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,404 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aep_to_domain.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,404 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_aep_to_epg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,404 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_ap.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,404 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_bd.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,405 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_bd_dhcp_label.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,405 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_bd_subnet.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,405 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_bd_to_l3out.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,405 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_bgp_rr_asn.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,406 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_bgp_rr_node.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,406 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_bulk_static_binding_to_epg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,406 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_ap.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,406 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_aws_provider.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,406 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_bgp_asn.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,407 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_cidr.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,407 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_ctx_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,407 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_epg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,407 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_epg_selector.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,408 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_external_epg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,408 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_external_epg_selector.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,408 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_provider.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,408 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_region.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,409 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_subnet.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,409 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_vpn_gateway.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,409 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_cloud_zone.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,409 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_config_export_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,409 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_config_rollback.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,410 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_config_snapshot.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,410 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_contract.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,410 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_contract_export.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,410 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_contract_subject.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,411 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_contract_subject_to_filter.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,411 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_contract_subject_to_service_graph.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,411 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_dhcp_relay.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,411 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_dhcp_relay_provider.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,412 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_dns_domain.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,412 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_dns_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,412 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_dns_provider.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,412 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_domain.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,413 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_domain_to_encap_pool.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,413 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_domain_to_vlan_pool.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,413 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_encap_pool.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,413 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_encap_pool_range.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,414 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_epg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,414 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_epg_monitoring_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,414 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,414 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract_interface.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,415 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract_master.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,415 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_epg_to_domain.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,415 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_esg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,415 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_esg_contract_master.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,416 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_esg_epg_selector.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,416 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_esg_ip_subnet_selector.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,416 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_esg_tag_selector.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,416 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_leaf_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,416 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_leaf_switch_assoc.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,417 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_node.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,417 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_pod_policy_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,417 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_scheduler.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,417 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_spine_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,418 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_spine_switch_assoc.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,418 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_switch_block.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,418 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_fabric_switch_policy_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,418 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_filter.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,419 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_filter_entry.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,419 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_firmware_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,419 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_firmware_group_node.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,419 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_firmware_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,419 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_firmware_source.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,420 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_igmp_interface_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,420 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_blacklist.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,420 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_config.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,420 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_description.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,421 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_cdp.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,421 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_fc.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,421 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_l2.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,421 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_breakout_port_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,422 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_policy_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,422 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,422 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_profile_fex_policy_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,422 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_link_level.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,423 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_lldp.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,423 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_mcp.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,423 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_ospf.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,423 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_port_channel.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,424 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_port_security.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,424 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_spanning_tree.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,424 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_interface_selector_to_switch_policy_leaf_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,424 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l2out.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,424 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l2out_extepg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,425 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l2out_extepg_to_contract.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,425 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_interface_path.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,425 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_interface_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,425 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_node_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,426 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,426 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_bgp_peer.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,426 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_extepg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,426 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_extepg_to_contract.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,427 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_extsubnet.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,427 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_interface.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,427 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_interface_secondary_ip.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,427 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,428 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_profile_ospf_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,428 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_vpc_member.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,428 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_node.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,428 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_node_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,429 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_route_tag_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,429 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_static_routes.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,429 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_l3out_static_routes_nexthop.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,429 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_maintenance_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,430 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_maintenance_group_node.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,430 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_maintenance_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,430 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_node_mgmt_epg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,430 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_ntp_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,431 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_ntp_server.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,431 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_rest.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,431 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_snmp_client.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,431 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_snmp_client_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,431 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_snmp_community_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,432 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_snmp_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,432 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_snmp_user.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,432 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_static_binding_to_epg.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,432 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_static_node_mgmt_address.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,433 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_switch_leaf_selector.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,433 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_switch_policy_leaf_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,433 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_switch_policy_vpc_protection_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,433 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_syslog_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,434 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_syslog_remote_dest.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,434 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_syslog_source.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,434 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_system.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,434 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_taboo_contract.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,435 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tag.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,435 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tenant.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,435 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tenant_action_rule_profile.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,435 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tenant_ep_retention_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,436 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_dst_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,436 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,436 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group_src.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,436 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group_to_dst_group.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,437 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vlan_pool.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,437 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vlan_pool_encap_block.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,437 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vmm_controller.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,437 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vmm_credential.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,437 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vmm_uplink.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,438 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vmm_uplink_container.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,438 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vmm_vswitch_policy.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,438 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vrf.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,438 root INFO copying ansible_collections/cisco/aci/plugins/modules/aci_vzany_to_contract.py -> build/lib/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:40,439 root INFO creating build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,439 root INFO copying ansible_collections/cisco/asa/CHANGELOG.rst -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,439 root INFO copying ansible_collections/cisco/asa/FILES.json -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,439 root INFO copying ansible_collections/cisco/asa/LICENSE -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,440 root INFO copying ansible_collections/cisco/asa/MANIFEST.json -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,440 root INFO copying ansible_collections/cisco/asa/README.md -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,440 root INFO copying ansible_collections/cisco/asa/bindep.txt -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,440 root INFO copying ansible_collections/cisco/asa/pyproject.toml -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,441 root INFO copying ansible_collections/cisco/asa/requirements.txt -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,441 root INFO copying ansible_collections/cisco/asa/test-requirements.txt -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,441 root INFO copying ansible_collections/cisco/asa/tox.ini -> build/lib/ansible_collections/cisco/asa 2023-04-28 05:57:40,441 root INFO creating build/lib/ansible_collections/cisco/asa/changelogs 2023-04-28 05:57:40,441 root INFO copying ansible_collections/cisco/asa/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/asa/changelogs 2023-04-28 05:57:40,442 root INFO copying ansible_collections/cisco/asa/changelogs/config.yaml -> build/lib/ansible_collections/cisco/asa/changelogs 2023-04-28 05:57:40,442 root INFO creating build/lib/ansible_collections/cisco/asa/changelogs/fragments 2023-04-28 05:57:40,442 root INFO copying ansible_collections/cisco/asa/changelogs/fragments/.keep -> build/lib/ansible_collections/cisco/asa/changelogs/fragments 2023-04-28 05:57:40,442 root INFO creating build/lib/ansible_collections/cisco/asa/meta 2023-04-28 05:57:40,442 root INFO copying ansible_collections/cisco/asa/meta/runtime.yml -> build/lib/ansible_collections/cisco/asa/meta 2023-04-28 05:57:40,442 root INFO creating build/lib/ansible_collections/cisco/asa/plugins 2023-04-28 05:57:40,443 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/action 2023-04-28 05:57:40,443 root INFO copying ansible_collections/cisco/asa/plugins/action/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/action 2023-04-28 05:57:40,443 root INFO copying ansible_collections/cisco/asa/plugins/action/asa.py -> build/lib/ansible_collections/cisco/asa/plugins/action 2023-04-28 05:57:40,443 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/cliconf 2023-04-28 05:57:40,443 root INFO copying ansible_collections/cisco/asa/plugins/cliconf/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/cliconf 2023-04-28 05:57:40,443 root INFO copying ansible_collections/cisco/asa/plugins/cliconf/asa.py -> build/lib/ansible_collections/cisco/asa/plugins/cliconf 2023-04-28 05:57:40,444 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/doc_fragments 2023-04-28 05:57:40,444 root INFO copying ansible_collections/cisco/asa/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/doc_fragments 2023-04-28 05:57:40,444 root INFO copying ansible_collections/cisco/asa/plugins/doc_fragments/asa.py -> build/lib/ansible_collections/cisco/asa/plugins/doc_fragments 2023-04-28 05:57:40,444 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils 2023-04-28 05:57:40,444 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils 2023-04-28 05:57:40,445 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network 2023-04-28 05:57:40,445 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa 2023-04-28 05:57:40,445 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa 2023-04-28 05:57:40,445 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/asa.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa 2023-04-28 05:57:40,445 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec 2023-04-28 05:57:40,445 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec 2023-04-28 05:57:40,446 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls 2023-04-28 05:57:40,446 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls 2023-04-28 05:57:40,446 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/acls.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls 2023-04-28 05:57:40,446 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts 2023-04-28 05:57:40,446 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts 2023-04-28 05:57:40,447 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/facts.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts 2023-04-28 05:57:40,447 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs 2023-04-28 05:57:40,447 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs 2023-04-28 05:57:40,447 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/ogs.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs 2023-04-28 05:57:40,447 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config 2023-04-28 05:57:40,447 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config 2023-04-28 05:57:40,448 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls 2023-04-28 05:57:40,448 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls 2023-04-28 05:57:40,448 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/acls.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls 2023-04-28 05:57:40,448 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs 2023-04-28 05:57:40,448 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs 2023-04-28 05:57:40,449 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/ogs.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs 2023-04-28 05:57:40,449 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts 2023-04-28 05:57:40,449 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts 2023-04-28 05:57:40,449 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/facts.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts 2023-04-28 05:57:40,449 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls 2023-04-28 05:57:40,450 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls 2023-04-28 05:57:40,450 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/acls.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls 2023-04-28 05:57:40,450 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy 2023-04-28 05:57:40,450 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy 2023-04-28 05:57:40,450 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/base.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy 2023-04-28 05:57:40,451 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs 2023-04-28 05:57:40,451 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs 2023-04-28 05:57:40,451 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/ogs.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs 2023-04-28 05:57:40,451 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:40,451 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:40,452 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/module.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:40,452 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/providers.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:40,452 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates 2023-04-28 05:57:40,452 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/acls.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates 2023-04-28 05:57:40,452 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/ogs.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates 2023-04-28 05:57:40,453 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils 2023-04-28 05:57:40,453 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils 2023-04-28 05:57:40,453 root INFO copying ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/utils.py -> build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils 2023-04-28 05:57:40,453 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:40,453 root INFO copying ansible_collections/cisco/asa/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:40,454 root INFO copying ansible_collections/cisco/asa/plugins/modules/asa_acls.py -> build/lib/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:40,454 root INFO copying ansible_collections/cisco/asa/plugins/modules/asa_command.py -> build/lib/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:40,454 root INFO copying ansible_collections/cisco/asa/plugins/modules/asa_config.py -> build/lib/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:40,454 root INFO copying ansible_collections/cisco/asa/plugins/modules/asa_facts.py -> build/lib/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:40,455 root INFO copying ansible_collections/cisco/asa/plugins/modules/asa_ogs.py -> build/lib/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:40,455 root INFO creating build/lib/ansible_collections/cisco/asa/plugins/terminal 2023-04-28 05:57:40,455 root INFO copying ansible_collections/cisco/asa/plugins/terminal/__init__.py -> build/lib/ansible_collections/cisco/asa/plugins/terminal 2023-04-28 05:57:40,455 root INFO copying ansible_collections/cisco/asa/plugins/terminal/asa.py -> build/lib/ansible_collections/cisco/asa/plugins/terminal 2023-04-28 05:57:40,455 root INFO creating build/lib/ansible_collections/cisco/dnac 2023-04-28 05:57:40,456 root INFO copying ansible_collections/cisco/dnac/FILES.json -> build/lib/ansible_collections/cisco/dnac 2023-04-28 05:57:40,456 root INFO copying ansible_collections/cisco/dnac/LICENSE -> build/lib/ansible_collections/cisco/dnac 2023-04-28 05:57:40,456 root INFO copying ansible_collections/cisco/dnac/MANIFEST.json -> build/lib/ansible_collections/cisco/dnac 2023-04-28 05:57:40,457 root INFO copying ansible_collections/cisco/dnac/Makefile -> build/lib/ansible_collections/cisco/dnac 2023-04-28 05:57:40,457 root INFO copying ansible_collections/cisco/dnac/README.md -> build/lib/ansible_collections/cisco/dnac 2023-04-28 05:57:40,457 root INFO copying ansible_collections/cisco/dnac/requirements.txt -> build/lib/ansible_collections/cisco/dnac 2023-04-28 05:57:40,457 root INFO creating build/lib/ansible_collections/cisco/dnac/changelogs 2023-04-28 05:57:40,457 root INFO copying ansible_collections/cisco/dnac/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/dnac/changelogs 2023-04-28 05:57:40,458 root INFO creating build/lib/ansible_collections/cisco/dnac/meta 2023-04-28 05:57:40,458 root INFO copying ansible_collections/cisco/dnac/meta/runtime.yml -> build/lib/ansible_collections/cisco/dnac/meta 2023-04-28 05:57:40,458 root INFO creating build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,458 root INFO copying ansible_collections/cisco/dnac/playbooks/application_set_info.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,458 root INFO copying ansible_collections/cisco/dnac/playbooks/application_sets.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,458 root INFO copying ansible_collections/cisco/dnac/playbooks/applications.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,459 root INFO copying ansible_collections/cisco/dnac/playbooks/authentication_import.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,459 root INFO copying ansible_collections/cisco/dnac/playbooks/command_runner_run_command.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,459 root INFO copying ansible_collections/cisco/dnac/playbooks/configuration_template_version_create.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,459 root INFO copying ansible_collections/cisco/dnac/playbooks/credentials.template -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,460 root INFO copying ansible_collections/cisco/dnac/playbooks/credentials.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,460 root INFO copying ansible_collections/cisco/dnac/playbooks/device_details.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,460 root INFO copying ansible_collections/cisco/dnac/playbooks/discovery.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,460 root INFO copying ansible_collections/cisco/dnac/playbooks/download_device_cmd_runner_output.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,460 root INFO copying ansible_collections/cisco/dnac/playbooks/global_credentials.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,461 root INFO copying ansible_collections/cisco/dnac/playbooks/global_credentials_info.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,461 root INFO copying ansible_collections/cisco/dnac/playbooks/global_pool.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,461 root INFO copying ansible_collections/cisco/dnac/playbooks/hosts -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,461 root INFO copying ansible_collections/cisco/dnac/playbooks/image_details.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,462 root INFO copying ansible_collections/cisco/dnac/playbooks/import_image_file.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,462 root INFO copying ansible_collections/cisco/dnac/playbooks/network_device_custom_prompt_info.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,462 root INFO copying ansible_collections/cisco/dnac/playbooks/network_device_info.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,462 root INFO copying ansible_collections/cisco/dnac/playbooks/network_device_update_role.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,462 root INFO copying ansible_collections/cisco/dnac/playbooks/pnp_device.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,463 root INFO copying ansible_collections/cisco/dnac/playbooks/reports_executions_info.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,463 root INFO copying ansible_collections/cisco/dnac/playbooks/reserve_ip_subpool.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,463 root INFO copying ansible_collections/cisco/dnac/playbooks/sda_fabric.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,463 root INFO copying ansible_collections/cisco/dnac/playbooks/sda_fabric_site.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,464 root INFO copying ansible_collections/cisco/dnac/playbooks/sda_virtual_network_v2.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,464 root INFO copying ansible_collections/cisco/dnac/playbooks/tag.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,464 root INFO copying ansible_collections/cisco/dnac/playbooks/template.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,464 root INFO copying ansible_collections/cisco/dnac/playbooks/template_pnp_intent.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,464 root INFO copying ansible_collections/cisco/dnac/playbooks/test_swim_module.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,465 root INFO copying ansible_collections/cisco/dnac/playbooks/wireless_enterprise_ssid.yml -> build/lib/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:40,465 root INFO creating build/lib/ansible_collections/cisco/dnac/playbooks/files 2023-04-28 05:57:40,465 root INFO copying ansible_collections/cisco/dnac/playbooks/files/test.template -> build/lib/ansible_collections/cisco/dnac/playbooks/files 2023-04-28 05:57:40,465 root INFO creating build/lib/ansible_collections/cisco/dnac/plugins 2023-04-28 05:57:40,465 root INFO copying ansible_collections/cisco/dnac/plugins/README.md -> build/lib/ansible_collections/cisco/dnac/plugins 2023-04-28 05:57:40,466 root INFO copying ansible_collections/cisco/dnac/plugins/__init__.py -> build/lib/ansible_collections/cisco/dnac/plugins 2023-04-28 05:57:40,466 root INFO creating build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,466 root INFO copying ansible_collections/cisco/dnac/plugins/action/accesspoint_configuration_details_by_task_id_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,466 root INFO copying ansible_collections/cisco/dnac/plugins/action/app_policy_default_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,466 root INFO copying ansible_collections/cisco/dnac/plugins/action/app_policy_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,467 root INFO copying ansible_collections/cisco/dnac/plugins/action/app_policy_intent_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,467 root INFO copying ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,467 root INFO copying ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,467 root INFO copying ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,467 root INFO copying ansible_collections/cisco/dnac/plugins/action/application_sets.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,468 root INFO copying ansible_collections/cisco/dnac/plugins/action/application_sets_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,468 root INFO copying ansible_collections/cisco/dnac/plugins/action/application_sets_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,468 root INFO copying ansible_collections/cisco/dnac/plugins/action/applications.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,468 root INFO copying ansible_collections/cisco/dnac/plugins/action/applications_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,469 root INFO copying ansible_collections/cisco/dnac/plugins/action/applications_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,469 root INFO copying ansible_collections/cisco/dnac/plugins/action/applications_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,469 root INFO copying ansible_collections/cisco/dnac/plugins/action/assign_device_to_site.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,469 root INFO copying ansible_collections/cisco/dnac/plugins/action/associate_site_to_network_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,469 root INFO copying ansible_collections/cisco/dnac/plugins/action/authentication_import_certificate.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,470 root INFO copying ansible_collections/cisco/dnac/plugins/action/authentication_import_certificate_p12.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,470 root INFO copying ansible_collections/cisco/dnac/plugins/action/authentication_policy_servers_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,470 root INFO copying ansible_collections/cisco/dnac/plugins/action/buildings_planned_access_points_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,470 root INFO copying ansible_collections/cisco/dnac/plugins/action/business_sda_hostonboarding_ssid_ippool.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,471 root INFO copying ansible_collections/cisco/dnac/plugins/action/business_sda_hostonboarding_ssid_ippool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,471 root INFO copying ansible_collections/cisco/dnac/plugins/action/business_sda_virtual_network_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,471 root INFO copying ansible_collections/cisco/dnac/plugins/action/business_sda_wireless_controller_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,471 root INFO copying ansible_collections/cisco/dnac/plugins/action/business_sda_wireless_controller_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,471 root INFO copying ansible_collections/cisco/dnac/plugins/action/cli_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,472 root INFO copying ansible_collections/cisco/dnac/plugins/action/client_detail_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,472 root INFO copying ansible_collections/cisco/dnac/plugins/action/client_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,472 root INFO copying ansible_collections/cisco/dnac/plugins/action/client_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,472 root INFO copying ansible_collections/cisco/dnac/plugins/action/client_proximity_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,473 root INFO copying ansible_collections/cisco/dnac/plugins/action/command_runner_run_command.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,473 root INFO copying ansible_collections/cisco/dnac/plugins/action/compliance_check_run.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,473 root INFO copying ansible_collections/cisco/dnac/plugins/action/compliance_device_by_id_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,473 root INFO copying ansible_collections/cisco/dnac/plugins/action/compliance_device_details_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,473 root INFO copying ansible_collections/cisco/dnac/plugins/action/compliance_device_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,474 root INFO copying ansible_collections/cisco/dnac/plugins/action/compliance_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,474 root INFO copying ansible_collections/cisco/dnac/plugins/action/compliance_device_status_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,474 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,474 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_clone.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,475 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,475 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,475 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,475 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,475 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_export_project.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,476 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_export_template.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,476 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_import_project.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,476 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_import_template.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,476 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,477 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_project.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,477 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_project_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,477 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_version_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,477 root INFO copying ansible_collections/cisco/dnac/plugins/action/configuration_template_version_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,478 root INFO copying ansible_collections/cisco/dnac/plugins/action/credential_to_site_by_siteid_create_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,478 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_configurations_export.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,478 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_credential_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,478 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_credential_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,478 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_credential_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,479 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_credential_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,479 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,479 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,479 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_family_identifiers_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,479 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,480 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_interface_by_ip_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,480 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_interface_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,480 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,480 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_interface_isis_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,481 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_interface_ospf_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,481 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_reboot_apreboot_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,481 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_replacement.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,481 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_replacement_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,482 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_replacement_deploy.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,482 root INFO copying ansible_collections/cisco/dnac/plugins/action/device_replacement_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,482 root INFO copying ansible_collections/cisco/dnac/plugins/action/disassociate_site_to_network_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,482 root INFO copying ansible_collections/cisco/dnac/plugins/action/disasterrecovery_system_operationstatus_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,482 root INFO copying ansible_collections/cisco/dnac/plugins/action/disasterrecovery_system_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,483 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,483 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,483 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,483 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,484 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_device_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,484 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,484 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_job_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,484 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_range_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,484 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,485 root INFO copying ansible_collections/cisco/dnac/plugins/action/discovery_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,485 root INFO copying ansible_collections/cisco/dnac/plugins/action/dna_command_runner_keywords_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,485 root INFO copying ansible_collections/cisco/dnac/plugins/action/dnac_packages_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,485 root INFO copying ansible_collections/cisco/dnac/plugins/action/dnacaap_management_execution_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,486 root INFO copying ansible_collections/cisco/dnac/plugins/action/endpoint_analytics_profiling_rules.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,486 root INFO copying ansible_collections/cisco/dnac/plugins/action/endpoint_analytics_profiling_rules_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,486 root INFO copying ansible_collections/cisco/dnac/plugins/action/eox_status_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,486 root INFO copying ansible_collections/cisco/dnac/plugins/action/eox_status_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,487 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_api_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,487 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_artifact_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,487 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_artifact_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,487 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_config_connector_types_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,487 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,488 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_email_config.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,488 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_email_config_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,488 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_email_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,488 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_email_config_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,489 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,489 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,489 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_parent_records_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,489 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,489 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_series_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,490 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_series_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,490 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_snmp_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,490 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,490 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,491 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_details_email_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,491 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_details_rest_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,491 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_details_syslog_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,491 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_email.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,492 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_email_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,492 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,492 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_rest.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,492 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_rest_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,492 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_syslog.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,493 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_subscription_syslog_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,493 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_syslog_config.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,493 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_syslog_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,493 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_webhook_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,494 root INFO copying ansible_collections/cisco/dnac/plugins/action/event_webhook_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,494 root INFO copying ansible_collections/cisco/dnac/plugins/action/execute_suggested_actions_commands.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,494 root INFO copying ansible_collections/cisco/dnac/plugins/action/file_import.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,494 root INFO copying ansible_collections/cisco/dnac/plugins/action/file_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,495 root INFO copying ansible_collections/cisco/dnac/plugins/action/file_namespace_files_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,495 root INFO copying ansible_collections/cisco/dnac/plugins/action/file_namespaces_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,495 root INFO copying ansible_collections/cisco/dnac/plugins/action/global_credential_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,495 root INFO copying ansible_collections/cisco/dnac/plugins/action/global_credential_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,495 root INFO copying ansible_collections/cisco/dnac/plugins/action/global_credential_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,496 root INFO copying ansible_collections/cisco/dnac/plugins/action/global_credential_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,496 root INFO copying ansible_collections/cisco/dnac/plugins/action/global_credential_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,496 root INFO copying ansible_collections/cisco/dnac/plugins/action/global_pool.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,496 root INFO copying ansible_collections/cisco/dnac/plugins/action/global_pool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,497 root INFO copying ansible_collections/cisco/dnac/plugins/action/golden_image_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,497 root INFO copying ansible_collections/cisco/dnac/plugins/action/golden_tag_image_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,497 root INFO copying ansible_collections/cisco/dnac/plugins/action/golden_tag_image_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,497 root INFO copying ansible_collections/cisco/dnac/plugins/action/http_read_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,497 root INFO copying ansible_collections/cisco/dnac/plugins/action/http_write_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,498 root INFO copying ansible_collections/cisco/dnac/plugins/action/integration_settings_instances_itsm.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,498 root INFO copying ansible_collections/cisco/dnac/plugins/action/integration_settings_instances_itsm_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,498 root INFO copying ansible_collections/cisco/dnac/plugins/action/interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,498 root INFO copying ansible_collections/cisco/dnac/plugins/action/interface_network_device_detail_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,499 root INFO copying ansible_collections/cisco/dnac/plugins/action/interface_network_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,499 root INFO copying ansible_collections/cisco/dnac/plugins/action/interface_network_device_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,499 root INFO copying ansible_collections/cisco/dnac/plugins/action/interface_operation_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,499 root INFO copying ansible_collections/cisco/dnac/plugins/action/interface_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,500 root INFO copying ansible_collections/cisco/dnac/plugins/action/issues_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,500 root INFO copying ansible_collections/cisco/dnac/plugins/action/issues_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,500 root INFO copying ansible_collections/cisco/dnac/plugins/action/itsm_cmdb_sync_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,500 root INFO copying ansible_collections/cisco/dnac/plugins/action/itsm_integration_events_failed_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,500 root INFO copying ansible_collections/cisco/dnac/plugins/action/itsm_integration_events_retry.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,501 root INFO copying ansible_collections/cisco/dnac/plugins/action/lan_automation_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,501 root INFO copying ansible_collections/cisco/dnac/plugins/action/lan_automation_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,501 root INFO copying ansible_collections/cisco/dnac/plugins/action/lan_automation_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,501 root INFO copying ansible_collections/cisco/dnac/plugins/action/lan_automation_log_by_serial_number_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,502 root INFO copying ansible_collections/cisco/dnac/plugins/action/lan_automation_log_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,502 root INFO copying ansible_collections/cisco/dnac/plugins/action/lan_automation_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,502 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,502 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_device_deregistration.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,502 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_device_license_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,503 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_device_license_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,503 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_device_registration.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,503 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_smart_account_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,503 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_term_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,504 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_usage_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,504 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_virtual_account_change.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,504 root INFO copying ansible_collections/cisco/dnac/plugins/action/license_virtual_account_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,505 root INFO copying ansible_collections/cisco/dnac/plugins/action/netconf_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,505 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,505 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,505 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_by_ip_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,506 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_by_serial_number_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,506 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_chassis_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,506 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_config_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,506 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,507 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,507 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_custom_prompt.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,507 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_custom_prompt_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,507 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_equipment_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,507 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_export.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,508 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_functional_capability_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,508 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_global_polling_interval_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,508 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,508 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_interface_neighbor_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,509 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_interface_poe_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,509 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_inventory_insight_link_mismatch_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,509 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_lexicographically_sorted_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,509 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_linecard_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,509 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_meraki_organization_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,510 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_module_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,510 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_module_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,510 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_poe_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,510 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_polling_interval_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,511 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,511 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_register_for_wsa_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,511 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_stack_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,511 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,512 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_supervisor_card_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,512 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_sync.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,512 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_update_role.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,512 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_user_defined_field.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,512 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_user_defined_field_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,513 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_vlan_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,513 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_wireless_lan_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,513 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_device_with_snmp_v3_des_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,513 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,514 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,514 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,514 root INFO copying ansible_collections/cisco/dnac/plugins/action/network_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,514 root INFO copying ansible_collections/cisco/dnac/plugins/action/nfv_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,515 root INFO copying ansible_collections/cisco/dnac/plugins/action/nfv_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,515 root INFO copying ansible_collections/cisco/dnac/plugins/action/nfv_provision.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,515 root INFO copying ansible_collections/cisco/dnac/plugins/action/nfv_provision_detail_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,515 root INFO copying ansible_collections/cisco/dnac/plugins/action/nfv_provision_details.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,515 root INFO copying ansible_collections/cisco/dnac/plugins/action/path_trace.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,516 root INFO copying ansible_collections/cisco/dnac/plugins/action/path_trace_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,516 root INFO copying ansible_collections/cisco/dnac/plugins/action/planned_access_points_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,516 root INFO copying ansible_collections/cisco/dnac/plugins/action/platform_nodes_configuration_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,516 root INFO copying ansible_collections/cisco/dnac/plugins/action/platform_release_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,517 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,517 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_authorize.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,517 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_claim.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,517 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_claim_to_site.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,518 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_config_preview.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,518 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,518 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_history_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,518 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_import.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,518 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,519 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_reset.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,519 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_device_unclaim.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,519 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_global_settings.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,519 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_global_settings_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,520 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_server_profile_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,520 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_smart_account_domains_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,520 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_add.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,520 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_deregister.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,520 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_devices_sync.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,521 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_sync_result_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,521 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_virtual_accounts_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,521 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_workflow.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,521 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_workflow_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,522 root INFO copying ansible_collections/cisco/dnac/plugins/action/pnp_workflow_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,522 root INFO copying ansible_collections/cisco/dnac/plugins/action/profiling_rules_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,522 root INFO copying ansible_collections/cisco/dnac/plugins/action/profiling_rules_in_bulk_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,522 root INFO copying ansible_collections/cisco/dnac/plugins/action/projects_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,522 root INFO copying ansible_collections/cisco/dnac/plugins/action/qos_device_interface.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,523 root INFO copying ansible_collections/cisco/dnac/plugins/action/qos_device_interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,523 root INFO copying ansible_collections/cisco/dnac/plugins/action/qos_device_interface_info_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,523 root INFO copying ansible_collections/cisco/dnac/plugins/action/reports.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,523 root INFO copying ansible_collections/cisco/dnac/plugins/action/reports_executions_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,524 root INFO copying ansible_collections/cisco/dnac/plugins/action/reports_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,524 root INFO copying ansible_collections/cisco/dnac/plugins/action/reports_view_group_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,524 root INFO copying ansible_collections/cisco/dnac/plugins/action/reports_view_group_view_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,524 root INFO copying ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,525 root INFO copying ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,525 root INFO copying ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,525 root INFO copying ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,525 root INFO copying ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,526 root INFO copying ansible_collections/cisco/dnac/plugins/action/role_permissions_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,526 root INFO copying ansible_collections/cisco/dnac/plugins/action/roles_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,526 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,526 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,526 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_device_role_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,527 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,527 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_authentication_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,527 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_authentication_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,527 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_border_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,528 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_border_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,528 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_control_plane_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,528 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_control_plane_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,528 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_edge_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,528 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_edge_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,529 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,529 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_site.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,529 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_fabric_site_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,529 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_multicast.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,530 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_multicast_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,530 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_access_point.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,530 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_access_point_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,530 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_user_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,531 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_user_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,531 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_provision_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,531 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_provision_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,531 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_virtual_network.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,531 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,532 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_ip_pool.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,532 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_ip_pool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,532 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,532 root INFO copying ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,533 root INFO copying ansible_collections/cisco/dnac/plugins/action/security_advisories_devices_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,533 root INFO copying ansible_collections/cisco/dnac/plugins/action/security_advisories_ids_per_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,533 root INFO copying ansible_collections/cisco/dnac/plugins/action/security_advisories_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,533 root INFO copying ansible_collections/cisco/dnac/plugins/action/security_advisories_per_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,534 root INFO copying ansible_collections/cisco/dnac/plugins/action/security_advisories_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,534 root INFO copying ansible_collections/cisco/dnac/plugins/action/sensor.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,534 root INFO copying ansible_collections/cisco/dnac/plugins/action/sensor_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,534 root INFO copying ansible_collections/cisco/dnac/plugins/action/sensor_test_run.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,535 root INFO copying ansible_collections/cisco/dnac/plugins/action/sensor_test_template_duplicate.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,535 root INFO copying ansible_collections/cisco/dnac/plugins/action/sensor_test_template_edit.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,535 root INFO copying ansible_collections/cisco/dnac/plugins/action/service_provider_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,535 root INFO copying ansible_collections/cisco/dnac/plugins/action/service_provider_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,535 root INFO copying ansible_collections/cisco/dnac/plugins/action/service_provider_profile_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,536 root INFO copying ansible_collections/cisco/dnac/plugins/action/service_provider_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,536 root INFO copying ansible_collections/cisco/dnac/plugins/action/service_provider_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,536 root INFO copying ansible_collections/cisco/dnac/plugins/action/service_provider_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,536 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_assign_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,537 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_assign_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,537 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,537 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,537 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,537 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_design_floormap.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,538 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_design_floormap_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,538 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,538 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,538 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_membership_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,539 root INFO copying ansible_collections/cisco/dnac/plugins/action/site_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,539 root INFO copying ansible_collections/cisco/dnac/plugins/action/snmp_properties.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,539 root INFO copying ansible_collections/cisco/dnac/plugins/action/snmp_properties_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,539 root INFO copying ansible_collections/cisco/dnac/plugins/action/snmpv2_read_community_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,539 root INFO copying ansible_collections/cisco/dnac/plugins/action/snmpv2_write_community_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,540 root INFO copying ansible_collections/cisco/dnac/plugins/action/snmpv3_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,540 root INFO copying ansible_collections/cisco/dnac/plugins/action/sp_profile_delete_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,540 root INFO copying ansible_collections/cisco/dnac/plugins/action/swim_image_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,540 root INFO copying ansible_collections/cisco/dnac/plugins/action/swim_import_local.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,541 root INFO copying ansible_collections/cisco/dnac/plugins/action/swim_import_via_url.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,541 root INFO copying ansible_collections/cisco/dnac/plugins/action/swim_trigger_activation.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,541 root INFO copying ansible_collections/cisco/dnac/plugins/action/swim_trigger_distribution.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,541 root INFO copying ansible_collections/cisco/dnac/plugins/action/syslog_config_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,542 root INFO copying ansible_collections/cisco/dnac/plugins/action/syslog_config_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,542 root INFO copying ansible_collections/cisco/dnac/plugins/action/system_health_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,542 root INFO copying ansible_collections/cisco/dnac/plugins/action/system_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,542 root INFO copying ansible_collections/cisco/dnac/plugins/action/system_performance_historical_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,542 root INFO copying ansible_collections/cisco/dnac/plugins/action/system_performance_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,543 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,543 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,543 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,543 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag_member.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,544 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag_member_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,544 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag_member_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,544 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag_member_type_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,544 root INFO copying ansible_collections/cisco/dnac/plugins/action/tag_membership.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,545 root INFO copying ansible_collections/cisco/dnac/plugins/action/task_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,545 root INFO copying ansible_collections/cisco/dnac/plugins/action/task_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,545 root INFO copying ansible_collections/cisco/dnac/plugins/action/task_operation_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,545 root INFO copying ansible_collections/cisco/dnac/plugins/action/task_tree_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,545 root INFO copying ansible_collections/cisco/dnac/plugins/action/template_preview.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,546 root INFO copying ansible_collections/cisco/dnac/plugins/action/templates_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,546 root INFO copying ansible_collections/cisco/dnac/plugins/action/threat_detail.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,546 root INFO copying ansible_collections/cisco/dnac/plugins/action/threat_detail_count.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,546 root INFO copying ansible_collections/cisco/dnac/plugins/action/threat_summary.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,547 root INFO copying ansible_collections/cisco/dnac/plugins/action/topology_layer_2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,547 root INFO copying ansible_collections/cisco/dnac/plugins/action/topology_layer_3_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,547 root INFO copying ansible_collections/cisco/dnac/plugins/action/topology_network_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,547 root INFO copying ansible_collections/cisco/dnac/plugins/action/topology_physical_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,547 root INFO copying ansible_collections/cisco/dnac/plugins/action/topology_site_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,548 root INFO copying ansible_collections/cisco/dnac/plugins/action/topology_vlan_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,548 root INFO copying ansible_collections/cisco/dnac/plugins/action/transit_peer_network.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,548 root INFO copying ansible_collections/cisco/dnac/plugins/action/transit_peer_network_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,548 root INFO copying ansible_collections/cisco/dnac/plugins/action/user.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,549 root INFO copying ansible_collections/cisco/dnac/plugins/action/user_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,549 root INFO copying ansible_collections/cisco/dnac/plugins/action/user_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,549 root INFO copying ansible_collections/cisco/dnac/plugins/action/users_external_servers_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,549 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_accespoint_configuration.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,550 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_accesspoint_configuration_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,550 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_dynamic_interface.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,550 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_dynamic_interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,550 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_enterprise_ssid.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,551 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_enterprise_ssid_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,551 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,551 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,551 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_provision_access_point.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,551 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_provision_device_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,552 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_provision_device_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,552 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_provision_ssid_create_provision.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,552 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_provision_ssid_delete_reprovision.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,552 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_psk_override.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,553 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_rf_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,553 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_rf_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,553 root INFO copying ansible_collections/cisco/dnac/plugins/action/wireless_sensor_test_results_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:40,553 root INFO creating build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:40,553 root INFO copying ansible_collections/cisco/dnac/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:40,554 root INFO copying ansible_collections/cisco/dnac/plugins/doc_fragments/intent_params.py -> build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:40,554 root INFO copying ansible_collections/cisco/dnac/plugins/doc_fragments/module.py -> build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:40,554 root INFO copying ansible_collections/cisco/dnac/plugins/doc_fragments/module_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:40,554 root INFO creating build/lib/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:40,554 root INFO copying ansible_collections/cisco/dnac/plugins/module_utils/__init__.py -> build/lib/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:40,555 root INFO copying ansible_collections/cisco/dnac/plugins/module_utils/dnac.py -> build/lib/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:40,555 root INFO copying ansible_collections/cisco/dnac/plugins/module_utils/exceptions.py -> build/lib/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:40,555 root INFO creating build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,555 root INFO copying ansible_collections/cisco/dnac/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,555 root INFO copying ansible_collections/cisco/dnac/plugins/modules/accesspoint_configuration_details_by_task_id_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,556 root INFO copying ansible_collections/cisco/dnac/plugins/modules/app_policy_default_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,556 root INFO copying ansible_collections/cisco/dnac/plugins/modules/app_policy_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,556 root INFO copying ansible_collections/cisco/dnac/plugins/modules/app_policy_intent_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,556 root INFO copying ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,556 root INFO copying ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,557 root INFO copying ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,557 root INFO copying ansible_collections/cisco/dnac/plugins/modules/application_sets.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,557 root INFO copying ansible_collections/cisco/dnac/plugins/modules/application_sets_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,557 root INFO copying ansible_collections/cisco/dnac/plugins/modules/application_sets_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,558 root INFO copying ansible_collections/cisco/dnac/plugins/modules/applications.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,558 root INFO copying ansible_collections/cisco/dnac/plugins/modules/applications_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,558 root INFO copying ansible_collections/cisco/dnac/plugins/modules/applications_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,558 root INFO copying ansible_collections/cisco/dnac/plugins/modules/applications_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,559 root INFO copying ansible_collections/cisco/dnac/plugins/modules/assign_device_to_site.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,559 root INFO copying ansible_collections/cisco/dnac/plugins/modules/associate_site_to_network_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,559 root INFO copying ansible_collections/cisco/dnac/plugins/modules/authentication_import_certificate.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,559 root INFO copying ansible_collections/cisco/dnac/plugins/modules/authentication_import_certificate_p12.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,559 root INFO copying ansible_collections/cisco/dnac/plugins/modules/authentication_policy_servers_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,560 root INFO copying ansible_collections/cisco/dnac/plugins/modules/buildings_planned_access_points_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,560 root INFO copying ansible_collections/cisco/dnac/plugins/modules/business_sda_hostonboarding_ssid_ippool.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,560 root INFO copying ansible_collections/cisco/dnac/plugins/modules/business_sda_hostonboarding_ssid_ippool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,560 root INFO copying ansible_collections/cisco/dnac/plugins/modules/business_sda_virtual_network_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,560 root INFO copying ansible_collections/cisco/dnac/plugins/modules/business_sda_wireless_controller_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,561 root INFO copying ansible_collections/cisco/dnac/plugins/modules/business_sda_wireless_controller_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,561 root INFO copying ansible_collections/cisco/dnac/plugins/modules/cli_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,561 root INFO copying ansible_collections/cisco/dnac/plugins/modules/client_detail_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,561 root INFO copying ansible_collections/cisco/dnac/plugins/modules/client_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,562 root INFO copying ansible_collections/cisco/dnac/plugins/modules/client_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,562 root INFO copying ansible_collections/cisco/dnac/plugins/modules/client_proximity_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,562 root INFO copying ansible_collections/cisco/dnac/plugins/modules/command_runner_run_command.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,562 root INFO copying ansible_collections/cisco/dnac/plugins/modules/compliance_check_run.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,562 root INFO copying ansible_collections/cisco/dnac/plugins/modules/compliance_device_by_id_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,563 root INFO copying ansible_collections/cisco/dnac/plugins/modules/compliance_device_details_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,563 root INFO copying ansible_collections/cisco/dnac/plugins/modules/compliance_device_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,563 root INFO copying ansible_collections/cisco/dnac/plugins/modules/compliance_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,563 root INFO copying ansible_collections/cisco/dnac/plugins/modules/compliance_device_status_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,564 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,564 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_clone.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,564 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,564 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,565 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,565 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,565 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_export_project.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,565 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_export_template.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,566 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_import_project.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,566 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_import_template.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,566 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,566 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_project.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,567 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_project_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,567 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_version_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,567 root INFO copying ansible_collections/cisco/dnac/plugins/modules/configuration_template_version_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,567 root INFO copying ansible_collections/cisco/dnac/plugins/modules/credential_to_site_by_siteid_create_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,567 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_configurations_export.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,568 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_credential_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,568 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_credential_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,568 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_credential_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,568 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_credential_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,569 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,569 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,569 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_family_identifiers_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,569 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,569 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_interface_by_ip_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,570 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_interface_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,570 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,570 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_interface_isis_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,570 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_interface_ospf_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,571 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_reboot_apreboot.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,571 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_reboot_apreboot_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,571 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_replacement.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,571 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_replacement_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,571 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_replacement_deploy.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,572 root INFO copying ansible_collections/cisco/dnac/plugins/modules/device_replacement_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,572 root INFO copying ansible_collections/cisco/dnac/plugins/modules/disassociate_site_to_network_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,572 root INFO copying ansible_collections/cisco/dnac/plugins/modules/disasterrecovery_system_operationstatus_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,572 root INFO copying ansible_collections/cisco/dnac/plugins/modules/disasterrecovery_system_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,573 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,573 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,573 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,573 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,573 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_device_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,574 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,574 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_job_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,574 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_range_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,574 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,575 root INFO copying ansible_collections/cisco/dnac/plugins/modules/discovery_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,575 root INFO copying ansible_collections/cisco/dnac/plugins/modules/dna_command_runner_keywords_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,575 root INFO copying ansible_collections/cisco/dnac/plugins/modules/dnac_packages_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,575 root INFO copying ansible_collections/cisco/dnac/plugins/modules/dnacaap_management_execution_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,576 root INFO copying ansible_collections/cisco/dnac/plugins/modules/endpoint_analytics_profiling_rules.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,576 root INFO copying ansible_collections/cisco/dnac/plugins/modules/endpoint_analytics_profiling_rules_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,576 root INFO copying ansible_collections/cisco/dnac/plugins/modules/eox_status_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,576 root INFO copying ansible_collections/cisco/dnac/plugins/modules/eox_status_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,576 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_api_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,577 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_artifact_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,577 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_artifact_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,577 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_config_connector_types_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,577 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,578 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_email_config.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,578 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_email_config_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,578 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_email_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,578 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_email_config_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,578 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,579 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,579 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_parent_records_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,579 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,579 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_series_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,580 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_series_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,580 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_snmp_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,580 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,580 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,581 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_email_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,581 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_rest_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,581 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_syslog_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,581 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_email.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,581 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_email_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,582 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,582 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_rest.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,582 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_rest_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,582 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_syslog.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,583 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_subscription_syslog_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,583 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_syslog_config.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,583 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_syslog_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,583 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_webhook_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,584 root INFO copying ansible_collections/cisco/dnac/plugins/modules/event_webhook_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,584 root INFO copying ansible_collections/cisco/dnac/plugins/modules/execute_suggested_actions_commands.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,584 root INFO copying ansible_collections/cisco/dnac/plugins/modules/file_import.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,584 root INFO copying ansible_collections/cisco/dnac/plugins/modules/file_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,584 root INFO copying ansible_collections/cisco/dnac/plugins/modules/file_namespace_files_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,585 root INFO copying ansible_collections/cisco/dnac/plugins/modules/file_namespaces_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,585 root INFO copying ansible_collections/cisco/dnac/plugins/modules/global_credential_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,585 root INFO copying ansible_collections/cisco/dnac/plugins/modules/global_credential_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,585 root INFO copying ansible_collections/cisco/dnac/plugins/modules/global_credential_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,586 root INFO copying ansible_collections/cisco/dnac/plugins/modules/global_credential_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,586 root INFO copying ansible_collections/cisco/dnac/plugins/modules/global_credential_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,586 root INFO copying ansible_collections/cisco/dnac/plugins/modules/global_pool.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,586 root INFO copying ansible_collections/cisco/dnac/plugins/modules/global_pool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,586 root INFO copying ansible_collections/cisco/dnac/plugins/modules/golden_image_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,587 root INFO copying ansible_collections/cisco/dnac/plugins/modules/golden_tag_image_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,587 root INFO copying ansible_collections/cisco/dnac/plugins/modules/golden_tag_image_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,587 root INFO copying ansible_collections/cisco/dnac/plugins/modules/http_read_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,587 root INFO copying ansible_collections/cisco/dnac/plugins/modules/http_write_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,588 root INFO copying ansible_collections/cisco/dnac/plugins/modules/integration_settings_instances_itsm.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,588 root INFO copying ansible_collections/cisco/dnac/plugins/modules/integration_settings_instances_itsm_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,588 root INFO copying ansible_collections/cisco/dnac/plugins/modules/interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,588 root INFO copying ansible_collections/cisco/dnac/plugins/modules/interface_network_device_detail_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,588 root INFO copying ansible_collections/cisco/dnac/plugins/modules/interface_network_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,589 root INFO copying ansible_collections/cisco/dnac/plugins/modules/interface_network_device_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,589 root INFO copying ansible_collections/cisco/dnac/plugins/modules/interface_operation_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,589 root INFO copying ansible_collections/cisco/dnac/plugins/modules/interface_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,589 root INFO copying ansible_collections/cisco/dnac/plugins/modules/issues_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,590 root INFO copying ansible_collections/cisco/dnac/plugins/modules/issues_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,590 root INFO copying ansible_collections/cisco/dnac/plugins/modules/itsm_cmdb_sync_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,590 root INFO copying ansible_collections/cisco/dnac/plugins/modules/itsm_integration_events_failed_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,590 root INFO copying ansible_collections/cisco/dnac/plugins/modules/itsm_integration_events_retry.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,590 root INFO copying ansible_collections/cisco/dnac/plugins/modules/lan_automation_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,591 root INFO copying ansible_collections/cisco/dnac/plugins/modules/lan_automation_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,591 root INFO copying ansible_collections/cisco/dnac/plugins/modules/lan_automation_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,591 root INFO copying ansible_collections/cisco/dnac/plugins/modules/lan_automation_log_by_serial_number_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,591 root INFO copying ansible_collections/cisco/dnac/plugins/modules/lan_automation_log_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,592 root INFO copying ansible_collections/cisco/dnac/plugins/modules/lan_automation_status_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,592 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,592 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_device_deregistration.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,592 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_device_license_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,593 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_device_license_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,593 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_device_registration.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,593 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_smart_account_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,593 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_term_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,593 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_usage_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,594 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_virtual_account_change.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,594 root INFO copying ansible_collections/cisco/dnac/plugins/modules/license_virtual_account_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,594 root INFO copying ansible_collections/cisco/dnac/plugins/modules/netconf_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,594 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,595 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,595 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_by_ip_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,595 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_by_serial_number_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,595 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_chassis_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,595 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_config_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,596 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_config_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,596 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,596 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_custom_prompt.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,596 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_custom_prompt_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,597 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_equipment_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,597 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_export.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,597 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_functional_capability_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,597 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_global_polling_interval_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,598 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,598 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_interface_neighbor_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,598 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_interface_poe_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,598 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_inventory_insight_link_mismatch_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,598 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_lexicographically_sorted_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,599 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_linecard_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,599 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_meraki_organization_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,599 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_module_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,599 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_module_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,600 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_poe_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,600 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_polling_interval_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,600 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_range_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,600 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_register_for_wsa_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,601 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_stack_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,601 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,601 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_supervisor_card_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,601 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_sync.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,601 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_update_role.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,602 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_user_defined_field.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,602 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_user_defined_field_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,602 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_vlan_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,602 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_wireless_lan_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,603 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_device_with_snmp_v3_des_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,603 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,603 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,603 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,603 root INFO copying ansible_collections/cisco/dnac/plugins/modules/network_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,604 root INFO copying ansible_collections/cisco/dnac/plugins/modules/nfv_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,604 root INFO copying ansible_collections/cisco/dnac/plugins/modules/nfv_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,604 root INFO copying ansible_collections/cisco/dnac/plugins/modules/nfv_provision.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,604 root INFO copying ansible_collections/cisco/dnac/plugins/modules/nfv_provision_detail_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,605 root INFO copying ansible_collections/cisco/dnac/plugins/modules/nfv_provision_details.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,605 root INFO copying ansible_collections/cisco/dnac/plugins/modules/path_trace.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,605 root INFO copying ansible_collections/cisco/dnac/plugins/modules/path_trace_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,605 root INFO copying ansible_collections/cisco/dnac/plugins/modules/planned_access_points_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,606 root INFO copying ansible_collections/cisco/dnac/plugins/modules/platform_nodes_configuration_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,606 root INFO copying ansible_collections/cisco/dnac/plugins/modules/platform_release_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,606 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,606 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_authorize.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,607 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_claim.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,607 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_claim_to_site.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,607 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_config_preview.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,607 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,608 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_history_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,608 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_import.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,608 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,608 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_reset.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,609 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_device_unclaim.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,609 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_global_settings.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,609 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_global_settings_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,609 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_intent.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,609 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_server_profile_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,610 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_smart_account_domains_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,610 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_add.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,610 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_deregister.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,610 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_devices_sync.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,611 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_sync_result_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,611 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_accounts_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,611 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_workflow.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,611 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_workflow_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,612 root INFO copying ansible_collections/cisco/dnac/plugins/modules/pnp_workflow_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,612 root INFO copying ansible_collections/cisco/dnac/plugins/modules/profiling_rules_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,612 root INFO copying ansible_collections/cisco/dnac/plugins/modules/profiling_rules_in_bulk_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,612 root INFO copying ansible_collections/cisco/dnac/plugins/modules/projects_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,612 root INFO copying ansible_collections/cisco/dnac/plugins/modules/qos_device_interface.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,613 root INFO copying ansible_collections/cisco/dnac/plugins/modules/qos_device_interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,613 root INFO copying ansible_collections/cisco/dnac/plugins/modules/qos_device_interface_info_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,613 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reports.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,613 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reports_executions_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,614 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reports_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,614 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reports_view_group_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,614 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reports_view_group_view_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,614 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,615 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,615 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,615 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,615 root INFO copying ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,615 root INFO copying ansible_collections/cisco/dnac/plugins/modules/role_permissions_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,616 root INFO copying ansible_collections/cisco/dnac/plugins/modules/roles_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,616 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,616 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,616 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_device_role_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,617 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,617 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_authentication_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,617 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_authentication_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,617 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_border_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,617 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_border_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,618 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_control_plane_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,618 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_control_plane_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,618 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_edge_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,618 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_edge_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,619 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,619 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_site.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,619 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_fabric_site_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,619 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_multicast.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,620 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_multicast_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,620 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_access_point.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,620 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_access_point_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,620 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_user_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,620 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_user_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,621 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_provision_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,621 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_provision_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,621 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,621 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,622 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_ip_pool.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,622 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_ip_pool_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,622 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,622 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,622 root INFO copying ansible_collections/cisco/dnac/plugins/modules/security_advisories_devices_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,623 root INFO copying ansible_collections/cisco/dnac/plugins/modules/security_advisories_ids_per_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,623 root INFO copying ansible_collections/cisco/dnac/plugins/modules/security_advisories_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,623 root INFO copying ansible_collections/cisco/dnac/plugins/modules/security_advisories_per_device_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,623 root INFO copying ansible_collections/cisco/dnac/plugins/modules/security_advisories_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,624 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sensor.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,624 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sensor_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,624 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sensor_test_run.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,624 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sensor_test_template_duplicate.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,625 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sensor_test_template_edit.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,625 root INFO copying ansible_collections/cisco/dnac/plugins/modules/service_provider_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,625 root INFO copying ansible_collections/cisco/dnac/plugins/modules/service_provider_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,625 root INFO copying ansible_collections/cisco/dnac/plugins/modules/service_provider_profile_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,625 root INFO copying ansible_collections/cisco/dnac/plugins/modules/service_provider_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,626 root INFO copying ansible_collections/cisco/dnac/plugins/modules/service_provider_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,626 root INFO copying ansible_collections/cisco/dnac/plugins/modules/service_provider_v2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,626 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_assign_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,626 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_assign_device.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,627 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,627 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,627 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_delete.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,627 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_design_floormap.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,627 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_design_floormap_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,628 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,628 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,628 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_intent.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,628 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_membership_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,629 root INFO copying ansible_collections/cisco/dnac/plugins/modules/site_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,629 root INFO copying ansible_collections/cisco/dnac/plugins/modules/snmp_properties.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,629 root INFO copying ansible_collections/cisco/dnac/plugins/modules/snmp_properties_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,630 root INFO copying ansible_collections/cisco/dnac/plugins/modules/snmpv2_read_community_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,630 root INFO copying ansible_collections/cisco/dnac/plugins/modules/snmpv2_write_community_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,630 root INFO copying ansible_collections/cisco/dnac/plugins/modules/snmpv3_credential.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,630 root INFO copying ansible_collections/cisco/dnac/plugins/modules/sp_profile_delete_v2.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,631 root INFO copying ansible_collections/cisco/dnac/plugins/modules/swim_image_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,631 root INFO copying ansible_collections/cisco/dnac/plugins/modules/swim_import_local.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,631 root INFO copying ansible_collections/cisco/dnac/plugins/modules/swim_import_via_url.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,631 root INFO copying ansible_collections/cisco/dnac/plugins/modules/swim_intent.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,632 root INFO copying ansible_collections/cisco/dnac/plugins/modules/swim_trigger_activation.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,632 root INFO copying ansible_collections/cisco/dnac/plugins/modules/swim_trigger_distribution.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,632 root INFO copying ansible_collections/cisco/dnac/plugins/modules/syslog_config_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,632 root INFO copying ansible_collections/cisco/dnac/plugins/modules/syslog_config_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,632 root INFO copying ansible_collections/cisco/dnac/plugins/modules/system_health_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,633 root INFO copying ansible_collections/cisco/dnac/plugins/modules/system_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,633 root INFO copying ansible_collections/cisco/dnac/plugins/modules/system_performance_historical_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,633 root INFO copying ansible_collections/cisco/dnac/plugins/modules/system_performance_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,633 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,634 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,634 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,634 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag_member.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,634 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag_member_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,634 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag_member_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,635 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag_member_type_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,635 root INFO copying ansible_collections/cisco/dnac/plugins/modules/tag_membership.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,635 root INFO copying ansible_collections/cisco/dnac/plugins/modules/task_count_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,635 root INFO copying ansible_collections/cisco/dnac/plugins/modules/task_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,636 root INFO copying ansible_collections/cisco/dnac/plugins/modules/task_operation_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,636 root INFO copying ansible_collections/cisco/dnac/plugins/modules/task_tree_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,636 root INFO copying ansible_collections/cisco/dnac/plugins/modules/template_intent.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,636 root INFO copying ansible_collections/cisco/dnac/plugins/modules/template_preview.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,637 root INFO copying ansible_collections/cisco/dnac/plugins/modules/templates_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,637 root INFO copying ansible_collections/cisco/dnac/plugins/modules/threat_detail.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,637 root INFO copying ansible_collections/cisco/dnac/plugins/modules/threat_detail_count.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,637 root INFO copying ansible_collections/cisco/dnac/plugins/modules/threat_summary.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,637 root INFO copying ansible_collections/cisco/dnac/plugins/modules/topology_layer_2_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,638 root INFO copying ansible_collections/cisco/dnac/plugins/modules/topology_layer_3_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,638 root INFO copying ansible_collections/cisco/dnac/plugins/modules/topology_network_health_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,638 root INFO copying ansible_collections/cisco/dnac/plugins/modules/topology_physical_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,638 root INFO copying ansible_collections/cisco/dnac/plugins/modules/topology_site_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,639 root INFO copying ansible_collections/cisco/dnac/plugins/modules/topology_vlan_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,639 root INFO copying ansible_collections/cisco/dnac/plugins/modules/transit_peer_network.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,639 root INFO copying ansible_collections/cisco/dnac/plugins/modules/transit_peer_network_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,639 root INFO copying ansible_collections/cisco/dnac/plugins/modules/user.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,639 root INFO copying ansible_collections/cisco/dnac/plugins/modules/user_enrichment_details_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,640 root INFO copying ansible_collections/cisco/dnac/plugins/modules/user_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,640 root INFO copying ansible_collections/cisco/dnac/plugins/modules/users_external_servers_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,640 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_accespoint_configuration.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,640 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_accesspoint_configuration_summary_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,641 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_dynamic_interface.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,641 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_dynamic_interface_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,641 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_enterprise_ssid.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,641 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_enterprise_ssid_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,642 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,642 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,642 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_provision_access_point.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,642 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_provision_device_create.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,642 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_provision_device_update.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,643 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_provision_ssid_create_provision.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,643 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_provision_ssid_delete_reprovision.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,643 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_psk_override.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,643 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_rf_profile.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,644 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_rf_profile_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,644 root INFO copying ansible_collections/cisco/dnac/plugins/modules/wireless_sensor_test_results_info.py -> build/lib/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:40,644 root INFO creating build/lib/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:40,644 root INFO copying ansible_collections/cisco/dnac/plugins/plugin_utils/__init__.py -> build/lib/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:40,644 root INFO copying ansible_collections/cisco/dnac/plugins/plugin_utils/dnac.py -> build/lib/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:40,645 root INFO copying ansible_collections/cisco/dnac/plugins/plugin_utils/exceptions.py -> build/lib/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:40,645 root INFO creating build/lib/ansible_collections/cisco/intersight 2023-04-28 05:57:40,645 root INFO copying ansible_collections/cisco/intersight/Development.md -> build/lib/ansible_collections/cisco/intersight 2023-04-28 05:57:40,645 root INFO copying ansible_collections/cisco/intersight/FILES.json -> build/lib/ansible_collections/cisco/intersight 2023-04-28 05:57:40,646 root INFO copying ansible_collections/cisco/intersight/LICENSE.txt -> build/lib/ansible_collections/cisco/intersight 2023-04-28 05:57:40,646 root INFO copying ansible_collections/cisco/intersight/MANIFEST.json -> build/lib/ansible_collections/cisco/intersight 2023-04-28 05:57:40,646 root INFO copying ansible_collections/cisco/intersight/README.md -> build/lib/ansible_collections/cisco/intersight 2023-04-28 05:57:40,646 root INFO copying ansible_collections/cisco/intersight/requirements.txt -> build/lib/ansible_collections/cisco/intersight 2023-04-28 05:57:40,646 root INFO creating build/lib/ansible_collections/cisco/intersight/meta 2023-04-28 05:57:40,647 root INFO copying ansible_collections/cisco/intersight/meta/execution-environment.yml -> build/lib/ansible_collections/cisco/intersight/meta 2023-04-28 05:57:40,647 root INFO copying ansible_collections/cisco/intersight/meta/runtime.yml -> build/lib/ansible_collections/cisco/intersight/meta 2023-04-28 05:57:40,647 root INFO creating build/lib/ansible_collections/cisco/intersight/misc 2023-04-28 05:57:40,647 root INFO copying ansible_collections/cisco/intersight/misc/CL2020 EMEAR DEVWKS-1542 Intersight Ansible Lab Guide.pdf -> build/lib/ansible_collections/cisco/intersight/misc 2023-04-28 05:57:40,649 root INFO copying ansible_collections/cisco/intersight/misc/README.md -> build/lib/ansible_collections/cisco/intersight/misc 2023-04-28 05:57:40,649 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,649 root INFO copying ansible_collections/cisco/intersight/playbooks/claim_device.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,649 root INFO copying ansible_collections/cisco/intersight/playbooks/cos_server_policies_and_profiles.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,650 root INFO copying ansible_collections/cisco/intersight/playbooks/deploy_server_profiles.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,650 root INFO copying ansible_collections/cisco/intersight/playbooks/derive_profiles.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,650 root INFO copying ansible_collections/cisco/intersight/playbooks/devnet_inventory -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,650 root INFO copying ansible_collections/cisco/intersight/playbooks/example_hx_host_vars -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,651 root INFO copying ansible_collections/cisco/intersight/playbooks/example_imm_inventory -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,651 root INFO copying ansible_collections/cisco/intersight/playbooks/example_inventory -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,651 root INFO copying ansible_collections/cisco/intersight/playbooks/firmware_direct_download.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,651 root INFO copying ansible_collections/cisco/intersight/playbooks/hcl_status.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,652 root INFO copying ansible_collections/cisco/intersight/playbooks/hyperflex_cluster_profiles.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,652 root INFO copying ansible_collections/cisco/intersight/playbooks/hyperflex_edge_cluster_profiles.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,652 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_boot_order_policy.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,652 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_domain_profile.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,653 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_eth_network.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,653 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_imc_access_policy.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,653 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_lan_connectivity_policy.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,653 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_local_user_policy.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,654 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_ntp_policy.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,654 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_port_policy.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,654 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_server_profile.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,654 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_server_profile_template.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,654 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_virtual_media_policy.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,655 root INFO copying ansible_collections/cisco/intersight/playbooks/intersight_vm_hosts.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,655 root INFO copying ansible_collections/cisco/intersight/playbooks/only_new_server_profiles.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,655 root INFO copying ansible_collections/cisco/intersight/playbooks/os_install.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,655 root INFO copying ansible_collections/cisco/intersight/playbooks/ova_workflow.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,656 root INFO copying ansible_collections/cisco/intersight/playbooks/profile_inventory -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,656 root INFO copying ansible_collections/cisco/intersight/playbooks/profile_with_buckets.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,656 root INFO copying ansible_collections/cisco/intersight/playbooks/pxe_boot.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,656 root INFO copying ansible_collections/cisco/intersight/playbooks/server_actions.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,656 root INFO copying ansible_collections/cisco/intersight/playbooks/server_firmware.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,657 root INFO copying ansible_collections/cisco/intersight/playbooks/servers_to_file.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,657 root INFO copying ansible_collections/cisco/intersight/playbooks/update_all_inventory.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,657 root INFO copying ansible_collections/cisco/intersight/playbooks/update_hx_edge_inventory.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,657 root INFO copying ansible_collections/cisco/intersight/playbooks/update_hx_inventory.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,658 root INFO copying ansible_collections/cisco/intersight/playbooks/update_standalone_inventory.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,658 root INFO copying ansible_collections/cisco/intersight/playbooks/vault_intersight_server_profile.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,658 root INFO copying ansible_collections/cisco/intersight/playbooks/vlans_to_file.yml -> build/lib/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:40,658 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles 2023-04-28 05:57:40,658 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies 2023-04-28 05:57:40,659 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies 2023-04-28 05:57:40,659 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support 2023-04-28 05:57:40,659 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support/tasks 2023-04-28 05:57:40,659 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support/tasks 2023-04-28 05:57:40,659 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network 2023-04-28 05:57:40,659 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network/tasks 2023-04-28 05:57:40,659 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network/tasks 2023-04-28 05:57:40,660 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile 2023-04-28 05:57:40,660 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/defaults 2023-04-28 05:57:40,660 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/defaults/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/defaults 2023-04-28 05:57:40,660 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/tasks 2023-04-28 05:57:40,660 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/tasks 2023-04-28 05:57:40,660 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage 2023-04-28 05:57:40,661 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage/tasks 2023-04-28 05:57:40,661 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage/tasks 2023-04-28 05:57:40,661 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy 2023-04-28 05:57:40,661 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy/tasks 2023-04-28 05:57:40,661 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy/tasks 2023-04-28 05:57:40,661 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network 2023-04-28 05:57:40,661 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network/tasks 2023-04-28 05:57:40,662 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network/tasks 2023-04-28 05:57:40,662 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile 2023-04-28 05:57:40,662 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/defaults 2023-04-28 05:57:40,662 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/defaults/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/defaults 2023-04-28 05:57:40,662 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/tasks 2023-04-28 05:57:40,662 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/tasks 2023-04-28 05:57:40,663 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage 2023-04-28 05:57:40,663 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage/tasks 2023-04-28 05:57:40,663 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage/tasks 2023-04-28 05:57:40,663 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version 2023-04-28 05:57:40,663 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version/tasks 2023-04-28 05:57:40,663 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version/tasks 2023-04-28 05:57:40,664 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc 2023-04-28 05:57:40,664 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc/tasks 2023-04-28 05:57:40,664 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc/tasks 2023-04-28 05:57:40,664 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org 2023-04-28 05:57:40,664 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org/tasks 2023-04-28 05:57:40,664 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org/tasks 2023-04-28 05:57:40,665 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi 2023-04-28 05:57:40,665 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi/tasks 2023-04-28 05:57:40,665 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi/tasks 2023-04-28 05:57:40,665 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential 2023-04-28 05:57:40,665 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential/tasks 2023-04-28 05:57:40,665 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential/tasks 2023-04-28 05:57:40,665 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config 2023-04-28 05:57:40,666 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config/tasks 2023-04-28 05:57:40,666 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config/tasks 2023-04-28 05:57:40,666 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles 2023-04-28 05:57:40,666 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles/tasks 2023-04-28 05:57:40,666 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles/tasks 2023-04-28 05:57:40,666 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy 2023-04-28 05:57:40,667 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy/tasks 2023-04-28 05:57:40,667 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy/tasks 2023-04-28 05:57:40,667 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version 2023-04-28 05:57:40,667 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version/tasks 2023-04-28 05:57:40,667 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version/tasks 2023-04-28 05:57:40,667 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config 2023-04-28 05:57:40,667 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config/tasks 2023-04-28 05:57:40,668 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config/tasks 2023-04-28 05:57:40,668 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter 2023-04-28 05:57:40,668 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter/tasks 2023-04-28 05:57:40,668 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter/tasks 2023-04-28 05:57:40,668 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies 2023-04-28 05:57:40,668 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies/tasks 2023-04-28 05:57:40,669 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies/tasks 2023-04-28 05:57:40,669 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/servers 2023-04-28 05:57:40,669 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/servers/actions 2023-04-28 05:57:40,669 root INFO creating build/lib/ansible_collections/cisco/intersight/playbooks/roles/servers/actions/tasks 2023-04-28 05:57:40,669 root INFO copying ansible_collections/cisco/intersight/playbooks/roles/servers/actions/tasks/main.yml -> build/lib/ansible_collections/cisco/intersight/playbooks/roles/servers/actions/tasks 2023-04-28 05:57:40,669 root INFO creating build/lib/ansible_collections/cisco/intersight/plugins 2023-04-28 05:57:40,669 root INFO copying ansible_collections/cisco/intersight/plugins/README.md -> build/lib/ansible_collections/cisco/intersight/plugins 2023-04-28 05:57:40,670 root INFO creating build/lib/ansible_collections/cisco/intersight/plugins/doc_fragments 2023-04-28 05:57:40,670 root INFO copying ansible_collections/cisco/intersight/plugins/doc_fragments/intersight.py -> build/lib/ansible_collections/cisco/intersight/plugins/doc_fragments 2023-04-28 05:57:40,670 root INFO creating build/lib/ansible_collections/cisco/intersight/plugins/module_utils 2023-04-28 05:57:40,670 root INFO copying ansible_collections/cisco/intersight/plugins/module_utils/intersight.py -> build/lib/ansible_collections/cisco/intersight/plugins/module_utils 2023-04-28 05:57:40,670 root INFO creating build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,671 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_boot_order_policy.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,671 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_imc_access_policy.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,671 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_info.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,671 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_local_user_policy.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,672 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_ntp_policy.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,672 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_rest_api.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,672 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_server_profile.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,672 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_target_claim.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,672 root INFO copying ansible_collections/cisco/intersight/plugins/modules/intersight_virtual_media_policy.py -> build/lib/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:40,673 root INFO creating build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,673 root INFO copying ansible_collections/cisco/ios/CHANGELOG.rst -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,673 root INFO copying ansible_collections/cisco/ios/FILES.json -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,674 root INFO copying ansible_collections/cisco/ios/LICENSE -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,674 root INFO copying ansible_collections/cisco/ios/MANIFEST.json -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,674 root INFO copying ansible_collections/cisco/ios/README.md -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,674 root INFO copying ansible_collections/cisco/ios/bindep.txt -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,675 root INFO copying ansible_collections/cisco/ios/codecov.yml -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,675 root INFO copying ansible_collections/cisco/ios/pyproject.toml -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,675 root INFO copying ansible_collections/cisco/ios/requirements.txt -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,675 root INFO copying ansible_collections/cisco/ios/test-requirements.txt -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,675 root INFO copying ansible_collections/cisco/ios/tox.ini -> build/lib/ansible_collections/cisco/ios 2023-04-28 05:57:40,676 root INFO creating build/lib/ansible_collections/cisco/ios/changelogs 2023-04-28 05:57:40,676 root INFO copying ansible_collections/cisco/ios/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/ios/changelogs 2023-04-28 05:57:40,676 root INFO copying ansible_collections/cisco/ios/changelogs/config.yaml -> build/lib/ansible_collections/cisco/ios/changelogs 2023-04-28 05:57:40,676 root INFO creating build/lib/ansible_collections/cisco/ios/changelogs/fragments 2023-04-28 05:57:40,676 root INFO copying ansible_collections/cisco/ios/changelogs/fragments/.keep -> build/lib/ansible_collections/cisco/ios/changelogs/fragments 2023-04-28 05:57:40,677 root INFO creating build/lib/ansible_collections/cisco/ios/meta 2023-04-28 05:57:40,677 root INFO copying ansible_collections/cisco/ios/meta/runtime.yml -> build/lib/ansible_collections/cisco/ios/meta 2023-04-28 05:57:40,677 root INFO creating build/lib/ansible_collections/cisco/ios/plugins 2023-04-28 05:57:40,677 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,677 root INFO copying ansible_collections/cisco/ios/plugins/action/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,678 root INFO copying ansible_collections/cisco/ios/plugins/action/acl_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,678 root INFO copying ansible_collections/cisco/ios/plugins/action/acls.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,678 root INFO copying ansible_collections/cisco/ios/plugins/action/banner.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,678 root INFO copying ansible_collections/cisco/ios/plugins/action/bgp.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,678 root INFO copying ansible_collections/cisco/ios/plugins/action/bgp_address_family.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,679 root INFO copying ansible_collections/cisco/ios/plugins/action/bgp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,679 root INFO copying ansible_collections/cisco/ios/plugins/action/command.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,679 root INFO copying ansible_collections/cisco/ios/plugins/action/config.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,679 root INFO copying ansible_collections/cisco/ios/plugins/action/facts.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,679 root INFO copying ansible_collections/cisco/ios/plugins/action/hostname.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,680 root INFO copying ansible_collections/cisco/ios/plugins/action/interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,680 root INFO copying ansible_collections/cisco/ios/plugins/action/ios.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,680 root INFO copying ansible_collections/cisco/ios/plugins/action/l2_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,680 root INFO copying ansible_collections/cisco/ios/plugins/action/l3_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,681 root INFO copying ansible_collections/cisco/ios/plugins/action/lacp.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,681 root INFO copying ansible_collections/cisco/ios/plugins/action/lacp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,681 root INFO copying ansible_collections/cisco/ios/plugins/action/lag_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,681 root INFO copying ansible_collections/cisco/ios/plugins/action/linkagg.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,681 root INFO copying ansible_collections/cisco/ios/plugins/action/lldp.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,682 root INFO copying ansible_collections/cisco/ios/plugins/action/lldp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,682 root INFO copying ansible_collections/cisco/ios/plugins/action/lldp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,682 root INFO copying ansible_collections/cisco/ios/plugins/action/logging.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,682 root INFO copying ansible_collections/cisco/ios/plugins/action/logging_global.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,683 root INFO copying ansible_collections/cisco/ios/plugins/action/ntp.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,683 root INFO copying ansible_collections/cisco/ios/plugins/action/ntp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,683 root INFO copying ansible_collections/cisco/ios/plugins/action/ospf_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,683 root INFO copying ansible_collections/cisco/ios/plugins/action/ospfv2.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,683 root INFO copying ansible_collections/cisco/ios/plugins/action/ospfv3.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,684 root INFO copying ansible_collections/cisco/ios/plugins/action/ping.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,684 root INFO copying ansible_collections/cisco/ios/plugins/action/prefix_lists.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,684 root INFO copying ansible_collections/cisco/ios/plugins/action/route_maps.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,684 root INFO copying ansible_collections/cisco/ios/plugins/action/snmp_server.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,685 root INFO copying ansible_collections/cisco/ios/plugins/action/static_routes.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,685 root INFO copying ansible_collections/cisco/ios/plugins/action/system.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,685 root INFO copying ansible_collections/cisco/ios/plugins/action/user.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,685 root INFO copying ansible_collections/cisco/ios/plugins/action/vlans.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,685 root INFO copying ansible_collections/cisco/ios/plugins/action/vrf.py -> build/lib/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:40,686 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/cliconf 2023-04-28 05:57:40,686 root INFO copying ansible_collections/cisco/ios/plugins/cliconf/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/cliconf 2023-04-28 05:57:40,686 root INFO copying ansible_collections/cisco/ios/plugins/cliconf/ios.py -> build/lib/ansible_collections/cisco/ios/plugins/cliconf 2023-04-28 05:57:40,686 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/doc_fragments 2023-04-28 05:57:40,686 root INFO copying ansible_collections/cisco/ios/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/doc_fragments 2023-04-28 05:57:40,687 root INFO copying ansible_collections/cisco/ios/plugins/doc_fragments/ios.py -> build/lib/ansible_collections/cisco/ios/plugins/doc_fragments 2023-04-28 05:57:40,687 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/filter 2023-04-28 05:57:40,687 root INFO copying ansible_collections/cisco/ios/plugins/filter/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/filter 2023-04-28 05:57:40,687 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/inventory 2023-04-28 05:57:40,687 root INFO copying ansible_collections/cisco/ios/plugins/inventory/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/inventory 2023-04-28 05:57:40,688 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils 2023-04-28 05:57:40,688 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils 2023-04-28 05:57:40,688 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network 2023-04-28 05:57:40,688 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network 2023-04-28 05:57:40,688 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios 2023-04-28 05:57:40,688 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios 2023-04-28 05:57:40,689 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/ios.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios 2023-04-28 05:57:40,689 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec 2023-04-28 05:57:40,689 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec 2023-04-28 05:57:40,689 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces 2023-04-28 05:57:40,689 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces 2023-04-28 05:57:40,689 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces 2023-04-28 05:57:40,690 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls 2023-04-28 05:57:40,690 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls 2023-04-28 05:57:40,690 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/acls.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls 2023-04-28 05:57:40,690 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family 2023-04-28 05:57:40,690 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family 2023-04-28 05:57:40,691 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family 2023-04-28 05:57:40,691 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global 2023-04-28 05:57:40,691 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global 2023-04-28 05:57:40,691 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global 2023-04-28 05:57:40,692 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts 2023-04-28 05:57:40,692 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts 2023-04-28 05:57:40,692 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/facts.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts 2023-04-28 05:57:40,692 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname 2023-04-28 05:57:40,692 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname 2023-04-28 05:57:40,692 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/hostname.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname 2023-04-28 05:57:40,693 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces 2023-04-28 05:57:40,693 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces 2023-04-28 05:57:40,693 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces 2023-04-28 05:57:40,693 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces 2023-04-28 05:57:40,693 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces 2023-04-28 05:57:40,694 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces 2023-04-28 05:57:40,694 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces 2023-04-28 05:57:40,694 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces 2023-04-28 05:57:40,694 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces 2023-04-28 05:57:40,694 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp 2023-04-28 05:57:40,695 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp 2023-04-28 05:57:40,695 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/lacp.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp 2023-04-28 05:57:40,695 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces 2023-04-28 05:57:40,695 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces 2023-04-28 05:57:40,695 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces 2023-04-28 05:57:40,696 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces 2023-04-28 05:57:40,696 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces 2023-04-28 05:57:40,696 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces 2023-04-28 05:57:40,696 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global 2023-04-28 05:57:40,696 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global 2023-04-28 05:57:40,696 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global 2023-04-28 05:57:40,697 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces 2023-04-28 05:57:40,697 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces 2023-04-28 05:57:40,697 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces 2023-04-28 05:57:40,697 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global 2023-04-28 05:57:40,697 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global 2023-04-28 05:57:40,698 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global 2023-04-28 05:57:40,698 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global 2023-04-28 05:57:40,698 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global 2023-04-28 05:57:40,698 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global 2023-04-28 05:57:40,698 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces 2023-04-28 05:57:40,699 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces 2023-04-28 05:57:40,699 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces 2023-04-28 05:57:40,699 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2 2023-04-28 05:57:40,699 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2 2023-04-28 05:57:40,699 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2 2023-04-28 05:57:40,700 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3 2023-04-28 05:57:40,700 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3 2023-04-28 05:57:40,700 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3 2023-04-28 05:57:40,700 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping 2023-04-28 05:57:40,700 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping 2023-04-28 05:57:40,701 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/ping.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping 2023-04-28 05:57:40,701 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists 2023-04-28 05:57:40,701 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists 2023-04-28 05:57:40,701 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists 2023-04-28 05:57:40,701 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps 2023-04-28 05:57:40,702 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps 2023-04-28 05:57:40,702 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/route_maps.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps 2023-04-28 05:57:40,702 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server 2023-04-28 05:57:40,702 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server 2023-04-28 05:57:40,702 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server 2023-04-28 05:57:40,703 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes 2023-04-28 05:57:40,703 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes 2023-04-28 05:57:40,703 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes 2023-04-28 05:57:40,703 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans 2023-04-28 05:57:40,703 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans 2023-04-28 05:57:40,704 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/vlans.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans 2023-04-28 05:57:40,704 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config 2023-04-28 05:57:40,704 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config 2023-04-28 05:57:40,704 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces 2023-04-28 05:57:40,704 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces 2023-04-28 05:57:40,705 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces 2023-04-28 05:57:40,705 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls 2023-04-28 05:57:40,705 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls 2023-04-28 05:57:40,705 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/acls.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls 2023-04-28 05:57:40,705 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family 2023-04-28 05:57:40,705 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family 2023-04-28 05:57:40,706 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family 2023-04-28 05:57:40,706 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global 2023-04-28 05:57:40,706 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global 2023-04-28 05:57:40,706 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global 2023-04-28 05:57:40,707 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname 2023-04-28 05:57:40,707 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname 2023-04-28 05:57:40,707 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/hostname.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname 2023-04-28 05:57:40,707 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces 2023-04-28 05:57:40,707 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces 2023-04-28 05:57:40,707 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces 2023-04-28 05:57:40,708 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces 2023-04-28 05:57:40,708 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces 2023-04-28 05:57:40,708 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces 2023-04-28 05:57:40,708 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces 2023-04-28 05:57:40,708 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces 2023-04-28 05:57:40,709 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces 2023-04-28 05:57:40,709 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp 2023-04-28 05:57:40,709 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp 2023-04-28 05:57:40,709 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/lacp.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp 2023-04-28 05:57:40,709 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces 2023-04-28 05:57:40,710 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces 2023-04-28 05:57:40,710 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces 2023-04-28 05:57:40,710 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces 2023-04-28 05:57:40,710 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces 2023-04-28 05:57:40,710 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces 2023-04-28 05:57:40,711 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global 2023-04-28 05:57:40,711 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global 2023-04-28 05:57:40,711 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global 2023-04-28 05:57:40,711 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces 2023-04-28 05:57:40,711 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces 2023-04-28 05:57:40,712 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces 2023-04-28 05:57:40,712 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global 2023-04-28 05:57:40,712 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global 2023-04-28 05:57:40,712 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global 2023-04-28 05:57:40,712 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global 2023-04-28 05:57:40,712 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global 2023-04-28 05:57:40,713 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global 2023-04-28 05:57:40,713 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces 2023-04-28 05:57:40,713 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces 2023-04-28 05:57:40,713 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces 2023-04-28 05:57:40,714 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2 2023-04-28 05:57:40,714 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2 2023-04-28 05:57:40,714 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2 2023-04-28 05:57:40,714 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3 2023-04-28 05:57:40,714 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3 2023-04-28 05:57:40,714 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3 2023-04-28 05:57:40,715 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping 2023-04-28 05:57:40,715 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping 2023-04-28 05:57:40,715 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/ping.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping 2023-04-28 05:57:40,715 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists 2023-04-28 05:57:40,715 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists 2023-04-28 05:57:40,716 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists 2023-04-28 05:57:40,716 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps 2023-04-28 05:57:40,716 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps 2023-04-28 05:57:40,716 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/route_maps.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps 2023-04-28 05:57:40,716 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server 2023-04-28 05:57:40,717 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server 2023-04-28 05:57:40,717 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server 2023-04-28 05:57:40,717 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes 2023-04-28 05:57:40,717 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes 2023-04-28 05:57:40,717 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes 2023-04-28 05:57:40,718 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans 2023-04-28 05:57:40,718 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans 2023-04-28 05:57:40,718 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/vlans.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans 2023-04-28 05:57:40,718 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts 2023-04-28 05:57:40,718 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts 2023-04-28 05:57:40,719 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/facts.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts 2023-04-28 05:57:40,719 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces 2023-04-28 05:57:40,719 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces 2023-04-28 05:57:40,719 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces 2023-04-28 05:57:40,719 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls 2023-04-28 05:57:40,720 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls 2023-04-28 05:57:40,720 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/acls.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls 2023-04-28 05:57:40,720 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family 2023-04-28 05:57:40,720 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family 2023-04-28 05:57:40,720 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family 2023-04-28 05:57:40,721 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global 2023-04-28 05:57:40,721 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global 2023-04-28 05:57:40,721 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global 2023-04-28 05:57:40,721 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname 2023-04-28 05:57:40,721 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname 2023-04-28 05:57:40,721 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/hostname.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname 2023-04-28 05:57:40,722 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces 2023-04-28 05:57:40,722 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces 2023-04-28 05:57:40,722 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces 2023-04-28 05:57:40,722 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces 2023-04-28 05:57:40,722 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces 2023-04-28 05:57:40,723 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces 2023-04-28 05:57:40,723 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces 2023-04-28 05:57:40,723 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces 2023-04-28 05:57:40,723 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces 2023-04-28 05:57:40,723 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp 2023-04-28 05:57:40,724 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp 2023-04-28 05:57:40,724 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/lacp.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp 2023-04-28 05:57:40,724 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces 2023-04-28 05:57:40,724 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces 2023-04-28 05:57:40,724 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces 2023-04-28 05:57:40,725 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces 2023-04-28 05:57:40,725 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces 2023-04-28 05:57:40,725 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces 2023-04-28 05:57:40,725 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy 2023-04-28 05:57:40,725 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy 2023-04-28 05:57:40,725 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/base.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy 2023-04-28 05:57:40,726 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global 2023-04-28 05:57:40,726 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global 2023-04-28 05:57:40,726 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global 2023-04-28 05:57:40,726 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces 2023-04-28 05:57:40,726 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces 2023-04-28 05:57:40,727 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces 2023-04-28 05:57:40,727 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global 2023-04-28 05:57:40,727 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global 2023-04-28 05:57:40,727 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global 2023-04-28 05:57:40,727 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global 2023-04-28 05:57:40,728 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global 2023-04-28 05:57:40,728 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global 2023-04-28 05:57:40,728 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces 2023-04-28 05:57:40,728 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces 2023-04-28 05:57:40,728 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces 2023-04-28 05:57:40,729 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2 2023-04-28 05:57:40,729 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2 2023-04-28 05:57:40,729 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2 2023-04-28 05:57:40,729 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3 2023-04-28 05:57:40,729 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3 2023-04-28 05:57:40,730 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3 2023-04-28 05:57:40,730 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists 2023-04-28 05:57:40,730 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists 2023-04-28 05:57:40,730 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists 2023-04-28 05:57:40,730 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps 2023-04-28 05:57:40,730 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps 2023-04-28 05:57:40,731 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/route_maps.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps 2023-04-28 05:57:40,731 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server 2023-04-28 05:57:40,731 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server 2023-04-28 05:57:40,731 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server 2023-04-28 05:57:40,731 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes 2023-04-28 05:57:40,732 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes 2023-04-28 05:57:40,732 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes 2023-04-28 05:57:40,732 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans 2023-04-28 05:57:40,732 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans 2023-04-28 05:57:40,732 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/vlans.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans 2023-04-28 05:57:40,733 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:40,733 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:40,733 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/module.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:40,733 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/providers.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:40,733 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli 2023-04-28 05:57:40,734 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli 2023-04-28 05:57:40,734 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config 2023-04-28 05:57:40,734 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config 2023-04-28 05:57:40,734 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/base.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config 2023-04-28 05:57:40,734 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:40,734 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:40,735 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/address_family.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:40,735 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/neighbors.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:40,735 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/process.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:40,735 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,736 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,736 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/acl_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,736 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/acls.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,736 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/bgp_address_family.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,737 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/bgp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,737 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/hostname.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,737 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,737 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/l2_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,738 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/l3_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,738 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/lag_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,738 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/logging_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,738 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ntp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,739 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospf_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,739 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospfv2.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,739 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospfv3.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,740 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ping.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,740 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/prefix_lists.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,740 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/route_maps.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,740 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/snmp_server.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,741 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/static_routes.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:40,741 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils 2023-04-28 05:57:40,741 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils 2023-04-28 05:57:40,741 root INFO copying ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/utils.py -> build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils 2023-04-28 05:57:40,742 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,742 root INFO copying ansible_collections/cisco/ios/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,742 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_acl_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,742 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_acls.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,743 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_banner.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,743 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_bgp.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,743 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_bgp_address_family.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,743 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_bgp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,744 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_command.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,744 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_config.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,744 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_facts.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,744 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_hostname.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,745 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,745 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_l2_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,745 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_l3_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,745 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_lacp.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,746 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_lacp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,746 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_lag_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,746 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_linkagg.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,746 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_lldp.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,747 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_lldp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,747 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_lldp_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,747 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_logging.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,747 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_logging_global.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,748 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_ntp.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,748 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_ntp_global.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,748 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_ospf_interfaces.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,748 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_ospfv2.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,749 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_ospfv3.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,749 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_ping.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,749 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_prefix_lists.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,750 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_route_maps.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,750 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_snmp_server.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,750 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_static_routes.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,750 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_system.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,751 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_user.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,751 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_vlans.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,751 root INFO copying ansible_collections/cisco/ios/plugins/modules/ios_vrf.py -> build/lib/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:40,751 root INFO creating build/lib/ansible_collections/cisco/ios/plugins/terminal 2023-04-28 05:57:40,752 root INFO copying ansible_collections/cisco/ios/plugins/terminal/__init__.py -> build/lib/ansible_collections/cisco/ios/plugins/terminal 2023-04-28 05:57:40,752 root INFO copying ansible_collections/cisco/ios/plugins/terminal/ios.py -> build/lib/ansible_collections/cisco/ios/plugins/terminal 2023-04-28 05:57:40,752 root INFO creating build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,752 root INFO copying ansible_collections/cisco/iosxr/CHANGELOG.rst -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,752 root INFO copying ansible_collections/cisco/iosxr/FILES.json -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,753 root INFO copying ansible_collections/cisco/iosxr/LICENSE -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,753 root INFO copying ansible_collections/cisco/iosxr/MANIFEST.json -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,754 root INFO copying ansible_collections/cisco/iosxr/README.md -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,754 root INFO copying ansible_collections/cisco/iosxr/bindep.txt -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,754 root INFO copying ansible_collections/cisco/iosxr/pyproject.toml -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,755 root INFO copying ansible_collections/cisco/iosxr/requirements.txt -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,755 root INFO copying ansible_collections/cisco/iosxr/test-requirements.txt -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,755 root INFO copying ansible_collections/cisco/iosxr/tox.ini -> build/lib/ansible_collections/cisco/iosxr 2023-04-28 05:57:40,755 root INFO creating build/lib/ansible_collections/cisco/iosxr/changelogs 2023-04-28 05:57:40,755 root INFO copying ansible_collections/cisco/iosxr/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/iosxr/changelogs 2023-04-28 05:57:40,756 root INFO copying ansible_collections/cisco/iosxr/changelogs/config.yaml -> build/lib/ansible_collections/cisco/iosxr/changelogs 2023-04-28 05:57:40,756 root INFO creating build/lib/ansible_collections/cisco/iosxr/changelogs/fragments 2023-04-28 05:57:40,756 root INFO copying ansible_collections/cisco/iosxr/changelogs/fragments/.keep -> build/lib/ansible_collections/cisco/iosxr/changelogs/fragments 2023-04-28 05:57:40,756 root INFO creating build/lib/ansible_collections/cisco/iosxr/meta 2023-04-28 05:57:40,756 root INFO copying ansible_collections/cisco/iosxr/meta/runtime.yml -> build/lib/ansible_collections/cisco/iosxr/meta 2023-04-28 05:57:40,757 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins 2023-04-28 05:57:40,757 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,757 root INFO copying ansible_collections/cisco/iosxr/plugins/action/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,757 root INFO copying ansible_collections/cisco/iosxr/plugins/action/acl_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,757 root INFO copying ansible_collections/cisco/iosxr/plugins/action/acls.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,757 root INFO copying ansible_collections/cisco/iosxr/plugins/action/banner.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,758 root INFO copying ansible_collections/cisco/iosxr/plugins/action/bgp.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,758 root INFO copying ansible_collections/cisco/iosxr/plugins/action/bgp_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,758 root INFO copying ansible_collections/cisco/iosxr/plugins/action/bgp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,758 root INFO copying ansible_collections/cisco/iosxr/plugins/action/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,759 root INFO copying ansible_collections/cisco/iosxr/plugins/action/command.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,759 root INFO copying ansible_collections/cisco/iosxr/plugins/action/config.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,759 root INFO copying ansible_collections/cisco/iosxr/plugins/action/facts.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,759 root INFO copying ansible_collections/cisco/iosxr/plugins/action/hostname.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,759 root INFO copying ansible_collections/cisco/iosxr/plugins/action/interface.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,760 root INFO copying ansible_collections/cisco/iosxr/plugins/action/interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,760 root INFO copying ansible_collections/cisco/iosxr/plugins/action/iosxr.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,760 root INFO copying ansible_collections/cisco/iosxr/plugins/action/l2_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,760 root INFO copying ansible_collections/cisco/iosxr/plugins/action/l3_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,760 root INFO copying ansible_collections/cisco/iosxr/plugins/action/lacp.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,761 root INFO copying ansible_collections/cisco/iosxr/plugins/action/lacp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,761 root INFO copying ansible_collections/cisco/iosxr/plugins/action/lag_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,761 root INFO copying ansible_collections/cisco/iosxr/plugins/action/lldp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,761 root INFO copying ansible_collections/cisco/iosxr/plugins/action/lldp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,762 root INFO copying ansible_collections/cisco/iosxr/plugins/action/logging.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,762 root INFO copying ansible_collections/cisco/iosxr/plugins/action/logging_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,762 root INFO copying ansible_collections/cisco/iosxr/plugins/action/netconf.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,762 root INFO copying ansible_collections/cisco/iosxr/plugins/action/ntp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,762 root INFO copying ansible_collections/cisco/iosxr/plugins/action/ospf_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,763 root INFO copying ansible_collections/cisco/iosxr/plugins/action/ospfv2.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,763 root INFO copying ansible_collections/cisco/iosxr/plugins/action/ospfv3.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,763 root INFO copying ansible_collections/cisco/iosxr/plugins/action/prefix_lists.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,763 root INFO copying ansible_collections/cisco/iosxr/plugins/action/snmp_server.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,764 root INFO copying ansible_collections/cisco/iosxr/plugins/action/static_routes.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,764 root INFO copying ansible_collections/cisco/iosxr/plugins/action/system.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,764 root INFO copying ansible_collections/cisco/iosxr/plugins/action/user.py -> build/lib/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:40,764 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/cliconf 2023-04-28 05:57:40,764 root INFO copying ansible_collections/cisco/iosxr/plugins/cliconf/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/cliconf 2023-04-28 05:57:40,765 root INFO copying ansible_collections/cisco/iosxr/plugins/cliconf/iosxr.py -> build/lib/ansible_collections/cisco/iosxr/plugins/cliconf 2023-04-28 05:57:40,765 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/doc_fragments 2023-04-28 05:57:40,765 root INFO copying ansible_collections/cisco/iosxr/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/doc_fragments 2023-04-28 05:57:40,765 root INFO copying ansible_collections/cisco/iosxr/plugins/doc_fragments/iosxr.py -> build/lib/ansible_collections/cisco/iosxr/plugins/doc_fragments 2023-04-28 05:57:40,765 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/filter 2023-04-28 05:57:40,765 root INFO copying ansible_collections/cisco/iosxr/plugins/filter/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/filter 2023-04-28 05:57:40,766 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/inventory 2023-04-28 05:57:40,766 root INFO copying ansible_collections/cisco/iosxr/plugins/inventory/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/inventory 2023-04-28 05:57:40,766 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils 2023-04-28 05:57:40,766 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils 2023-04-28 05:57:40,766 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network 2023-04-28 05:57:40,766 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network 2023-04-28 05:57:40,767 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr 2023-04-28 05:57:40,767 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr 2023-04-28 05:57:40,767 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/iosxr.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr 2023-04-28 05:57:40,767 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec 2023-04-28 05:57:40,767 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec 2023-04-28 05:57:40,768 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces 2023-04-28 05:57:40,768 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces 2023-04-28 05:57:40,768 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces 2023-04-28 05:57:40,768 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls 2023-04-28 05:57:40,768 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls 2023-04-28 05:57:40,769 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/acls.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls 2023-04-28 05:57:40,769 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family 2023-04-28 05:57:40,769 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family 2023-04-28 05:57:40,769 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family 2023-04-28 05:57:40,769 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global 2023-04-28 05:57:40,770 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global 2023-04-28 05:57:40,770 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global 2023-04-28 05:57:40,770 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family 2023-04-28 05:57:40,770 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family 2023-04-28 05:57:40,770 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family 2023-04-28 05:57:40,771 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts 2023-04-28 05:57:40,771 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts 2023-04-28 05:57:40,771 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/facts.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts 2023-04-28 05:57:40,771 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname 2023-04-28 05:57:40,771 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname 2023-04-28 05:57:40,772 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/hostname.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname 2023-04-28 05:57:40,772 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces 2023-04-28 05:57:40,772 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces 2023-04-28 05:57:40,772 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces 2023-04-28 05:57:40,772 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces 2023-04-28 05:57:40,773 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces 2023-04-28 05:57:40,773 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces 2023-04-28 05:57:40,773 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces 2023-04-28 05:57:40,773 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces 2023-04-28 05:57:40,773 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces 2023-04-28 05:57:40,774 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp 2023-04-28 05:57:40,774 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp 2023-04-28 05:57:40,774 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/lacp.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp 2023-04-28 05:57:40,774 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces 2023-04-28 05:57:40,774 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces 2023-04-28 05:57:40,774 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces 2023-04-28 05:57:40,775 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces 2023-04-28 05:57:40,775 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces 2023-04-28 05:57:40,775 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces 2023-04-28 05:57:40,775 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global 2023-04-28 05:57:40,775 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global 2023-04-28 05:57:40,776 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global 2023-04-28 05:57:40,776 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces 2023-04-28 05:57:40,776 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces 2023-04-28 05:57:40,776 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces 2023-04-28 05:57:40,776 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global 2023-04-28 05:57:40,777 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global 2023-04-28 05:57:40,777 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global 2023-04-28 05:57:40,777 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global 2023-04-28 05:57:40,777 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global 2023-04-28 05:57:40,777 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global 2023-04-28 05:57:40,778 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces 2023-04-28 05:57:40,778 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces 2023-04-28 05:57:40,778 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces 2023-04-28 05:57:40,778 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2 2023-04-28 05:57:40,778 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2 2023-04-28 05:57:40,779 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2 2023-04-28 05:57:40,779 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3 2023-04-28 05:57:40,779 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3 2023-04-28 05:57:40,779 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3 2023-04-28 05:57:40,780 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping 2023-04-28 05:57:40,780 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping 2023-04-28 05:57:40,780 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/ping.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping 2023-04-28 05:57:40,780 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists 2023-04-28 05:57:40,780 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists 2023-04-28 05:57:40,780 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists 2023-04-28 05:57:40,781 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server 2023-04-28 05:57:40,781 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server 2023-04-28 05:57:40,781 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server 2023-04-28 05:57:40,781 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes 2023-04-28 05:57:40,781 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes 2023-04-28 05:57:40,782 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes 2023-04-28 05:57:40,782 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config 2023-04-28 05:57:40,782 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config 2023-04-28 05:57:40,782 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces 2023-04-28 05:57:40,782 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces 2023-04-28 05:57:40,783 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces 2023-04-28 05:57:40,783 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls 2023-04-28 05:57:40,783 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls 2023-04-28 05:57:40,783 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/acls.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls 2023-04-28 05:57:40,783 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family 2023-04-28 05:57:40,784 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family 2023-04-28 05:57:40,784 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family 2023-04-28 05:57:40,784 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global 2023-04-28 05:57:40,784 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global 2023-04-28 05:57:40,784 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global 2023-04-28 05:57:40,785 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family 2023-04-28 05:57:40,785 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family 2023-04-28 05:57:40,785 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family 2023-04-28 05:57:40,785 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname 2023-04-28 05:57:40,785 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname 2023-04-28 05:57:40,786 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/hostname.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname 2023-04-28 05:57:40,786 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces 2023-04-28 05:57:40,786 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces 2023-04-28 05:57:40,786 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces 2023-04-28 05:57:40,786 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces 2023-04-28 05:57:40,786 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces 2023-04-28 05:57:40,787 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces 2023-04-28 05:57:40,787 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces 2023-04-28 05:57:40,787 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces 2023-04-28 05:57:40,787 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces 2023-04-28 05:57:40,788 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp 2023-04-28 05:57:40,788 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp 2023-04-28 05:57:40,788 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/lacp.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp 2023-04-28 05:57:40,788 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces 2023-04-28 05:57:40,788 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces 2023-04-28 05:57:40,788 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces 2023-04-28 05:57:40,789 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces 2023-04-28 05:57:40,789 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces 2023-04-28 05:57:40,789 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces 2023-04-28 05:57:40,789 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global 2023-04-28 05:57:40,789 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global 2023-04-28 05:57:40,790 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global 2023-04-28 05:57:40,790 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces 2023-04-28 05:57:40,790 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces 2023-04-28 05:57:40,790 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces 2023-04-28 05:57:40,790 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global 2023-04-28 05:57:40,791 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global 2023-04-28 05:57:40,791 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global 2023-04-28 05:57:40,791 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global 2023-04-28 05:57:40,791 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global 2023-04-28 05:57:40,791 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global 2023-04-28 05:57:40,792 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces 2023-04-28 05:57:40,792 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces 2023-04-28 05:57:40,792 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces 2023-04-28 05:57:40,792 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2 2023-04-28 05:57:40,792 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2 2023-04-28 05:57:40,793 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2 2023-04-28 05:57:40,793 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3 2023-04-28 05:57:40,793 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3 2023-04-28 05:57:40,793 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3 2023-04-28 05:57:40,793 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping 2023-04-28 05:57:40,794 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping 2023-04-28 05:57:40,794 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/ping.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping 2023-04-28 05:57:40,794 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists 2023-04-28 05:57:40,794 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists 2023-04-28 05:57:40,794 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists 2023-04-28 05:57:40,795 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server 2023-04-28 05:57:40,795 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server 2023-04-28 05:57:40,795 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server 2023-04-28 05:57:40,795 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes 2023-04-28 05:57:40,795 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes 2023-04-28 05:57:40,795 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes 2023-04-28 05:57:40,796 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts 2023-04-28 05:57:40,796 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts 2023-04-28 05:57:40,796 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/facts.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts 2023-04-28 05:57:40,796 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces 2023-04-28 05:57:40,796 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces 2023-04-28 05:57:40,797 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces 2023-04-28 05:57:40,797 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls 2023-04-28 05:57:40,797 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls 2023-04-28 05:57:40,797 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/acls.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls 2023-04-28 05:57:40,797 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family 2023-04-28 05:57:40,798 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family 2023-04-28 05:57:40,798 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family 2023-04-28 05:57:40,798 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global 2023-04-28 05:57:40,798 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global 2023-04-28 05:57:40,798 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global 2023-04-28 05:57:40,799 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family 2023-04-28 05:57:40,799 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family 2023-04-28 05:57:40,799 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family 2023-04-28 05:57:40,799 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname 2023-04-28 05:57:40,799 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname 2023-04-28 05:57:40,800 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/hostname.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname 2023-04-28 05:57:40,800 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces 2023-04-28 05:57:40,800 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces 2023-04-28 05:57:40,800 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces 2023-04-28 05:57:40,800 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces 2023-04-28 05:57:40,800 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces 2023-04-28 05:57:40,801 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces 2023-04-28 05:57:40,801 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces 2023-04-28 05:57:40,801 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces 2023-04-28 05:57:40,801 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces 2023-04-28 05:57:40,802 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp 2023-04-28 05:57:40,802 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp 2023-04-28 05:57:40,802 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/lacp.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp 2023-04-28 05:57:40,802 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces 2023-04-28 05:57:40,802 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces 2023-04-28 05:57:40,802 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces 2023-04-28 05:57:40,803 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces 2023-04-28 05:57:40,803 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces 2023-04-28 05:57:40,803 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces 2023-04-28 05:57:40,803 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy 2023-04-28 05:57:40,803 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy 2023-04-28 05:57:40,804 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/base.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy 2023-04-28 05:57:40,804 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global 2023-04-28 05:57:40,804 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global 2023-04-28 05:57:40,804 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global 2023-04-28 05:57:40,804 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces 2023-04-28 05:57:40,805 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces 2023-04-28 05:57:40,805 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces 2023-04-28 05:57:40,805 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global 2023-04-28 05:57:40,805 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global 2023-04-28 05:57:40,805 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global 2023-04-28 05:57:40,806 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global 2023-04-28 05:57:40,806 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global 2023-04-28 05:57:40,806 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global 2023-04-28 05:57:40,806 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces 2023-04-28 05:57:40,806 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces 2023-04-28 05:57:40,806 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces 2023-04-28 05:57:40,807 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2 2023-04-28 05:57:40,807 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2 2023-04-28 05:57:40,807 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2 2023-04-28 05:57:40,807 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3 2023-04-28 05:57:40,807 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3 2023-04-28 05:57:40,808 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3 2023-04-28 05:57:40,808 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists 2023-04-28 05:57:40,808 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists 2023-04-28 05:57:40,808 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists 2023-04-28 05:57:40,808 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server 2023-04-28 05:57:40,809 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server 2023-04-28 05:57:40,809 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server 2023-04-28 05:57:40,809 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes 2023-04-28 05:57:40,809 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes 2023-04-28 05:57:40,809 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes 2023-04-28 05:57:40,810 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:40,810 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:40,810 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/module.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:40,810 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/providers.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:40,810 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli 2023-04-28 05:57:40,811 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli 2023-04-28 05:57:40,811 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config 2023-04-28 05:57:40,811 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config 2023-04-28 05:57:40,811 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:40,811 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:40,811 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:40,812 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/neighbors.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:40,812 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/process.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:40,812 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,812 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,812 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/acl_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,813 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,813 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,813 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,814 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/hostname.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,814 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/logging_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,814 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ntp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,814 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospf_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,815 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospfv2.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,815 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospfv3.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,815 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ping.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,816 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/prefix_lists.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,816 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/snmp_server.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:40,816 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils 2023-04-28 05:57:40,816 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils 2023-04-28 05:57:40,817 root INFO copying ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/utils.py -> build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils 2023-04-28 05:57:40,817 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,817 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,817 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_acl_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,817 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_acls.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,818 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_banner.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,818 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,818 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,818 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,819 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,819 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_command.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,819 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_config.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,820 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_facts.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,820 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_hostname.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,820 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,820 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_l2_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,820 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_l3_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,821 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_lacp.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,821 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_lacp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,821 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_lag_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,821 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_lldp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,822 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_lldp_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,822 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_logging.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,822 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_logging_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,822 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_netconf.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,823 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_ntp_global.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,823 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospf_interfaces.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,823 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospfv2.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,824 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospfv3.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,824 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_ping.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,824 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_prefix_lists.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,824 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_snmp_server.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,825 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_static_routes.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,825 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_system.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,825 root INFO copying ansible_collections/cisco/iosxr/plugins/modules/iosxr_user.py -> build/lib/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:40,826 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/netconf 2023-04-28 05:57:40,826 root INFO copying ansible_collections/cisco/iosxr/plugins/netconf/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/netconf 2023-04-28 05:57:40,826 root INFO copying ansible_collections/cisco/iosxr/plugins/netconf/iosxr.py -> build/lib/ansible_collections/cisco/iosxr/plugins/netconf 2023-04-28 05:57:40,826 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins 2023-04-28 05:57:40,826 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc 2023-04-28 05:57:40,826 root INFO copying ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc 2023-04-28 05:57:40,827 root INFO copying ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/iosxr.py -> build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc 2023-04-28 05:57:40,827 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb 2023-04-28 05:57:40,827 root INFO copying ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb 2023-04-28 05:57:40,827 root INFO copying ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/ems_grpc_pb2.py -> build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb 2023-04-28 05:57:40,828 root INFO creating build/lib/ansible_collections/cisco/iosxr/plugins/terminal 2023-04-28 05:57:40,828 root INFO copying ansible_collections/cisco/iosxr/plugins/terminal/__init__.py -> build/lib/ansible_collections/cisco/iosxr/plugins/terminal 2023-04-28 05:57:40,828 root INFO copying ansible_collections/cisco/iosxr/plugins/terminal/iosxr.py -> build/lib/ansible_collections/cisco/iosxr/plugins/terminal 2023-04-28 05:57:40,828 root INFO creating build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,828 root INFO copying ansible_collections/cisco/ise/FILES.json -> build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,829 root INFO copying ansible_collections/cisco/ise/LICENSE -> build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,829 root INFO copying ansible_collections/cisco/ise/MANIFEST.json -> build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,829 root INFO copying ansible_collections/cisco/ise/Makefile -> build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,829 root INFO copying ansible_collections/cisco/ise/README.md -> build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,830 root INFO copying ansible_collections/cisco/ise/hosts -> build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,830 root INFO copying ansible_collections/cisco/ise/requirements.txt -> build/lib/ansible_collections/cisco/ise 2023-04-28 05:57:40,830 root INFO creating build/lib/ansible_collections/cisco/ise/changelogs 2023-04-28 05:57:40,830 root INFO copying ansible_collections/cisco/ise/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/ise/changelogs 2023-04-28 05:57:40,831 root INFO creating build/lib/ansible_collections/cisco/ise/meta 2023-04-28 05:57:40,831 root INFO copying ansible_collections/cisco/ise/meta/runtime.yml -> build/lib/ansible_collections/cisco/ise/meta 2023-04-28 05:57:40,831 root INFO creating build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,831 root INFO copying ansible_collections/cisco/ise/playbooks/aci_settings.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,831 root INFO copying ansible_collections/cisco/ise/playbooks/active_directory.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,831 root INFO copying ansible_collections/cisco/ise/playbooks/allowed_protocols.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,832 root INFO copying ansible_collections/cisco/ise/playbooks/anc_policy.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,832 root INFO copying ansible_collections/cisco/ise/playbooks/authorization_profile.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,832 root INFO copying ansible_collections/cisco/ise/playbooks/aws_deployment.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,832 root INFO copying ansible_collections/cisco/ise/playbooks/azure_deployment.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,833 root INFO copying ansible_collections/cisco/ise/playbooks/b.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,833 root INFO copying ansible_collections/cisco/ise/playbooks/backup_create.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,833 root INFO copying ansible_collections/cisco/ise/playbooks/backup_restore.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,833 root INFO copying ansible_collections/cisco/ise/playbooks/backup_schedule.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,833 root INFO copying ansible_collections/cisco/ise/playbooks/byod_portal.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,834 root INFO copying ansible_collections/cisco/ise/playbooks/certificate_management.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,834 root INFO copying ansible_collections/cisco/ise/playbooks/certificate_profile.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,834 root INFO copying ansible_collections/cisco/ise/playbooks/certificates.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,834 root INFO copying ansible_collections/cisco/ise/playbooks/credentials.template -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,835 root INFO copying ansible_collections/cisco/ise/playbooks/credentials.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,835 root INFO copying ansible_collections/cisco/ise/playbooks/csr_export.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,835 root INFO copying ansible_collections/cisco/ise/playbooks/deployment_info.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,835 root INFO copying ansible_collections/cisco/ise/playbooks/device_administration_authentication_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,835 root INFO copying ansible_collections/cisco/ise/playbooks/device_administration_authorization_exception_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,836 root INFO copying ansible_collections/cisco/ise/playbooks/device_administration_authorization_global_exception_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,836 root INFO copying ansible_collections/cisco/ise/playbooks/device_administration_authorization_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,836 root INFO copying ansible_collections/cisco/ise/playbooks/device_administration_network_conditions.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,836 root INFO copying ansible_collections/cisco/ise/playbooks/device_administration_policy_set.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,837 root INFO copying ansible_collections/cisco/ise/playbooks/device_administration_time_date_conditions.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,837 root INFO copying ansible_collections/cisco/ise/playbooks/downloadable_acl.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,837 root INFO copying ansible_collections/cisco/ise/playbooks/egress_matrix_cell.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,837 root INFO copying ansible_collections/cisco/ise/playbooks/endpoint.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,837 root INFO copying ansible_collections/cisco/ise/playbooks/endpoint_certificate.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,838 root INFO copying ansible_collections/cisco/ise/playbooks/endpoint_group.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,838 root INFO copying ansible_collections/cisco/ise/playbooks/filter_policy.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,838 root INFO copying ansible_collections/cisco/ise/playbooks/hosts -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,838 root INFO copying ansible_collections/cisco/ise/playbooks/identity_group.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,839 root INFO copying ansible_collections/cisco/ise/playbooks/internal_user.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,839 root INFO copying ansible_collections/cisco/ise/playbooks/my_device_portal.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,839 root INFO copying ansible_collections/cisco/ise/playbooks/native_supplicant_profile.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,839 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_authentication_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,839 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_authorization_exception_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,840 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_authorization_global_exception_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,840 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_authorization_rules.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,840 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_conditions.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,840 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_dictionary.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,841 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_dictionary_attribute.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,841 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_network_condition.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,841 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_policy_set.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,841 root INFO copying ansible_collections/cisco/ise/playbooks/network_access_time_date_conditions.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,841 root INFO copying ansible_collections/cisco/ise/playbooks/network_device.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,842 root INFO copying ansible_collections/cisco/ise/playbooks/network_device_group.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,842 root INFO copying ansible_collections/cisco/ise/playbooks/network_device_group_deparments.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,842 root INFO copying ansible_collections/cisco/ise/playbooks/personas_deployment.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,842 root INFO copying ansible_collections/cisco/ise/playbooks/playbookstest.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,843 root INFO copying ansible_collections/cisco/ise/playbooks/portal_global_setting.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,843 root INFO copying ansible_collections/cisco/ise/playbooks/portal_theme.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,843 root INFO copying ansible_collections/cisco/ise/playbooks/profiler-services.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,843 root INFO copying ansible_collections/cisco/ise/playbooks/radius_server_sequence.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,843 root INFO copying ansible_collections/cisco/ise/playbooks/sponsor_portal.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,844 root INFO copying ansible_collections/cisco/ise/playbooks/support_bundle.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,844 root INFO copying ansible_collections/cisco/ise/playbooks/system_certificate.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,844 root INFO copying ansible_collections/cisco/ise/playbooks/trustsec_nbarapp.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,844 root INFO copying ansible_collections/cisco/ise/playbooks/trustsec_sg_vn_mapping.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,845 root INFO copying ansible_collections/cisco/ise/playbooks/trustsec_vn.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,845 root INFO copying ansible_collections/cisco/ise/playbooks/trustsec_vn_vlan_mapping.yml -> build/lib/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:40,845 root INFO creating build/lib/ansible_collections/cisco/ise/playbooks/group_vars 2023-04-28 05:57:40,845 root INFO copying ansible_collections/cisco/ise/playbooks/group_vars/ise_servers -> build/lib/ansible_collections/cisco/ise/playbooks/group_vars 2023-04-28 05:57:40,845 root INFO creating build/lib/ansible_collections/cisco/ise/playbooks/vars 2023-04-28 05:57:40,846 root INFO copying ansible_collections/cisco/ise/playbooks/vars/device_administration_time_date_conditions.yml -> build/lib/ansible_collections/cisco/ise/playbooks/vars 2023-04-28 05:57:40,846 root INFO creating build/lib/ansible_collections/cisco/ise/plugins 2023-04-28 05:57:40,846 root INFO creating build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,846 root INFO copying ansible_collections/cisco/ise/plugins/action/aci_bindings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,846 root INFO copying ansible_collections/cisco/ise/plugins/action/aci_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,847 root INFO copying ansible_collections/cisco/ise/plugins/action/aci_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,847 root INFO copying ansible_collections/cisco/ise/plugins/action/aci_test_connectivity.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,847 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,847 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_add_groups.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,847 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_groups_by_domain_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,848 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,848 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_is_user_member_of_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,848 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_join_domain.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,848 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_join_domain_with_all_nodes.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,848 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_leave_domain.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,849 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_leave_domain_with_all_nodes.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,849 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_trusted_domains_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,849 root INFO copying ansible_collections/cisco/ise/plugins/action/active_directory_user_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,849 root INFO copying ansible_collections/cisco/ise/plugins/action/admin_user_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,850 root INFO copying ansible_collections/cisco/ise/plugins/action/allowed_protocols.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,850 root INFO copying ansible_collections/cisco/ise/plugins/action/allowed_protocols_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,850 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_endpoint_apply.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,850 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_endpoint_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,851 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_endpoint_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,851 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_endpoint_clear.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,851 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_endpoint_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,851 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_policy.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,851 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_policy_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,852 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_policy_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,852 root INFO copying ansible_collections/cisco/ise/plugins/action/anc_policy_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,852 root INFO copying ansible_collections/cisco/ise/plugins/action/authorization_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,852 root INFO copying ansible_collections/cisco/ise/plugins/action/authorization_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,853 root INFO copying ansible_collections/cisco/ise/plugins/action/backup_cancel.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,853 root INFO copying ansible_collections/cisco/ise/plugins/action/backup_config.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,853 root INFO copying ansible_collections/cisco/ise/plugins/action/backup_last_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,853 root INFO copying ansible_collections/cisco/ise/plugins/action/backup_restore.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,853 root INFO copying ansible_collections/cisco/ise/plugins/action/backup_schedule_config.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,854 root INFO copying ansible_collections/cisco/ise/plugins/action/backup_schedule_config_update.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,854 root INFO copying ansible_collections/cisco/ise/plugins/action/bind_signed_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,854 root INFO copying ansible_collections/cisco/ise/plugins/action/byod_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,854 root INFO copying ansible_collections/cisco/ise/plugins/action/byod_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,855 root INFO copying ansible_collections/cisco/ise/plugins/action/certificate_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,855 root INFO copying ansible_collections/cisco/ise/plugins/action/certificate_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,855 root INFO copying ansible_collections/cisco/ise/plugins/action/certificate_template_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,855 root INFO copying ansible_collections/cisco/ise/plugins/action/csr_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,856 root INFO copying ansible_collections/cisco/ise/plugins/action/csr_export_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,856 root INFO copying ansible_collections/cisco/ise/plugins/action/csr_generate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,856 root INFO copying ansible_collections/cisco/ise/plugins/action/csr_generate_intermediate_ca.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,856 root INFO copying ansible_collections/cisco/ise/plugins/action/csr_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,856 root INFO copying ansible_collections/cisco/ise/plugins/action/deployment_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,857 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_authentication_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,857 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_authentication_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,857 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_authentication_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,857 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_authorization_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,858 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_authorization_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,858 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_authorization_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,858 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_command_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,858 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,858 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_authentication_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,859 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_authorization_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,859 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,859 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,859 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_authentication_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,860 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_authorization_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,860 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,860 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,860 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,860 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,861 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_identity_stores_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,861 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,861 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,861 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,862 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_network_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,862 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_network_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,862 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_policy_set.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,862 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,863 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_policy_set_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,863 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_profiles_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,863 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_service_names_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,863 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_time_date_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,863 root INFO copying ansible_collections/cisco/ise/plugins/action/device_administration_time_date_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,864 root INFO copying ansible_collections/cisco/ise/plugins/action/downloadable_acl.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,864 root INFO copying ansible_collections/cisco/ise/plugins/action/downloadable_acl_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,864 root INFO copying ansible_collections/cisco/ise/plugins/action/egress_matrix_cell.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,864 root INFO copying ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,865 root INFO copying ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,865 root INFO copying ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_clear_all.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,865 root INFO copying ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_clone.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,865 root INFO copying ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,866 root INFO copying ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_set_all_status.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,866 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,866 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,866 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,866 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,867 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_deregister.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,867 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_get_rejected_endpoints_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,867 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_group.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,867 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,868 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,868 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_register.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,868 root INFO copying ansible_collections/cisco/ise/plugins/action/endpoint_release_rejected_endpoint.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,868 root INFO copying ansible_collections/cisco/ise/plugins/action/external_radius_server.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,869 root INFO copying ansible_collections/cisco/ise/plugins/action/external_radius_server_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,869 root INFO copying ansible_collections/cisco/ise/plugins/action/filter_policy.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,869 root INFO copying ansible_collections/cisco/ise/plugins/action/filter_policy_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,869 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_location_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,870 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_smtp_notification_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,870 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_smtp_notification_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,870 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_ssid.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,870 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_ssid_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,871 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_type.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,871 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_type_email.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,871 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,871 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_type_sms.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,871 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,872 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,872 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,872 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,872 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_change_sponsor_password.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,873 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_deny.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,873 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_email.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,873 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,873 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_reinstate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,874 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_reset_password.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,874 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_sms.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,874 root INFO copying ansible_collections/cisco/ise/plugins/action/guest_user_suspend.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,874 root INFO copying ansible_collections/cisco/ise/plugins/action/hotpatch_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,874 root INFO copying ansible_collections/cisco/ise/plugins/action/hotpatch_install.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,875 root INFO copying ansible_collections/cisco/ise/plugins/action/hotpatch_rollback.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,875 root INFO copying ansible_collections/cisco/ise/plugins/action/hotspot_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,875 root INFO copying ansible_collections/cisco/ise/plugins/action/hotspot_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,875 root INFO copying ansible_collections/cisco/ise/plugins/action/id_store_sequence.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,876 root INFO copying ansible_collections/cisco/ise/plugins/action/id_store_sequence_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,876 root INFO copying ansible_collections/cisco/ise/plugins/action/identity_group.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,876 root INFO copying ansible_collections/cisco/ise/plugins/action/identity_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,876 root INFO copying ansible_collections/cisco/ise/plugins/action/internal_user.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,877 root INFO copying ansible_collections/cisco/ise/plugins/action/internal_user_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,877 root INFO copying ansible_collections/cisco/ise/plugins/action/ise_root_ca_regenerate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,877 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_connection_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,877 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_eval_license_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,877 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_feature_to_tier_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,878 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_registration_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,878 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_registration_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,878 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_smart_state_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,878 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_smart_state_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,879 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_tier_state_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,879 root INFO copying ansible_collections/cisco/ise/plugins/action/licensing_tier_state_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,879 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_account_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,880 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_athentication_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,880 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_authentication_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,880 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_failure_reasons_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,880 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_active_count_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,881 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_active_list_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,881 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_auth_list_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,881 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_by_ip_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,881 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_by_mac_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,881 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_by_nas_ip_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,882 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_by_username_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,882 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_delete_all.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,882 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_disconnect_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,882 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_posture_count_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,883 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_profiler_count_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,883 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_session_reauthentication_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,883 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_sessions_by_session_id_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,883 root INFO copying ansible_collections/cisco/ise/plugins/action/mnt_version_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,884 root INFO copying ansible_collections/cisco/ise/plugins/action/my_device_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,884 root INFO copying ansible_collections/cisco/ise/plugins/action/my_device_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,884 root INFO copying ansible_collections/cisco/ise/plugins/action/native_supplicant_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,884 root INFO copying ansible_collections/cisco/ise/plugins/action/native_supplicant_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,884 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,885 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,885 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,885 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,885 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,886 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,886 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,886 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_authentication_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,886 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_authorization_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,887 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,887 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,887 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_dictionary.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,887 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attribute.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,887 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attribute_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,888 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_authentication_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,888 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_authorization_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,888 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,888 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_dictionary_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,889 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,889 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,889 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,889 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_identity_stores_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,890 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,890 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,890 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules_reset_hitcounts.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,890 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_network_condition.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,891 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_network_condition_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,891 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_policy_set.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,891 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,891 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_policy_set_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,891 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_profiles_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,892 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_security_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,892 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_service_name_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,892 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_time_date_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,892 root INFO copying ansible_collections/cisco/ise/plugins/action/network_access_time_date_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,893 root INFO copying ansible_collections/cisco/ise/plugins/action/network_device.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,893 root INFO copying ansible_collections/cisco/ise/plugins/action/network_device_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,893 root INFO copying ansible_collections/cisco/ise/plugins/action/network_device_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,893 root INFO copying ansible_collections/cisco/ise/plugins/action/network_device_group.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,894 root INFO copying ansible_collections/cisco/ise/plugins/action/network_device_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,894 root INFO copying ansible_collections/cisco/ise/plugins/action/network_device_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,894 root INFO copying ansible_collections/cisco/ise/plugins/action/node_deployment.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,894 root INFO copying ansible_collections/cisco/ise/plugins/action/node_deployment_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,894 root INFO copying ansible_collections/cisco/ise/plugins/action/node_deployment_sync.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,895 root INFO copying ansible_collections/cisco/ise/plugins/action/node_group.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,895 root INFO copying ansible_collections/cisco/ise/plugins/action/node_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,895 root INFO copying ansible_collections/cisco/ise/plugins/action/node_group_node_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,895 root INFO copying ansible_collections/cisco/ise/plugins/action/node_group_node_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,896 root INFO copying ansible_collections/cisco/ise/plugins/action/node_group_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,896 root INFO copying ansible_collections/cisco/ise/plugins/action/node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,896 root INFO copying ansible_collections/cisco/ise/plugins/action/node_primary_to_standalone.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,896 root INFO copying ansible_collections/cisco/ise/plugins/action/node_promotion.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,897 root INFO copying ansible_collections/cisco/ise/plugins/action/node_replication_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,897 root INFO copying ansible_collections/cisco/ise/plugins/action/node_secondary_to_primary.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,897 root INFO copying ansible_collections/cisco/ise/plugins/action/node_services_interfaces_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,897 root INFO copying ansible_collections/cisco/ise/plugins/action/node_services_profiler_probe_config.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,897 root INFO copying ansible_collections/cisco/ise/plugins/action/node_services_profiler_probe_config_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,898 root INFO copying ansible_collections/cisco/ise/plugins/action/node_services_sxp_interfaces.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,898 root INFO copying ansible_collections/cisco/ise/plugins/action/node_services_sxp_interfaces_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,898 root INFO copying ansible_collections/cisco/ise/plugins/action/node_standalone_to_primary.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,898 root INFO copying ansible_collections/cisco/ise/plugins/action/node_sync.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,899 root INFO copying ansible_collections/cisco/ise/plugins/action/pan_ha.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,899 root INFO copying ansible_collections/cisco/ise/plugins/action/pan_ha_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,899 root INFO copying ansible_collections/cisco/ise/plugins/action/pan_ha_update.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,899 root INFO copying ansible_collections/cisco/ise/plugins/action/patch_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,900 root INFO copying ansible_collections/cisco/ise/plugins/action/patch_install.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,900 root INFO copying ansible_collections/cisco/ise/plugins/action/patch_rollback.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,900 root INFO copying ansible_collections/cisco/ise/plugins/action/personas_check_standalone.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,900 root INFO copying ansible_collections/cisco/ise/plugins/action/personas_export_certs.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,901 root INFO copying ansible_collections/cisco/ise/plugins/action/personas_promote_primary.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,901 root INFO copying ansible_collections/cisco/ise/plugins/action/personas_register_node.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,901 root INFO copying ansible_collections/cisco/ise/plugins/action/personas_update_roles_services.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,901 root INFO copying ansible_collections/cisco/ise/plugins/action/portal_global_setting.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,901 root INFO copying ansible_collections/cisco/ise/plugins/action/portal_global_setting_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,902 root INFO copying ansible_collections/cisco/ise/plugins/action/portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,902 root INFO copying ansible_collections/cisco/ise/plugins/action/portal_theme.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,902 root INFO copying ansible_collections/cisco/ise/plugins/action/portal_theme_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,902 root INFO copying ansible_collections/cisco/ise/plugins/action/profiler_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,903 root INFO copying ansible_collections/cisco/ise/plugins/action/proxy_connection_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,903 root INFO copying ansible_collections/cisco/ise/plugins/action/proxy_connection_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,903 root INFO copying ansible_collections/cisco/ise/plugins/action/px_grid_node_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,903 root INFO copying ansible_collections/cisco/ise/plugins/action/px_grid_node_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,904 root INFO copying ansible_collections/cisco/ise/plugins/action/px_grid_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,904 root INFO copying ansible_collections/cisco/ise/plugins/action/px_grid_settings_auto_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,904 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_access_secret.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,904 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_account_activate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,904 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_account_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,905 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_authorization.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,905 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_bindings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,905 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_egress_matrices_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,905 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_egress_policies_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,906 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_endpoint_by_mac_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,906 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_by_os_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,906 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_by_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,906 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,906 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_failures_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,907 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_healths_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,907 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_node_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,907 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_node_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,907 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,908 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_performances_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,908 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_profiles_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,908 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_security_group_acls_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,908 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_security_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,908 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_service_lookup.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,909 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_service_register.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,909 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_service_reregister.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,909 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_service_unregister.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,909 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_session_by_ip_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,910 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_session_by_mac_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,910 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_session_for_recovery_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,910 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_sessions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,910 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_settings_auto_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,910 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_user_group_by_username_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,911 root INFO copying ansible_collections/cisco/ise/plugins/action/pxgrid_user_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,911 root INFO copying ansible_collections/cisco/ise/plugins/action/radius_server_sequence.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,911 root INFO copying ansible_collections/cisco/ise/plugins/action/radius_server_sequence_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,911 root INFO copying ansible_collections/cisco/ise/plugins/action/renew_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,912 root INFO copying ansible_collections/cisco/ise/plugins/action/repository.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,912 root INFO copying ansible_collections/cisco/ise/plugins/action/repository_files_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,912 root INFO copying ansible_collections/cisco/ise/plugins/action/repository_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,912 root INFO copying ansible_collections/cisco/ise/plugins/action/resource_version_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,913 root INFO copying ansible_collections/cisco/ise/plugins/action/rest_id_store.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,913 root INFO copying ansible_collections/cisco/ise/plugins/action/rest_id_store_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,913 root INFO copying ansible_collections/cisco/ise/plugins/action/self_registered_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,913 root INFO copying ansible_collections/cisco/ise/plugins/action/self_registered_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,914 root INFO copying ansible_collections/cisco/ise/plugins/action/selfsigned_certificate_generate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,914 root INFO copying ansible_collections/cisco/ise/plugins/action/session_service_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,914 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_acl.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,914 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_acl_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,914 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_acl_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,915 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_acl_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,915 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,915 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,915 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,916 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,916 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy_all.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,916 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,916 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_group.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,917 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_group_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,917 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_group_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,917 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,917 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy_all.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,917 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,918 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,918 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,918 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,918 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,919 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,919 root INFO copying ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,919 root INFO copying ansible_collections/cisco/ise/plugins/action/sgt.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,919 root INFO copying ansible_collections/cisco/ise/plugins/action/sgt_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,920 root INFO copying ansible_collections/cisco/ise/plugins/action/sgt_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,920 root INFO copying ansible_collections/cisco/ise/plugins/action/sgt_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,920 root INFO copying ansible_collections/cisco/ise/plugins/action/sms_provider_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,920 root INFO copying ansible_collections/cisco/ise/plugins/action/sponsor_group.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,920 root INFO copying ansible_collections/cisco/ise/plugins/action/sponsor_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,921 root INFO copying ansible_collections/cisco/ise/plugins/action/sponsor_group_member_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,921 root INFO copying ansible_collections/cisco/ise/plugins/action/sponsor_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,921 root INFO copying ansible_collections/cisco/ise/plugins/action/sponsor_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,921 root INFO copying ansible_collections/cisco/ise/plugins/action/sponsored_guest_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,922 root INFO copying ansible_collections/cisco/ise/plugins/action/sponsored_guest_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,922 root INFO copying ansible_collections/cisco/ise/plugins/action/support_bundle.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,922 root INFO copying ansible_collections/cisco/ise/plugins/action/support_bundle_download.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,922 root INFO copying ansible_collections/cisco/ise/plugins/action/support_bundle_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,923 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_connections.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,923 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_connections_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,923 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_connections_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,923 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_connections_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,923 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_local_bindings.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,924 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,924 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,924 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,924 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_vpns.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,925 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_vpns_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,925 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_vpns_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,925 root INFO copying ansible_collections/cisco/ise/plugins/action/sxp_vpns_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,925 root INFO copying ansible_collections/cisco/ise/plugins/action/system_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,926 root INFO copying ansible_collections/cisco/ise/plugins/action/system_certificate_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,926 root INFO copying ansible_collections/cisco/ise/plugins/action/system_certificate_export_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,926 root INFO copying ansible_collections/cisco/ise/plugins/action/system_certificate_import.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,926 root INFO copying ansible_collections/cisco/ise/plugins/action/system_certificate_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,926 root INFO copying ansible_collections/cisco/ise/plugins/action/system_config_version_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,927 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_command_sets.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,927 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_command_sets_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,927 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_external_servers.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,927 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_external_servers_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,928 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,928 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,928 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_server_sequence.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,928 root INFO copying ansible_collections/cisco/ise/plugins/action/tacacs_server_sequence_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,929 root INFO copying ansible_collections/cisco/ise/plugins/action/tasks_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,929 root INFO copying ansible_collections/cisco/ise/plugins/action/telemetry_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,929 root INFO copying ansible_collections/cisco/ise/plugins/action/threat_vulnerabilities_clear.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,929 root INFO copying ansible_collections/cisco/ise/plugins/action/transport_gateway_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,930 root INFO copying ansible_collections/cisco/ise/plugins/action/transport_gateway_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,930 root INFO copying ansible_collections/cisco/ise/plugins/action/trusted_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,930 root INFO copying ansible_collections/cisco/ise/plugins/action/trusted_certificate_export_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,930 root INFO copying ansible_collections/cisco/ise/plugins/action/trusted_certificate_import.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,930 root INFO copying ansible_collections/cisco/ise/plugins/action/trusted_certificate_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,931 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_nbar_app.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,931 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_nbar_app_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,931 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,931 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,932 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,932 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_update.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,932 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,932 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,933 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,933 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,933 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_update.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,933 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,933 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,934 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_create.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,934 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,934 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_update.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,934 root INFO copying ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:40,935 root INFO creating build/lib/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:40,935 root INFO copying ansible_collections/cisco/ise/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:40,935 root INFO copying ansible_collections/cisco/ise/plugins/doc_fragments/module.py -> build/lib/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:40,935 root INFO copying ansible_collections/cisco/ise/plugins/doc_fragments/module_info.py -> build/lib/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:40,935 root INFO creating build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,935 root INFO copying ansible_collections/cisco/ise/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,936 root INFO copying ansible_collections/cisco/ise/plugins/modules/aci_bindings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,936 root INFO copying ansible_collections/cisco/ise/plugins/modules/aci_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,936 root INFO copying ansible_collections/cisco/ise/plugins/modules/aci_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,936 root INFO copying ansible_collections/cisco/ise/plugins/modules/aci_test_connectivity.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,937 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,937 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_add_groups.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,937 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_groups_by_domain_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,937 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,938 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_is_user_member_of_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,938 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_join_domain.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,938 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_join_domain_with_all_nodes.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,938 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_leave_domain.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,938 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_leave_domain_with_all_nodes.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,939 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_trusted_domains_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,939 root INFO copying ansible_collections/cisco/ise/plugins/modules/active_directory_user_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,939 root INFO copying ansible_collections/cisco/ise/plugins/modules/admin_user_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,939 root INFO copying ansible_collections/cisco/ise/plugins/modules/allowed_protocols.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,940 root INFO copying ansible_collections/cisco/ise/plugins/modules/allowed_protocols_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,940 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_endpoint_apply.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,940 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_endpoint_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,940 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_endpoint_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,940 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_endpoint_clear.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,941 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_endpoint_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,941 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_policy.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,941 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_policy_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,941 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_policy_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,942 root INFO copying ansible_collections/cisco/ise/plugins/modules/anc_policy_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,942 root INFO copying ansible_collections/cisco/ise/plugins/modules/authorization_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,942 root INFO copying ansible_collections/cisco/ise/plugins/modules/authorization_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,942 root INFO copying ansible_collections/cisco/ise/plugins/modules/backup_cancel.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,942 root INFO copying ansible_collections/cisco/ise/plugins/modules/backup_config.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,943 root INFO copying ansible_collections/cisco/ise/plugins/modules/backup_last_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,943 root INFO copying ansible_collections/cisco/ise/plugins/modules/backup_restore.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,943 root INFO copying ansible_collections/cisco/ise/plugins/modules/backup_schedule_config.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,943 root INFO copying ansible_collections/cisco/ise/plugins/modules/backup_schedule_config_update.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,944 root INFO copying ansible_collections/cisco/ise/plugins/modules/bind_signed_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,944 root INFO copying ansible_collections/cisco/ise/plugins/modules/byod_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,944 root INFO copying ansible_collections/cisco/ise/plugins/modules/byod_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,944 root INFO copying ansible_collections/cisco/ise/plugins/modules/certificate_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,945 root INFO copying ansible_collections/cisco/ise/plugins/modules/certificate_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,945 root INFO copying ansible_collections/cisco/ise/plugins/modules/certificate_template_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,945 root INFO copying ansible_collections/cisco/ise/plugins/modules/csr_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,945 root INFO copying ansible_collections/cisco/ise/plugins/modules/csr_export_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,945 root INFO copying ansible_collections/cisco/ise/plugins/modules/csr_generate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,946 root INFO copying ansible_collections/cisco/ise/plugins/modules/csr_generate_intermediate_ca.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,946 root INFO copying ansible_collections/cisco/ise/plugins/modules/csr_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,946 root INFO copying ansible_collections/cisco/ise/plugins/modules/deployment_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,946 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,947 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,947 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,947 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,947 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,948 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,948 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_command_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,948 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,948 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_authentication_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,948 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_authorization_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,949 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,949 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,949 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_authentication_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,949 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_authorization_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,950 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,950 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,950 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,950 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,950 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_identity_stores_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,951 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,951 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,951 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,951 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_network_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,952 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_network_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,952 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,952 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,952 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,953 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_profiles_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,953 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_service_names_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,953 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_time_date_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,953 root INFO copying ansible_collections/cisco/ise/plugins/modules/device_administration_time_date_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,953 root INFO copying ansible_collections/cisco/ise/plugins/modules/downloadable_acl.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,954 root INFO copying ansible_collections/cisco/ise/plugins/modules/downloadable_acl_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,954 root INFO copying ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,954 root INFO copying ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,954 root INFO copying ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,955 root INFO copying ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_clear_all.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,955 root INFO copying ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_clone.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,955 root INFO copying ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,955 root INFO copying ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_set_all_status.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,955 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,956 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,956 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,956 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,956 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_deregister.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,957 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_get_rejected_endpoints_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,957 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_group.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,957 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,957 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,958 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_register.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,958 root INFO copying ansible_collections/cisco/ise/plugins/modules/endpoint_release_rejected_endpoint.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,958 root INFO copying ansible_collections/cisco/ise/plugins/modules/external_radius_server.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,958 root INFO copying ansible_collections/cisco/ise/plugins/modules/external_radius_server_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,959 root INFO copying ansible_collections/cisco/ise/plugins/modules/filter_policy.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,959 root INFO copying ansible_collections/cisco/ise/plugins/modules/filter_policy_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,959 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_location_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,959 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_smtp_notification_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,959 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_smtp_notification_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,960 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_ssid.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,960 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_ssid_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,960 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_type.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,960 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_type_email.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,961 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,961 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_type_sms.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,961 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,961 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,961 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,962 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,962 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_change_sponsor_password.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,962 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_deny.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,962 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_email.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,963 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,963 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_reinstate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,963 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_reset_password.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,963 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_sms.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,964 root INFO copying ansible_collections/cisco/ise/plugins/modules/guest_user_suspend.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,964 root INFO copying ansible_collections/cisco/ise/plugins/modules/hotpatch_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,964 root INFO copying ansible_collections/cisco/ise/plugins/modules/hotpatch_install.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,964 root INFO copying ansible_collections/cisco/ise/plugins/modules/hotpatch_rollback.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,964 root INFO copying ansible_collections/cisco/ise/plugins/modules/hotspot_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,965 root INFO copying ansible_collections/cisco/ise/plugins/modules/hotspot_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,965 root INFO copying ansible_collections/cisco/ise/plugins/modules/id_store_sequence.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,965 root INFO copying ansible_collections/cisco/ise/plugins/modules/id_store_sequence_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,965 root INFO copying ansible_collections/cisco/ise/plugins/modules/identity_group.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,966 root INFO copying ansible_collections/cisco/ise/plugins/modules/identity_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,966 root INFO copying ansible_collections/cisco/ise/plugins/modules/internal_user.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,966 root INFO copying ansible_collections/cisco/ise/plugins/modules/internal_user_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,966 root INFO copying ansible_collections/cisco/ise/plugins/modules/ise_root_ca_regenerate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,967 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_connection_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,967 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_eval_license_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,967 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_feature_to_tier_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,967 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_registration_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,968 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_registration_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,968 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_smart_state_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,968 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_smart_state_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,968 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_tier_state_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,969 root INFO copying ansible_collections/cisco/ise/plugins/modules/licensing_tier_state_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,969 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_account_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,969 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_athentication_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,969 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_authentication_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,969 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_failure_reasons_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,970 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_active_count_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,970 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_active_list_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,970 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_auth_list_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,970 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_by_ip_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,971 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_by_mac_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,971 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_by_nas_ip_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,971 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_by_username_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,971 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_delete_all.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,971 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_disconnect_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,972 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_posture_count_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,972 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_profiler_count_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,972 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_session_reauthentication_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,972 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_sessions_by_session_id_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,973 root INFO copying ansible_collections/cisco/ise/plugins/modules/mnt_version_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,973 root INFO copying ansible_collections/cisco/ise/plugins/modules/my_device_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,973 root INFO copying ansible_collections/cisco/ise/plugins/modules/my_device_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,973 root INFO copying ansible_collections/cisco/ise/plugins/modules/native_supplicant_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,974 root INFO copying ansible_collections/cisco/ise/plugins/modules/native_supplicant_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,974 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,974 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,974 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,975 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,975 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,975 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,975 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,975 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_authentication_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,976 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_authorization_rule_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,976 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,976 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,976 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_dictionary.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,977 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attribute.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,977 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attribute_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,977 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_authentication_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,977 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_authorization_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,978 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,978 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,978 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,978 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,978 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,979 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_identity_stores_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,979 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,979 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,979 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules_reset_hitcounts.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,980 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_network_condition.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,980 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_network_condition_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,980 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_policy_set.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,980 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_policy_set_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,981 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_policy_set_reset_hitcount.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,981 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_profiles_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,981 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_security_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,981 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_service_name_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,981 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_time_date_conditions.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,982 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_access_time_date_conditions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,982 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_device.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,982 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_device_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,982 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_device_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,983 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_device_group.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,983 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_device_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,983 root INFO copying ansible_collections/cisco/ise/plugins/modules/network_device_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,983 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_deployment.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,984 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_deployment_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,984 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_deployment_sync.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,984 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_group.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,984 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,984 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_group_node_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,985 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_group_node_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,985 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_group_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,985 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,985 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_primary_to_standalone.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,986 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_promotion.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,986 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_replication_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,986 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_secondary_to_primary.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,986 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_services_interfaces_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,986 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_services_profiler_probe_config.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,987 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_services_profiler_probe_config_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,987 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_services_sxp_interfaces.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,987 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_services_sxp_interfaces_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,987 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_standalone_to_primary.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,988 root INFO copying ansible_collections/cisco/ise/plugins/modules/node_sync.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,988 root INFO copying ansible_collections/cisco/ise/plugins/modules/pan_ha.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,988 root INFO copying ansible_collections/cisco/ise/plugins/modules/pan_ha_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,988 root INFO copying ansible_collections/cisco/ise/plugins/modules/pan_ha_update.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,988 root INFO copying ansible_collections/cisco/ise/plugins/modules/patch_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,989 root INFO copying ansible_collections/cisco/ise/plugins/modules/patch_install.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,989 root INFO copying ansible_collections/cisco/ise/plugins/modules/patch_rollback.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,989 root INFO copying ansible_collections/cisco/ise/plugins/modules/personas_check_standalone.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,989 root INFO copying ansible_collections/cisco/ise/plugins/modules/personas_export_certs.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,990 root INFO copying ansible_collections/cisco/ise/plugins/modules/personas_promote_primary.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,990 root INFO copying ansible_collections/cisco/ise/plugins/modules/personas_register_node.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,990 root INFO copying ansible_collections/cisco/ise/plugins/modules/personas_update_roles_services.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,990 root INFO copying ansible_collections/cisco/ise/plugins/modules/portal_global_setting.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,991 root INFO copying ansible_collections/cisco/ise/plugins/modules/portal_global_setting_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,991 root INFO copying ansible_collections/cisco/ise/plugins/modules/portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,991 root INFO copying ansible_collections/cisco/ise/plugins/modules/portal_theme.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,991 root INFO copying ansible_collections/cisco/ise/plugins/modules/portal_theme_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,991 root INFO copying ansible_collections/cisco/ise/plugins/modules/profiler_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,992 root INFO copying ansible_collections/cisco/ise/plugins/modules/proxy_connection_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,992 root INFO copying ansible_collections/cisco/ise/plugins/modules/proxy_connection_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,992 root INFO copying ansible_collections/cisco/ise/plugins/modules/px_grid_node_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,992 root INFO copying ansible_collections/cisco/ise/plugins/modules/px_grid_node_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,992 root INFO copying ansible_collections/cisco/ise/plugins/modules/px_grid_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,993 root INFO copying ansible_collections/cisco/ise/plugins/modules/px_grid_settings_auto_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,993 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_access_secret.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,993 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_account_activate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,993 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_account_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,994 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_authorization.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,994 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_bindings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,994 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_egress_matrices_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,994 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_egress_policies_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,995 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoint_by_mac_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,995 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_by_os_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,995 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_by_type_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,995 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,995 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_failures_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,996 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_healths_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,996 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_node_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,996 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_node_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,996 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,997 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_performances_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,997 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_profiles_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,997 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_security_group_acls_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,997 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_security_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,997 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_service_lookup.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,998 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_service_register.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,998 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_service_reregister.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,998 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_service_unregister.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,998 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_session_by_ip_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,999 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_session_by_mac_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,999 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_session_for_recovery_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,999 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_sessions_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,999 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_settings_auto_approve.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:40,999 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_user_group_by_username_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,000 root INFO copying ansible_collections/cisco/ise/plugins/modules/pxgrid_user_groups_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,000 root INFO copying ansible_collections/cisco/ise/plugins/modules/radius_server_sequence.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,000 root INFO copying ansible_collections/cisco/ise/plugins/modules/radius_server_sequence_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,000 root INFO copying ansible_collections/cisco/ise/plugins/modules/renew_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,001 root INFO copying ansible_collections/cisco/ise/plugins/modules/repository.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,001 root INFO copying ansible_collections/cisco/ise/plugins/modules/repository_files_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,001 root INFO copying ansible_collections/cisco/ise/plugins/modules/repository_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,001 root INFO copying ansible_collections/cisco/ise/plugins/modules/resource_version_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,002 root INFO copying ansible_collections/cisco/ise/plugins/modules/rest_id_store.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,002 root INFO copying ansible_collections/cisco/ise/plugins/modules/rest_id_store_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,002 root INFO copying ansible_collections/cisco/ise/plugins/modules/self_registered_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,002 root INFO copying ansible_collections/cisco/ise/plugins/modules/self_registered_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,003 root INFO copying ansible_collections/cisco/ise/plugins/modules/selfsigned_certificate_generate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,003 root INFO copying ansible_collections/cisco/ise/plugins/modules/session_service_node_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,003 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_acl.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,003 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_acl_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,003 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_acl_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,004 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_acl_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,004 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,004 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,005 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,005 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,005 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy_all.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,005 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,006 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_group.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,006 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,006 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,006 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,007 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy_all.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,007 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,007 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,007 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,007 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,008 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,008 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,008 root INFO copying ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,008 root INFO copying ansible_collections/cisco/ise/plugins/modules/sgt.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,009 root INFO copying ansible_collections/cisco/ise/plugins/modules/sgt_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,009 root INFO copying ansible_collections/cisco/ise/plugins/modules/sgt_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,009 root INFO copying ansible_collections/cisco/ise/plugins/modules/sgt_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,009 root INFO copying ansible_collections/cisco/ise/plugins/modules/sms_provider_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,010 root INFO copying ansible_collections/cisco/ise/plugins/modules/sponsor_group.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,010 root INFO copying ansible_collections/cisco/ise/plugins/modules/sponsor_group_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,010 root INFO copying ansible_collections/cisco/ise/plugins/modules/sponsor_group_member_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,010 root INFO copying ansible_collections/cisco/ise/plugins/modules/sponsor_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,010 root INFO copying ansible_collections/cisco/ise/plugins/modules/sponsor_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,011 root INFO copying ansible_collections/cisco/ise/plugins/modules/sponsored_guest_portal.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,011 root INFO copying ansible_collections/cisco/ise/plugins/modules/sponsored_guest_portal_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,011 root INFO copying ansible_collections/cisco/ise/plugins/modules/support_bundle.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,011 root INFO copying ansible_collections/cisco/ise/plugins/modules/support_bundle_download.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,012 root INFO copying ansible_collections/cisco/ise/plugins/modules/support_bundle_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,012 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_connections.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,012 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_connections_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,012 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_connections_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,013 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_connections_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,013 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,013 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,013 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,014 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,014 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_vpns.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,014 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_vpns_bulk_monitor_status_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,014 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_vpns_bulk_request.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,014 root INFO copying ansible_collections/cisco/ise/plugins/modules/sxp_vpns_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,015 root INFO copying ansible_collections/cisco/ise/plugins/modules/system_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,015 root INFO copying ansible_collections/cisco/ise/plugins/modules/system_certificate_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,015 root INFO copying ansible_collections/cisco/ise/plugins/modules/system_certificate_export_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,015 root INFO copying ansible_collections/cisco/ise/plugins/modules/system_certificate_import.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,016 root INFO copying ansible_collections/cisco/ise/plugins/modules/system_certificate_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,016 root INFO copying ansible_collections/cisco/ise/plugins/modules/system_config_version_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,016 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_command_sets.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,016 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_command_sets_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,016 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_external_servers.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,017 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_external_servers_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,017 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_profile.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,017 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_profile_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,017 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_server_sequence.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,018 root INFO copying ansible_collections/cisco/ise/plugins/modules/tacacs_server_sequence_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,018 root INFO copying ansible_collections/cisco/ise/plugins/modules/tasks_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,018 root INFO copying ansible_collections/cisco/ise/plugins/modules/telemetry_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,018 root INFO copying ansible_collections/cisco/ise/plugins/modules/threat_vulnerabilities_clear.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,018 root INFO copying ansible_collections/cisco/ise/plugins/modules/transport_gateway_settings.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,019 root INFO copying ansible_collections/cisco/ise/plugins/modules/transport_gateway_settings_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,019 root INFO copying ansible_collections/cisco/ise/plugins/modules/trusted_certificate.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,019 root INFO copying ansible_collections/cisco/ise/plugins/modules/trusted_certificate_export_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,019 root INFO copying ansible_collections/cisco/ise/plugins/modules/trusted_certificate_import.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,020 root INFO copying ansible_collections/cisco/ise/plugins/modules/trusted_certificate_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,020 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_nbar_app.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,020 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_nbar_app_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,020 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,021 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,021 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,021 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_update.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,021 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,021 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,022 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,022 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,022 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_update.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,022 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,023 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,023 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_create.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,023 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_delete.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,023 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_update.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,023 root INFO copying ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_info.py -> build/lib/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:41,024 root INFO creating build/lib/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:41,024 root INFO copying ansible_collections/cisco/ise/plugins/plugin_utils/__init__.py -> build/lib/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:41,024 root INFO copying ansible_collections/cisco/ise/plugins/plugin_utils/exceptions.py -> build/lib/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:41,024 root INFO copying ansible_collections/cisco/ise/plugins/plugin_utils/ise.py -> build/lib/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:41,024 root INFO copying ansible_collections/cisco/ise/plugins/plugin_utils/personas_utils.py -> build/lib/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:41,025 root INFO creating build/lib/ansible_collections/cisco/ise/roles 2023-04-28 05:57:41,025 root INFO creating build/lib/ansible_collections/cisco/ise/roles/aws_deployment 2023-04-28 05:57:41,025 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/README.md -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment 2023-04-28 05:57:41,025 root INFO creating build/lib/ansible_collections/cisco/ise/roles/aws_deployment/defaults 2023-04-28 05:57:41,025 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/defaults/main.yml -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment/defaults 2023-04-28 05:57:41,026 root INFO creating build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks 2023-04-28 05:57:41,026 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/tasks/main.yml -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks 2023-04-28 05:57:41,026 root INFO creating build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:41,026 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/aws.yml -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:41,026 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/large_deployment.yml -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:41,026 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/medium_deployment.yml -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:41,027 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/single_node.yml -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:41,027 root INFO copying ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/small_deployment.yml -> build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:41,027 root INFO creating build/lib/ansible_collections/cisco/ise/roles/personas_deployment 2023-04-28 05:57:41,027 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/.travis.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment 2023-04-28 05:57:41,027 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/README.md -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment 2023-04-28 05:57:41,028 root INFO creating build/lib/ansible_collections/cisco/ise/roles/personas_deployment/defaults 2023-04-28 05:57:41,028 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/defaults/main.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/defaults 2023-04-28 05:57:41,028 root INFO creating build/lib/ansible_collections/cisco/ise/roles/personas_deployment/handlers 2023-04-28 05:57:41,028 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/handlers/main.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/handlers 2023-04-28 05:57:41,028 root INFO creating build/lib/ansible_collections/cisco/ise/roles/personas_deployment/meta 2023-04-28 05:57:41,029 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/meta/main.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/meta 2023-04-28 05:57:41,029 root INFO creating build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:41,029 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/tasks/large_deployment.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:41,029 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/tasks/main.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:41,029 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/tasks/medium_deployment.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:41,030 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/tasks/small_deployment.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:41,030 root INFO creating build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tests 2023-04-28 05:57:41,030 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/tests/inventory -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tests 2023-04-28 05:57:41,030 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/tests/test.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tests 2023-04-28 05:57:41,030 root INFO creating build/lib/ansible_collections/cisco/ise/roles/personas_deployment/vars 2023-04-28 05:57:41,030 root INFO copying ansible_collections/cisco/ise/roles/personas_deployment/vars/main.yml -> build/lib/ansible_collections/cisco/ise/roles/personas_deployment/vars 2023-04-28 05:57:41,031 root INFO creating build/lib/ansible_collections/cisco/meraki 2023-04-28 05:57:41,031 root INFO copying ansible_collections/cisco/meraki/CHANGELOG.rst -> build/lib/ansible_collections/cisco/meraki 2023-04-28 05:57:41,031 root INFO copying ansible_collections/cisco/meraki/COPYING -> build/lib/ansible_collections/cisco/meraki 2023-04-28 05:57:41,031 root INFO copying ansible_collections/cisco/meraki/FILES.json -> build/lib/ansible_collections/cisco/meraki 2023-04-28 05:57:41,032 root INFO copying ansible_collections/cisco/meraki/MANIFEST.json -> build/lib/ansible_collections/cisco/meraki 2023-04-28 05:57:41,032 root INFO copying ansible_collections/cisco/meraki/README.md -> build/lib/ansible_collections/cisco/meraki 2023-04-28 05:57:41,032 root INFO copying ansible_collections/cisco/meraki/contributing.md -> build/lib/ansible_collections/cisco/meraki 2023-04-28 05:57:41,032 root INFO creating build/lib/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:41,032 root INFO copying ansible_collections/cisco/meraki/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:41,033 root INFO copying ansible_collections/cisco/meraki/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:41,033 root INFO copying ansible_collections/cisco/meraki/changelogs/config.yaml -> build/lib/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:41,033 root INFO creating build/lib/ansible_collections/cisco/meraki/meta 2023-04-28 05:57:41,033 root INFO copying ansible_collections/cisco/meraki/meta/execution-environment.yml -> build/lib/ansible_collections/cisco/meraki/meta 2023-04-28 05:57:41,034 root INFO copying ansible_collections/cisco/meraki/meta/runtime.yml -> build/lib/ansible_collections/cisco/meraki/meta 2023-04-28 05:57:41,034 root INFO creating build/lib/ansible_collections/cisco/meraki/plugins 2023-04-28 05:57:41,034 root INFO creating build/lib/ansible_collections/cisco/meraki/plugins/doc_fragments 2023-04-28 05:57:41,034 root INFO copying ansible_collections/cisco/meraki/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/meraki/plugins/doc_fragments 2023-04-28 05:57:41,034 root INFO copying ansible_collections/cisco/meraki/plugins/doc_fragments/meraki.py -> build/lib/ansible_collections/cisco/meraki/plugins/doc_fragments 2023-04-28 05:57:41,034 root INFO creating build/lib/ansible_collections/cisco/meraki/plugins/module_utils 2023-04-28 05:57:41,035 root INFO creating build/lib/ansible_collections/cisco/meraki/plugins/module_utils/network 2023-04-28 05:57:41,035 root INFO creating build/lib/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki 2023-04-28 05:57:41,035 root INFO copying ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/__init__.py -> build/lib/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki 2023-04-28 05:57:41,035 root INFO copying ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/meraki.py -> build/lib/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki 2023-04-28 05:57:41,035 root INFO creating build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,035 root INFO copying ansible_collections/cisco/meraki/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,036 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_action_batch.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,036 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_admin.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,036 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_alert.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,036 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_config_template.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,037 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_device.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,037 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_firewalled_services.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,037 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_management_interface.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,037 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mr_l3_firewall.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,037 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mr_l7_firewall.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,038 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mr_radio.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,038 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mr_rf_profile.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,038 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mr_settings.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,038 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mr_ssid.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,039 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_access_list.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,039 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_access_policies.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,039 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_l3_interface.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,039 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_link_aggregation.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,040 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_ospf.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,040 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_stack.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,040 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_stack_l3_interface.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,040 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_storm_control.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,041 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_ms_switchport.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,041 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_content_filtering.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,041 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_intrusion_prevention.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,041 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l2_interface.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,041 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l3_firewall.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,042 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l7_firewall.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,042 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_malware.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,042 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_nat.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,043 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_network_vlan_settings.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,043 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_site_to_site_firewall.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,043 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_site_to_site_vpn.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,043 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_static_route.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,043 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_third_party_vpn_peers.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,044 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_uplink_bandwidth.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,044 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_mx_vlan.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,044 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_network.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,044 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_network_settings.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,045 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_organization.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,045 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_snmp.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,045 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_syslog.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,045 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_webhook.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,046 root INFO copying ansible_collections/cisco/meraki/plugins/modules/meraki_webhook_payload_template.py -> build/lib/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:41,046 root INFO creating build/lib/ansible_collections/cisco/meraki/scripts 2023-04-28 05:57:41,046 root INFO creating build/lib/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:41,046 root INFO copying ansible_collections/cisco/meraki/scripts/sublime-build/build.py -> build/lib/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:41,046 root INFO copying ansible_collections/cisco/meraki/scripts/sublime-build/build.py.generic -> build/lib/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:41,047 root INFO copying ansible_collections/cisco/meraki/scripts/sublime-build/requirements.txt -> build/lib/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:41,047 root INFO creating build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,047 root INFO copying ansible_collections/cisco/mso/CHANGELOG.rst -> build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,047 root INFO copying ansible_collections/cisco/mso/FILES.json -> build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,047 root INFO copying ansible_collections/cisco/mso/LICENSE -> build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,048 root INFO copying ansible_collections/cisco/mso/MANIFEST.json -> build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,048 root INFO copying ansible_collections/cisco/mso/README.md -> build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,048 root INFO copying ansible_collections/cisco/mso/codecov.yml -> build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,048 root INFO copying ansible_collections/cisco/mso/requirements.txt -> build/lib/ansible_collections/cisco/mso 2023-04-28 05:57:41,049 root INFO creating build/lib/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:41,049 root INFO copying ansible_collections/cisco/mso/changelogs/.gitignore -> build/lib/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:41,049 root INFO copying ansible_collections/cisco/mso/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:41,049 root INFO copying ansible_collections/cisco/mso/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:41,049 root INFO copying ansible_collections/cisco/mso/changelogs/config.yaml -> build/lib/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:41,050 root INFO creating build/lib/ansible_collections/cisco/mso/meta 2023-04-28 05:57:41,050 root INFO copying ansible_collections/cisco/mso/meta/runtime.yml -> build/lib/ansible_collections/cisco/mso/meta 2023-04-28 05:57:41,050 root INFO creating build/lib/ansible_collections/cisco/mso/plugins 2023-04-28 05:57:41,050 root INFO copying ansible_collections/cisco/mso/plugins/.DS_Store -> build/lib/ansible_collections/cisco/mso/plugins 2023-04-28 05:57:41,050 root INFO creating build/lib/ansible_collections/cisco/mso/plugins/doc_fragments 2023-04-28 05:57:41,050 root INFO copying ansible_collections/cisco/mso/plugins/doc_fragments/modules.py -> build/lib/ansible_collections/cisco/mso/plugins/doc_fragments 2023-04-28 05:57:41,051 root INFO creating build/lib/ansible_collections/cisco/mso/plugins/httpapi 2023-04-28 05:57:41,051 root INFO copying ansible_collections/cisco/mso/plugins/httpapi/mso.py -> build/lib/ansible_collections/cisco/mso/plugins/httpapi 2023-04-28 05:57:41,051 root INFO creating build/lib/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:41,051 root INFO copying ansible_collections/cisco/mso/plugins/module_utils/constants.py -> build/lib/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:41,051 root INFO copying ansible_collections/cisco/mso/plugins/module_utils/mso.py -> build/lib/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:41,052 root INFO copying ansible_collections/cisco/mso/plugins/module_utils/schema.py -> build/lib/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:41,052 root INFO creating build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,052 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_backup.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,052 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_backup_schedule.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,053 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_dhcp_option_policy.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,053 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_dhcp_option_policy_option.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,053 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_dhcp_relay_policy.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,053 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_dhcp_relay_policy_provider.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,054 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_label.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,054 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_remote_location.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,054 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_rest.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,054 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_role.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,054 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,055 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_clone.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,055 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,055 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,055 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,056 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_bulk_staticport.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,056 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_domain.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,056 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_selector.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,056 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_staticleaf.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,057 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_staticport.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,057 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_subnet.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,057 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,057 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd_l3out.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,058 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd_subnet.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,058 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_external_epg.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,058 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_external_epg_selector.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,058 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_l3out.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,058 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_service_graph.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,059 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,059 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,059 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_cidr.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,059 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_cidr_subnet.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,060 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_hub_network.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,060 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,060 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,060 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,061 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_contract.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,061 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_selector.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,061 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_subnet.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,061 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,061 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd_dhcp_policy.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,062 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd_subnet.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,062 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_clone.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,062 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_contract_filter.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,062 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_contract_service_graph.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,063 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_deploy.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,063 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_deploy_status.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,063 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,063 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_contract.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,064 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_selector.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,064 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_subnet.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,064 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_externalepg.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,064 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_filter_entry.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,064 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_l3out.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,065 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_migrate.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,065 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_service_graph.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,065 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_vrf.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,065 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_template_vrf_contract.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,066 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_schema_validate.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,066 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_service_node_type.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,066 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_site.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,066 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_tenant.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,067 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_tenant_site.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,067 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_user.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,067 root INFO copying ansible_collections/cisco/mso/plugins/modules/mso_version.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,067 root INFO copying ansible_collections/cisco/mso/plugins/modules/ndo_schema_template_deploy.py -> build/lib/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:41,068 root INFO creating build/lib/ansible_collections/cisco/nso 2023-04-28 05:57:41,068 root INFO copying ansible_collections/cisco/nso/CHANGELOG.rst -> build/lib/ansible_collections/cisco/nso 2023-04-28 05:57:41,068 root INFO copying ansible_collections/cisco/nso/FILES.json -> build/lib/ansible_collections/cisco/nso 2023-04-28 05:57:41,068 root INFO copying ansible_collections/cisco/nso/LICENSE -> build/lib/ansible_collections/cisco/nso 2023-04-28 05:57:41,068 root INFO copying ansible_collections/cisco/nso/MANIFEST.json -> build/lib/ansible_collections/cisco/nso 2023-04-28 05:57:41,069 root INFO copying ansible_collections/cisco/nso/README.md -> build/lib/ansible_collections/cisco/nso 2023-04-28 05:57:41,069 root INFO creating build/lib/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:41,069 root INFO copying ansible_collections/cisco/nso/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:41,069 root INFO copying ansible_collections/cisco/nso/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:41,069 root INFO copying ansible_collections/cisco/nso/changelogs/config.yaml -> build/lib/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:41,070 root INFO creating build/lib/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:41,070 root INFO copying ansible_collections/cisco/nso/changelogs/fragments/1.0.1.yml -> build/lib/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:41,070 root INFO copying ansible_collections/cisco/nso/changelogs/fragments/1.0.2.yml -> build/lib/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:41,070 root INFO copying ansible_collections/cisco/nso/changelogs/fragments/1.0.3.yml -> build/lib/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:41,070 root INFO creating build/lib/ansible_collections/cisco/nso/meta 2023-04-28 05:57:41,071 root INFO copying ansible_collections/cisco/nso/meta/runtime.yml -> build/lib/ansible_collections/cisco/nso/meta 2023-04-28 05:57:41,071 root INFO creating build/lib/ansible_collections/cisco/nso/plugins 2023-04-28 05:57:41,071 root INFO creating build/lib/ansible_collections/cisco/nso/plugins/doc_fragments 2023-04-28 05:57:41,071 root INFO copying ansible_collections/cisco/nso/plugins/doc_fragments/nso.py -> build/lib/ansible_collections/cisco/nso/plugins/doc_fragments 2023-04-28 05:57:41,071 root INFO creating build/lib/ansible_collections/cisco/nso/plugins/module_utils 2023-04-28 05:57:41,071 root INFO copying ansible_collections/cisco/nso/plugins/module_utils/__init__.py -> build/lib/ansible_collections/cisco/nso/plugins/module_utils 2023-04-28 05:57:41,072 root INFO copying ansible_collections/cisco/nso/plugins/module_utils/nso.py -> build/lib/ansible_collections/cisco/nso/plugins/module_utils 2023-04-28 05:57:41,072 root INFO creating build/lib/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:41,072 root INFO copying ansible_collections/cisco/nso/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:41,072 root INFO copying ansible_collections/cisco/nso/plugins/modules/nso_action.py -> build/lib/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:41,072 root INFO copying ansible_collections/cisco/nso/plugins/modules/nso_config.py -> build/lib/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:41,073 root INFO copying ansible_collections/cisco/nso/plugins/modules/nso_query.py -> build/lib/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:41,073 root INFO copying ansible_collections/cisco/nso/plugins/modules/nso_show.py -> build/lib/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:41,073 root INFO copying ansible_collections/cisco/nso/plugins/modules/nso_verify.py -> build/lib/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:41,073 root INFO creating build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,073 root INFO copying ansible_collections/cisco/nxos/CHANGELOG.rst -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,074 root INFO copying ansible_collections/cisco/nxos/FILES.json -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,075 root INFO copying ansible_collections/cisco/nxos/LICENSE -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,075 root INFO copying ansible_collections/cisco/nxos/MANIFEST.json -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,075 root INFO copying ansible_collections/cisco/nxos/README.md -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,075 root INFO copying ansible_collections/cisco/nxos/bindep.txt -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,076 root INFO copying ansible_collections/cisco/nxos/codecov.yml -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,076 root INFO copying ansible_collections/cisco/nxos/pyproject.toml -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,076 root INFO copying ansible_collections/cisco/nxos/requirements.txt -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,076 root INFO copying ansible_collections/cisco/nxos/test-requirements.txt -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,077 root INFO copying ansible_collections/cisco/nxos/tox.ini -> build/lib/ansible_collections/cisco/nxos 2023-04-28 05:57:41,077 root INFO creating build/lib/ansible_collections/cisco/nxos/changelogs 2023-04-28 05:57:41,077 root INFO copying ansible_collections/cisco/nxos/changelogs/changelog.yaml -> build/lib/ansible_collections/cisco/nxos/changelogs 2023-04-28 05:57:41,077 root INFO copying ansible_collections/cisco/nxos/changelogs/config.yaml -> build/lib/ansible_collections/cisco/nxos/changelogs 2023-04-28 05:57:41,077 root INFO creating build/lib/ansible_collections/cisco/nxos/changelogs/fragments 2023-04-28 05:57:41,078 root INFO copying ansible_collections/cisco/nxos/changelogs/fragments/.keep -> build/lib/ansible_collections/cisco/nxos/changelogs/fragments 2023-04-28 05:57:41,078 root INFO creating build/lib/ansible_collections/cisco/nxos/meta 2023-04-28 05:57:41,078 root INFO copying ansible_collections/cisco/nxos/meta/runtime.yml -> build/lib/ansible_collections/cisco/nxos/meta 2023-04-28 05:57:41,078 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins 2023-04-28 05:57:41,078 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,078 root INFO copying ansible_collections/cisco/nxos/plugins/action/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,079 root INFO copying ansible_collections/cisco/nxos/plugins/action/aaa_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,079 root INFO copying ansible_collections/cisco/nxos/plugins/action/aaa_server_host.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,079 root INFO copying ansible_collections/cisco/nxos/plugins/action/acl.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,079 root INFO copying ansible_collections/cisco/nxos/plugins/action/acl_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,080 root INFO copying ansible_collections/cisco/nxos/plugins/action/acl_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,080 root INFO copying ansible_collections/cisco/nxos/plugins/action/acls.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,080 root INFO copying ansible_collections/cisco/nxos/plugins/action/banner.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,080 root INFO copying ansible_collections/cisco/nxos/plugins/action/bfd_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,080 root INFO copying ansible_collections/cisco/nxos/plugins/action/bfd_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,081 root INFO copying ansible_collections/cisco/nxos/plugins/action/bgp.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,081 root INFO copying ansible_collections/cisco/nxos/plugins/action/bgp_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,081 root INFO copying ansible_collections/cisco/nxos/plugins/action/bgp_af.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,081 root INFO copying ansible_collections/cisco/nxos/plugins/action/bgp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,082 root INFO copying ansible_collections/cisco/nxos/plugins/action/bgp_neighbor.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,082 root INFO copying ansible_collections/cisco/nxos/plugins/action/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,082 root INFO copying ansible_collections/cisco/nxos/plugins/action/bgp_neighbor_af.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,082 root INFO copying ansible_collections/cisco/nxos/plugins/action/command.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,082 root INFO copying ansible_collections/cisco/nxos/plugins/action/config.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,083 root INFO copying ansible_collections/cisco/nxos/plugins/action/devicealias.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,083 root INFO copying ansible_collections/cisco/nxos/plugins/action/evpn_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,083 root INFO copying ansible_collections/cisco/nxos/plugins/action/evpn_vni.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,083 root INFO copying ansible_collections/cisco/nxos/plugins/action/facts.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,084 root INFO copying ansible_collections/cisco/nxos/plugins/action/feature.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,084 root INFO copying ansible_collections/cisco/nxos/plugins/action/file_copy.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,084 root INFO copying ansible_collections/cisco/nxos/plugins/action/gir.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,084 root INFO copying ansible_collections/cisco/nxos/plugins/action/gir_profile_management.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,084 root INFO copying ansible_collections/cisco/nxos/plugins/action/hostname.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,085 root INFO copying ansible_collections/cisco/nxos/plugins/action/hsrp.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,085 root INFO copying ansible_collections/cisco/nxos/plugins/action/hsrp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,085 root INFO copying ansible_collections/cisco/nxos/plugins/action/igmp.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,085 root INFO copying ansible_collections/cisco/nxos/plugins/action/igmp_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,086 root INFO copying ansible_collections/cisco/nxos/plugins/action/igmp_snooping.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,086 root INFO copying ansible_collections/cisco/nxos/plugins/action/install_os.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,086 root INFO copying ansible_collections/cisco/nxos/plugins/action/interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,086 root INFO copying ansible_collections/cisco/nxos/plugins/action/interface_ospf.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,087 root INFO copying ansible_collections/cisco/nxos/plugins/action/interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,087 root INFO copying ansible_collections/cisco/nxos/plugins/action/l2_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,087 root INFO copying ansible_collections/cisco/nxos/plugins/action/l2_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,087 root INFO copying ansible_collections/cisco/nxos/plugins/action/l3_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,087 root INFO copying ansible_collections/cisco/nxos/plugins/action/l3_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,088 root INFO copying ansible_collections/cisco/nxos/plugins/action/lacp.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,088 root INFO copying ansible_collections/cisco/nxos/plugins/action/lacp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,088 root INFO copying ansible_collections/cisco/nxos/plugins/action/lag_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,088 root INFO copying ansible_collections/cisco/nxos/plugins/action/linkagg.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,089 root INFO copying ansible_collections/cisco/nxos/plugins/action/lldp.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,089 root INFO copying ansible_collections/cisco/nxos/plugins/action/lldp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,089 root INFO copying ansible_collections/cisco/nxos/plugins/action/lldp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,089 root INFO copying ansible_collections/cisco/nxos/plugins/action/logging.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,089 root INFO copying ansible_collections/cisco/nxos/plugins/action/logging_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,090 root INFO copying ansible_collections/cisco/nxos/plugins/action/ntp.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,090 root INFO copying ansible_collections/cisco/nxos/plugins/action/ntp_auth.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,090 root INFO copying ansible_collections/cisco/nxos/plugins/action/ntp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,090 root INFO copying ansible_collections/cisco/nxos/plugins/action/ntp_options.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,091 root INFO copying ansible_collections/cisco/nxos/plugins/action/nxapi.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,091 root INFO copying ansible_collections/cisco/nxos/plugins/action/nxos.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,091 root INFO copying ansible_collections/cisco/nxos/plugins/action/ospf.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,091 root INFO copying ansible_collections/cisco/nxos/plugins/action/ospf_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,092 root INFO copying ansible_collections/cisco/nxos/plugins/action/ospf_vrf.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,092 root INFO copying ansible_collections/cisco/nxos/plugins/action/ospfv2.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,092 root INFO copying ansible_collections/cisco/nxos/plugins/action/ospfv3.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,092 root INFO copying ansible_collections/cisco/nxos/plugins/action/overlay_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,092 root INFO copying ansible_collections/cisco/nxos/plugins/action/pim.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,093 root INFO copying ansible_collections/cisco/nxos/plugins/action/pim_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,093 root INFO copying ansible_collections/cisco/nxos/plugins/action/pim_rp_address.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,093 root INFO copying ansible_collections/cisco/nxos/plugins/action/ping.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,093 root INFO copying ansible_collections/cisco/nxos/plugins/action/prefix_lists.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,094 root INFO copying ansible_collections/cisco/nxos/plugins/action/reboot.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,094 root INFO copying ansible_collections/cisco/nxos/plugins/action/rollback.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,094 root INFO copying ansible_collections/cisco/nxos/plugins/action/route_maps.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,094 root INFO copying ansible_collections/cisco/nxos/plugins/action/rpm.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,094 root INFO copying ansible_collections/cisco/nxos/plugins/action/smu.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,095 root INFO copying ansible_collections/cisco/nxos/plugins/action/snapshot.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,095 root INFO copying ansible_collections/cisco/nxos/plugins/action/snmp_community.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,095 root INFO copying ansible_collections/cisco/nxos/plugins/action/snmp_contact.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,095 root INFO copying ansible_collections/cisco/nxos/plugins/action/snmp_host.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,096 root INFO copying ansible_collections/cisco/nxos/plugins/action/snmp_location.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,096 root INFO copying ansible_collections/cisco/nxos/plugins/action/snmp_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,096 root INFO copying ansible_collections/cisco/nxos/plugins/action/snmp_traps.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,096 root INFO copying ansible_collections/cisco/nxos/plugins/action/snmp_user.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,097 root INFO copying ansible_collections/cisco/nxos/plugins/action/static_route.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,097 root INFO copying ansible_collections/cisco/nxos/plugins/action/static_routes.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,097 root INFO copying ansible_collections/cisco/nxos/plugins/action/system.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,097 root INFO copying ansible_collections/cisco/nxos/plugins/action/telemetry.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,097 root INFO copying ansible_collections/cisco/nxos/plugins/action/udld.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,098 root INFO copying ansible_collections/cisco/nxos/plugins/action/udld_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,098 root INFO copying ansible_collections/cisco/nxos/plugins/action/user.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,098 root INFO copying ansible_collections/cisco/nxos/plugins/action/vlan.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,098 root INFO copying ansible_collections/cisco/nxos/plugins/action/vlans.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,099 root INFO copying ansible_collections/cisco/nxos/plugins/action/vpc.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,099 root INFO copying ansible_collections/cisco/nxos/plugins/action/vpc_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,099 root INFO copying ansible_collections/cisco/nxos/plugins/action/vrf.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,099 root INFO copying ansible_collections/cisco/nxos/plugins/action/vrf_af.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,100 root INFO copying ansible_collections/cisco/nxos/plugins/action/vrf_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,100 root INFO copying ansible_collections/cisco/nxos/plugins/action/vrrp.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,100 root INFO copying ansible_collections/cisco/nxos/plugins/action/vsan.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,100 root INFO copying ansible_collections/cisco/nxos/plugins/action/vtp_domain.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,100 root INFO copying ansible_collections/cisco/nxos/plugins/action/vtp_password.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,101 root INFO copying ansible_collections/cisco/nxos/plugins/action/vtp_version.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,101 root INFO copying ansible_collections/cisco/nxos/plugins/action/vxlan_vtep.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,101 root INFO copying ansible_collections/cisco/nxos/plugins/action/vxlan_vtep_vni.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,101 root INFO copying ansible_collections/cisco/nxos/plugins/action/zone_zoneset.py -> build/lib/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:41,102 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/cliconf 2023-04-28 05:57:41,102 root INFO copying ansible_collections/cisco/nxos/plugins/cliconf/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/cliconf 2023-04-28 05:57:41,102 root INFO copying ansible_collections/cisco/nxos/plugins/cliconf/nxos.py -> build/lib/ansible_collections/cisco/nxos/plugins/cliconf 2023-04-28 05:57:41,102 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/doc_fragments 2023-04-28 05:57:41,102 root INFO copying ansible_collections/cisco/nxos/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/doc_fragments 2023-04-28 05:57:41,102 root INFO copying ansible_collections/cisco/nxos/plugins/doc_fragments/nxos.py -> build/lib/ansible_collections/cisco/nxos/plugins/doc_fragments 2023-04-28 05:57:41,103 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/filter 2023-04-28 05:57:41,103 root INFO copying ansible_collections/cisco/nxos/plugins/filter/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/filter 2023-04-28 05:57:41,103 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/httpapi 2023-04-28 05:57:41,103 root INFO copying ansible_collections/cisco/nxos/plugins/httpapi/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/httpapi 2023-04-28 05:57:41,103 root INFO copying ansible_collections/cisco/nxos/plugins/httpapi/nxos.py -> build/lib/ansible_collections/cisco/nxos/plugins/httpapi 2023-04-28 05:57:41,104 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/inventory 2023-04-28 05:57:41,104 root INFO copying ansible_collections/cisco/nxos/plugins/inventory/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/inventory 2023-04-28 05:57:41,104 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils 2023-04-28 05:57:41,104 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils 2023-04-28 05:57:41,104 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network 2023-04-28 05:57:41,104 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network 2023-04-28 05:57:41,105 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos 2023-04-28 05:57:41,105 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos 2023-04-28 05:57:41,105 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/nxos.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos 2023-04-28 05:57:41,105 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec 2023-04-28 05:57:41,105 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec 2023-04-28 05:57:41,106 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces 2023-04-28 05:57:41,106 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces 2023-04-28 05:57:41,106 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces 2023-04-28 05:57:41,106 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls 2023-04-28 05:57:41,106 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls 2023-04-28 05:57:41,107 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/acls.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls 2023-04-28 05:57:41,107 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces 2023-04-28 05:57:41,107 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces 2023-04-28 05:57:41,107 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/bfd_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces 2023-04-28 05:57:41,107 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family 2023-04-28 05:57:41,107 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family 2023-04-28 05:57:41,108 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family 2023-04-28 05:57:41,108 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global 2023-04-28 05:57:41,108 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global 2023-04-28 05:57:41,108 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global 2023-04-28 05:57:41,109 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family 2023-04-28 05:57:41,109 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family 2023-04-28 05:57:41,109 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family 2023-04-28 05:57:41,109 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts 2023-04-28 05:57:41,109 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts 2023-04-28 05:57:41,109 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/facts.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts 2023-04-28 05:57:41,110 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname 2023-04-28 05:57:41,110 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname 2023-04-28 05:57:41,110 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/hostname.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname 2023-04-28 05:57:41,110 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces 2023-04-28 05:57:41,110 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces 2023-04-28 05:57:41,111 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/hsrp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces 2023-04-28 05:57:41,111 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces 2023-04-28 05:57:41,111 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces 2023-04-28 05:57:41,111 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces 2023-04-28 05:57:41,111 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces 2023-04-28 05:57:41,112 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces 2023-04-28 05:57:41,112 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces 2023-04-28 05:57:41,112 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces 2023-04-28 05:57:41,112 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces 2023-04-28 05:57:41,112 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces 2023-04-28 05:57:41,113 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp 2023-04-28 05:57:41,113 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp 2023-04-28 05:57:41,113 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/lacp.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp 2023-04-28 05:57:41,113 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces 2023-04-28 05:57:41,113 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces 2023-04-28 05:57:41,113 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces 2023-04-28 05:57:41,114 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces 2023-04-28 05:57:41,114 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces 2023-04-28 05:57:41,114 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces 2023-04-28 05:57:41,114 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global 2023-04-28 05:57:41,114 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global 2023-04-28 05:57:41,115 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global 2023-04-28 05:57:41,115 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces 2023-04-28 05:57:41,115 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces 2023-04-28 05:57:41,115 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces 2023-04-28 05:57:41,115 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global 2023-04-28 05:57:41,116 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global 2023-04-28 05:57:41,116 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global 2023-04-28 05:57:41,116 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global 2023-04-28 05:57:41,116 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global 2023-04-28 05:57:41,116 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global 2023-04-28 05:57:41,117 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces 2023-04-28 05:57:41,117 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces 2023-04-28 05:57:41,117 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces 2023-04-28 05:57:41,117 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2 2023-04-28 05:57:41,117 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2 2023-04-28 05:57:41,117 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2 2023-04-28 05:57:41,118 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3 2023-04-28 05:57:41,118 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3 2023-04-28 05:57:41,118 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3 2023-04-28 05:57:41,118 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists 2023-04-28 05:57:41,119 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists 2023-04-28 05:57:41,119 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists 2023-04-28 05:57:41,119 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps 2023-04-28 05:57:41,119 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps 2023-04-28 05:57:41,119 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/route_maps.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps 2023-04-28 05:57:41,120 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server 2023-04-28 05:57:41,120 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server 2023-04-28 05:57:41,120 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server 2023-04-28 05:57:41,120 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes 2023-04-28 05:57:41,120 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes 2023-04-28 05:57:41,121 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes 2023-04-28 05:57:41,121 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry 2023-04-28 05:57:41,121 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry 2023-04-28 05:57:41,121 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/telemetry.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry 2023-04-28 05:57:41,121 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans 2023-04-28 05:57:41,121 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans 2023-04-28 05:57:41,122 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/vlans.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans 2023-04-28 05:57:41,122 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref 2023-04-28 05:57:41,122 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref 2023-04-28 05:57:41,122 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry 2023-04-28 05:57:41,122 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry 2023-04-28 05:57:41,123 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/telemetry.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry 2023-04-28 05:57:41,123 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config 2023-04-28 05:57:41,123 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config 2023-04-28 05:57:41,123 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces 2023-04-28 05:57:41,123 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces 2023-04-28 05:57:41,123 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces 2023-04-28 05:57:41,124 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls 2023-04-28 05:57:41,124 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls 2023-04-28 05:57:41,124 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/acls.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls 2023-04-28 05:57:41,124 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces 2023-04-28 05:57:41,124 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces 2023-04-28 05:57:41,125 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/bfd_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces 2023-04-28 05:57:41,125 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family 2023-04-28 05:57:41,125 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family 2023-04-28 05:57:41,125 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family 2023-04-28 05:57:41,126 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global 2023-04-28 05:57:41,126 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global 2023-04-28 05:57:41,126 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global 2023-04-28 05:57:41,126 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family 2023-04-28 05:57:41,126 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family 2023-04-28 05:57:41,126 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family 2023-04-28 05:57:41,127 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname 2023-04-28 05:57:41,127 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname 2023-04-28 05:57:41,127 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/hostname.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname 2023-04-28 05:57:41,127 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces 2023-04-28 05:57:41,127 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces 2023-04-28 05:57:41,128 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/hsrp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces 2023-04-28 05:57:41,128 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces 2023-04-28 05:57:41,128 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces 2023-04-28 05:57:41,128 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces 2023-04-28 05:57:41,128 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces 2023-04-28 05:57:41,129 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces 2023-04-28 05:57:41,129 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces 2023-04-28 05:57:41,129 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces 2023-04-28 05:57:41,130 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces 2023-04-28 05:57:41,130 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces 2023-04-28 05:57:41,130 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp 2023-04-28 05:57:41,130 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp 2023-04-28 05:57:41,130 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/lacp.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp 2023-04-28 05:57:41,131 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces 2023-04-28 05:57:41,131 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces 2023-04-28 05:57:41,131 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces 2023-04-28 05:57:41,131 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces 2023-04-28 05:57:41,131 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces 2023-04-28 05:57:41,132 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces 2023-04-28 05:57:41,132 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global 2023-04-28 05:57:41,132 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global 2023-04-28 05:57:41,132 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global 2023-04-28 05:57:41,132 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces 2023-04-28 05:57:41,132 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces 2023-04-28 05:57:41,133 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces 2023-04-28 05:57:41,133 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global 2023-04-28 05:57:41,133 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global 2023-04-28 05:57:41,133 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global 2023-04-28 05:57:41,134 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global 2023-04-28 05:57:41,134 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global 2023-04-28 05:57:41,134 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global 2023-04-28 05:57:41,134 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces 2023-04-28 05:57:41,134 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces 2023-04-28 05:57:41,134 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces 2023-04-28 05:57:41,135 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2 2023-04-28 05:57:41,135 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2 2023-04-28 05:57:41,135 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2 2023-04-28 05:57:41,135 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3 2023-04-28 05:57:41,135 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3 2023-04-28 05:57:41,136 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3 2023-04-28 05:57:41,136 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists 2023-04-28 05:57:41,136 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists 2023-04-28 05:57:41,136 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists 2023-04-28 05:57:41,136 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps 2023-04-28 05:57:41,137 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps 2023-04-28 05:57:41,137 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/route_maps.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps 2023-04-28 05:57:41,137 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server 2023-04-28 05:57:41,137 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server 2023-04-28 05:57:41,137 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server 2023-04-28 05:57:41,138 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes 2023-04-28 05:57:41,138 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes 2023-04-28 05:57:41,138 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes 2023-04-28 05:57:41,138 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry 2023-04-28 05:57:41,138 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry 2023-04-28 05:57:41,139 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/telemetry.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry 2023-04-28 05:57:41,139 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans 2023-04-28 05:57:41,139 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans 2023-04-28 05:57:41,139 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/vlans.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans 2023-04-28 05:57:41,139 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts 2023-04-28 05:57:41,140 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts 2023-04-28 05:57:41,140 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/facts.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts 2023-04-28 05:57:41,140 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces 2023-04-28 05:57:41,140 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces 2023-04-28 05:57:41,140 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces 2023-04-28 05:57:41,141 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls 2023-04-28 05:57:41,141 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls 2023-04-28 05:57:41,141 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/acls.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls 2023-04-28 05:57:41,141 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces 2023-04-28 05:57:41,141 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces 2023-04-28 05:57:41,142 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/bfd_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces 2023-04-28 05:57:41,142 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family 2023-04-28 05:57:41,142 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family 2023-04-28 05:57:41,142 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family 2023-04-28 05:57:41,142 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global 2023-04-28 05:57:41,142 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global 2023-04-28 05:57:41,143 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/bgp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global 2023-04-28 05:57:41,143 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family 2023-04-28 05:57:41,143 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family 2023-04-28 05:57:41,143 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family 2023-04-28 05:57:41,143 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname 2023-04-28 05:57:41,144 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname 2023-04-28 05:57:41,144 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/hostname.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname 2023-04-28 05:57:41,144 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces 2023-04-28 05:57:41,144 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces 2023-04-28 05:57:41,144 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/hsrp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces 2023-04-28 05:57:41,145 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces 2023-04-28 05:57:41,145 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces 2023-04-28 05:57:41,145 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces 2023-04-28 05:57:41,145 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces 2023-04-28 05:57:41,145 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces 2023-04-28 05:57:41,146 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces 2023-04-28 05:57:41,146 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces 2023-04-28 05:57:41,146 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces 2023-04-28 05:57:41,146 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces 2023-04-28 05:57:41,146 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp 2023-04-28 05:57:41,146 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp 2023-04-28 05:57:41,147 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/lacp.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp 2023-04-28 05:57:41,147 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces 2023-04-28 05:57:41,147 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces 2023-04-28 05:57:41,147 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces 2023-04-28 05:57:41,147 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces 2023-04-28 05:57:41,148 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces 2023-04-28 05:57:41,148 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces 2023-04-28 05:57:41,148 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy 2023-04-28 05:57:41,148 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy 2023-04-28 05:57:41,148 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/base.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy 2023-04-28 05:57:41,149 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global 2023-04-28 05:57:41,149 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global 2023-04-28 05:57:41,149 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/lldp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global 2023-04-28 05:57:41,149 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces 2023-04-28 05:57:41,149 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces 2023-04-28 05:57:41,150 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces 2023-04-28 05:57:41,150 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global 2023-04-28 05:57:41,150 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global 2023-04-28 05:57:41,150 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/logging_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global 2023-04-28 05:57:41,150 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global 2023-04-28 05:57:41,151 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global 2023-04-28 05:57:41,151 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/ntp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global 2023-04-28 05:57:41,151 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces 2023-04-28 05:57:41,151 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces 2023-04-28 05:57:41,151 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces 2023-04-28 05:57:41,152 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2 2023-04-28 05:57:41,152 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2 2023-04-28 05:57:41,152 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/ospfv2.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2 2023-04-28 05:57:41,152 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3 2023-04-28 05:57:41,152 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3 2023-04-28 05:57:41,152 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/ospfv3.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3 2023-04-28 05:57:41,153 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists 2023-04-28 05:57:41,153 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists 2023-04-28 05:57:41,153 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists 2023-04-28 05:57:41,153 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps 2023-04-28 05:57:41,153 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps 2023-04-28 05:57:41,154 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/route_maps.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps 2023-04-28 05:57:41,154 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server 2023-04-28 05:57:41,154 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server 2023-04-28 05:57:41,154 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/snmp_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server 2023-04-28 05:57:41,154 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes 2023-04-28 05:57:41,154 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes 2023-04-28 05:57:41,155 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/static_routes.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes 2023-04-28 05:57:41,155 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry 2023-04-28 05:57:41,155 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry 2023-04-28 05:57:41,155 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/telemetry.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry 2023-04-28 05:57:41,155 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans 2023-04-28 05:57:41,156 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans 2023-04-28 05:57:41,156 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/vlans.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans 2023-04-28 05:57:41,156 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,156 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,156 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,157 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,157 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,157 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/hostname.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,158 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/logging_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,158 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ntp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,158 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospf_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,158 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospfv2.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,159 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospfv3.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,159 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/prefix_lists.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,159 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/route_maps.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,159 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/snmp_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:41,160 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils 2023-04-28 05:57:41,160 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils 2023-04-28 05:57:41,160 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/utils.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils 2023-04-28 05:57:41,160 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry 2023-04-28 05:57:41,160 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry 2023-04-28 05:57:41,161 root INFO copying ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/telemetry.py -> build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry 2023-04-28 05:57:41,161 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,161 root INFO copying ansible_collections/cisco/nxos/plugins/modules/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,161 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_aaa_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,161 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_aaa_server_host.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,162 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_acl_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,162 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_acls.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,162 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_banner.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,162 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bfd_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,163 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bfd_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,163 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bgp.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,163 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,163 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_af.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,164 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,164 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,164 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor_address_family.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,164 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor_af.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,165 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_command.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,165 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_config.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,165 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_devicealias.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,165 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_evpn_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,166 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_evpn_vni.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,166 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_facts.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,166 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_feature.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,166 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_file_copy.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,167 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_gir.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,167 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_gir_profile_management.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,167 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_hostname.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,167 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_hsrp.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,168 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_hsrp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,168 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_igmp.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,168 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_igmp_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,168 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_igmp_snooping.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,168 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_install_os.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,169 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,169 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_l2_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,169 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_l3_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,169 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_lacp.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,170 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_lacp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,170 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_lag_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,170 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_lldp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,170 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_lldp_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,171 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_logging.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,171 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_logging_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,171 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ntp.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,171 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_auth.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,172 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,172 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_options.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,172 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_nxapi.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,172 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ospf_interfaces.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,173 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ospfv2.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,173 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ospfv3.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,173 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_overlay_global.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,173 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_pim.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,174 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_pim_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,174 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_pim_rp_address.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,174 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_ping.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,174 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_prefix_lists.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,175 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_reboot.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,175 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_rollback.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,175 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_route_maps.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,175 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_rpm.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,176 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snapshot.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,176 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_community.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,176 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_contact.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,176 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_host.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,177 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_location.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,177 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_server.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,177 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_traps.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,177 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_user.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,178 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_static_routes.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,178 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_system.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,178 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_telemetry.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,178 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_udld.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,179 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_udld_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,179 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_user.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,179 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vlans.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,179 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vpc.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,179 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vpc_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,180 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vrf.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,180 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vrf_af.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,180 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vrf_interface.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,180 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vrrp.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,181 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vsan.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,181 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_domain.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,181 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_password.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,181 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_version.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,182 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vxlan_vtep.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,182 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_vxlan_vtep_vni.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,182 root INFO copying ansible_collections/cisco/nxos/plugins/modules/nxos_zone_zoneset.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:41,182 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:41,183 root INFO copying ansible_collections/cisco/nxos/plugins/modules/storage/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:41,183 root INFO copying ansible_collections/cisco/nxos/plugins/modules/storage/nxos_devicealias.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:41,183 root INFO copying ansible_collections/cisco/nxos/plugins/modules/storage/nxos_vsan.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:41,183 root INFO copying ansible_collections/cisco/nxos/plugins/modules/storage/nxos_zone_zoneset.py -> build/lib/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:41,184 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/netconf 2023-04-28 05:57:41,184 root INFO copying ansible_collections/cisco/nxos/plugins/netconf/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/netconf 2023-04-28 05:57:41,184 root INFO copying ansible_collections/cisco/nxos/plugins/netconf/nxos.py -> build/lib/ansible_collections/cisco/nxos/plugins/netconf 2023-04-28 05:57:41,184 root INFO creating build/lib/ansible_collections/cisco/nxos/plugins/terminal 2023-04-28 05:57:41,184 root INFO copying ansible_collections/cisco/nxos/plugins/terminal/__init__.py -> build/lib/ansible_collections/cisco/nxos/plugins/terminal 2023-04-28 05:57:41,184 root INFO copying ansible_collections/cisco/nxos/plugins/terminal/nxos.py -> build/lib/ansible_collections/cisco/nxos/plugins/terminal 2023-04-28 05:57:41,185 root INFO creating build/lib/ansible_collections/cisco/ucs 2023-04-28 05:57:41,185 root INFO copying ansible_collections/cisco/ucs/Development.md -> build/lib/ansible_collections/cisco/ucs 2023-04-28 05:57:41,185 root INFO copying ansible_collections/cisco/ucs/FILES.json -> build/lib/ansible_collections/cisco/ucs 2023-04-28 05:57:41,185 root INFO copying ansible_collections/cisco/ucs/LICENSE.txt -> build/lib/ansible_collections/cisco/ucs 2023-04-28 05:57:41,185 root INFO copying ansible_collections/cisco/ucs/MANIFEST.json -> build/lib/ansible_collections/cisco/ucs 2023-04-28 05:57:41,186 root INFO copying ansible_collections/cisco/ucs/README.md -> build/lib/ansible_collections/cisco/ucs 2023-04-28 05:57:41,186 root INFO copying ansible_collections/cisco/ucs/requirements.txt -> build/lib/ansible_collections/cisco/ucs 2023-04-28 05:57:41,186 root INFO creating build/lib/ansible_collections/cisco/ucs/meta 2023-04-28 05:57:41,186 root INFO copying ansible_collections/cisco/ucs/meta/runtime.yml -> build/lib/ansible_collections/cisco/ucs/meta 2023-04-28 05:57:41,186 root INFO creating build/lib/ansible_collections/cisco/ucs/misc 2023-04-28 05:57:41,187 root INFO copying ansible_collections/cisco/ucs/misc/Impact DNW07 UCS Ansible Collection Lab Guide.pdf -> build/lib/ansible_collections/cisco/ucs/misc 2023-04-28 05:57:41,187 root INFO copying ansible_collections/cisco/ucs/misc/README.md -> build/lib/ansible_collections/cisco/ucs/misc 2023-04-28 05:57:41,188 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,188 root INFO copying ansible_collections/cisco/ucs/playbooks/example_playbook.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,188 root INFO copying ansible_collections/cisco/ucs/playbooks/fw_download_config_hfp.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,188 root INFO copying ansible_collections/cisco/ucs/playbooks/inventory -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,188 root INFO copying ansible_collections/cisco/ucs/playbooks/sandbox_inventory -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,189 root INFO copying ansible_collections/cisco/ucs/playbooks/server_deploy.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,189 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_disk_group_policy.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,189 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_dns_server.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,189 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_graphics_card_policy.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,190 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_ip_pool.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,190 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_lan_connectivity.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,190 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_mac_pool.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,190 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_managed_objects.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,190 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_ntp_server.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,191 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_org.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,191 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_query.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,191 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_san_connectivity.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,191 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_scrub_policy.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,191 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_serial_over_lan_policy.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,192 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_server_maintenance.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,192 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_service_profile_association.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,192 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_service_profile_from_template.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,192 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_service_profile_template.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,193 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_sp_vnic_order.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,193 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_storage_profile.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,193 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_system_qos.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,193 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_timezone.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,193 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_uuid_pool.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,194 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_vhba_template.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,194 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_vlan_find.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,194 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_vlan_to_group.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,194 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_vlans.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,195 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_vnic_template.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,195 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_vsans.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,195 root INFO copying ansible_collections/cisco/ucs/playbooks/ucs_wwn_pool.yml -> build/lib/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:41,195 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles 2023-04-28 05:57:41,195 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers 2023-04-28 05:57:41,195 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/defaults 2023-04-28 05:57:41,196 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/defaults/tasks 2023-04-28 05:57:41,196 root INFO copying ansible_collections/cisco/ucs/playbooks/roles/servers/defaults/tasks/main.yml -> build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/defaults/tasks 2023-04-28 05:57:41,196 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates 2023-04-28 05:57:41,196 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates/tasks 2023-04-28 05:57:41,196 root INFO copying ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates/tasks/main.yml -> build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates/tasks 2023-04-28 05:57:41,196 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles 2023-04-28 05:57:41,197 root INFO creating build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles/tasks 2023-04-28 05:57:41,197 root INFO copying ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles/tasks/main.yml -> build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles/tasks 2023-04-28 05:57:41,197 root INFO creating build/lib/ansible_collections/cisco/ucs/plugins 2023-04-28 05:57:41,197 root INFO copying ansible_collections/cisco/ucs/plugins/README.md -> build/lib/ansible_collections/cisco/ucs/plugins 2023-04-28 05:57:41,197 root INFO creating build/lib/ansible_collections/cisco/ucs/plugins/doc_fragments 2023-04-28 05:57:41,197 root INFO copying ansible_collections/cisco/ucs/plugins/doc_fragments/ucs.py -> build/lib/ansible_collections/cisco/ucs/plugins/doc_fragments 2023-04-28 05:57:41,198 root INFO creating build/lib/ansible_collections/cisco/ucs/plugins/module_utils 2023-04-28 05:57:41,198 root INFO copying ansible_collections/cisco/ucs/plugins/module_utils/ucs.py -> build/lib/ansible_collections/cisco/ucs/plugins/module_utils 2023-04-28 05:57:41,198 root INFO creating build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,198 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_disk_group_policy.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,198 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_dns_server.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,199 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_graphics_card_policy.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,199 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_ip_pool.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,199 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_lan_connectivity.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,199 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_mac_pool.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,200 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_managed_objects.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,200 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_ntp_server.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,200 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_org.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,200 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_query.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,201 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_san_connectivity.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,201 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_scrub_policy.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,201 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_serial_over_lan_policy.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,201 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_server_maintenance.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,201 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_association.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,202 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_from_template.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,202 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_template.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,202 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_sp_vnic_order.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,202 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_storage_profile.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,203 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_system_qos.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,203 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_timezone.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,203 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_uuid_pool.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,203 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_vhba_template.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,204 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_vlan_find.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,204 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_vlan_to_group.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,204 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_vlans.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,204 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_vnic_template.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,204 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_vsans.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,205 root INFO copying ansible_collections/cisco/ucs/plugins/modules/ucs_wwn_pool.py -> build/lib/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:41,205 root INFO creating build/lib/ansible_collections/cloud 2023-04-28 05:57:41,205 root INFO creating build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,205 root INFO copying ansible_collections/cloud/common/CHANGELOG.rst -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,205 root INFO copying ansible_collections/cloud/common/FILES.json -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,206 root INFO copying ansible_collections/cloud/common/LICENSE -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,206 root INFO copying ansible_collections/cloud/common/MANIFEST.json -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,206 root INFO copying ansible_collections/cloud/common/README.md -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,206 root INFO copying ansible_collections/cloud/common/requirements.txt -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,207 root INFO copying ansible_collections/cloud/common/test-requirements.txt -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,207 root INFO copying ansible_collections/cloud/common/tox.ini -> build/lib/ansible_collections/cloud/common 2023-04-28 05:57:41,207 root INFO creating build/lib/ansible_collections/cloud/common/changelogs 2023-04-28 05:57:41,207 root INFO copying ansible_collections/cloud/common/changelogs/changelog.yaml -> build/lib/ansible_collections/cloud/common/changelogs 2023-04-28 05:57:41,207 root INFO copying ansible_collections/cloud/common/changelogs/config.yaml -> build/lib/ansible_collections/cloud/common/changelogs 2023-04-28 05:57:41,208 root INFO creating build/lib/ansible_collections/cloud/common/changelogs/fragments 2023-04-28 05:57:41,208 root INFO copying ansible_collections/cloud/common/changelogs/fragments/.keep -> build/lib/ansible_collections/cloud/common/changelogs/fragments 2023-04-28 05:57:41,208 root INFO creating build/lib/ansible_collections/cloud/common/meta 2023-04-28 05:57:41,208 root INFO copying ansible_collections/cloud/common/meta/runtime.yml -> build/lib/ansible_collections/cloud/common/meta 2023-04-28 05:57:41,208 root INFO creating build/lib/ansible_collections/cloud/common/plugins 2023-04-28 05:57:41,208 root INFO creating build/lib/ansible_collections/cloud/common/plugins/lookup 2023-04-28 05:57:41,209 root INFO copying ansible_collections/cloud/common/plugins/lookup/turbo_demo.py -> build/lib/ansible_collections/cloud/common/plugins/lookup 2023-04-28 05:57:41,209 root INFO creating build/lib/ansible_collections/cloud/common/plugins/module_utils 2023-04-28 05:57:41,209 root INFO copying ansible_collections/cloud/common/plugins/module_utils/turbo_demo.py -> build/lib/ansible_collections/cloud/common/plugins/module_utils 2023-04-28 05:57:41,209 root INFO creating build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:41,209 root INFO copying ansible_collections/cloud/common/plugins/module_utils/turbo/common.py -> build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:41,209 root INFO copying ansible_collections/cloud/common/plugins/module_utils/turbo/exceptions.py -> build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:41,210 root INFO copying ansible_collections/cloud/common/plugins/module_utils/turbo/module.py -> build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:41,210 root INFO copying ansible_collections/cloud/common/plugins/module_utils/turbo/server.py -> build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:41,210 root INFO creating build/lib/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:41,210 root INFO copying ansible_collections/cloud/common/plugins/modules/turbo_demo.py -> build/lib/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:41,211 root INFO copying ansible_collections/cloud/common/plugins/modules/turbo_fail.py -> build/lib/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:41,211 root INFO copying ansible_collections/cloud/common/plugins/modules/turbo_import.py -> build/lib/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:41,211 root INFO creating build/lib/ansible_collections/cloud/common/plugins/plugin_utils 2023-04-28 05:57:41,211 root INFO creating build/lib/ansible_collections/cloud/common/plugins/plugin_utils/turbo 2023-04-28 05:57:41,211 root INFO copying ansible_collections/cloud/common/plugins/plugin_utils/turbo/lookup.py -> build/lib/ansible_collections/cloud/common/plugins/plugin_utils/turbo 2023-04-28 05:57:41,212 root INFO creating build/lib/ansible_collections/cloudscale_ch 2023-04-28 05:57:41,212 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,212 root INFO copying ansible_collections/cloudscale_ch/cloud/CHANGELOG.rst -> build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,212 root INFO copying ansible_collections/cloudscale_ch/cloud/CONTRIBUTING.md -> build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,212 root INFO copying ansible_collections/cloudscale_ch/cloud/COPYING -> build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,212 root INFO copying ansible_collections/cloudscale_ch/cloud/FILES.json -> build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,213 root INFO copying ansible_collections/cloudscale_ch/cloud/MANIFEST.json -> build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,213 root INFO copying ansible_collections/cloudscale_ch/cloud/README.md -> build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,213 root INFO copying ansible_collections/cloudscale_ch/cloud/codecov.yml -> build/lib/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:41,213 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:41,214 root INFO copying ansible_collections/cloudscale_ch/cloud/changelogs/.gitignore -> build/lib/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:41,214 root INFO copying ansible_collections/cloudscale_ch/cloud/changelogs/changelog.yaml -> build/lib/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:41,214 root INFO copying ansible_collections/cloudscale_ch/cloud/changelogs/config.yaml -> build/lib/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:41,214 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/changelogs/fragments 2023-04-28 05:57:41,214 root INFO copying ansible_collections/cloudscale_ch/cloud/changelogs/fragments/.keep -> build/lib/ansible_collections/cloudscale_ch/cloud/changelogs/fragments 2023-04-28 05:57:41,215 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/meta 2023-04-28 05:57:41,215 root INFO copying ansible_collections/cloudscale_ch/cloud/meta/runtime.yml -> build/lib/ansible_collections/cloudscale_ch/cloud/meta 2023-04-28 05:57:41,215 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/plugins 2023-04-28 05:57:41,215 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments 2023-04-28 05:57:41,215 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments 2023-04-28 05:57:41,215 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/api_parameters.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments 2023-04-28 05:57:41,216 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/plugins/inventory 2023-04-28 05:57:41,216 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/inventory/__init__.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/inventory 2023-04-28 05:57:41,216 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/inventory/inventory.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/inventory 2023-04-28 05:57:41,216 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/plugins/module_utils 2023-04-28 05:57:41,216 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/module_utils/api.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/module_utils 2023-04-28 05:57:41,216 root INFO creating build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,217 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/__init__.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,217 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/custom_image.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,217 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/floating_ip.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,217 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/network.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,217 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/objects_user.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,218 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/server.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,218 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/server_group.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,218 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/subnet.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,218 root INFO copying ansible_collections/cloudscale_ch/cloud/plugins/modules/volume.py -> build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:41,219 root INFO creating build/lib/ansible_collections/community 2023-04-28 05:57:41,219 root INFO creating build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,219 root INFO copying ansible_collections/community/aws/CHANGELOG.rst -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,219 root INFO copying ansible_collections/community/aws/CONTRIBUTING.md -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,220 root INFO copying ansible_collections/community/aws/COPYING -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,220 root INFO copying ansible_collections/community/aws/FILES.json -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,221 root INFO copying ansible_collections/community/aws/MANIFEST.json -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,221 root INFO copying ansible_collections/community/aws/README.md -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,221 root INFO copying ansible_collections/community/aws/bindep.txt -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,221 root INFO copying ansible_collections/community/aws/requirements.txt -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,222 root INFO copying ansible_collections/community/aws/test-requirements.txt -> build/lib/ansible_collections/community/aws 2023-04-28 05:57:41,222 root INFO creating build/lib/ansible_collections/community/aws/changelogs 2023-04-28 05:57:41,222 root INFO copying ansible_collections/community/aws/changelogs/changelog.yaml -> build/lib/ansible_collections/community/aws/changelogs 2023-04-28 05:57:41,222 root INFO copying ansible_collections/community/aws/changelogs/config.yaml -> build/lib/ansible_collections/community/aws/changelogs 2023-04-28 05:57:41,223 root INFO creating build/lib/ansible_collections/community/aws/changelogs/fragments 2023-04-28 05:57:41,223 root INFO copying ansible_collections/community/aws/changelogs/fragments/.keep -> build/lib/ansible_collections/community/aws/changelogs/fragments 2023-04-28 05:57:41,223 root INFO creating build/lib/ansible_collections/community/aws/meta 2023-04-28 05:57:41,223 root INFO copying ansible_collections/community/aws/meta/runtime.yml -> build/lib/ansible_collections/community/aws/meta 2023-04-28 05:57:41,223 root INFO creating build/lib/ansible_collections/community/aws/plugins 2023-04-28 05:57:41,224 root INFO creating build/lib/ansible_collections/community/aws/plugins/connection 2023-04-28 05:57:41,224 root INFO copying ansible_collections/community/aws/plugins/connection/__init__.py -> build/lib/ansible_collections/community/aws/plugins/connection 2023-04-28 05:57:41,224 root INFO copying ansible_collections/community/aws/plugins/connection/aws_ssm.py -> build/lib/ansible_collections/community/aws/plugins/connection 2023-04-28 05:57:41,224 root INFO creating build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,224 root INFO copying ansible_collections/community/aws/plugins/module_utils/base.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,224 root INFO copying ansible_collections/community/aws/plugins/module_utils/ec2.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,225 root INFO copying ansible_collections/community/aws/plugins/module_utils/etag.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,225 root INFO copying ansible_collections/community/aws/plugins/module_utils/networkfirewall.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,225 root INFO copying ansible_collections/community/aws/plugins/module_utils/opensearch.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,226 root INFO copying ansible_collections/community/aws/plugins/module_utils/sns.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,226 root INFO copying ansible_collections/community/aws/plugins/module_utils/transitgateway.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,226 root INFO copying ansible_collections/community/aws/plugins/module_utils/wafv2.py -> build/lib/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:41,226 root INFO creating build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,226 root INFO copying ansible_collections/community/aws/plugins/modules/__init__.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,227 root INFO copying ansible_collections/community/aws/plugins/modules/accessanalyzer_validate_policy_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,227 root INFO copying ansible_collections/community/aws/plugins/modules/acm_certificate.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,227 root INFO copying ansible_collections/community/aws/plugins/modules/acm_certificate_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,227 root INFO copying ansible_collections/community/aws/plugins/modules/api_gateway.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,228 root INFO copying ansible_collections/community/aws/plugins/modules/api_gateway_domain.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,228 root INFO copying ansible_collections/community/aws/plugins/modules/application_autoscaling_policy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,228 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_complete_lifecycle_action.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,228 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_instance_refresh.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,229 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_instance_refresh_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,229 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_launch_config.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,229 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_launch_config_find.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,229 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_launch_config_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,229 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_lifecycle_hook.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,230 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_policy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,230 root INFO copying ansible_collections/community/aws/plugins/modules/autoscaling_scheduled_action.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,230 root INFO copying ansible_collections/community/aws/plugins/modules/aws_region_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,230 root INFO copying ansible_collections/community/aws/plugins/modules/batch_compute_environment.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,231 root INFO copying ansible_collections/community/aws/plugins/modules/batch_job_definition.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,231 root INFO copying ansible_collections/community/aws/plugins/modules/batch_job_queue.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,231 root INFO copying ansible_collections/community/aws/plugins/modules/cloudformation_exports_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,231 root INFO copying ansible_collections/community/aws/plugins/modules/cloudformation_stack_set.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,232 root INFO copying ansible_collections/community/aws/plugins/modules/cloudfront_distribution.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,232 root INFO copying ansible_collections/community/aws/plugins/modules/cloudfront_distribution_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,232 root INFO copying ansible_collections/community/aws/plugins/modules/cloudfront_invalidation.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,232 root INFO copying ansible_collections/community/aws/plugins/modules/cloudfront_origin_access_identity.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,233 root INFO copying ansible_collections/community/aws/plugins/modules/cloudfront_response_headers_policy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,233 root INFO copying ansible_collections/community/aws/plugins/modules/codebuild_project.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,233 root INFO copying ansible_collections/community/aws/plugins/modules/codecommit_repository.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,233 root INFO copying ansible_collections/community/aws/plugins/modules/codepipeline.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,234 root INFO copying ansible_collections/community/aws/plugins/modules/config_aggregation_authorization.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,234 root INFO copying ansible_collections/community/aws/plugins/modules/config_aggregator.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,234 root INFO copying ansible_collections/community/aws/plugins/modules/config_delivery_channel.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,234 root INFO copying ansible_collections/community/aws/plugins/modules/config_recorder.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,235 root INFO copying ansible_collections/community/aws/plugins/modules/config_rule.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,235 root INFO copying ansible_collections/community/aws/plugins/modules/data_pipeline.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,235 root INFO copying ansible_collections/community/aws/plugins/modules/directconnect_confirm_connection.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,235 root INFO copying ansible_collections/community/aws/plugins/modules/directconnect_connection.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,236 root INFO copying ansible_collections/community/aws/plugins/modules/directconnect_gateway.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,236 root INFO copying ansible_collections/community/aws/plugins/modules/directconnect_link_aggregation_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,236 root INFO copying ansible_collections/community/aws/plugins/modules/directconnect_virtual_interface.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,236 root INFO copying ansible_collections/community/aws/plugins/modules/dms_endpoint.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,237 root INFO copying ansible_collections/community/aws/plugins/modules/dms_replication_subnet_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,237 root INFO copying ansible_collections/community/aws/plugins/modules/dynamodb_table.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,237 root INFO copying ansible_collections/community/aws/plugins/modules/dynamodb_ttl.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,237 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_ami_copy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,237 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_customer_gateway.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,238 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_customer_gateway_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,238 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_launch_template.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,238 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_placement_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,238 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_placement_group_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,239 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_snapshot_copy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,239 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_transit_gateway.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,239 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,239 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_vpc_attachment.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,240 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_vpc_attachment_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,240 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_egress_igw.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,240 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_nacl.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,240 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_nacl_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,241 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_peer.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,241 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_peering_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,241 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_vgw.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,241 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_vgw_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,242 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_vpn.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,242 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_vpc_vpn_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,242 root INFO copying ansible_collections/community/aws/plugins/modules/ec2_win_password.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,242 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_attribute.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,243 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_cluster.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,243 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_ecr.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,243 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_service.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,243 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_service_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,244 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_tag.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,244 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_task.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,244 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_taskdefinition.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,244 root INFO copying ansible_collections/community/aws/plugins/modules/ecs_taskdefinition_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,245 root INFO copying ansible_collections/community/aws/plugins/modules/efs.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,245 root INFO copying ansible_collections/community/aws/plugins/modules/efs_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,245 root INFO copying ansible_collections/community/aws/plugins/modules/efs_tag.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,245 root INFO copying ansible_collections/community/aws/plugins/modules/eks_cluster.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,246 root INFO copying ansible_collections/community/aws/plugins/modules/eks_fargate_profile.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,246 root INFO copying ansible_collections/community/aws/plugins/modules/eks_nodegroup.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,246 root INFO copying ansible_collections/community/aws/plugins/modules/elasticache.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,246 root INFO copying ansible_collections/community/aws/plugins/modules/elasticache_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,247 root INFO copying ansible_collections/community/aws/plugins/modules/elasticache_parameter_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,247 root INFO copying ansible_collections/community/aws/plugins/modules/elasticache_snapshot.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,247 root INFO copying ansible_collections/community/aws/plugins/modules/elasticache_subnet_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,247 root INFO copying ansible_collections/community/aws/plugins/modules/elasticbeanstalk_app.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,248 root INFO copying ansible_collections/community/aws/plugins/modules/elb_classic_lb_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,248 root INFO copying ansible_collections/community/aws/plugins/modules/elb_instance.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,248 root INFO copying ansible_collections/community/aws/plugins/modules/elb_network_lb.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,248 root INFO copying ansible_collections/community/aws/plugins/modules/elb_target.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,249 root INFO copying ansible_collections/community/aws/plugins/modules/elb_target_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,249 root INFO copying ansible_collections/community/aws/plugins/modules/elb_target_group_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,249 root INFO copying ansible_collections/community/aws/plugins/modules/elb_target_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,249 root INFO copying ansible_collections/community/aws/plugins/modules/glue_connection.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,250 root INFO copying ansible_collections/community/aws/plugins/modules/glue_crawler.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,250 root INFO copying ansible_collections/community/aws/plugins/modules/glue_job.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,250 root INFO copying ansible_collections/community/aws/plugins/modules/iam_access_key.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,250 root INFO copying ansible_collections/community/aws/plugins/modules/iam_access_key_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,251 root INFO copying ansible_collections/community/aws/plugins/modules/iam_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,251 root INFO copying ansible_collections/community/aws/plugins/modules/iam_managed_policy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,251 root INFO copying ansible_collections/community/aws/plugins/modules/iam_mfa_device_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,251 root INFO copying ansible_collections/community/aws/plugins/modules/iam_password_policy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,252 root INFO copying ansible_collections/community/aws/plugins/modules/iam_role.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,252 root INFO copying ansible_collections/community/aws/plugins/modules/iam_role_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,252 root INFO copying ansible_collections/community/aws/plugins/modules/iam_saml_federation.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,252 root INFO copying ansible_collections/community/aws/plugins/modules/iam_server_certificate.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,253 root INFO copying ansible_collections/community/aws/plugins/modules/iam_server_certificate_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,253 root INFO copying ansible_collections/community/aws/plugins/modules/inspector_target.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,253 root INFO copying ansible_collections/community/aws/plugins/modules/kinesis_stream.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,253 root INFO copying ansible_collections/community/aws/plugins/modules/lightsail.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,254 root INFO copying ansible_collections/community/aws/plugins/modules/lightsail_static_ip.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,254 root INFO copying ansible_collections/community/aws/plugins/modules/msk_cluster.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,254 root INFO copying ansible_collections/community/aws/plugins/modules/msk_config.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,255 root INFO copying ansible_collections/community/aws/plugins/modules/networkfirewall.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,255 root INFO copying ansible_collections/community/aws/plugins/modules/networkfirewall_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,255 root INFO copying ansible_collections/community/aws/plugins/modules/networkfirewall_policy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,255 root INFO copying ansible_collections/community/aws/plugins/modules/networkfirewall_policy_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,256 root INFO copying ansible_collections/community/aws/plugins/modules/networkfirewall_rule_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,256 root INFO copying ansible_collections/community/aws/plugins/modules/networkfirewall_rule_group_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,256 root INFO copying ansible_collections/community/aws/plugins/modules/opensearch.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,256 root INFO copying ansible_collections/community/aws/plugins/modules/opensearch_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,257 root INFO copying ansible_collections/community/aws/plugins/modules/redshift.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,257 root INFO copying ansible_collections/community/aws/plugins/modules/redshift_cross_region_snapshots.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,257 root INFO copying ansible_collections/community/aws/plugins/modules/redshift_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,257 root INFO copying ansible_collections/community/aws/plugins/modules/redshift_subnet_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,258 root INFO copying ansible_collections/community/aws/plugins/modules/s3_bucket_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,258 root INFO copying ansible_collections/community/aws/plugins/modules/s3_bucket_notification.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,258 root INFO copying ansible_collections/community/aws/plugins/modules/s3_cors.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,258 root INFO copying ansible_collections/community/aws/plugins/modules/s3_lifecycle.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,259 root INFO copying ansible_collections/community/aws/plugins/modules/s3_logging.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,259 root INFO copying ansible_collections/community/aws/plugins/modules/s3_metrics_configuration.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,259 root INFO copying ansible_collections/community/aws/plugins/modules/s3_sync.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,259 root INFO copying ansible_collections/community/aws/plugins/modules/s3_website.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,260 root INFO copying ansible_collections/community/aws/plugins/modules/secretsmanager_secret.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,260 root INFO copying ansible_collections/community/aws/plugins/modules/ses_identity.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,260 root INFO copying ansible_collections/community/aws/plugins/modules/ses_identity_policy.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,260 root INFO copying ansible_collections/community/aws/plugins/modules/ses_rule_set.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,261 root INFO copying ansible_collections/community/aws/plugins/modules/sns.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,261 root INFO copying ansible_collections/community/aws/plugins/modules/sns_topic.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,261 root INFO copying ansible_collections/community/aws/plugins/modules/sns_topic_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,261 root INFO copying ansible_collections/community/aws/plugins/modules/sqs_queue.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,262 root INFO copying ansible_collections/community/aws/plugins/modules/ssm_parameter.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,262 root INFO copying ansible_collections/community/aws/plugins/modules/stepfunctions_state_machine.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,262 root INFO copying ansible_collections/community/aws/plugins/modules/stepfunctions_state_machine_execution.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,262 root INFO copying ansible_collections/community/aws/plugins/modules/storagegateway_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,263 root INFO copying ansible_collections/community/aws/plugins/modules/sts_assume_role.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,263 root INFO copying ansible_collections/community/aws/plugins/modules/sts_session_token.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,263 root INFO copying ansible_collections/community/aws/plugins/modules/waf_condition.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,264 root INFO copying ansible_collections/community/aws/plugins/modules/waf_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,264 root INFO copying ansible_collections/community/aws/plugins/modules/waf_rule.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,264 root INFO copying ansible_collections/community/aws/plugins/modules/waf_web_acl.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,264 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_ip_set.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,265 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_ip_set_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,265 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_resources.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,265 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_resources_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,265 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_rule_group.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,265 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_rule_group_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,266 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_web_acl.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,266 root INFO copying ansible_collections/community/aws/plugins/modules/wafv2_web_acl_info.py -> build/lib/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:41,266 root INFO creating build/lib/ansible_collections/community/azure 2023-04-28 05:57:41,266 root INFO copying ansible_collections/community/azure/CHANGELOG.rst -> build/lib/ansible_collections/community/azure 2023-04-28 05:57:41,267 root INFO copying ansible_collections/community/azure/COPYING -> build/lib/ansible_collections/community/azure 2023-04-28 05:57:41,267 root INFO copying ansible_collections/community/azure/FILES.json -> build/lib/ansible_collections/community/azure 2023-04-28 05:57:41,267 root INFO copying ansible_collections/community/azure/MANIFEST.json -> build/lib/ansible_collections/community/azure 2023-04-28 05:57:41,267 root INFO copying ansible_collections/community/azure/README.md -> build/lib/ansible_collections/community/azure 2023-04-28 05:57:41,267 root INFO copying ansible_collections/community/azure/shippable.yml -> build/lib/ansible_collections/community/azure 2023-04-28 05:57:41,268 root INFO creating build/lib/ansible_collections/community/azure/changelogs 2023-04-28 05:57:41,268 root INFO copying ansible_collections/community/azure/changelogs/changelog.yaml -> build/lib/ansible_collections/community/azure/changelogs 2023-04-28 05:57:41,268 root INFO copying ansible_collections/community/azure/changelogs/config.yaml -> build/lib/ansible_collections/community/azure/changelogs 2023-04-28 05:57:41,268 root INFO creating build/lib/ansible_collections/community/azure/changelogs/fragments 2023-04-28 05:57:41,268 root INFO copying ansible_collections/community/azure/changelogs/fragments/.keep -> build/lib/ansible_collections/community/azure/changelogs/fragments 2023-04-28 05:57:41,269 root INFO creating build/lib/ansible_collections/community/azure/meta 2023-04-28 05:57:41,269 root INFO copying ansible_collections/community/azure/meta/action_groups.yml -> build/lib/ansible_collections/community/azure/meta 2023-04-28 05:57:41,269 root INFO copying ansible_collections/community/azure/meta/runtime.yml -> build/lib/ansible_collections/community/azure/meta 2023-04-28 05:57:41,269 root INFO creating build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,269 root INFO copying ansible_collections/community/ciscosmb/CHANGELOG.rst -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,270 root INFO copying ansible_collections/community/ciscosmb/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,270 root INFO copying ansible_collections/community/ciscosmb/CONTRIBUTING.md -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,270 root INFO copying ansible_collections/community/ciscosmb/FILES.json -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,270 root INFO copying ansible_collections/community/ciscosmb/LICENSE -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,271 root INFO copying ansible_collections/community/ciscosmb/MANIFEST.json -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,271 root INFO copying ansible_collections/community/ciscosmb/README.md -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,271 root INFO copying ansible_collections/community/ciscosmb/RELEASE_POLICY.md -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,271 root INFO copying ansible_collections/community/ciscosmb/galaxy-importer.cfg -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,271 root INFO copying ansible_collections/community/ciscosmb/requirements-dev.txt -> build/lib/ansible_collections/community/ciscosmb 2023-04-28 05:57:41,272 root INFO creating build/lib/ansible_collections/community/ciscosmb/changelogs 2023-04-28 05:57:41,272 root INFO copying ansible_collections/community/ciscosmb/changelogs/changelog.yaml -> build/lib/ansible_collections/community/ciscosmb/changelogs 2023-04-28 05:57:41,272 root INFO copying ansible_collections/community/ciscosmb/changelogs/config.yaml -> build/lib/ansible_collections/community/ciscosmb/changelogs 2023-04-28 05:57:41,272 root INFO creating build/lib/ansible_collections/community/ciscosmb/changelogs/fragments 2023-04-28 05:57:41,272 root INFO copying ansible_collections/community/ciscosmb/changelogs/fragments/.keep -> build/lib/ansible_collections/community/ciscosmb/changelogs/fragments 2023-04-28 05:57:41,273 root INFO creating build/lib/ansible_collections/community/ciscosmb/meta 2023-04-28 05:57:41,273 root INFO copying ansible_collections/community/ciscosmb/meta/runtime.yml -> build/lib/ansible_collections/community/ciscosmb/meta 2023-04-28 05:57:41,273 root INFO creating build/lib/ansible_collections/community/ciscosmb/plugins 2023-04-28 05:57:41,273 root INFO creating build/lib/ansible_collections/community/ciscosmb/plugins/cliconf 2023-04-28 05:57:41,273 root INFO copying ansible_collections/community/ciscosmb/plugins/cliconf/ciscosmb.py -> build/lib/ansible_collections/community/ciscosmb/plugins/cliconf 2023-04-28 05:57:41,273 root INFO creating build/lib/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:41,274 root INFO copying ansible_collections/community/ciscosmb/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:41,274 root INFO copying ansible_collections/community/ciscosmb/plugins/module_utils/ciscosmb.py -> build/lib/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:41,274 root INFO copying ansible_collections/community/ciscosmb/plugins/module_utils/ciscosmb_canonical_map.py -> build/lib/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:41,274 root INFO creating build/lib/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:41,274 root INFO copying ansible_collections/community/ciscosmb/plugins/modules/__init__.py -> build/lib/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:41,275 root INFO copying ansible_collections/community/ciscosmb/plugins/modules/command.py -> build/lib/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:41,275 root INFO copying ansible_collections/community/ciscosmb/plugins/modules/facts.py -> build/lib/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:41,275 root INFO creating build/lib/ansible_collections/community/ciscosmb/plugins/terminal 2023-04-28 05:57:41,275 root INFO copying ansible_collections/community/ciscosmb/plugins/terminal/ciscosmb.py -> build/lib/ansible_collections/community/ciscosmb/plugins/terminal 2023-04-28 05:57:41,275 root INFO creating build/lib/ansible_collections/community/crypto 2023-04-28 05:57:41,276 root INFO copying ansible_collections/community/crypto/CHANGELOG.rst -> build/lib/ansible_collections/community/crypto 2023-04-28 05:57:41,276 root INFO copying ansible_collections/community/crypto/CHANGELOG.rst.license -> build/lib/ansible_collections/community/crypto 2023-04-28 05:57:41,276 root INFO copying ansible_collections/community/crypto/COPYING -> build/lib/ansible_collections/community/crypto 2023-04-28 05:57:41,276 root INFO copying ansible_collections/community/crypto/FILES.json -> build/lib/ansible_collections/community/crypto 2023-04-28 05:57:41,277 root INFO copying ansible_collections/community/crypto/MANIFEST.json -> build/lib/ansible_collections/community/crypto 2023-04-28 05:57:41,277 root INFO copying ansible_collections/community/crypto/README.md -> build/lib/ansible_collections/community/crypto 2023-04-28 05:57:41,277 root INFO creating build/lib/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:41,277 root INFO copying ansible_collections/community/crypto/LICENSES/Apache-2.0.txt -> build/lib/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:41,278 root INFO copying ansible_collections/community/crypto/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:41,278 root INFO copying ansible_collections/community/crypto/LICENSES/BSD-3-Clause.txt -> build/lib/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:41,278 root INFO copying ansible_collections/community/crypto/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:41,278 root INFO copying ansible_collections/community/crypto/LICENSES/PSF-2.0.txt -> build/lib/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:41,279 root INFO creating build/lib/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:41,279 root INFO copying ansible_collections/community/crypto/changelogs/changelog.yaml -> build/lib/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:41,279 root INFO copying ansible_collections/community/crypto/changelogs/changelog.yaml.license -> build/lib/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:41,279 root INFO copying ansible_collections/community/crypto/changelogs/config.yaml -> build/lib/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:41,279 root INFO creating build/lib/ansible_collections/community/crypto/changelogs/fragments 2023-04-28 05:57:41,280 root INFO copying ansible_collections/community/crypto/changelogs/fragments/.keep -> build/lib/ansible_collections/community/crypto/changelogs/fragments 2023-04-28 05:57:41,280 root INFO creating build/lib/ansible_collections/community/crypto/meta 2023-04-28 05:57:41,280 root INFO copying ansible_collections/community/crypto/meta/ee-bindep.txt -> build/lib/ansible_collections/community/crypto/meta 2023-04-28 05:57:41,280 root INFO copying ansible_collections/community/crypto/meta/ee-requirements.txt -> build/lib/ansible_collections/community/crypto/meta 2023-04-28 05:57:41,280 root INFO copying ansible_collections/community/crypto/meta/execution-environment.yml -> build/lib/ansible_collections/community/crypto/meta 2023-04-28 05:57:41,281 root INFO copying ansible_collections/community/crypto/meta/runtime.yml -> build/lib/ansible_collections/community/crypto/meta 2023-04-28 05:57:41,281 root INFO creating build/lib/ansible_collections/community/crypto/plugins 2023-04-28 05:57:41,281 root INFO creating build/lib/ansible_collections/community/crypto/plugins/action 2023-04-28 05:57:41,281 root INFO copying ansible_collections/community/crypto/plugins/action/openssl_privatekey_pipe.py -> build/lib/ansible_collections/community/crypto/plugins/action 2023-04-28 05:57:41,281 root INFO creating build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,281 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/acme.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,282 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,282 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/ecs_credential.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,282 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/module_certificate.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,282 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/module_csr.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,282 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/module_privatekey.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,283 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/module_privatekey_convert.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,283 root INFO copying ansible_collections/community/crypto/plugins/doc_fragments/name_encoding.py -> build/lib/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:41,283 root INFO creating build/lib/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:41,283 root INFO copying ansible_collections/community/crypto/plugins/filter/openssl_csr_info.py -> build/lib/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:41,284 root INFO copying ansible_collections/community/crypto/plugins/filter/openssl_privatekey_info.py -> build/lib/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:41,284 root INFO copying ansible_collections/community/crypto/plugins/filter/openssl_publickey_info.py -> build/lib/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:41,284 root INFO copying ansible_collections/community/crypto/plugins/filter/split_pem.py -> build/lib/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:41,284 root INFO copying ansible_collections/community/crypto/plugins/filter/x509_certificate_info.py -> build/lib/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:41,285 root INFO copying ansible_collections/community/crypto/plugins/filter/x509_crl_info.py -> build/lib/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:41,285 root INFO creating build/lib/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:41,285 root INFO copying ansible_collections/community/crypto/plugins/module_utils/_version.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:41,285 root INFO copying ansible_collections/community/crypto/plugins/module_utils/io.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:41,285 root INFO copying ansible_collections/community/crypto/plugins/module_utils/version.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:41,286 root INFO creating build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,286 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/account.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,286 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/acme.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,286 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/backend_cryptography.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,286 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/backend_openssl_cli.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,287 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/backends.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,287 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/certificates.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,287 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/challenges.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,287 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/errors.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,288 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/io.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,288 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/orders.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,288 root INFO copying ansible_collections/community/crypto/plugins/module_utils/acme/utils.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:41,288 root INFO creating build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,288 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/_asn1.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,289 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/_obj2txt.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,289 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/_objects.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,289 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/_objects_data.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,289 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/basic.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,290 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/cryptography_crl.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,290 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/cryptography_support.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,290 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/math.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,290 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/openssh.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,291 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/pem.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,291 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/support.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:41,291 root INFO creating build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,291 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,291 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_acme.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,292 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_entrust.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,292 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_info.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,292 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_ownca.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,292 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_selfsigned.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,293 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/common.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,293 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/crl_info.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,293 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/csr.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,293 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/csr_info.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,294 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,294 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey_convert.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,294 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey_info.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,294 root INFO copying ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/publickey_info.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:41,295 root INFO creating build/lib/ansible_collections/community/crypto/plugins/module_utils/ecs 2023-04-28 05:57:41,295 root INFO copying ansible_collections/community/crypto/plugins/module_utils/ecs/api.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/ecs 2023-04-28 05:57:41,295 root INFO creating build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:41,295 root INFO copying ansible_collections/community/crypto/plugins/module_utils/openssh/certificate.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:41,295 root INFO copying ansible_collections/community/crypto/plugins/module_utils/openssh/cryptography.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:41,296 root INFO copying ansible_collections/community/crypto/plugins/module_utils/openssh/utils.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:41,296 root INFO creating build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/backends 2023-04-28 05:57:41,296 root INFO copying ansible_collections/community/crypto/plugins/module_utils/openssh/backends/common.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/backends 2023-04-28 05:57:41,296 root INFO copying ansible_collections/community/crypto/plugins/module_utils/openssh/backends/keypair_backend.py -> build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/backends 2023-04-28 05:57:41,297 root INFO creating build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,297 root INFO copying ansible_collections/community/crypto/plugins/modules/acme_account.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,297 root INFO copying ansible_collections/community/crypto/plugins/modules/acme_account_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,297 root INFO copying ansible_collections/community/crypto/plugins/modules/acme_certificate.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,297 root INFO copying ansible_collections/community/crypto/plugins/modules/acme_certificate_revoke.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,298 root INFO copying ansible_collections/community/crypto/plugins/modules/acme_challenge_cert_helper.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,298 root INFO copying ansible_collections/community/crypto/plugins/modules/acme_inspect.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,298 root INFO copying ansible_collections/community/crypto/plugins/modules/certificate_complete_chain.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,298 root INFO copying ansible_collections/community/crypto/plugins/modules/crypto_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,299 root INFO copying ansible_collections/community/crypto/plugins/modules/ecs_certificate.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,299 root INFO copying ansible_collections/community/crypto/plugins/modules/ecs_domain.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,299 root INFO copying ansible_collections/community/crypto/plugins/modules/get_certificate.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,299 root INFO copying ansible_collections/community/crypto/plugins/modules/luks_device.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,300 root INFO copying ansible_collections/community/crypto/plugins/modules/openssh_cert.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,300 root INFO copying ansible_collections/community/crypto/plugins/modules/openssh_keypair.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,300 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_csr.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,301 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_csr_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,301 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_csr_pipe.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,301 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_dhparam.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,301 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_pkcs12.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,301 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_privatekey.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,302 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_privatekey_convert.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,302 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_privatekey_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,302 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_privatekey_pipe.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,302 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_publickey.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,303 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_publickey_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,303 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_signature.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,303 root INFO copying ansible_collections/community/crypto/plugins/modules/openssl_signature_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,303 root INFO copying ansible_collections/community/crypto/plugins/modules/x509_certificate.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,304 root INFO copying ansible_collections/community/crypto/plugins/modules/x509_certificate_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,304 root INFO copying ansible_collections/community/crypto/plugins/modules/x509_certificate_pipe.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,304 root INFO copying ansible_collections/community/crypto/plugins/modules/x509_crl.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,304 root INFO copying ansible_collections/community/crypto/plugins/modules/x509_crl_info.py -> build/lib/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:41,305 root INFO creating build/lib/ansible_collections/community/crypto/plugins/plugin_utils 2023-04-28 05:57:41,305 root INFO copying ansible_collections/community/crypto/plugins/plugin_utils/action_module.py -> build/lib/ansible_collections/community/crypto/plugins/plugin_utils 2023-04-28 05:57:41,305 root INFO copying ansible_collections/community/crypto/plugins/plugin_utils/filter_module.py -> build/lib/ansible_collections/community/crypto/plugins/plugin_utils 2023-04-28 05:57:41,305 root INFO creating build/lib/ansible_collections/community/digitalocean 2023-04-28 05:57:41,305 root INFO copying ansible_collections/community/digitalocean/CHANGELOG.rst -> build/lib/ansible_collections/community/digitalocean 2023-04-28 05:57:41,306 root INFO copying ansible_collections/community/digitalocean/COPYING -> build/lib/ansible_collections/community/digitalocean 2023-04-28 05:57:41,306 root INFO copying ansible_collections/community/digitalocean/FILES.json -> build/lib/ansible_collections/community/digitalocean 2023-04-28 05:57:41,306 root INFO copying ansible_collections/community/digitalocean/MANIFEST.json -> build/lib/ansible_collections/community/digitalocean 2023-04-28 05:57:41,306 root INFO copying ansible_collections/community/digitalocean/README.md -> build/lib/ansible_collections/community/digitalocean 2023-04-28 05:57:41,307 root INFO copying ansible_collections/community/digitalocean/codecov.yml -> build/lib/ansible_collections/community/digitalocean 2023-04-28 05:57:41,307 root INFO creating build/lib/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:41,307 root INFO copying ansible_collections/community/digitalocean/changelogs/.gitignore -> build/lib/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:41,307 root INFO copying ansible_collections/community/digitalocean/changelogs/changelog.yaml -> build/lib/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:41,308 root INFO copying ansible_collections/community/digitalocean/changelogs/config.yaml -> build/lib/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:41,308 root INFO creating build/lib/ansible_collections/community/digitalocean/changelogs/fragments 2023-04-28 05:57:41,308 root INFO copying ansible_collections/community/digitalocean/changelogs/fragments/.keep -> build/lib/ansible_collections/community/digitalocean/changelogs/fragments 2023-04-28 05:57:41,308 root INFO creating build/lib/ansible_collections/community/digitalocean/meta 2023-04-28 05:57:41,308 root INFO copying ansible_collections/community/digitalocean/meta/runtime.yml -> build/lib/ansible_collections/community/digitalocean/meta 2023-04-28 05:57:41,308 root INFO creating build/lib/ansible_collections/community/digitalocean/plugins 2023-04-28 05:57:41,309 root INFO creating build/lib/ansible_collections/community/digitalocean/plugins/doc_fragments 2023-04-28 05:57:41,309 root INFO copying ansible_collections/community/digitalocean/plugins/doc_fragments/digital_ocean.py -> build/lib/ansible_collections/community/digitalocean/plugins/doc_fragments 2023-04-28 05:57:41,309 root INFO creating build/lib/ansible_collections/community/digitalocean/plugins/inventory 2023-04-28 05:57:41,309 root INFO copying ansible_collections/community/digitalocean/plugins/inventory/digitalocean.py -> build/lib/ansible_collections/community/digitalocean/plugins/inventory 2023-04-28 05:57:41,309 root INFO creating build/lib/ansible_collections/community/digitalocean/plugins/module_utils 2023-04-28 05:57:41,309 root INFO copying ansible_collections/community/digitalocean/plugins/module_utils/digital_ocean.py -> build/lib/ansible_collections/community/digitalocean/plugins/module_utils 2023-04-28 05:57:41,310 root INFO creating build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,310 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,310 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_account_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,310 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_account_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,310 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_balance_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,311 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_block_storage.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,311 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_cdn_endpoints.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,311 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_cdn_endpoints_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,311 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,312 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,312 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,312 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_database.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,312 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_database_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,312 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,313 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,313 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,313 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_record.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,313 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_record_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,314 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_droplet.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,314 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_droplet_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,314 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,314 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,315 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,315 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,315 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,315 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,316 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_image_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,316 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_image_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,316 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_kubernetes.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,316 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_kubernetes_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,317 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,317 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,317 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,317 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_monitoring_alerts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,318 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_monitoring_alerts_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,318 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_project.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,318 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_project_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,318 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_region_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,318 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_region_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,319 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_size_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,319 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_size_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,319 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,319 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,320 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,320 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_spaces.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,320 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_spaces_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,320 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,321 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,321 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,321 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,321 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,321 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,322 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_volume_facts.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,322 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_volume_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,322 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_vpc.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,322 root INFO copying ansible_collections/community/digitalocean/plugins/modules/digital_ocean_vpc_info.py -> build/lib/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:41,323 root INFO creating build/lib/ansible_collections/community/digitalocean/scripts 2023-04-28 05:57:41,323 root INFO creating build/lib/ansible_collections/community/digitalocean/scripts/inventory 2023-04-28 05:57:41,323 root INFO copying ansible_collections/community/digitalocean/scripts/inventory/digital_ocean.ini -> build/lib/ansible_collections/community/digitalocean/scripts/inventory 2023-04-28 05:57:41,323 root INFO copying ansible_collections/community/digitalocean/scripts/inventory/digital_ocean.py -> build/lib/ansible_collections/community/digitalocean/scripts/inventory 2023-04-28 05:57:41,323 root INFO creating build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,323 root INFO copying ansible_collections/community/dns/CHANGELOG.rst -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,324 root INFO copying ansible_collections/community/dns/CHANGELOG.rst.license -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,324 root INFO copying ansible_collections/community/dns/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,324 root INFO copying ansible_collections/community/dns/COPYING -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,324 root INFO copying ansible_collections/community/dns/FILES.json -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,325 root INFO copying ansible_collections/community/dns/MANIFEST.json -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,325 root INFO copying ansible_collections/community/dns/README.md -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,325 root INFO copying ansible_collections/community/dns/TESTING.md -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,325 root INFO copying ansible_collections/community/dns/codecov.yml -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,326 root INFO copying ansible_collections/community/dns/update-docs-fragments.py -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,326 root INFO copying ansible_collections/community/dns/update-psl.sh -> build/lib/ansible_collections/community/dns 2023-04-28 05:57:41,326 root INFO creating build/lib/ansible_collections/community/dns/LICENSES 2023-04-28 05:57:41,326 root INFO copying ansible_collections/community/dns/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/dns/LICENSES 2023-04-28 05:57:41,326 root INFO copying ansible_collections/community/dns/LICENSES/MPL-2.0.txt -> build/lib/ansible_collections/community/dns/LICENSES 2023-04-28 05:57:41,327 root INFO creating build/lib/ansible_collections/community/dns/changelogs 2023-04-28 05:57:41,327 root INFO copying ansible_collections/community/dns/changelogs/changelog.yaml -> build/lib/ansible_collections/community/dns/changelogs 2023-04-28 05:57:41,327 root INFO copying ansible_collections/community/dns/changelogs/changelog.yaml.license -> build/lib/ansible_collections/community/dns/changelogs 2023-04-28 05:57:41,327 root INFO copying ansible_collections/community/dns/changelogs/config.yaml -> build/lib/ansible_collections/community/dns/changelogs 2023-04-28 05:57:41,328 root INFO creating build/lib/ansible_collections/community/dns/changelogs/fragments 2023-04-28 05:57:41,328 root INFO copying ansible_collections/community/dns/changelogs/fragments/.keep -> build/lib/ansible_collections/community/dns/changelogs/fragments 2023-04-28 05:57:41,328 root INFO creating build/lib/ansible_collections/community/dns/meta 2023-04-28 05:57:41,328 root INFO copying ansible_collections/community/dns/meta/ee-requirements.txt -> build/lib/ansible_collections/community/dns/meta 2023-04-28 05:57:41,328 root INFO copying ansible_collections/community/dns/meta/execution-environment.yml -> build/lib/ansible_collections/community/dns/meta 2023-04-28 05:57:41,328 root INFO copying ansible_collections/community/dns/meta/runtime.yml -> build/lib/ansible_collections/community/dns/meta 2023-04-28 05:57:41,329 root INFO creating build/lib/ansible_collections/community/dns/plugins 2023-04-28 05:57:41,329 root INFO copying ansible_collections/community/dns/plugins/public_suffix_list.dat -> build/lib/ansible_collections/community/dns/plugins 2023-04-28 05:57:41,329 root INFO copying ansible_collections/community/dns/plugins/public_suffix_list.dat.license -> build/lib/ansible_collections/community/dns/plugins 2023-04-28 05:57:41,330 root INFO creating build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,330 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,330 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/filters.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,330 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/hetzner.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,330 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/hosttech.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,331 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/inventory_records.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,331 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/module_record.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,331 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/module_record_info.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,331 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/module_record_set.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,331 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/module_record_set_info.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,332 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/module_record_sets.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,332 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/module_zone_info.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,332 root INFO copying ansible_collections/community/dns/plugins/doc_fragments/options.py -> build/lib/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:41,332 root INFO creating build/lib/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:41,332 root INFO copying ansible_collections/community/dns/plugins/filter/domain_suffix.py -> build/lib/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:41,333 root INFO copying ansible_collections/community/dns/plugins/filter/get_public_suffix.yml -> build/lib/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:41,333 root INFO copying ansible_collections/community/dns/plugins/filter/get_registrable_domain.yml -> build/lib/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:41,333 root INFO copying ansible_collections/community/dns/plugins/filter/remove_public_suffix.yml -> build/lib/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:41,333 root INFO copying ansible_collections/community/dns/plugins/filter/remove_registrable_domain.yml -> build/lib/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:41,334 root INFO creating build/lib/ansible_collections/community/dns/plugins/inventory 2023-04-28 05:57:41,334 root INFO copying ansible_collections/community/dns/plugins/inventory/hetzner_dns_records.py -> build/lib/ansible_collections/community/dns/plugins/inventory 2023-04-28 05:57:41,334 root INFO copying ansible_collections/community/dns/plugins/inventory/hosttech_dns_records.py -> build/lib/ansible_collections/community/dns/plugins/inventory 2023-04-28 05:57:41,334 root INFO creating build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,334 root INFO copying ansible_collections/community/dns/plugins/module_utils/argspec.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,335 root INFO copying ansible_collections/community/dns/plugins/module_utils/http.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,335 root INFO copying ansible_collections/community/dns/plugins/module_utils/json_api_helper.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,335 root INFO copying ansible_collections/community/dns/plugins/module_utils/names.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,335 root INFO copying ansible_collections/community/dns/plugins/module_utils/options.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,335 root INFO copying ansible_collections/community/dns/plugins/module_utils/provider.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,336 root INFO copying ansible_collections/community/dns/plugins/module_utils/record.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,336 root INFO copying ansible_collections/community/dns/plugins/module_utils/resolver.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,336 root INFO copying ansible_collections/community/dns/plugins/module_utils/wsdl.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,336 root INFO copying ansible_collections/community/dns/plugins/module_utils/zone.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,337 root INFO copying ansible_collections/community/dns/plugins/module_utils/zone_record_api.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,337 root INFO copying ansible_collections/community/dns/plugins/module_utils/zone_record_helpers.py -> build/lib/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:41,337 root INFO creating build/lib/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:41,337 root INFO copying ansible_collections/community/dns/plugins/module_utils/conversion/base.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:41,337 root INFO copying ansible_collections/community/dns/plugins/module_utils/conversion/converter.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:41,338 root INFO copying ansible_collections/community/dns/plugins/module_utils/conversion/txt.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:41,338 root INFO creating build/lib/ansible_collections/community/dns/plugins/module_utils/hetzner 2023-04-28 05:57:41,338 root INFO copying ansible_collections/community/dns/plugins/module_utils/hetzner/api.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/hetzner 2023-04-28 05:57:41,338 root INFO creating build/lib/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:41,338 root INFO copying ansible_collections/community/dns/plugins/module_utils/hosttech/api.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:41,339 root INFO copying ansible_collections/community/dns/plugins/module_utils/hosttech/json_api.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:41,339 root INFO copying ansible_collections/community/dns/plugins/module_utils/hosttech/wsdl_api.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:41,339 root INFO creating build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,339 root INFO copying ansible_collections/community/dns/plugins/module_utils/module/_utils.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,339 root INFO copying ansible_collections/community/dns/plugins/module_utils/module/record.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,340 root INFO copying ansible_collections/community/dns/plugins/module_utils/module/record_info.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,340 root INFO copying ansible_collections/community/dns/plugins/module_utils/module/record_set.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,340 root INFO copying ansible_collections/community/dns/plugins/module_utils/module/record_set_info.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,340 root INFO copying ansible_collections/community/dns/plugins/module_utils/module/record_sets.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,341 root INFO copying ansible_collections/community/dns/plugins/module_utils/module/zone_info.py -> build/lib/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:41,341 root INFO creating build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,341 root INFO copying ansible_collections/community/dns/plugins/modules/hetzner_dns_record.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,341 root INFO copying ansible_collections/community/dns/plugins/modules/hetzner_dns_record_info.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,341 root INFO copying ansible_collections/community/dns/plugins/modules/hetzner_dns_record_set.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,342 root INFO copying ansible_collections/community/dns/plugins/modules/hetzner_dns_record_set_info.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,342 root INFO copying ansible_collections/community/dns/plugins/modules/hetzner_dns_record_sets.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,342 root INFO copying ansible_collections/community/dns/plugins/modules/hetzner_dns_zone_info.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,342 root INFO copying ansible_collections/community/dns/plugins/modules/hosttech_dns_record.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,343 root INFO copying ansible_collections/community/dns/plugins/modules/hosttech_dns_record_info.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,343 root INFO copying ansible_collections/community/dns/plugins/modules/hosttech_dns_record_set.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,343 root INFO copying ansible_collections/community/dns/plugins/modules/hosttech_dns_record_set_info.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,343 root INFO copying ansible_collections/community/dns/plugins/modules/hosttech_dns_record_sets.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,343 root INFO copying ansible_collections/community/dns/plugins/modules/hosttech_dns_records.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,344 root INFO copying ansible_collections/community/dns/plugins/modules/hosttech_dns_zone_info.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,344 root INFO copying ansible_collections/community/dns/plugins/modules/wait_for_txt.py -> build/lib/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:41,344 root INFO creating build/lib/ansible_collections/community/dns/plugins/plugin_utils 2023-04-28 05:57:41,344 root INFO copying ansible_collections/community/dns/plugins/plugin_utils/public_suffix.py -> build/lib/ansible_collections/community/dns/plugins/plugin_utils 2023-04-28 05:57:41,344 root INFO copying ansible_collections/community/dns/plugins/plugin_utils/templated_options.py -> build/lib/ansible_collections/community/dns/plugins/plugin_utils 2023-04-28 05:57:41,345 root INFO creating build/lib/ansible_collections/community/dns/plugins/plugin_utils/inventory 2023-04-28 05:57:41,345 root INFO copying ansible_collections/community/dns/plugins/plugin_utils/inventory/records.py -> build/lib/ansible_collections/community/dns/plugins/plugin_utils/inventory 2023-04-28 05:57:41,345 root INFO creating build/lib/ansible_collections/community/docker 2023-04-28 05:57:41,345 root INFO copying ansible_collections/community/docker/CHANGELOG.rst -> build/lib/ansible_collections/community/docker 2023-04-28 05:57:41,345 root INFO copying ansible_collections/community/docker/CHANGELOG.rst.license -> build/lib/ansible_collections/community/docker 2023-04-28 05:57:41,346 root INFO copying ansible_collections/community/docker/COPYING -> build/lib/ansible_collections/community/docker 2023-04-28 05:57:41,346 root INFO copying ansible_collections/community/docker/FILES.json -> build/lib/ansible_collections/community/docker 2023-04-28 05:57:41,346 root INFO copying ansible_collections/community/docker/MANIFEST.json -> build/lib/ansible_collections/community/docker 2023-04-28 05:57:41,347 root INFO copying ansible_collections/community/docker/README.md -> build/lib/ansible_collections/community/docker 2023-04-28 05:57:41,347 root INFO creating build/lib/ansible_collections/community/docker/LICENSES 2023-04-28 05:57:41,347 root INFO copying ansible_collections/community/docker/LICENSES/Apache-2.0.txt -> build/lib/ansible_collections/community/docker/LICENSES 2023-04-28 05:57:41,347 root INFO copying ansible_collections/community/docker/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/docker/LICENSES 2023-04-28 05:57:41,348 root INFO creating build/lib/ansible_collections/community/docker/changelogs 2023-04-28 05:57:41,348 root INFO copying ansible_collections/community/docker/changelogs/changelog.yaml -> build/lib/ansible_collections/community/docker/changelogs 2023-04-28 05:57:41,348 root INFO copying ansible_collections/community/docker/changelogs/changelog.yaml.license -> build/lib/ansible_collections/community/docker/changelogs 2023-04-28 05:57:41,348 root INFO copying ansible_collections/community/docker/changelogs/config.yaml -> build/lib/ansible_collections/community/docker/changelogs 2023-04-28 05:57:41,348 root INFO creating build/lib/ansible_collections/community/docker/changelogs/fragments 2023-04-28 05:57:41,349 root INFO copying ansible_collections/community/docker/changelogs/fragments/.keep -> build/lib/ansible_collections/community/docker/changelogs/fragments 2023-04-28 05:57:41,349 root INFO creating build/lib/ansible_collections/community/docker/meta 2023-04-28 05:57:41,349 root INFO copying ansible_collections/community/docker/meta/ee-bindep.txt -> build/lib/ansible_collections/community/docker/meta 2023-04-28 05:57:41,349 root INFO copying ansible_collections/community/docker/meta/ee-requirements.txt -> build/lib/ansible_collections/community/docker/meta 2023-04-28 05:57:41,349 root INFO copying ansible_collections/community/docker/meta/execution-environment.yml -> build/lib/ansible_collections/community/docker/meta 2023-04-28 05:57:41,350 root INFO copying ansible_collections/community/docker/meta/runtime.yml -> build/lib/ansible_collections/community/docker/meta 2023-04-28 05:57:41,350 root INFO creating build/lib/ansible_collections/community/docker/plugins 2023-04-28 05:57:41,350 root INFO creating build/lib/ansible_collections/community/docker/plugins/action 2023-04-28 05:57:41,350 root INFO copying ansible_collections/community/docker/plugins/action/docker_container_copy_into.py -> build/lib/ansible_collections/community/docker/plugins/action 2023-04-28 05:57:41,350 root INFO creating build/lib/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:41,350 root INFO copying ansible_collections/community/docker/plugins/connection/docker.py -> build/lib/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:41,351 root INFO copying ansible_collections/community/docker/plugins/connection/docker_api.py -> build/lib/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:41,351 root INFO copying ansible_collections/community/docker/plugins/connection/nsenter.py -> build/lib/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:41,351 root INFO creating build/lib/ansible_collections/community/docker/plugins/doc_fragments 2023-04-28 05:57:41,351 root INFO copying ansible_collections/community/docker/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/docker/plugins/doc_fragments 2023-04-28 05:57:41,351 root INFO copying ansible_collections/community/docker/plugins/doc_fragments/docker.py -> build/lib/ansible_collections/community/docker/plugins/doc_fragments 2023-04-28 05:57:41,352 root INFO creating build/lib/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:41,352 root INFO copying ansible_collections/community/docker/plugins/inventory/docker_containers.py -> build/lib/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:41,352 root INFO copying ansible_collections/community/docker/plugins/inventory/docker_machine.py -> build/lib/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:41,352 root INFO copying ansible_collections/community/docker/plugins/inventory/docker_swarm.py -> build/lib/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:41,352 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,353 root INFO copying ansible_collections/community/docker/plugins/module_utils/_scramble.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,353 root INFO copying ansible_collections/community/docker/plugins/module_utils/common.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,353 root INFO copying ansible_collections/community/docker/plugins/module_utils/common_api.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,353 root INFO copying ansible_collections/community/docker/plugins/module_utils/copy.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,354 root INFO copying ansible_collections/community/docker/plugins/module_utils/image_archive.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,354 root INFO copying ansible_collections/community/docker/plugins/module_utils/socket_handler.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,354 root INFO copying ansible_collections/community/docker/plugins/module_utils/socket_helper.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,354 root INFO copying ansible_collections/community/docker/plugins/module_utils/swarm.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,355 root INFO copying ansible_collections/community/docker/plugins/module_utils/util.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,355 root INFO copying ansible_collections/community/docker/plugins/module_utils/version.py -> build/lib/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:41,355 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:41,355 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/_import_helper.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:41,355 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/auth.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:41,356 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/constants.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:41,356 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/errors.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:41,356 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/tls.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:41,356 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils/_api/api 2023-04-28 05:57:41,356 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/api/client.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/api 2023-04-28 05:57:41,357 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/api/daemon.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/api 2023-04-28 05:57:41,357 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:41,357 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/credentials/constants.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:41,357 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/credentials/errors.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:41,357 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/credentials/store.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:41,358 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/credentials/utils.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:41,358 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:41,358 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/transport/basehttpadapter.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:41,358 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/transport/npipeconn.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:41,358 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/transport/npipesocket.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:41,359 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/transport/sshconn.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:41,359 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/transport/ssladapter.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:41,359 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/transport/unixconn.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:41,359 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils/_api/types 2023-04-28 05:57:41,359 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/types/daemon.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/types 2023-04-28 05:57:41,360 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,360 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/build.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,360 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/config.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,360 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/decorators.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,361 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/fnmatch.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,361 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/json_stream.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,361 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/ports.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,361 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/proxy.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,361 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/socket.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,362 root INFO copying ansible_collections/community/docker/plugins/module_utils/_api/utils/utils.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:41,362 root INFO creating build/lib/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:41,362 root INFO copying ansible_collections/community/docker/plugins/module_utils/module_container/base.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:41,362 root INFO copying ansible_collections/community/docker/plugins/module_utils/module_container/docker_api.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:41,363 root INFO copying ansible_collections/community/docker/plugins/module_utils/module_container/module.py -> build/lib/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:41,363 root INFO creating build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,363 root INFO copying ansible_collections/community/docker/plugins/modules/current_container_facts.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,363 root INFO copying ansible_collections/community/docker/plugins/modules/docker_compose.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,364 root INFO copying ansible_collections/community/docker/plugins/modules/docker_config.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,364 root INFO copying ansible_collections/community/docker/plugins/modules/docker_container.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,364 root INFO copying ansible_collections/community/docker/plugins/modules/docker_container_copy_into.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,364 root INFO copying ansible_collections/community/docker/plugins/modules/docker_container_exec.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,365 root INFO copying ansible_collections/community/docker/plugins/modules/docker_container_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,365 root INFO copying ansible_collections/community/docker/plugins/modules/docker_host_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,365 root INFO copying ansible_collections/community/docker/plugins/modules/docker_image.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,365 root INFO copying ansible_collections/community/docker/plugins/modules/docker_image_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,366 root INFO copying ansible_collections/community/docker/plugins/modules/docker_image_load.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,366 root INFO copying ansible_collections/community/docker/plugins/modules/docker_login.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,366 root INFO copying ansible_collections/community/docker/plugins/modules/docker_network.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,366 root INFO copying ansible_collections/community/docker/plugins/modules/docker_network_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,366 root INFO copying ansible_collections/community/docker/plugins/modules/docker_node.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,367 root INFO copying ansible_collections/community/docker/plugins/modules/docker_node_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,367 root INFO copying ansible_collections/community/docker/plugins/modules/docker_plugin.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,367 root INFO copying ansible_collections/community/docker/plugins/modules/docker_prune.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,367 root INFO copying ansible_collections/community/docker/plugins/modules/docker_secret.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,368 root INFO copying ansible_collections/community/docker/plugins/modules/docker_stack.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,368 root INFO copying ansible_collections/community/docker/plugins/modules/docker_stack_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,368 root INFO copying ansible_collections/community/docker/plugins/modules/docker_stack_task_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,368 root INFO copying ansible_collections/community/docker/plugins/modules/docker_swarm.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,369 root INFO copying ansible_collections/community/docker/plugins/modules/docker_swarm_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,369 root INFO copying ansible_collections/community/docker/plugins/modules/docker_swarm_service.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,369 root INFO copying ansible_collections/community/docker/plugins/modules/docker_swarm_service_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,369 root INFO copying ansible_collections/community/docker/plugins/modules/docker_volume.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,370 root INFO copying ansible_collections/community/docker/plugins/modules/docker_volume_info.py -> build/lib/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:41,370 root INFO creating build/lib/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:41,370 root INFO copying ansible_collections/community/docker/plugins/plugin_utils/common.py -> build/lib/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:41,370 root INFO copying ansible_collections/community/docker/plugins/plugin_utils/common_api.py -> build/lib/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:41,370 root INFO copying ansible_collections/community/docker/plugins/plugin_utils/socket_handler.py -> build/lib/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:41,371 root INFO creating build/lib/ansible_collections/community/fortios 2023-04-28 05:57:41,371 root INFO copying ansible_collections/community/fortios/CHANGELOG.rst -> build/lib/ansible_collections/community/fortios 2023-04-28 05:57:41,371 root INFO copying ansible_collections/community/fortios/FILES.json -> build/lib/ansible_collections/community/fortios 2023-04-28 05:57:41,371 root INFO copying ansible_collections/community/fortios/LICENSE -> build/lib/ansible_collections/community/fortios 2023-04-28 05:57:41,372 root INFO copying ansible_collections/community/fortios/MANIFEST.json -> build/lib/ansible_collections/community/fortios 2023-04-28 05:57:41,372 root INFO copying ansible_collections/community/fortios/README.md -> build/lib/ansible_collections/community/fortios 2023-04-28 05:57:41,372 root INFO creating build/lib/ansible_collections/community/fortios/changelogs 2023-04-28 05:57:41,372 root INFO copying ansible_collections/community/fortios/changelogs/changelog.yaml -> build/lib/ansible_collections/community/fortios/changelogs 2023-04-28 05:57:41,372 root INFO copying ansible_collections/community/fortios/changelogs/config.yaml -> build/lib/ansible_collections/community/fortios/changelogs 2023-04-28 05:57:41,373 root INFO creating build/lib/ansible_collections/community/fortios/changelogs/fragments 2023-04-28 05:57:41,373 root INFO copying ansible_collections/community/fortios/changelogs/fragments/.keep -> build/lib/ansible_collections/community/fortios/changelogs/fragments 2023-04-28 05:57:41,373 root INFO creating build/lib/ansible_collections/community/fortios/meta 2023-04-28 05:57:41,373 root INFO copying ansible_collections/community/fortios/meta/runtime.yml -> build/lib/ansible_collections/community/fortios/meta 2023-04-28 05:57:41,373 root INFO creating build/lib/ansible_collections/community/fortios/plugins 2023-04-28 05:57:41,373 root INFO creating build/lib/ansible_collections/community/fortios/plugins/httpapi 2023-04-28 05:57:41,374 root INFO copying ansible_collections/community/fortios/plugins/httpapi/fortianalyzer.py -> build/lib/ansible_collections/community/fortios/plugins/httpapi 2023-04-28 05:57:41,374 root INFO copying ansible_collections/community/fortios/plugins/httpapi/fortimanager.py -> build/lib/ansible_collections/community/fortios/plugins/httpapi 2023-04-28 05:57:41,374 root INFO creating build/lib/ansible_collections/community/fortios/plugins/module_utils 2023-04-28 05:57:41,374 root INFO creating build/lib/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer 2023-04-28 05:57:41,374 root INFO copying ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/common.py -> build/lib/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer 2023-04-28 05:57:41,374 root INFO copying ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/fortianalyzer.py -> build/lib/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer 2023-04-28 05:57:41,375 root INFO creating build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,375 root INFO copying ansible_collections/community/fortios/plugins/modules/faz_device.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,375 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_device.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,375 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_device_config.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,376 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_device_group.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,376 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_device_provision_template.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,376 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_address.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,376 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_ippool.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,377 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_ippool6.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,377 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_service.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,377 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_vip.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,377 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_fwpol_ipv4.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,378 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_fwpol_package.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,378 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_ha.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,378 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_provisioning.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,378 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_query.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,379 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_script.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,379 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_appctrl.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,380 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_av.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,380 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_dns.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,380 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_ips.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,380 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_profile_group.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,381 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_proxy.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,381 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_spam.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,381 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_ssl_ssh.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,381 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_voip.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,382 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_waf.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,382 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_wanopt.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,382 root INFO copying ansible_collections/community/fortios/plugins/modules/fmgr_secprof_web.py -> build/lib/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:41,382 root INFO creating build/lib/ansible_collections/community/general 2023-04-28 05:57:41,383 root INFO copying ansible_collections/community/general/CHANGELOG.rst -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,383 root INFO copying ansible_collections/community/general/CHANGELOG.rst.license -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,383 root INFO copying ansible_collections/community/general/CONTRIBUTING.md -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,383 root INFO copying ansible_collections/community/general/COPYING -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,384 root INFO copying ansible_collections/community/general/FILES.json -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,385 root INFO copying ansible_collections/community/general/MANIFEST.json -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,385 root INFO copying ansible_collections/community/general/README.md -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,385 root INFO copying ansible_collections/community/general/commit-rights.md -> build/lib/ansible_collections/community/general 2023-04-28 05:57:41,386 root INFO creating build/lib/ansible_collections/community/general/LICENSES 2023-04-28 05:57:41,386 root INFO copying ansible_collections/community/general/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/community/general/LICENSES 2023-04-28 05:57:41,386 root INFO copying ansible_collections/community/general/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/general/LICENSES 2023-04-28 05:57:41,386 root INFO copying ansible_collections/community/general/LICENSES/MIT.txt -> build/lib/ansible_collections/community/general/LICENSES 2023-04-28 05:57:41,387 root INFO copying ansible_collections/community/general/LICENSES/PSF-2.0.txt -> build/lib/ansible_collections/community/general/LICENSES 2023-04-28 05:57:41,387 root INFO creating build/lib/ansible_collections/community/general/changelogs 2023-04-28 05:57:41,387 root INFO copying ansible_collections/community/general/changelogs/.gitignore -> build/lib/ansible_collections/community/general/changelogs 2023-04-28 05:57:41,387 root INFO copying ansible_collections/community/general/changelogs/changelog.yaml -> build/lib/ansible_collections/community/general/changelogs 2023-04-28 05:57:41,388 root INFO copying ansible_collections/community/general/changelogs/changelog.yaml.license -> build/lib/ansible_collections/community/general/changelogs 2023-04-28 05:57:41,388 root INFO copying ansible_collections/community/general/changelogs/config.yaml -> build/lib/ansible_collections/community/general/changelogs 2023-04-28 05:57:41,388 root INFO creating build/lib/ansible_collections/community/general/changelogs/fragments 2023-04-28 05:57:41,389 root INFO copying ansible_collections/community/general/changelogs/fragments/.keep -> build/lib/ansible_collections/community/general/changelogs/fragments 2023-04-28 05:57:41,389 root INFO creating build/lib/ansible_collections/community/general/meta 2023-04-28 05:57:41,389 root INFO copying ansible_collections/community/general/meta/runtime.yml -> build/lib/ansible_collections/community/general/meta 2023-04-28 05:57:41,390 root INFO creating build/lib/ansible_collections/community/general/plugins 2023-04-28 05:57:41,390 root INFO creating build/lib/ansible_collections/community/general/plugins/action 2023-04-28 05:57:41,390 root INFO copying ansible_collections/community/general/plugins/action/iptables_state.py -> build/lib/ansible_collections/community/general/plugins/action 2023-04-28 05:57:41,390 root INFO copying ansible_collections/community/general/plugins/action/shutdown.py -> build/lib/ansible_collections/community/general/plugins/action 2023-04-28 05:57:41,390 root INFO creating build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,390 root INFO copying ansible_collections/community/general/plugins/become/doas.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,391 root INFO copying ansible_collections/community/general/plugins/become/dzdo.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,391 root INFO copying ansible_collections/community/general/plugins/become/ksu.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,391 root INFO copying ansible_collections/community/general/plugins/become/machinectl.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,391 root INFO copying ansible_collections/community/general/plugins/become/pbrun.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,392 root INFO copying ansible_collections/community/general/plugins/become/pfexec.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,392 root INFO copying ansible_collections/community/general/plugins/become/pmrun.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,392 root INFO copying ansible_collections/community/general/plugins/become/sesu.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,392 root INFO copying ansible_collections/community/general/plugins/become/sudosu.py -> build/lib/ansible_collections/community/general/plugins/become 2023-04-28 05:57:41,392 root INFO creating build/lib/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:41,393 root INFO copying ansible_collections/community/general/plugins/cache/memcached.py -> build/lib/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:41,393 root INFO copying ansible_collections/community/general/plugins/cache/pickle.py -> build/lib/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:41,393 root INFO copying ansible_collections/community/general/plugins/cache/redis.py -> build/lib/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:41,393 root INFO copying ansible_collections/community/general/plugins/cache/yaml.py -> build/lib/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:41,393 root INFO creating build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,394 root INFO copying ansible_collections/community/general/plugins/callback/cgroup_memory_recap.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,394 root INFO copying ansible_collections/community/general/plugins/callback/context_demo.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,394 root INFO copying ansible_collections/community/general/plugins/callback/counter_enabled.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,394 root INFO copying ansible_collections/community/general/plugins/callback/dense.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,395 root INFO copying ansible_collections/community/general/plugins/callback/diy.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,395 root INFO copying ansible_collections/community/general/plugins/callback/elastic.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,395 root INFO copying ansible_collections/community/general/plugins/callback/hipchat.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,395 root INFO copying ansible_collections/community/general/plugins/callback/jabber.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,396 root INFO copying ansible_collections/community/general/plugins/callback/log_plays.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,396 root INFO copying ansible_collections/community/general/plugins/callback/loganalytics.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,396 root INFO copying ansible_collections/community/general/plugins/callback/logdna.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,396 root INFO copying ansible_collections/community/general/plugins/callback/logentries.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,396 root INFO copying ansible_collections/community/general/plugins/callback/logstash.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,397 root INFO copying ansible_collections/community/general/plugins/callback/mail.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,397 root INFO copying ansible_collections/community/general/plugins/callback/nrdp.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,397 root INFO copying ansible_collections/community/general/plugins/callback/null.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,397 root INFO copying ansible_collections/community/general/plugins/callback/opentelemetry.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,398 root INFO copying ansible_collections/community/general/plugins/callback/say.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,398 root INFO copying ansible_collections/community/general/plugins/callback/selective.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,398 root INFO copying ansible_collections/community/general/plugins/callback/slack.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,398 root INFO copying ansible_collections/community/general/plugins/callback/splunk.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,399 root INFO copying ansible_collections/community/general/plugins/callback/sumologic.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,399 root INFO copying ansible_collections/community/general/plugins/callback/syslog_json.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,399 root INFO copying ansible_collections/community/general/plugins/callback/unixy.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,399 root INFO copying ansible_collections/community/general/plugins/callback/yaml.py -> build/lib/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:41,399 root INFO creating build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,400 root INFO copying ansible_collections/community/general/plugins/connection/chroot.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,400 root INFO copying ansible_collections/community/general/plugins/connection/funcd.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,400 root INFO copying ansible_collections/community/general/plugins/connection/iocage.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,400 root INFO copying ansible_collections/community/general/plugins/connection/jail.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,401 root INFO copying ansible_collections/community/general/plugins/connection/lxc.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,401 root INFO copying ansible_collections/community/general/plugins/connection/lxd.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,401 root INFO copying ansible_collections/community/general/plugins/connection/qubes.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,401 root INFO copying ansible_collections/community/general/plugins/connection/saltstack.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,401 root INFO copying ansible_collections/community/general/plugins/connection/zone.py -> build/lib/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:41,402 root INFO creating build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,402 root INFO copying ansible_collections/community/general/plugins/doc_fragments/alicloud.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,402 root INFO copying ansible_collections/community/general/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,402 root INFO copying ansible_collections/community/general/plugins/doc_fragments/auth_basic.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,402 root INFO copying ansible_collections/community/general/plugins/doc_fragments/bitbucket.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,403 root INFO copying ansible_collections/community/general/plugins/doc_fragments/dimensiondata.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,403 root INFO copying ansible_collections/community/general/plugins/doc_fragments/dimensiondata_wait.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,403 root INFO copying ansible_collections/community/general/plugins/doc_fragments/emc.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,403 root INFO copying ansible_collections/community/general/plugins/doc_fragments/gitlab.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,404 root INFO copying ansible_collections/community/general/plugins/doc_fragments/hpe3par.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,404 root INFO copying ansible_collections/community/general/plugins/doc_fragments/hwc.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,404 root INFO copying ansible_collections/community/general/plugins/doc_fragments/ibm_storage.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,404 root INFO copying ansible_collections/community/general/plugins/doc_fragments/influxdb.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,404 root INFO copying ansible_collections/community/general/plugins/doc_fragments/ipa.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,405 root INFO copying ansible_collections/community/general/plugins/doc_fragments/keycloak.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,405 root INFO copying ansible_collections/community/general/plugins/doc_fragments/ldap.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,405 root INFO copying ansible_collections/community/general/plugins/doc_fragments/lxca_common.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,405 root INFO copying ansible_collections/community/general/plugins/doc_fragments/manageiq.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,405 root INFO copying ansible_collections/community/general/plugins/doc_fragments/nomad.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,406 root INFO copying ansible_collections/community/general/plugins/doc_fragments/oneview.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,406 root INFO copying ansible_collections/community/general/plugins/doc_fragments/online.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,406 root INFO copying ansible_collections/community/general/plugins/doc_fragments/opennebula.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,406 root INFO copying ansible_collections/community/general/plugins/doc_fragments/openswitch.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,407 root INFO copying ansible_collections/community/general/plugins/doc_fragments/oracle.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,407 root INFO copying ansible_collections/community/general/plugins/doc_fragments/oracle_creatable_resource.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,407 root INFO copying ansible_collections/community/general/plugins/doc_fragments/oracle_display_name_option.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,407 root INFO copying ansible_collections/community/general/plugins/doc_fragments/oracle_name_option.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,407 root INFO copying ansible_collections/community/general/plugins/doc_fragments/oracle_tags.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,408 root INFO copying ansible_collections/community/general/plugins/doc_fragments/oracle_wait_options.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,408 root INFO copying ansible_collections/community/general/plugins/doc_fragments/pritunl.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,408 root INFO copying ansible_collections/community/general/plugins/doc_fragments/proxmox.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,408 root INFO copying ansible_collections/community/general/plugins/doc_fragments/purestorage.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,409 root INFO copying ansible_collections/community/general/plugins/doc_fragments/rackspace.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,409 root INFO copying ansible_collections/community/general/plugins/doc_fragments/redis.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,409 root INFO copying ansible_collections/community/general/plugins/doc_fragments/rundeck.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,409 root INFO copying ansible_collections/community/general/plugins/doc_fragments/scaleway.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,409 root INFO copying ansible_collections/community/general/plugins/doc_fragments/scaleway_waitable_resource.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,410 root INFO copying ansible_collections/community/general/plugins/doc_fragments/utm.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,410 root INFO copying ansible_collections/community/general/plugins/doc_fragments/vexata.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,410 root INFO copying ansible_collections/community/general/plugins/doc_fragments/xenserver.py -> build/lib/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:41,410 root INFO creating build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,410 root INFO copying ansible_collections/community/general/plugins/filter/counter.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,411 root INFO copying ansible_collections/community/general/plugins/filter/crc32.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,411 root INFO copying ansible_collections/community/general/plugins/filter/dict.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,411 root INFO copying ansible_collections/community/general/plugins/filter/dict_kv.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,411 root INFO copying ansible_collections/community/general/plugins/filter/from_csv.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,412 root INFO copying ansible_collections/community/general/plugins/filter/groupby_as_dict.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,412 root INFO copying ansible_collections/community/general/plugins/filter/hashids.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,412 root INFO copying ansible_collections/community/general/plugins/filter/hashids_decode.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,412 root INFO copying ansible_collections/community/general/plugins/filter/hashids_encode.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,412 root INFO copying ansible_collections/community/general/plugins/filter/jc.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,413 root INFO copying ansible_collections/community/general/plugins/filter/json_query.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,413 root INFO copying ansible_collections/community/general/plugins/filter/lists_mergeby.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,413 root INFO copying ansible_collections/community/general/plugins/filter/random_mac.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,413 root INFO copying ansible_collections/community/general/plugins/filter/time.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,414 root INFO copying ansible_collections/community/general/plugins/filter/to_days.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,414 root INFO copying ansible_collections/community/general/plugins/filter/to_hours.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,414 root INFO copying ansible_collections/community/general/plugins/filter/to_milliseconds.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,414 root INFO copying ansible_collections/community/general/plugins/filter/to_minutes.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,414 root INFO copying ansible_collections/community/general/plugins/filter/to_months.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,415 root INFO copying ansible_collections/community/general/plugins/filter/to_seconds.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,415 root INFO copying ansible_collections/community/general/plugins/filter/to_time_unit.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,415 root INFO copying ansible_collections/community/general/plugins/filter/to_weeks.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,415 root INFO copying ansible_collections/community/general/plugins/filter/to_years.yml -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,416 root INFO copying ansible_collections/community/general/plugins/filter/unicode_normalize.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,416 root INFO copying ansible_collections/community/general/plugins/filter/version_sort.py -> build/lib/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:41,416 root INFO creating build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,416 root INFO copying ansible_collections/community/general/plugins/inventory/cobbler.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,416 root INFO copying ansible_collections/community/general/plugins/inventory/gitlab_runners.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,417 root INFO copying ansible_collections/community/general/plugins/inventory/icinga2.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,417 root INFO copying ansible_collections/community/general/plugins/inventory/linode.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,417 root INFO copying ansible_collections/community/general/plugins/inventory/lxd.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,417 root INFO copying ansible_collections/community/general/plugins/inventory/nmap.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,418 root INFO copying ansible_collections/community/general/plugins/inventory/online.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,418 root INFO copying ansible_collections/community/general/plugins/inventory/opennebula.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,418 root INFO copying ansible_collections/community/general/plugins/inventory/proxmox.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,418 root INFO copying ansible_collections/community/general/plugins/inventory/scaleway.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,419 root INFO copying ansible_collections/community/general/plugins/inventory/stackpath_compute.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,419 root INFO copying ansible_collections/community/general/plugins/inventory/virtualbox.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,419 root INFO copying ansible_collections/community/general/plugins/inventory/xen_orchestra.py -> build/lib/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:41,419 root INFO creating build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,419 root INFO copying ansible_collections/community/general/plugins/lookup/bitwarden.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,420 root INFO copying ansible_collections/community/general/plugins/lookup/cartesian.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,420 root INFO copying ansible_collections/community/general/plugins/lookup/chef_databag.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,420 root INFO copying ansible_collections/community/general/plugins/lookup/collection_version.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,420 root INFO copying ansible_collections/community/general/plugins/lookup/consul_kv.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,421 root INFO copying ansible_collections/community/general/plugins/lookup/credstash.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,421 root INFO copying ansible_collections/community/general/plugins/lookup/cyberarkpassword.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,421 root INFO copying ansible_collections/community/general/plugins/lookup/dependent.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,421 root INFO copying ansible_collections/community/general/plugins/lookup/dig.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,421 root INFO copying ansible_collections/community/general/plugins/lookup/dnstxt.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,422 root INFO copying ansible_collections/community/general/plugins/lookup/dsv.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,422 root INFO copying ansible_collections/community/general/plugins/lookup/etcd.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,422 root INFO copying ansible_collections/community/general/plugins/lookup/etcd3.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,422 root INFO copying ansible_collections/community/general/plugins/lookup/filetree.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,423 root INFO copying ansible_collections/community/general/plugins/lookup/flattened.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,423 root INFO copying ansible_collections/community/general/plugins/lookup/hiera.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,423 root INFO copying ansible_collections/community/general/plugins/lookup/keyring.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,423 root INFO copying ansible_collections/community/general/plugins/lookup/lastpass.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,423 root INFO copying ansible_collections/community/general/plugins/lookup/lmdb_kv.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,424 root INFO copying ansible_collections/community/general/plugins/lookup/manifold.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,424 root INFO copying ansible_collections/community/general/plugins/lookup/merge_variables.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,424 root INFO copying ansible_collections/community/general/plugins/lookup/onepassword.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,424 root INFO copying ansible_collections/community/general/plugins/lookup/onepassword_raw.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,425 root INFO copying ansible_collections/community/general/plugins/lookup/passwordstore.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,425 root INFO copying ansible_collections/community/general/plugins/lookup/random_pet.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,425 root INFO copying ansible_collections/community/general/plugins/lookup/random_string.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,425 root INFO copying ansible_collections/community/general/plugins/lookup/random_words.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,425 root INFO copying ansible_collections/community/general/plugins/lookup/redis.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,426 root INFO copying ansible_collections/community/general/plugins/lookup/revbitspss.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,426 root INFO copying ansible_collections/community/general/plugins/lookup/shelvefile.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,426 root INFO copying ansible_collections/community/general/plugins/lookup/tss.py -> build/lib/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:41,426 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,427 root INFO copying ansible_collections/community/general/plugins/module_utils/_mount.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,427 root INFO copying ansible_collections/community/general/plugins/module_utils/_stormssh.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,427 root INFO copying ansible_collections/community/general/plugins/module_utils/alicloud_ecs.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,427 root INFO copying ansible_collections/community/general/plugins/module_utils/btrfs.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,427 root INFO copying ansible_collections/community/general/plugins/module_utils/cloud.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,428 root INFO copying ansible_collections/community/general/plugins/module_utils/cmd_runner.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,428 root INFO copying ansible_collections/community/general/plugins/module_utils/csv.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,428 root INFO copying ansible_collections/community/general/plugins/module_utils/database.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,428 root INFO copying ansible_collections/community/general/plugins/module_utils/deps.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,429 root INFO copying ansible_collections/community/general/plugins/module_utils/dimensiondata.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,429 root INFO copying ansible_collections/community/general/plugins/module_utils/gandi_livedns_api.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,429 root INFO copying ansible_collections/community/general/plugins/module_utils/gconftool2.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,429 root INFO copying ansible_collections/community/general/plugins/module_utils/gitlab.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,429 root INFO copying ansible_collections/community/general/plugins/module_utils/heroku.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,430 root INFO copying ansible_collections/community/general/plugins/module_utils/hwc_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,430 root INFO copying ansible_collections/community/general/plugins/module_utils/ibm_sa_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,430 root INFO copying ansible_collections/community/general/plugins/module_utils/ilo_redfish_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,430 root INFO copying ansible_collections/community/general/plugins/module_utils/influxdb.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,431 root INFO copying ansible_collections/community/general/plugins/module_utils/ipa.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,431 root INFO copying ansible_collections/community/general/plugins/module_utils/jenkins.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,431 root INFO copying ansible_collections/community/general/plugins/module_utils/known_hosts.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,431 root INFO copying ansible_collections/community/general/plugins/module_utils/ldap.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,431 root INFO copying ansible_collections/community/general/plugins/module_utils/linode.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,432 root INFO copying ansible_collections/community/general/plugins/module_utils/lxd.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,432 root INFO copying ansible_collections/community/general/plugins/module_utils/manageiq.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,432 root INFO copying ansible_collections/community/general/plugins/module_utils/memset.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,432 root INFO copying ansible_collections/community/general/plugins/module_utils/module_helper.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,433 root INFO copying ansible_collections/community/general/plugins/module_utils/ocapi_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,433 root INFO copying ansible_collections/community/general/plugins/module_utils/oneandone.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,433 root INFO copying ansible_collections/community/general/plugins/module_utils/onepassword.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,433 root INFO copying ansible_collections/community/general/plugins/module_utils/oneview.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,434 root INFO copying ansible_collections/community/general/plugins/module_utils/online.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,434 root INFO copying ansible_collections/community/general/plugins/module_utils/opennebula.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,434 root INFO copying ansible_collections/community/general/plugins/module_utils/pipx.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,434 root INFO copying ansible_collections/community/general/plugins/module_utils/proxmox.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,435 root INFO copying ansible_collections/community/general/plugins/module_utils/puppet.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,435 root INFO copying ansible_collections/community/general/plugins/module_utils/pure.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,435 root INFO copying ansible_collections/community/general/plugins/module_utils/rax.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,435 root INFO copying ansible_collections/community/general/plugins/module_utils/redfish_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,436 root INFO copying ansible_collections/community/general/plugins/module_utils/redhat.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,436 root INFO copying ansible_collections/community/general/plugins/module_utils/redis.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,436 root INFO copying ansible_collections/community/general/plugins/module_utils/rundeck.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,436 root INFO copying ansible_collections/community/general/plugins/module_utils/saslprep.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,437 root INFO copying ansible_collections/community/general/plugins/module_utils/scaleway.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,437 root INFO copying ansible_collections/community/general/plugins/module_utils/ssh.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,437 root INFO copying ansible_collections/community/general/plugins/module_utils/univention_umc.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,437 root INFO copying ansible_collections/community/general/plugins/module_utils/utm_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,437 root INFO copying ansible_collections/community/general/plugins/module_utils/version.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,438 root INFO copying ansible_collections/community/general/plugins/module_utils/vexata.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,438 root INFO copying ansible_collections/community/general/plugins/module_utils/wdc_redfish_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,438 root INFO copying ansible_collections/community/general/plugins/module_utils/xenserver.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,438 root INFO copying ansible_collections/community/general/plugins/module_utils/xfconf.py -> build/lib/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:41,439 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/identity 2023-04-28 05:57:41,439 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/identity/keycloak 2023-04-28 05:57:41,439 root INFO copying ansible_collections/community/general/plugins/module_utils/identity/keycloak/keycloak.py -> build/lib/ansible_collections/community/general/plugins/module_utils/identity/keycloak 2023-04-28 05:57:41,439 root INFO copying ansible_collections/community/general/plugins/module_utils/identity/keycloak/keycloak_clientsecret.py -> build/lib/ansible_collections/community/general/plugins/module_utils/identity/keycloak 2023-04-28 05:57:41,439 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:41,440 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/base.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:41,440 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/deco.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:41,440 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/exceptions.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:41,440 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/module_helper.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:41,440 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:41,441 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/mixins/cmd.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:41,441 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/mixins/deprecate_attrs.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:41,441 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/mixins/deps.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:41,441 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/mixins/state.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:41,442 root INFO copying ansible_collections/community/general/plugins/module_utils/mh/mixins/vars.py -> build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:41,442 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/net_tools 2023-04-28 05:57:41,442 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/net_tools/pritunl 2023-04-28 05:57:41,442 root INFO copying ansible_collections/community/general/plugins/module_utils/net_tools/pritunl/api.py -> build/lib/ansible_collections/community/general/plugins/module_utils/net_tools/pritunl 2023-04-28 05:57:41,442 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/oracle 2023-04-28 05:57:41,442 root INFO copying ansible_collections/community/general/plugins/module_utils/oracle/oci_utils.py -> build/lib/ansible_collections/community/general/plugins/module_utils/oracle 2023-04-28 05:57:41,443 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/remote_management 2023-04-28 05:57:41,443 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/remote_management/lxca 2023-04-28 05:57:41,443 root INFO copying ansible_collections/community/general/plugins/module_utils/remote_management/lxca/common.py -> build/lib/ansible_collections/community/general/plugins/module_utils/remote_management/lxca 2023-04-28 05:57:41,443 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/source_control 2023-04-28 05:57:41,443 root INFO copying ansible_collections/community/general/plugins/module_utils/source_control/bitbucket.py -> build/lib/ansible_collections/community/general/plugins/module_utils/source_control 2023-04-28 05:57:41,444 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/storage 2023-04-28 05:57:41,444 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/storage/emc 2023-04-28 05:57:41,444 root INFO copying ansible_collections/community/general/plugins/module_utils/storage/emc/emc_vnx.py -> build/lib/ansible_collections/community/general/plugins/module_utils/storage/emc 2023-04-28 05:57:41,444 root INFO creating build/lib/ansible_collections/community/general/plugins/module_utils/storage/hpe3par 2023-04-28 05:57:41,444 root INFO copying ansible_collections/community/general/plugins/module_utils/storage/hpe3par/hpe3par.py -> build/lib/ansible_collections/community/general/plugins/module_utils/storage/hpe3par 2023-04-28 05:57:41,444 root INFO creating build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,445 root INFO copying ansible_collections/community/general/plugins/modules/aerospike_migrations.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,445 root INFO copying ansible_collections/community/general/plugins/modules/airbrake_deployment.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,445 root INFO copying ansible_collections/community/general/plugins/modules/aix_devices.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,445 root INFO copying ansible_collections/community/general/plugins/modules/aix_filesystem.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,446 root INFO copying ansible_collections/community/general/plugins/modules/aix_inittab.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,446 root INFO copying ansible_collections/community/general/plugins/modules/aix_lvg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,446 root INFO copying ansible_collections/community/general/plugins/modules/aix_lvol.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,446 root INFO copying ansible_collections/community/general/plugins/modules/alerta_customer.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,446 root INFO copying ansible_collections/community/general/plugins/modules/ali_instance.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,447 root INFO copying ansible_collections/community/general/plugins/modules/ali_instance_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,447 root INFO copying ansible_collections/community/general/plugins/modules/alternatives.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,447 root INFO copying ansible_collections/community/general/plugins/modules/ansible_galaxy_install.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,447 root INFO copying ansible_collections/community/general/plugins/modules/apache2_mod_proxy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,448 root INFO copying ansible_collections/community/general/plugins/modules/apache2_module.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,448 root INFO copying ansible_collections/community/general/plugins/modules/apk.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,448 root INFO copying ansible_collections/community/general/plugins/modules/apt_repo.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,448 root INFO copying ansible_collections/community/general/plugins/modules/apt_rpm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,449 root INFO copying ansible_collections/community/general/plugins/modules/archive.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,449 root INFO copying ansible_collections/community/general/plugins/modules/atomic_container.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,449 root INFO copying ansible_collections/community/general/plugins/modules/atomic_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,449 root INFO copying ansible_collections/community/general/plugins/modules/atomic_image.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,449 root INFO copying ansible_collections/community/general/plugins/modules/awall.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,450 root INFO copying ansible_collections/community/general/plugins/modules/beadm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,450 root INFO copying ansible_collections/community/general/plugins/modules/bearychat.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,450 root INFO copying ansible_collections/community/general/plugins/modules/bigpanda.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,450 root INFO copying ansible_collections/community/general/plugins/modules/bitbucket_access_key.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,451 root INFO copying ansible_collections/community/general/plugins/modules/bitbucket_pipeline_key_pair.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,451 root INFO copying ansible_collections/community/general/plugins/modules/bitbucket_pipeline_known_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,451 root INFO copying ansible_collections/community/general/plugins/modules/bitbucket_pipeline_variable.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,451 root INFO copying ansible_collections/community/general/plugins/modules/bower.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,451 root INFO copying ansible_collections/community/general/plugins/modules/btrfs_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,452 root INFO copying ansible_collections/community/general/plugins/modules/btrfs_subvolume.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,452 root INFO copying ansible_collections/community/general/plugins/modules/bundler.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,452 root INFO copying ansible_collections/community/general/plugins/modules/bzr.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,452 root INFO copying ansible_collections/community/general/plugins/modules/campfire.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,453 root INFO copying ansible_collections/community/general/plugins/modules/capabilities.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,453 root INFO copying ansible_collections/community/general/plugins/modules/cargo.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,453 root INFO copying ansible_collections/community/general/plugins/modules/catapult.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,453 root INFO copying ansible_collections/community/general/plugins/modules/circonus_annotation.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,454 root INFO copying ansible_collections/community/general/plugins/modules/cisco_webex.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,454 root INFO copying ansible_collections/community/general/plugins/modules/clc_aa_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,454 root INFO copying ansible_collections/community/general/plugins/modules/clc_alert_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,454 root INFO copying ansible_collections/community/general/plugins/modules/clc_blueprint_package.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,455 root INFO copying ansible_collections/community/general/plugins/modules/clc_firewall_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,455 root INFO copying ansible_collections/community/general/plugins/modules/clc_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,455 root INFO copying ansible_collections/community/general/plugins/modules/clc_loadbalancer.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,455 root INFO copying ansible_collections/community/general/plugins/modules/clc_modify_server.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,456 root INFO copying ansible_collections/community/general/plugins/modules/clc_publicip.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,456 root INFO copying ansible_collections/community/general/plugins/modules/clc_server.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,456 root INFO copying ansible_collections/community/general/plugins/modules/clc_server_snapshot.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,456 root INFO copying ansible_collections/community/general/plugins/modules/cloud_init_data_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,457 root INFO copying ansible_collections/community/general/plugins/modules/cloudflare_dns.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,457 root INFO copying ansible_collections/community/general/plugins/modules/cobbler_sync.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,457 root INFO copying ansible_collections/community/general/plugins/modules/cobbler_system.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,457 root INFO copying ansible_collections/community/general/plugins/modules/composer.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,458 root INFO copying ansible_collections/community/general/plugins/modules/consul.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,458 root INFO copying ansible_collections/community/general/plugins/modules/consul_acl.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,458 root INFO copying ansible_collections/community/general/plugins/modules/consul_kv.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,458 root INFO copying ansible_collections/community/general/plugins/modules/consul_session.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,459 root INFO copying ansible_collections/community/general/plugins/modules/copr.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,459 root INFO copying ansible_collections/community/general/plugins/modules/cpanm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,459 root INFO copying ansible_collections/community/general/plugins/modules/cronvar.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,459 root INFO copying ansible_collections/community/general/plugins/modules/crypttab.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,459 root INFO copying ansible_collections/community/general/plugins/modules/datadog_downtime.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,460 root INFO copying ansible_collections/community/general/plugins/modules/datadog_event.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,460 root INFO copying ansible_collections/community/general/plugins/modules/datadog_monitor.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,460 root INFO copying ansible_collections/community/general/plugins/modules/dconf.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,460 root INFO copying ansible_collections/community/general/plugins/modules/deploy_helper.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,461 root INFO copying ansible_collections/community/general/plugins/modules/dimensiondata_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,461 root INFO copying ansible_collections/community/general/plugins/modules/dimensiondata_vlan.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,461 root INFO copying ansible_collections/community/general/plugins/modules/discord.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,461 root INFO copying ansible_collections/community/general/plugins/modules/django_manage.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,462 root INFO copying ansible_collections/community/general/plugins/modules/dnf_versionlock.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,462 root INFO copying ansible_collections/community/general/plugins/modules/dnsimple.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,462 root INFO copying ansible_collections/community/general/plugins/modules/dnsimple_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,462 root INFO copying ansible_collections/community/general/plugins/modules/dnsmadeeasy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,463 root INFO copying ansible_collections/community/general/plugins/modules/dpkg_divert.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,463 root INFO copying ansible_collections/community/general/plugins/modules/easy_install.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,463 root INFO copying ansible_collections/community/general/plugins/modules/ejabberd_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,463 root INFO copying ansible_collections/community/general/plugins/modules/elasticsearch_plugin.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,464 root INFO copying ansible_collections/community/general/plugins/modules/emc_vnx_sg_member.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,464 root INFO copying ansible_collections/community/general/plugins/modules/etcd3.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,464 root INFO copying ansible_collections/community/general/plugins/modules/facter.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,464 root INFO copying ansible_collections/community/general/plugins/modules/filesize.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,465 root INFO copying ansible_collections/community/general/plugins/modules/filesystem.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,465 root INFO copying ansible_collections/community/general/plugins/modules/flatpak.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,465 root INFO copying ansible_collections/community/general/plugins/modules/flatpak_remote.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,465 root INFO copying ansible_collections/community/general/plugins/modules/flowdock.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,465 root INFO copying ansible_collections/community/general/plugins/modules/gandi_livedns.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,466 root INFO copying ansible_collections/community/general/plugins/modules/gconftool2.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,466 root INFO copying ansible_collections/community/general/plugins/modules/gconftool2_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,466 root INFO copying ansible_collections/community/general/plugins/modules/gem.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,466 root INFO copying ansible_collections/community/general/plugins/modules/git_config.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,467 root INFO copying ansible_collections/community/general/plugins/modules/github_deploy_key.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,467 root INFO copying ansible_collections/community/general/plugins/modules/github_issue.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,467 root INFO copying ansible_collections/community/general/plugins/modules/github_key.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,467 root INFO copying ansible_collections/community/general/plugins/modules/github_release.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,468 root INFO copying ansible_collections/community/general/plugins/modules/github_repo.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,468 root INFO copying ansible_collections/community/general/plugins/modules/github_webhook.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,468 root INFO copying ansible_collections/community/general/plugins/modules/github_webhook_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,468 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_branch.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,468 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_deploy_key.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,469 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,469 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_group_members.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,469 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_group_variable.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,469 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_hook.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,470 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_project.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,470 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_project_badge.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,470 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_project_members.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,470 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_project_variable.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,471 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_protected_branch.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,471 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_runner.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,471 root INFO copying ansible_collections/community/general/plugins/modules/gitlab_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,471 root INFO copying ansible_collections/community/general/plugins/modules/grove.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,472 root INFO copying ansible_collections/community/general/plugins/modules/gunicorn.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,472 root INFO copying ansible_collections/community/general/plugins/modules/hana_query.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,472 root INFO copying ansible_collections/community/general/plugins/modules/haproxy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,472 root INFO copying ansible_collections/community/general/plugins/modules/heroku_collaborator.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,473 root INFO copying ansible_collections/community/general/plugins/modules/hg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,473 root INFO copying ansible_collections/community/general/plugins/modules/hipchat.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,473 root INFO copying ansible_collections/community/general/plugins/modules/homebrew.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,473 root INFO copying ansible_collections/community/general/plugins/modules/homebrew_cask.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,474 root INFO copying ansible_collections/community/general/plugins/modules/homebrew_tap.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,474 root INFO copying ansible_collections/community/general/plugins/modules/homectl.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,474 root INFO copying ansible_collections/community/general/plugins/modules/honeybadger_deployment.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,474 root INFO copying ansible_collections/community/general/plugins/modules/hpilo_boot.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,475 root INFO copying ansible_collections/community/general/plugins/modules/hpilo_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,475 root INFO copying ansible_collections/community/general/plugins/modules/hponcfg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,475 root INFO copying ansible_collections/community/general/plugins/modules/htpasswd.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,475 root INFO copying ansible_collections/community/general/plugins/modules/hwc_ecs_instance.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,476 root INFO copying ansible_collections/community/general/plugins/modules/hwc_evs_disk.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,476 root INFO copying ansible_collections/community/general/plugins/modules/hwc_network_vpc.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,476 root INFO copying ansible_collections/community/general/plugins/modules/hwc_smn_topic.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,476 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_eip.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,477 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_peering_connect.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,477 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_port.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,477 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_private_ip.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,477 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_route.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,478 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_security_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,478 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_security_group_rule.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,478 root INFO copying ansible_collections/community/general/plugins/modules/hwc_vpc_subnet.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,478 root INFO copying ansible_collections/community/general/plugins/modules/ibm_sa_domain.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,479 root INFO copying ansible_collections/community/general/plugins/modules/ibm_sa_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,479 root INFO copying ansible_collections/community/general/plugins/modules/ibm_sa_host_ports.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,479 root INFO copying ansible_collections/community/general/plugins/modules/ibm_sa_pool.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,479 root INFO copying ansible_collections/community/general/plugins/modules/ibm_sa_vol.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,479 root INFO copying ansible_collections/community/general/plugins/modules/ibm_sa_vol_map.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,480 root INFO copying ansible_collections/community/general/plugins/modules/icinga2_feature.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,480 root INFO copying ansible_collections/community/general/plugins/modules/icinga2_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,480 root INFO copying ansible_collections/community/general/plugins/modules/idrac_redfish_command.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,480 root INFO copying ansible_collections/community/general/plugins/modules/idrac_redfish_config.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,481 root INFO copying ansible_collections/community/general/plugins/modules/idrac_redfish_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,481 root INFO copying ansible_collections/community/general/plugins/modules/ilo_redfish_command.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,481 root INFO copying ansible_collections/community/general/plugins/modules/ilo_redfish_config.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,481 root INFO copying ansible_collections/community/general/plugins/modules/ilo_redfish_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,482 root INFO copying ansible_collections/community/general/plugins/modules/imc_rest.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,482 root INFO copying ansible_collections/community/general/plugins/modules/imgadm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,482 root INFO copying ansible_collections/community/general/plugins/modules/infinity.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,482 root INFO copying ansible_collections/community/general/plugins/modules/influxdb_database.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,483 root INFO copying ansible_collections/community/general/plugins/modules/influxdb_query.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,483 root INFO copying ansible_collections/community/general/plugins/modules/influxdb_retention_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,483 root INFO copying ansible_collections/community/general/plugins/modules/influxdb_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,483 root INFO copying ansible_collections/community/general/plugins/modules/influxdb_write.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,484 root INFO copying ansible_collections/community/general/plugins/modules/ini_file.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,484 root INFO copying ansible_collections/community/general/plugins/modules/installp.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,484 root INFO copying ansible_collections/community/general/plugins/modules/interfaces_file.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,484 root INFO copying ansible_collections/community/general/plugins/modules/ip_netns.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,485 root INFO copying ansible_collections/community/general/plugins/modules/ipa_config.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,485 root INFO copying ansible_collections/community/general/plugins/modules/ipa_dnsrecord.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,485 root INFO copying ansible_collections/community/general/plugins/modules/ipa_dnszone.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,485 root INFO copying ansible_collections/community/general/plugins/modules/ipa_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,485 root INFO copying ansible_collections/community/general/plugins/modules/ipa_hbacrule.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,486 root INFO copying ansible_collections/community/general/plugins/modules/ipa_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,486 root INFO copying ansible_collections/community/general/plugins/modules/ipa_hostgroup.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,486 root INFO copying ansible_collections/community/general/plugins/modules/ipa_otpconfig.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,486 root INFO copying ansible_collections/community/general/plugins/modules/ipa_otptoken.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,487 root INFO copying ansible_collections/community/general/plugins/modules/ipa_pwpolicy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,487 root INFO copying ansible_collections/community/general/plugins/modules/ipa_role.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,487 root INFO copying ansible_collections/community/general/plugins/modules/ipa_service.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,487 root INFO copying ansible_collections/community/general/plugins/modules/ipa_subca.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,488 root INFO copying ansible_collections/community/general/plugins/modules/ipa_sudocmd.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,488 root INFO copying ansible_collections/community/general/plugins/modules/ipa_sudocmdgroup.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,488 root INFO copying ansible_collections/community/general/plugins/modules/ipa_sudorule.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,488 root INFO copying ansible_collections/community/general/plugins/modules/ipa_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,489 root INFO copying ansible_collections/community/general/plugins/modules/ipa_vault.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,489 root INFO copying ansible_collections/community/general/plugins/modules/ipify_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,489 root INFO copying ansible_collections/community/general/plugins/modules/ipinfoio_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,489 root INFO copying ansible_collections/community/general/plugins/modules/ipmi_boot.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,489 root INFO copying ansible_collections/community/general/plugins/modules/ipmi_power.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,490 root INFO copying ansible_collections/community/general/plugins/modules/iptables_state.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,490 root INFO copying ansible_collections/community/general/plugins/modules/ipwcli_dns.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,490 root INFO copying ansible_collections/community/general/plugins/modules/irc.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,490 root INFO copying ansible_collections/community/general/plugins/modules/iso_create.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,491 root INFO copying ansible_collections/community/general/plugins/modules/iso_customize.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,491 root INFO copying ansible_collections/community/general/plugins/modules/iso_extract.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,491 root INFO copying ansible_collections/community/general/plugins/modules/jabber.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,491 root INFO copying ansible_collections/community/general/plugins/modules/java_cert.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,492 root INFO copying ansible_collections/community/general/plugins/modules/java_keystore.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,492 root INFO copying ansible_collections/community/general/plugins/modules/jboss.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,492 root INFO copying ansible_collections/community/general/plugins/modules/jenkins_build.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,492 root INFO copying ansible_collections/community/general/plugins/modules/jenkins_job.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,493 root INFO copying ansible_collections/community/general/plugins/modules/jenkins_job_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,493 root INFO copying ansible_collections/community/general/plugins/modules/jenkins_plugin.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,493 root INFO copying ansible_collections/community/general/plugins/modules/jenkins_script.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,493 root INFO copying ansible_collections/community/general/plugins/modules/jira.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,494 root INFO copying ansible_collections/community/general/plugins/modules/kdeconfig.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,494 root INFO copying ansible_collections/community/general/plugins/modules/kernel_blacklist.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,494 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_authentication.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,494 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_authz_authorization_scope.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,495 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_client.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,495 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_client_rolemapping.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,495 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_clientscope.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,495 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_clientscope_type.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,496 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_clientsecret_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,496 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_clientsecret_regenerate.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,496 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_clienttemplate.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,496 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,497 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_identity_provider.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,497 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_realm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,497 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_realm_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,497 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_role.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,498 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_user_federation.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,498 root INFO copying ansible_collections/community/general/plugins/modules/keycloak_user_rolemapping.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,498 root INFO copying ansible_collections/community/general/plugins/modules/keyring.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,498 root INFO copying ansible_collections/community/general/plugins/modules/keyring_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,499 root INFO copying ansible_collections/community/general/plugins/modules/kibana_plugin.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,499 root INFO copying ansible_collections/community/general/plugins/modules/launchd.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,499 root INFO copying ansible_collections/community/general/plugins/modules/layman.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,499 root INFO copying ansible_collections/community/general/plugins/modules/lbu.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,500 root INFO copying ansible_collections/community/general/plugins/modules/ldap_attrs.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,500 root INFO copying ansible_collections/community/general/plugins/modules/ldap_entry.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,500 root INFO copying ansible_collections/community/general/plugins/modules/ldap_passwd.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,500 root INFO copying ansible_collections/community/general/plugins/modules/ldap_search.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,500 root INFO copying ansible_collections/community/general/plugins/modules/librato_annotation.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,501 root INFO copying ansible_collections/community/general/plugins/modules/linode.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,501 root INFO copying ansible_collections/community/general/plugins/modules/linode_v4.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,501 root INFO copying ansible_collections/community/general/plugins/modules/listen_ports_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,501 root INFO copying ansible_collections/community/general/plugins/modules/lldp.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,502 root INFO copying ansible_collections/community/general/plugins/modules/locale_gen.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,502 root INFO copying ansible_collections/community/general/plugins/modules/logentries.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,502 root INFO copying ansible_collections/community/general/plugins/modules/logentries_msg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,502 root INFO copying ansible_collections/community/general/plugins/modules/logstash_plugin.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,503 root INFO copying ansible_collections/community/general/plugins/modules/lvg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,503 root INFO copying ansible_collections/community/general/plugins/modules/lvol.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,503 root INFO copying ansible_collections/community/general/plugins/modules/lxc_container.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,503 root INFO copying ansible_collections/community/general/plugins/modules/lxca_cmms.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,504 root INFO copying ansible_collections/community/general/plugins/modules/lxca_nodes.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,504 root INFO copying ansible_collections/community/general/plugins/modules/lxd_container.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,505 root INFO copying ansible_collections/community/general/plugins/modules/lxd_profile.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,505 root INFO copying ansible_collections/community/general/plugins/modules/lxd_project.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,505 root INFO copying ansible_collections/community/general/plugins/modules/macports.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,505 root INFO copying ansible_collections/community/general/plugins/modules/mail.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,505 root INFO copying ansible_collections/community/general/plugins/modules/make.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,506 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_alert_profiles.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,506 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_alerts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,506 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,506 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_policies.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,507 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_policies_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,507 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_provider.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,507 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_tags.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,507 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_tags_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,508 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_tenant.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,508 root INFO copying ansible_collections/community/general/plugins/modules/manageiq_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,508 root INFO copying ansible_collections/community/general/plugins/modules/mas.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,508 root INFO copying ansible_collections/community/general/plugins/modules/matrix.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,509 root INFO copying ansible_collections/community/general/plugins/modules/mattermost.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,509 root INFO copying ansible_collections/community/general/plugins/modules/maven_artifact.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,509 root INFO copying ansible_collections/community/general/plugins/modules/memset_dns_reload.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,509 root INFO copying ansible_collections/community/general/plugins/modules/memset_memstore_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,510 root INFO copying ansible_collections/community/general/plugins/modules/memset_server_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,510 root INFO copying ansible_collections/community/general/plugins/modules/memset_zone.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,510 root INFO copying ansible_collections/community/general/plugins/modules/memset_zone_domain.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,510 root INFO copying ansible_collections/community/general/plugins/modules/memset_zone_record.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,511 root INFO copying ansible_collections/community/general/plugins/modules/mksysb.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,511 root INFO copying ansible_collections/community/general/plugins/modules/modprobe.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,511 root INFO copying ansible_collections/community/general/plugins/modules/monit.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,511 root INFO copying ansible_collections/community/general/plugins/modules/mqtt.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,511 root INFO copying ansible_collections/community/general/plugins/modules/mssql_db.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,512 root INFO copying ansible_collections/community/general/plugins/modules/mssql_script.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,512 root INFO copying ansible_collections/community/general/plugins/modules/nagios.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,512 root INFO copying ansible_collections/community/general/plugins/modules/netcup_dns.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,512 root INFO copying ansible_collections/community/general/plugins/modules/newrelic_deployment.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,513 root INFO copying ansible_collections/community/general/plugins/modules/nexmo.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,513 root INFO copying ansible_collections/community/general/plugins/modules/nginx_status_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,513 root INFO copying ansible_collections/community/general/plugins/modules/nictagadm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,513 root INFO copying ansible_collections/community/general/plugins/modules/nmcli.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,514 root INFO copying ansible_collections/community/general/plugins/modules/nomad_job.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,514 root INFO copying ansible_collections/community/general/plugins/modules/nomad_job_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,514 root INFO copying ansible_collections/community/general/plugins/modules/nosh.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,515 root INFO copying ansible_collections/community/general/plugins/modules/npm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,515 root INFO copying ansible_collections/community/general/plugins/modules/nsupdate.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,515 root INFO copying ansible_collections/community/general/plugins/modules/ocapi_command.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,515 root INFO copying ansible_collections/community/general/plugins/modules/ocapi_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,516 root INFO copying ansible_collections/community/general/plugins/modules/oci_vcn.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,516 root INFO copying ansible_collections/community/general/plugins/modules/odbc.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,516 root INFO copying ansible_collections/community/general/plugins/modules/office_365_connector_card.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,516 root INFO copying ansible_collections/community/general/plugins/modules/ohai.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,516 root INFO copying ansible_collections/community/general/plugins/modules/omapi_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,517 root INFO copying ansible_collections/community/general/plugins/modules/one_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,517 root INFO copying ansible_collections/community/general/plugins/modules/one_image.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,517 root INFO copying ansible_collections/community/general/plugins/modules/one_image_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,517 root INFO copying ansible_collections/community/general/plugins/modules/one_service.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,518 root INFO copying ansible_collections/community/general/plugins/modules/one_template.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,518 root INFO copying ansible_collections/community/general/plugins/modules/one_vm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,518 root INFO copying ansible_collections/community/general/plugins/modules/oneandone_firewall_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,518 root INFO copying ansible_collections/community/general/plugins/modules/oneandone_load_balancer.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,519 root INFO copying ansible_collections/community/general/plugins/modules/oneandone_monitoring_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,519 root INFO copying ansible_collections/community/general/plugins/modules/oneandone_private_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,519 root INFO copying ansible_collections/community/general/plugins/modules/oneandone_public_ip.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,519 root INFO copying ansible_collections/community/general/plugins/modules/oneandone_server.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,520 root INFO copying ansible_collections/community/general/plugins/modules/onepassword_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,520 root INFO copying ansible_collections/community/general/plugins/modules/oneview_datacenter_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,520 root INFO copying ansible_collections/community/general/plugins/modules/oneview_enclosure_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,520 root INFO copying ansible_collections/community/general/plugins/modules/oneview_ethernet_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,521 root INFO copying ansible_collections/community/general/plugins/modules/oneview_ethernet_network_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,521 root INFO copying ansible_collections/community/general/plugins/modules/oneview_fc_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,521 root INFO copying ansible_collections/community/general/plugins/modules/oneview_fc_network_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,521 root INFO copying ansible_collections/community/general/plugins/modules/oneview_fcoe_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,522 root INFO copying ansible_collections/community/general/plugins/modules/oneview_fcoe_network_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,522 root INFO copying ansible_collections/community/general/plugins/modules/oneview_logical_interconnect_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,522 root INFO copying ansible_collections/community/general/plugins/modules/oneview_logical_interconnect_group_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,522 root INFO copying ansible_collections/community/general/plugins/modules/oneview_network_set.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,523 root INFO copying ansible_collections/community/general/plugins/modules/oneview_network_set_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,523 root INFO copying ansible_collections/community/general/plugins/modules/oneview_san_manager.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,523 root INFO copying ansible_collections/community/general/plugins/modules/oneview_san_manager_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,523 root INFO copying ansible_collections/community/general/plugins/modules/online_server_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,524 root INFO copying ansible_collections/community/general/plugins/modules/online_user_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,524 root INFO copying ansible_collections/community/general/plugins/modules/open_iscsi.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,524 root INFO copying ansible_collections/community/general/plugins/modules/openbsd_pkg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,524 root INFO copying ansible_collections/community/general/plugins/modules/opendj_backendprop.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,525 root INFO copying ansible_collections/community/general/plugins/modules/openwrt_init.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,525 root INFO copying ansible_collections/community/general/plugins/modules/opkg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,525 root INFO copying ansible_collections/community/general/plugins/modules/osx_defaults.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,525 root INFO copying ansible_collections/community/general/plugins/modules/ovh_ip_failover.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,526 root INFO copying ansible_collections/community/general/plugins/modules/ovh_ip_loadbalancing_backend.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,526 root INFO copying ansible_collections/community/general/plugins/modules/ovh_monthly_billing.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,526 root INFO copying ansible_collections/community/general/plugins/modules/pacemaker_cluster.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,526 root INFO copying ansible_collections/community/general/plugins/modules/packet_device.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,527 root INFO copying ansible_collections/community/general/plugins/modules/packet_ip_subnet.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,527 root INFO copying ansible_collections/community/general/plugins/modules/packet_project.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,527 root INFO copying ansible_collections/community/general/plugins/modules/packet_sshkey.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,527 root INFO copying ansible_collections/community/general/plugins/modules/packet_volume.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,527 root INFO copying ansible_collections/community/general/plugins/modules/packet_volume_attachment.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,528 root INFO copying ansible_collections/community/general/plugins/modules/pacman.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,528 root INFO copying ansible_collections/community/general/plugins/modules/pacman_key.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,528 root INFO copying ansible_collections/community/general/plugins/modules/pagerduty.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,528 root INFO copying ansible_collections/community/general/plugins/modules/pagerduty_alert.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,529 root INFO copying ansible_collections/community/general/plugins/modules/pagerduty_change.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,529 root INFO copying ansible_collections/community/general/plugins/modules/pagerduty_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,529 root INFO copying ansible_collections/community/general/plugins/modules/pam_limits.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,529 root INFO copying ansible_collections/community/general/plugins/modules/pamd.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,530 root INFO copying ansible_collections/community/general/plugins/modules/parted.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,530 root INFO copying ansible_collections/community/general/plugins/modules/pear.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,530 root INFO copying ansible_collections/community/general/plugins/modules/pids.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,530 root INFO copying ansible_collections/community/general/plugins/modules/pingdom.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,531 root INFO copying ansible_collections/community/general/plugins/modules/pip_package_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,531 root INFO copying ansible_collections/community/general/plugins/modules/pipx.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,531 root INFO copying ansible_collections/community/general/plugins/modules/pipx_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,531 root INFO copying ansible_collections/community/general/plugins/modules/pkg5.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,532 root INFO copying ansible_collections/community/general/plugins/modules/pkg5_publisher.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,532 root INFO copying ansible_collections/community/general/plugins/modules/pkgin.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,532 root INFO copying ansible_collections/community/general/plugins/modules/pkgng.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,532 root INFO copying ansible_collections/community/general/plugins/modules/pkgutil.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,532 root INFO copying ansible_collections/community/general/plugins/modules/pmem.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,533 root INFO copying ansible_collections/community/general/plugins/modules/portage.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,533 root INFO copying ansible_collections/community/general/plugins/modules/portinstall.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,533 root INFO copying ansible_collections/community/general/plugins/modules/pritunl_org.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,533 root INFO copying ansible_collections/community/general/plugins/modules/pritunl_org_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,534 root INFO copying ansible_collections/community/general/plugins/modules/pritunl_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,534 root INFO copying ansible_collections/community/general/plugins/modules/pritunl_user_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,534 root INFO copying ansible_collections/community/general/plugins/modules/profitbricks.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,534 root INFO copying ansible_collections/community/general/plugins/modules/profitbricks_datacenter.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,535 root INFO copying ansible_collections/community/general/plugins/modules/profitbricks_nic.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,535 root INFO copying ansible_collections/community/general/plugins/modules/profitbricks_volume.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,535 root INFO copying ansible_collections/community/general/plugins/modules/profitbricks_volume_attachments.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,535 root INFO copying ansible_collections/community/general/plugins/modules/proxmox.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,536 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_disk.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,536 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_domain_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,536 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_group_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,536 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_kvm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,537 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_nic.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,537 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_snap.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,537 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_storage_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,537 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_tasks_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,538 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_template.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,538 root INFO copying ansible_collections/community/general/plugins/modules/proxmox_user_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,538 root INFO copying ansible_collections/community/general/plugins/modules/pubnub_blocks.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,538 root INFO copying ansible_collections/community/general/plugins/modules/pulp_repo.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,539 root INFO copying ansible_collections/community/general/plugins/modules/puppet.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,539 root INFO copying ansible_collections/community/general/plugins/modules/pushbullet.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,539 root INFO copying ansible_collections/community/general/plugins/modules/pushover.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,539 root INFO copying ansible_collections/community/general/plugins/modules/python_requirements_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,540 root INFO copying ansible_collections/community/general/plugins/modules/rax.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,540 root INFO copying ansible_collections/community/general/plugins/modules/rax_cbs.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,540 root INFO copying ansible_collections/community/general/plugins/modules/rax_cbs_attachments.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,540 root INFO copying ansible_collections/community/general/plugins/modules/rax_cdb.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,541 root INFO copying ansible_collections/community/general/plugins/modules/rax_cdb_database.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,541 root INFO copying ansible_collections/community/general/plugins/modules/rax_cdb_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,541 root INFO copying ansible_collections/community/general/plugins/modules/rax_clb.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,541 root INFO copying ansible_collections/community/general/plugins/modules/rax_clb_nodes.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,541 root INFO copying ansible_collections/community/general/plugins/modules/rax_clb_ssl.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,542 root INFO copying ansible_collections/community/general/plugins/modules/rax_dns.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,542 root INFO copying ansible_collections/community/general/plugins/modules/rax_dns_record.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,542 root INFO copying ansible_collections/community/general/plugins/modules/rax_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,542 root INFO copying ansible_collections/community/general/plugins/modules/rax_files.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,543 root INFO copying ansible_collections/community/general/plugins/modules/rax_files_objects.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,543 root INFO copying ansible_collections/community/general/plugins/modules/rax_identity.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,543 root INFO copying ansible_collections/community/general/plugins/modules/rax_keypair.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,543 root INFO copying ansible_collections/community/general/plugins/modules/rax_meta.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,544 root INFO copying ansible_collections/community/general/plugins/modules/rax_mon_alarm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,544 root INFO copying ansible_collections/community/general/plugins/modules/rax_mon_check.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,544 root INFO copying ansible_collections/community/general/plugins/modules/rax_mon_entity.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,544 root INFO copying ansible_collections/community/general/plugins/modules/rax_mon_notification.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,545 root INFO copying ansible_collections/community/general/plugins/modules/rax_mon_notification_plan.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,545 root INFO copying ansible_collections/community/general/plugins/modules/rax_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,545 root INFO copying ansible_collections/community/general/plugins/modules/rax_queue.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,545 root INFO copying ansible_collections/community/general/plugins/modules/rax_scaling_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,546 root INFO copying ansible_collections/community/general/plugins/modules/rax_scaling_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,546 root INFO copying ansible_collections/community/general/plugins/modules/read_csv.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,546 root INFO copying ansible_collections/community/general/plugins/modules/redfish_command.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,546 root INFO copying ansible_collections/community/general/plugins/modules/redfish_config.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,547 root INFO copying ansible_collections/community/general/plugins/modules/redfish_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,547 root INFO copying ansible_collections/community/general/plugins/modules/redhat_subscription.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,547 root INFO copying ansible_collections/community/general/plugins/modules/redis.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,547 root INFO copying ansible_collections/community/general/plugins/modules/redis_data.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,548 root INFO copying ansible_collections/community/general/plugins/modules/redis_data_incr.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,548 root INFO copying ansible_collections/community/general/plugins/modules/redis_data_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,548 root INFO copying ansible_collections/community/general/plugins/modules/redis_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,548 root INFO copying ansible_collections/community/general/plugins/modules/rhevm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,548 root INFO copying ansible_collections/community/general/plugins/modules/rhn_channel.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,549 root INFO copying ansible_collections/community/general/plugins/modules/rhn_register.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,549 root INFO copying ansible_collections/community/general/plugins/modules/rhsm_release.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,549 root INFO copying ansible_collections/community/general/plugins/modules/rhsm_repository.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,549 root INFO copying ansible_collections/community/general/plugins/modules/riak.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,550 root INFO copying ansible_collections/community/general/plugins/modules/rocketchat.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,550 root INFO copying ansible_collections/community/general/plugins/modules/rollbar_deployment.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,550 root INFO copying ansible_collections/community/general/plugins/modules/rpm_ostree_pkg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,550 root INFO copying ansible_collections/community/general/plugins/modules/rundeck_acl_policy.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,551 root INFO copying ansible_collections/community/general/plugins/modules/rundeck_job_executions_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,551 root INFO copying ansible_collections/community/general/plugins/modules/rundeck_job_run.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,551 root INFO copying ansible_collections/community/general/plugins/modules/rundeck_project.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,551 root INFO copying ansible_collections/community/general/plugins/modules/runit.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,552 root INFO copying ansible_collections/community/general/plugins/modules/sap_task_list_execute.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,552 root INFO copying ansible_collections/community/general/plugins/modules/sapcar_extract.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,552 root INFO copying ansible_collections/community/general/plugins/modules/say.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,552 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_compute.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,552 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_compute_private_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,553 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_container.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,553 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_container_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,553 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_container_namespace.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,553 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_container_namespace_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,554 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_container_registry.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,554 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_container_registry_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,554 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_database_backup.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,554 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_function.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,555 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_function_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,555 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_function_namespace.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,555 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_function_namespace_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,555 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_image_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,556 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_ip.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,556 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_ip_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,556 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_lb.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,556 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_organization_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,557 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_private_network.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,557 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_security_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,557 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_security_group_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,557 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_security_group_rule.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,557 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_server_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,558 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_snapshot_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,558 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_sshkey.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,558 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_user_data.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,558 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_volume.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,559 root INFO copying ansible_collections/community/general/plugins/modules/scaleway_volume_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,559 root INFO copying ansible_collections/community/general/plugins/modules/sefcontext.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,559 root INFO copying ansible_collections/community/general/plugins/modules/selinux_permissive.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,559 root INFO copying ansible_collections/community/general/plugins/modules/selogin.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,560 root INFO copying ansible_collections/community/general/plugins/modules/sendgrid.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,560 root INFO copying ansible_collections/community/general/plugins/modules/sensu_check.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,560 root INFO copying ansible_collections/community/general/plugins/modules/sensu_client.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,560 root INFO copying ansible_collections/community/general/plugins/modules/sensu_handler.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,561 root INFO copying ansible_collections/community/general/plugins/modules/sensu_silence.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,561 root INFO copying ansible_collections/community/general/plugins/modules/sensu_subscription.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,561 root INFO copying ansible_collections/community/general/plugins/modules/seport.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,561 root INFO copying ansible_collections/community/general/plugins/modules/serverless.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,561 root INFO copying ansible_collections/community/general/plugins/modules/shutdown.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,562 root INFO copying ansible_collections/community/general/plugins/modules/sl_vm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,562 root INFO copying ansible_collections/community/general/plugins/modules/slack.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,562 root INFO copying ansible_collections/community/general/plugins/modules/slackpkg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,562 root INFO copying ansible_collections/community/general/plugins/modules/smartos_image_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,563 root INFO copying ansible_collections/community/general/plugins/modules/snap.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,563 root INFO copying ansible_collections/community/general/plugins/modules/snap_alias.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,563 root INFO copying ansible_collections/community/general/plugins/modules/snmp_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,563 root INFO copying ansible_collections/community/general/plugins/modules/solaris_zone.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,564 root INFO copying ansible_collections/community/general/plugins/modules/sorcery.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,564 root INFO copying ansible_collections/community/general/plugins/modules/spectrum_device.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,564 root INFO copying ansible_collections/community/general/plugins/modules/spectrum_model_attrs.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,564 root INFO copying ansible_collections/community/general/plugins/modules/spotinst_aws_elastigroup.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,565 root INFO copying ansible_collections/community/general/plugins/modules/ss_3par_cpg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,565 root INFO copying ansible_collections/community/general/plugins/modules/ssh_config.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,565 root INFO copying ansible_collections/community/general/plugins/modules/stackdriver.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,565 root INFO copying ansible_collections/community/general/plugins/modules/stacki_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,566 root INFO copying ansible_collections/community/general/plugins/modules/statsd.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,566 root INFO copying ansible_collections/community/general/plugins/modules/statusio_maintenance.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,566 root INFO copying ansible_collections/community/general/plugins/modules/sudoers.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,566 root INFO copying ansible_collections/community/general/plugins/modules/supervisorctl.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,567 root INFO copying ansible_collections/community/general/plugins/modules/svc.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,567 root INFO copying ansible_collections/community/general/plugins/modules/svr4pkg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,567 root INFO copying ansible_collections/community/general/plugins/modules/swdepot.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,567 root INFO copying ansible_collections/community/general/plugins/modules/swupd.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,568 root INFO copying ansible_collections/community/general/plugins/modules/syslogger.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,568 root INFO copying ansible_collections/community/general/plugins/modules/syspatch.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,568 root INFO copying ansible_collections/community/general/plugins/modules/sysrc.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,568 root INFO copying ansible_collections/community/general/plugins/modules/sysupgrade.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,568 root INFO copying ansible_collections/community/general/plugins/modules/taiga_issue.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,569 root INFO copying ansible_collections/community/general/plugins/modules/telegram.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,569 root INFO copying ansible_collections/community/general/plugins/modules/terraform.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,569 root INFO copying ansible_collections/community/general/plugins/modules/timezone.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,570 root INFO copying ansible_collections/community/general/plugins/modules/twilio.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,570 root INFO copying ansible_collections/community/general/plugins/modules/typetalk.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,570 root INFO copying ansible_collections/community/general/plugins/modules/udm_dns_record.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,570 root INFO copying ansible_collections/community/general/plugins/modules/udm_dns_zone.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,570 root INFO copying ansible_collections/community/general/plugins/modules/udm_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,571 root INFO copying ansible_collections/community/general/plugins/modules/udm_share.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,571 root INFO copying ansible_collections/community/general/plugins/modules/udm_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,571 root INFO copying ansible_collections/community/general/plugins/modules/ufw.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,571 root INFO copying ansible_collections/community/general/plugins/modules/uptimerobot.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,572 root INFO copying ansible_collections/community/general/plugins/modules/urpmi.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,572 root INFO copying ansible_collections/community/general/plugins/modules/utm_aaa_group.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,572 root INFO copying ansible_collections/community/general/plugins/modules/utm_aaa_group_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,572 root INFO copying ansible_collections/community/general/plugins/modules/utm_ca_host_key_cert.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,573 root INFO copying ansible_collections/community/general/plugins/modules/utm_ca_host_key_cert_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,573 root INFO copying ansible_collections/community/general/plugins/modules/utm_dns_host.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,573 root INFO copying ansible_collections/community/general/plugins/modules/utm_network_interface_address.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,573 root INFO copying ansible_collections/community/general/plugins/modules/utm_network_interface_address_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,574 root INFO copying ansible_collections/community/general/plugins/modules/utm_proxy_auth_profile.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,574 root INFO copying ansible_collections/community/general/plugins/modules/utm_proxy_exception.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,574 root INFO copying ansible_collections/community/general/plugins/modules/utm_proxy_frontend.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,574 root INFO copying ansible_collections/community/general/plugins/modules/utm_proxy_frontend_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,574 root INFO copying ansible_collections/community/general/plugins/modules/utm_proxy_location.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,575 root INFO copying ansible_collections/community/general/plugins/modules/utm_proxy_location_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,575 root INFO copying ansible_collections/community/general/plugins/modules/vdo.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,575 root INFO copying ansible_collections/community/general/plugins/modules/vertica_configuration.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,575 root INFO copying ansible_collections/community/general/plugins/modules/vertica_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,576 root INFO copying ansible_collections/community/general/plugins/modules/vertica_role.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,576 root INFO copying ansible_collections/community/general/plugins/modules/vertica_schema.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,576 root INFO copying ansible_collections/community/general/plugins/modules/vertica_user.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,576 root INFO copying ansible_collections/community/general/plugins/modules/vexata_eg.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,577 root INFO copying ansible_collections/community/general/plugins/modules/vexata_volume.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,577 root INFO copying ansible_collections/community/general/plugins/modules/vmadm.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,577 root INFO copying ansible_collections/community/general/plugins/modules/wakeonlan.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,577 root INFO copying ansible_collections/community/general/plugins/modules/wdc_redfish_command.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,578 root INFO copying ansible_collections/community/general/plugins/modules/wdc_redfish_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,578 root INFO copying ansible_collections/community/general/plugins/modules/webfaction_app.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,578 root INFO copying ansible_collections/community/general/plugins/modules/webfaction_db.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,578 root INFO copying ansible_collections/community/general/plugins/modules/webfaction_domain.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,579 root INFO copying ansible_collections/community/general/plugins/modules/webfaction_mailbox.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,579 root INFO copying ansible_collections/community/general/plugins/modules/webfaction_site.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,579 root INFO copying ansible_collections/community/general/plugins/modules/xattr.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,579 root INFO copying ansible_collections/community/general/plugins/modules/xbps.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,579 root INFO copying ansible_collections/community/general/plugins/modules/xcc_redfish_command.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,580 root INFO copying ansible_collections/community/general/plugins/modules/xenserver_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,580 root INFO copying ansible_collections/community/general/plugins/modules/xenserver_guest.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,580 root INFO copying ansible_collections/community/general/plugins/modules/xenserver_guest_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,581 root INFO copying ansible_collections/community/general/plugins/modules/xenserver_guest_powerstate.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,581 root INFO copying ansible_collections/community/general/plugins/modules/xfconf.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,581 root INFO copying ansible_collections/community/general/plugins/modules/xfconf_info.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,581 root INFO copying ansible_collections/community/general/plugins/modules/xfs_quota.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,582 root INFO copying ansible_collections/community/general/plugins/modules/xml.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,582 root INFO copying ansible_collections/community/general/plugins/modules/yarn.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,582 root INFO copying ansible_collections/community/general/plugins/modules/yum_versionlock.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,582 root INFO copying ansible_collections/community/general/plugins/modules/zfs.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,583 root INFO copying ansible_collections/community/general/plugins/modules/zfs_delegate_admin.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,583 root INFO copying ansible_collections/community/general/plugins/modules/zfs_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,583 root INFO copying ansible_collections/community/general/plugins/modules/znode.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,583 root INFO copying ansible_collections/community/general/plugins/modules/zpool_facts.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,584 root INFO copying ansible_collections/community/general/plugins/modules/zypper.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,584 root INFO copying ansible_collections/community/general/plugins/modules/zypper_repository.py -> build/lib/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:41,584 root INFO creating build/lib/ansible_collections/community/general/plugins/test 2023-04-28 05:57:41,584 root INFO copying ansible_collections/community/general/plugins/test/a_module.py -> build/lib/ansible_collections/community/general/plugins/test 2023-04-28 05:57:41,584 root INFO creating build/lib/ansible_collections/community/google 2023-04-28 05:57:41,585 root INFO copying ansible_collections/community/google/CHANGELOG.rst -> build/lib/ansible_collections/community/google 2023-04-28 05:57:41,585 root INFO copying ansible_collections/community/google/FILES.json -> build/lib/ansible_collections/community/google 2023-04-28 05:57:41,585 root INFO copying ansible_collections/community/google/LICENSE -> build/lib/ansible_collections/community/google 2023-04-28 05:57:41,585 root INFO copying ansible_collections/community/google/MANIFEST.json -> build/lib/ansible_collections/community/google 2023-04-28 05:57:41,585 root INFO copying ansible_collections/community/google/README.md -> build/lib/ansible_collections/community/google 2023-04-28 05:57:41,586 root INFO creating build/lib/ansible_collections/community/google/changelogs 2023-04-28 05:57:41,586 root INFO copying ansible_collections/community/google/changelogs/changelog.yaml -> build/lib/ansible_collections/community/google/changelogs 2023-04-28 05:57:41,586 root INFO copying ansible_collections/community/google/changelogs/config.yaml -> build/lib/ansible_collections/community/google/changelogs 2023-04-28 05:57:41,586 root INFO creating build/lib/ansible_collections/community/google/changelogs/fragments 2023-04-28 05:57:41,586 root INFO copying ansible_collections/community/google/changelogs/fragments/.keep -> build/lib/ansible_collections/community/google/changelogs/fragments 2023-04-28 05:57:41,587 root INFO creating build/lib/ansible_collections/community/google/meta 2023-04-28 05:57:41,587 root INFO copying ansible_collections/community/google/meta/runtime.yml -> build/lib/ansible_collections/community/google/meta 2023-04-28 05:57:41,587 root INFO creating build/lib/ansible_collections/community/google/plugins 2023-04-28 05:57:41,587 root INFO creating build/lib/ansible_collections/community/google/plugins/doc_fragments 2023-04-28 05:57:41,587 root INFO copying ansible_collections/community/google/plugins/doc_fragments/_gcp.py -> build/lib/ansible_collections/community/google/plugins/doc_fragments 2023-04-28 05:57:41,587 root INFO creating build/lib/ansible_collections/community/google/plugins/lookup 2023-04-28 05:57:41,588 root INFO copying ansible_collections/community/google/plugins/lookup/gcp_storage_file.py -> build/lib/ansible_collections/community/google/plugins/lookup 2023-04-28 05:57:41,588 root INFO creating build/lib/ansible_collections/community/google/plugins/module_utils 2023-04-28 05:57:41,588 root INFO copying ansible_collections/community/google/plugins/module_utils/gce.py -> build/lib/ansible_collections/community/google/plugins/module_utils 2023-04-28 05:57:41,588 root INFO copying ansible_collections/community/google/plugins/module_utils/gcp.py -> build/lib/ansible_collections/community/google/plugins/module_utils 2023-04-28 05:57:41,588 root INFO creating build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,589 root INFO copying ansible_collections/community/google/plugins/modules/gc_storage.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,589 root INFO copying ansible_collections/community/google/plugins/modules/gce_eip.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,589 root INFO copying ansible_collections/community/google/plugins/modules/gce_img.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,589 root INFO copying ansible_collections/community/google/plugins/modules/gce_instance_template.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,589 root INFO copying ansible_collections/community/google/plugins/modules/gce_labels.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,590 root INFO copying ansible_collections/community/google/plugins/modules/gce_lb.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,590 root INFO copying ansible_collections/community/google/plugins/modules/gce_mig.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,590 root INFO copying ansible_collections/community/google/plugins/modules/gce_net.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,590 root INFO copying ansible_collections/community/google/plugins/modules/gce_pd.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,591 root INFO copying ansible_collections/community/google/plugins/modules/gce_snapshot.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,591 root INFO copying ansible_collections/community/google/plugins/modules/gce_tag.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,591 root INFO copying ansible_collections/community/google/plugins/modules/gcpubsub.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,591 root INFO copying ansible_collections/community/google/plugins/modules/gcpubsub_info.py -> build/lib/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:41,592 root INFO creating build/lib/ansible_collections/community/google/scripts 2023-04-28 05:57:41,592 root INFO creating build/lib/ansible_collections/community/google/scripts/inventory 2023-04-28 05:57:41,592 root INFO copying ansible_collections/community/google/scripts/inventory/gce.ini -> build/lib/ansible_collections/community/google/scripts/inventory 2023-04-28 05:57:41,592 root INFO copying ansible_collections/community/google/scripts/inventory/gce.py -> build/lib/ansible_collections/community/google/scripts/inventory 2023-04-28 05:57:41,592 root INFO creating build/lib/ansible_collections/community/grafana 2023-04-28 05:57:41,592 root INFO copying ansible_collections/community/grafana/CHANGELOG.rst -> build/lib/ansible_collections/community/grafana 2023-04-28 05:57:41,593 root INFO copying ansible_collections/community/grafana/FILES.json -> build/lib/ansible_collections/community/grafana 2023-04-28 05:57:41,593 root INFO copying ansible_collections/community/grafana/LICENSE -> build/lib/ansible_collections/community/grafana 2023-04-28 05:57:41,593 root INFO copying ansible_collections/community/grafana/MANIFEST.json -> build/lib/ansible_collections/community/grafana 2023-04-28 05:57:41,594 root INFO copying ansible_collections/community/grafana/README.md -> build/lib/ansible_collections/community/grafana 2023-04-28 05:57:41,594 root INFO copying ansible_collections/community/grafana/codecov.yml -> build/lib/ansible_collections/community/grafana 2023-04-28 05:57:41,594 root INFO creating build/lib/ansible_collections/community/grafana/changelogs 2023-04-28 05:57:41,594 root INFO copying ansible_collections/community/grafana/changelogs/changelog.yaml -> build/lib/ansible_collections/community/grafana/changelogs 2023-04-28 05:57:41,594 root INFO copying ansible_collections/community/grafana/changelogs/config.yaml -> build/lib/ansible_collections/community/grafana/changelogs 2023-04-28 05:57:41,595 root INFO creating build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,595 root INFO copying ansible_collections/community/grafana/changelogs/fragments/0-copy_ignore_txt.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,595 root INFO copying ansible_collections/community/grafana/changelogs/fragments/0.1.0.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,595 root INFO copying ansible_collections/community/grafana/changelogs/fragments/0.2.0.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,595 root INFO copying ansible_collections/community/grafana/changelogs/fragments/0.2.1.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,596 root INFO copying ansible_collections/community/grafana/changelogs/fragments/0.2.2.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,596 root INFO copying ansible_collections/community/grafana/changelogs/fragments/00_drop_eol_ansible.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,596 root INFO copying ansible_collections/community/grafana/changelogs/fragments/01_grafana_bump.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,596 root INFO copying ansible_collections/community/grafana/changelogs/fragments/1.0.0.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,596 root INFO copying ansible_collections/community/grafana/changelogs/fragments/1.2.0.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,597 root INFO copying ansible_collections/community/grafana/changelogs/fragments/1.2.1.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,597 root INFO copying ansible_collections/community/grafana/changelogs/fragments/1.2.2.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,597 root INFO copying ansible_collections/community/grafana/changelogs/fragments/1.2.3.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,597 root INFO copying ansible_collections/community/grafana/changelogs/fragments/1.3.1.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,597 root INFO copying ansible_collections/community/grafana/changelogs/fragments/1.5.3.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,598 root INFO copying ansible_collections/community/grafana/changelogs/fragments/136_add_grafana_action_groups.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,598 root INFO copying ansible_collections/community/grafana/changelogs/fragments/158-grafana_dashboard-lookup-api-key.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,598 root INFO copying ansible_collections/community/grafana/changelogs/fragments/170_remove_requirement_ds_type_ds_url.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,598 root INFO copying ansible_collections/community/grafana/changelogs/fragments/172_support_azure_datasource.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,599 root INFO copying ansible_collections/community/grafana/changelogs/fragments/186_check_fragments.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,599 root INFO copying ansible_collections/community/grafana/changelogs/fragments/191.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,599 root INFO copying ansible_collections/community/grafana/changelogs/fragments/230-uid-datasource.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,599 root INFO copying ansible_collections/community/grafana/changelogs/fragments/239_keyerror_grafana_url.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,599 root INFO copying ansible_collections/community/grafana/changelogs/fragments/248_ds_update_error_grafana_9.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,600 root INFO copying ansible_collections/community/grafana/changelogs/fragments/257_pretty_printed_dashboard_export.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,600 root INFO copying ansible_collections/community/grafana/changelogs/fragments/265-url-encode-user.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,600 root INFO copying ansible_collections/community/grafana/changelogs/fragments/270-gha--ansible-test--integration.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,600 root INFO copying ansible_collections/community/grafana/changelogs/fragments/277-gha-ansible-test-versions.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,601 root INFO copying ansible_collections/community/grafana/changelogs/fragments/288_get_actual_org_encode.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,601 root INFO copying ansible_collections/community/grafana/changelogs/fragments/add-units-datasource.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,601 root INFO copying ansible_collections/community/grafana/changelogs/fragments/ci.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,601 root INFO copying ansible_collections/community/grafana/changelogs/fragments/datasource-issue-204.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,601 root INFO copying ansible_collections/community/grafana/changelogs/fragments/fix-263.yaml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,602 root INFO copying ansible_collections/community/grafana/changelogs/fragments/fix_slashes_in_datasources.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,602 root INFO copying ansible_collections/community/grafana/changelogs/fragments/grafana_users_note.yaml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,602 root INFO copying ansible_collections/community/grafana/changelogs/fragments/notifi_channel_refacto.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,602 root INFO copying ansible_collections/community/grafana/changelogs/fragments/threema.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,602 root INFO copying ansible_collections/community/grafana/changelogs/fragments/update_deprecation.yml -> build/lib/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:41,603 root INFO creating build/lib/ansible_collections/community/grafana/hacking 2023-04-28 05:57:41,603 root INFO copying ansible_collections/community/grafana/hacking/NEED_FRAGMENT -> build/lib/ansible_collections/community/grafana/hacking 2023-04-28 05:57:41,603 root INFO copying ansible_collections/community/grafana/hacking/check_fragment.sh -> build/lib/ansible_collections/community/grafana/hacking 2023-04-28 05:57:41,603 root INFO copying ansible_collections/community/grafana/hacking/find_grafana_versions.py -> build/lib/ansible_collections/community/grafana/hacking 2023-04-28 05:57:41,604 root INFO copying ansible_collections/community/grafana/hacking/requirements.txt -> build/lib/ansible_collections/community/grafana/hacking 2023-04-28 05:57:41,604 root INFO creating build/lib/ansible_collections/community/grafana/meta 2023-04-28 05:57:41,604 root INFO copying ansible_collections/community/grafana/meta/runtime.yml -> build/lib/ansible_collections/community/grafana/meta 2023-04-28 05:57:41,604 root INFO creating build/lib/ansible_collections/community/grafana/plugins 2023-04-28 05:57:41,604 root INFO creating build/lib/ansible_collections/community/grafana/plugins/callback 2023-04-28 05:57:41,604 root INFO copying ansible_collections/community/grafana/plugins/callback/__init__.py -> build/lib/ansible_collections/community/grafana/plugins/callback 2023-04-28 05:57:41,605 root INFO copying ansible_collections/community/grafana/plugins/callback/grafana_annotations.py -> build/lib/ansible_collections/community/grafana/plugins/callback 2023-04-28 05:57:41,605 root INFO creating build/lib/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:41,605 root INFO copying ansible_collections/community/grafana/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:41,605 root INFO copying ansible_collections/community/grafana/plugins/doc_fragments/api_key.py -> build/lib/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:41,605 root INFO copying ansible_collections/community/grafana/plugins/doc_fragments/basic_auth.py -> build/lib/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:41,606 root INFO creating build/lib/ansible_collections/community/grafana/plugins/lookup 2023-04-28 05:57:41,606 root INFO copying ansible_collections/community/grafana/plugins/lookup/__init__.py -> build/lib/ansible_collections/community/grafana/plugins/lookup 2023-04-28 05:57:41,606 root INFO copying ansible_collections/community/grafana/plugins/lookup/grafana_dashboard.py -> build/lib/ansible_collections/community/grafana/plugins/lookup 2023-04-28 05:57:41,606 root INFO creating build/lib/ansible_collections/community/grafana/plugins/module_utils 2023-04-28 05:57:41,606 root INFO copying ansible_collections/community/grafana/plugins/module_utils/base.py -> build/lib/ansible_collections/community/grafana/plugins/module_utils 2023-04-28 05:57:41,606 root INFO creating build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,607 root INFO copying ansible_collections/community/grafana/plugins/modules/__init__.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,607 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_dashboard.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,607 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_datasource.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,607 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_folder.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,608 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_notification_channel.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,608 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_organization.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,608 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_plugin.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,608 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_team.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,609 root INFO copying ansible_collections/community/grafana/plugins/modules/grafana_user.py -> build/lib/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:41,609 root INFO creating build/lib/ansible_collections/community/hashi_vault 2023-04-28 05:57:41,609 root INFO copying ansible_collections/community/hashi_vault/CHANGELOG.rst -> build/lib/ansible_collections/community/hashi_vault 2023-04-28 05:57:41,609 root INFO copying ansible_collections/community/hashi_vault/FILES.json -> build/lib/ansible_collections/community/hashi_vault 2023-04-28 05:57:41,610 root INFO copying ansible_collections/community/hashi_vault/LICENSE -> build/lib/ansible_collections/community/hashi_vault 2023-04-28 05:57:41,610 root INFO copying ansible_collections/community/hashi_vault/MANIFEST.json -> build/lib/ansible_collections/community/hashi_vault 2023-04-28 05:57:41,610 root INFO copying ansible_collections/community/hashi_vault/README.md -> build/lib/ansible_collections/community/hashi_vault 2023-04-28 05:57:41,610 root INFO copying ansible_collections/community/hashi_vault/codecov.yml -> build/lib/ansible_collections/community/hashi_vault 2023-04-28 05:57:41,610 root INFO creating build/lib/ansible_collections/community/hashi_vault/LICENSES 2023-04-28 05:57:41,611 root INFO copying ansible_collections/community/hashi_vault/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/community/hashi_vault/LICENSES 2023-04-28 05:57:41,611 root INFO copying ansible_collections/community/hashi_vault/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/hashi_vault/LICENSES 2023-04-28 05:57:41,611 root INFO creating build/lib/ansible_collections/community/hashi_vault/changelogs 2023-04-28 05:57:41,611 root INFO copying ansible_collections/community/hashi_vault/changelogs/changelog.yaml -> build/lib/ansible_collections/community/hashi_vault/changelogs 2023-04-28 05:57:41,611 root INFO copying ansible_collections/community/hashi_vault/changelogs/config.yaml -> build/lib/ansible_collections/community/hashi_vault/changelogs 2023-04-28 05:57:41,612 root INFO creating build/lib/ansible_collections/community/hashi_vault/changelogs/fragments 2023-04-28 05:57:41,612 root INFO copying ansible_collections/community/hashi_vault/changelogs/fragments/.keep -> build/lib/ansible_collections/community/hashi_vault/changelogs/fragments 2023-04-28 05:57:41,612 root INFO creating build/lib/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:41,612 root INFO copying ansible_collections/community/hashi_vault/meta/ee-requirements.txt -> build/lib/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:41,612 root INFO copying ansible_collections/community/hashi_vault/meta/execution-environment.yml -> build/lib/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:41,613 root INFO copying ansible_collections/community/hashi_vault/meta/runtime.yml -> build/lib/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:41,613 root INFO creating build/lib/ansible_collections/community/hashi_vault/plugins 2023-04-28 05:57:41,613 root INFO creating build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:41,613 root INFO copying ansible_collections/community/hashi_vault/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:41,613 root INFO copying ansible_collections/community/hashi_vault/plugins/doc_fragments/auth.py -> build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:41,614 root INFO copying ansible_collections/community/hashi_vault/plugins/doc_fragments/connection.py -> build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:41,614 root INFO copying ansible_collections/community/hashi_vault/plugins/doc_fragments/engine_mount.py -> build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:41,614 root INFO copying ansible_collections/community/hashi_vault/plugins/doc_fragments/token_create.py -> build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:41,614 root INFO copying ansible_collections/community/hashi_vault/plugins/doc_fragments/wrapping.py -> build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:41,614 root INFO creating build/lib/ansible_collections/community/hashi_vault/plugins/filter 2023-04-28 05:57:41,615 root INFO copying ansible_collections/community/hashi_vault/plugins/filter/vault_login_token.py -> build/lib/ansible_collections/community/hashi_vault/plugins/filter 2023-04-28 05:57:41,615 root INFO copying ansible_collections/community/hashi_vault/plugins/filter/vault_login_token.yml -> build/lib/ansible_collections/community/hashi_vault/plugins/filter 2023-04-28 05:57:41,615 root INFO creating build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,615 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/hashi_vault.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,615 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_ansible_settings.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,616 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_kv1_get.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,616 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_kv2_get.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,616 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_list.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,616 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_login.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,616 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_read.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,617 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_token_create.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,617 root INFO copying ansible_collections/community/hashi_vault/plugins/lookup/vault_write.py -> build/lib/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:41,617 root INFO creating build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,617 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_approle.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,618 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_aws_iam.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,618 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_azure.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,618 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_cert.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,618 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_jwt.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,618 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_ldap.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,619 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_none.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,619 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_token.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,619 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_userpass.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,619 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_authenticator.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,619 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_connection_options.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,620 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_hashi_vault_common.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,620 root INFO copying ansible_collections/community/hashi_vault/plugins/module_utils/_hashi_vault_module.py -> build/lib/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:41,620 root INFO creating build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,620 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_kv1_get.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,621 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_delete.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,621 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_get.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,621 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_write.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,621 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_list.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,621 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_login.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,622 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_pki_generate_certificate.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,622 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_read.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,622 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_token_create.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,622 root INFO copying ansible_collections/community/hashi_vault/plugins/modules/vault_write.py -> build/lib/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:41,623 root INFO creating build/lib/ansible_collections/community/hashi_vault/plugins/plugin_utils 2023-04-28 05:57:41,623 root INFO copying ansible_collections/community/hashi_vault/plugins/plugin_utils/_hashi_vault_lookup_base.py -> build/lib/ansible_collections/community/hashi_vault/plugins/plugin_utils 2023-04-28 05:57:41,623 root INFO copying ansible_collections/community/hashi_vault/plugins/plugin_utils/_hashi_vault_plugin.py -> build/lib/ansible_collections/community/hashi_vault/plugins/plugin_utils 2023-04-28 05:57:41,623 root INFO creating build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,623 root INFO copying ansible_collections/community/hrobot/CHANGELOG.rst -> build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,624 root INFO copying ansible_collections/community/hrobot/CHANGELOG.rst.license -> build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,624 root INFO copying ansible_collections/community/hrobot/COPYING -> build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,624 root INFO copying ansible_collections/community/hrobot/FILES.json -> build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,624 root INFO copying ansible_collections/community/hrobot/MANIFEST.json -> build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,625 root INFO copying ansible_collections/community/hrobot/README.md -> build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,625 root INFO copying ansible_collections/community/hrobot/codecov.yml -> build/lib/ansible_collections/community/hrobot 2023-04-28 05:57:41,625 root INFO creating build/lib/ansible_collections/community/hrobot/LICENSES 2023-04-28 05:57:41,625 root INFO copying ansible_collections/community/hrobot/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/community/hrobot/LICENSES 2023-04-28 05:57:41,625 root INFO copying ansible_collections/community/hrobot/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/hrobot/LICENSES 2023-04-28 05:57:41,626 root INFO creating build/lib/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:41,626 root INFO copying ansible_collections/community/hrobot/changelogs/changelog.yaml -> build/lib/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:41,626 root INFO copying ansible_collections/community/hrobot/changelogs/changelog.yaml.license -> build/lib/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:41,626 root INFO copying ansible_collections/community/hrobot/changelogs/config.yaml -> build/lib/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:41,626 root INFO creating build/lib/ansible_collections/community/hrobot/changelogs/fragments 2023-04-28 05:57:41,627 root INFO copying ansible_collections/community/hrobot/changelogs/fragments/.keep -> build/lib/ansible_collections/community/hrobot/changelogs/fragments 2023-04-28 05:57:41,627 root INFO creating build/lib/ansible_collections/community/hrobot/meta 2023-04-28 05:57:41,627 root INFO copying ansible_collections/community/hrobot/meta/execution-environment.yml -> build/lib/ansible_collections/community/hrobot/meta 2023-04-28 05:57:41,627 root INFO copying ansible_collections/community/hrobot/meta/runtime.yml -> build/lib/ansible_collections/community/hrobot/meta 2023-04-28 05:57:41,627 root INFO creating build/lib/ansible_collections/community/hrobot/plugins 2023-04-28 05:57:41,627 root INFO creating build/lib/ansible_collections/community/hrobot/plugins/doc_fragments 2023-04-28 05:57:41,628 root INFO copying ansible_collections/community/hrobot/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/hrobot/plugins/doc_fragments 2023-04-28 05:57:41,628 root INFO copying ansible_collections/community/hrobot/plugins/doc_fragments/robot.py -> build/lib/ansible_collections/community/hrobot/plugins/doc_fragments 2023-04-28 05:57:41,628 root INFO creating build/lib/ansible_collections/community/hrobot/plugins/inventory 2023-04-28 05:57:41,628 root INFO copying ansible_collections/community/hrobot/plugins/inventory/robot.py -> build/lib/ansible_collections/community/hrobot/plugins/inventory 2023-04-28 05:57:41,628 root INFO creating build/lib/ansible_collections/community/hrobot/plugins/module_utils 2023-04-28 05:57:41,629 root INFO copying ansible_collections/community/hrobot/plugins/module_utils/failover.py -> build/lib/ansible_collections/community/hrobot/plugins/module_utils 2023-04-28 05:57:41,629 root INFO copying ansible_collections/community/hrobot/plugins/module_utils/robot.py -> build/lib/ansible_collections/community/hrobot/plugins/module_utils 2023-04-28 05:57:41,629 root INFO creating build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,629 root INFO copying ansible_collections/community/hrobot/plugins/modules/boot.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,630 root INFO copying ansible_collections/community/hrobot/plugins/modules/failover_ip.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,630 root INFO copying ansible_collections/community/hrobot/plugins/modules/failover_ip_info.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,630 root INFO copying ansible_collections/community/hrobot/plugins/modules/firewall.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,630 root INFO copying ansible_collections/community/hrobot/plugins/modules/firewall_info.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,631 root INFO copying ansible_collections/community/hrobot/plugins/modules/reset.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,631 root INFO copying ansible_collections/community/hrobot/plugins/modules/reverse_dns.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,631 root INFO copying ansible_collections/community/hrobot/plugins/modules/server.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,631 root INFO copying ansible_collections/community/hrobot/plugins/modules/server_info.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,632 root INFO copying ansible_collections/community/hrobot/plugins/modules/ssh_key.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,632 root INFO copying ansible_collections/community/hrobot/plugins/modules/ssh_key_info.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,632 root INFO copying ansible_collections/community/hrobot/plugins/modules/v_switch.py -> build/lib/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:41,632 root INFO creating build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,632 root INFO copying ansible_collections/community/libvirt/CHANGELOG.rst -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,633 root INFO copying ansible_collections/community/libvirt/CONTRIBUTING.md -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,633 root INFO copying ansible_collections/community/libvirt/COPYING -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,633 root INFO copying ansible_collections/community/libvirt/FILES.json -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,633 root INFO copying ansible_collections/community/libvirt/MAINTAINERS -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,634 root INFO copying ansible_collections/community/libvirt/MAINTAINING.md -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,634 root INFO copying ansible_collections/community/libvirt/MANIFEST.json -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,634 root INFO copying ansible_collections/community/libvirt/README.md -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,634 root INFO copying ansible_collections/community/libvirt/REVIEW_CHECKLIST.md -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,634 root INFO copying ansible_collections/community/libvirt/shippable.yml -> build/lib/ansible_collections/community/libvirt 2023-04-28 05:57:41,635 root INFO creating build/lib/ansible_collections/community/libvirt/changelogs 2023-04-28 05:57:41,635 root INFO copying ansible_collections/community/libvirt/changelogs/changelog.yaml -> build/lib/ansible_collections/community/libvirt/changelogs 2023-04-28 05:57:41,635 root INFO copying ansible_collections/community/libvirt/changelogs/config.yaml -> build/lib/ansible_collections/community/libvirt/changelogs 2023-04-28 05:57:41,635 root INFO creating build/lib/ansible_collections/community/libvirt/meta 2023-04-28 05:57:41,635 root INFO copying ansible_collections/community/libvirt/meta/runtime.yml -> build/lib/ansible_collections/community/libvirt/meta 2023-04-28 05:57:41,636 root INFO creating build/lib/ansible_collections/community/libvirt/plugins 2023-04-28 05:57:41,636 root INFO creating build/lib/ansible_collections/community/libvirt/plugins/connection 2023-04-28 05:57:41,636 root INFO copying ansible_collections/community/libvirt/plugins/connection/libvirt_lxc.py -> build/lib/ansible_collections/community/libvirt/plugins/connection 2023-04-28 05:57:41,636 root INFO copying ansible_collections/community/libvirt/plugins/connection/libvirt_qemu.py -> build/lib/ansible_collections/community/libvirt/plugins/connection 2023-04-28 05:57:41,636 root INFO creating build/lib/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:41,636 root INFO copying ansible_collections/community/libvirt/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:41,637 root INFO copying ansible_collections/community/libvirt/plugins/doc_fragments/requirements.py -> build/lib/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:41,637 root INFO copying ansible_collections/community/libvirt/plugins/doc_fragments/virt.py -> build/lib/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:41,637 root INFO creating build/lib/ansible_collections/community/libvirt/plugins/inventory 2023-04-28 05:57:41,637 root INFO copying ansible_collections/community/libvirt/plugins/inventory/__init__.py -> build/lib/ansible_collections/community/libvirt/plugins/inventory 2023-04-28 05:57:41,637 root INFO copying ansible_collections/community/libvirt/plugins/inventory/libvirt.py -> build/lib/ansible_collections/community/libvirt/plugins/inventory 2023-04-28 05:57:41,638 root INFO creating build/lib/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:41,638 root INFO copying ansible_collections/community/libvirt/plugins/modules/virt.py -> build/lib/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:41,638 root INFO copying ansible_collections/community/libvirt/plugins/modules/virt_net.py -> build/lib/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:41,638 root INFO copying ansible_collections/community/libvirt/plugins/modules/virt_pool.py -> build/lib/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:41,639 root INFO creating build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,639 root INFO copying ansible_collections/community/mongodb/CHANGELOG.rst -> build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,639 root INFO copying ansible_collections/community/mongodb/COPYING -> build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,639 root INFO copying ansible_collections/community/mongodb/FILES.json -> build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,639 root INFO copying ansible_collections/community/mongodb/MANIFEST.json -> build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,640 root INFO copying ansible_collections/community/mongodb/README.md -> build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,640 root INFO copying ansible_collections/community/mongodb/requirements-3.6.txt -> build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,640 root INFO copying ansible_collections/community/mongodb/requirements-3.8.txt -> build/lib/ansible_collections/community/mongodb 2023-04-28 05:57:41,640 root INFO creating build/lib/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:41,640 root INFO copying ansible_collections/community/mongodb/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:41,641 root INFO copying ansible_collections/community/mongodb/changelogs/changelog.yaml -> build/lib/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:41,641 root INFO copying ansible_collections/community/mongodb/changelogs/config.yaml -> build/lib/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:41,641 root INFO creating build/lib/ansible_collections/community/mongodb/meta 2023-04-28 05:57:41,641 root INFO copying ansible_collections/community/mongodb/meta/runtime.yml -> build/lib/ansible_collections/community/mongodb/meta 2023-04-28 05:57:41,642 root INFO creating build/lib/ansible_collections/community/mongodb/plugins 2023-04-28 05:57:41,642 root INFO creating build/lib/ansible_collections/community/mongodb/plugins/cache 2023-04-28 05:57:41,642 root INFO copying ansible_collections/community/mongodb/plugins/cache/__init__.py -> build/lib/ansible_collections/community/mongodb/plugins/cache 2023-04-28 05:57:41,642 root INFO copying ansible_collections/community/mongodb/plugins/cache/mongodb.py -> build/lib/ansible_collections/community/mongodb/plugins/cache 2023-04-28 05:57:41,642 root INFO creating build/lib/ansible_collections/community/mongodb/plugins/doc_fragments 2023-04-28 05:57:41,642 root INFO copying ansible_collections/community/mongodb/plugins/doc_fragments/login_options.py -> build/lib/ansible_collections/community/mongodb/plugins/doc_fragments 2023-04-28 05:57:41,643 root INFO copying ansible_collections/community/mongodb/plugins/doc_fragments/ssl_options.py -> build/lib/ansible_collections/community/mongodb/plugins/doc_fragments 2023-04-28 05:57:41,643 root INFO creating build/lib/ansible_collections/community/mongodb/plugins/lookup 2023-04-28 05:57:41,643 root INFO copying ansible_collections/community/mongodb/plugins/lookup/__init__.py -> build/lib/ansible_collections/community/mongodb/plugins/lookup 2023-04-28 05:57:41,643 root INFO copying ansible_collections/community/mongodb/plugins/lookup/mongodb.py -> build/lib/ansible_collections/community/mongodb/plugins/lookup 2023-04-28 05:57:41,643 root INFO creating build/lib/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:41,643 root INFO copying ansible_collections/community/mongodb/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:41,644 root INFO copying ansible_collections/community/mongodb/plugins/module_utils/mongodb_common.py -> build/lib/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:41,644 root INFO copying ansible_collections/community/mongodb/plugins/module_utils/mongodb_shell.py -> build/lib/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:41,644 root INFO creating build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,644 root INFO copying ansible_collections/community/mongodb/plugins/modules/__init__.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,644 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_balancer.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,645 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_index.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,645 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_info.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,645 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_maintenance.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,645 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_monitoring.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,646 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_oplog.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,646 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_parameter.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,646 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_replicaset.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,646 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_role.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,647 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_schema.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,647 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_shard.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,647 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_shard_tag.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,647 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_shard_zone.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,647 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_shell.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,648 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_shutdown.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,648 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_status.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,648 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_stepdown.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,648 root INFO copying ansible_collections/community/mongodb/plugins/modules/mongodb_user.py -> build/lib/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:41,649 root INFO creating build/lib/ansible_collections/community/mongodb/roles 2023-04-28 05:57:41,649 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth 2023-04-28 05:57:41,649 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/.yamllint -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth 2023-04-28 05:57:41,649 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth 2023-04-28 05:57:41,649 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/defaults 2023-04-28 05:57:41,649 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/defaults/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/defaults 2023-04-28 05:57:41,650 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/meta 2023-04-28 05:57:41,650 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/meta 2023-04-28 05:57:41,650 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule 2023-04-28 05:57:41,650 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:41,650 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:41,651 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:41,651 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:41,651 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:41,651 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests 2023-04-28 05:57:41,651 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests 2023-04-28 05:57:41,652 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:41,652 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:41,652 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:41,652 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:41,652 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests 2023-04-28 05:57:41,652 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests 2023-04-28 05:57:41,653 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/tasks 2023-04-28 05:57:41,653 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/tasks 2023-04-28 05:57:41,653 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/tasks/mongodb_auth_user.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/tasks 2023-04-28 05:57:41,653 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:41,653 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/vars/Amazon.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:41,654 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/vars/RedHat-7.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:41,654 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/vars/RedHat-8.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:41,654 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/vars/default.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:41,654 root INFO copying ansible_collections/community/mongodb/roles/mongodb_auth/vars/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:41,654 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config 2023-04-28 05:57:41,655 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/.yamllint -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config 2023-04-28 05:57:41,655 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config 2023-04-28 05:57:41,655 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/defaults 2023-04-28 05:57:41,655 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/defaults/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/defaults 2023-04-28 05:57:41,655 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/handlers 2023-04-28 05:57:41,656 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/handlers/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/handlers 2023-04-28 05:57:41,656 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/meta 2023-04-28 05:57:41,656 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/meta 2023-04-28 05:57:41,656 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule 2023-04-28 05:57:41,656 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:41,656 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:41,657 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:41,657 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:41,657 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:41,657 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests 2023-04-28 05:57:41,657 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests 2023-04-28 05:57:41,658 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:41,658 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:41,658 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:41,658 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:41,658 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:41,659 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests 2023-04-28 05:57:41,659 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests 2023-04-28 05:57:41,659 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:41,659 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:41,659 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:41,660 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:41,660 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests 2023-04-28 05:57:41,660 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests 2023-04-28 05:57:41,660 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/tasks 2023-04-28 05:57:41,660 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/tasks 2023-04-28 05:57:41,661 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/templates 2023-04-28 05:57:41,661 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/templates/configsrv.conf.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/templates 2023-04-28 05:57:41,661 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:41,661 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/vars/Debian.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:41,661 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/vars/RedHat.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:41,661 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/vars/default.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:41,662 root INFO copying ansible_collections/community/mongodb/roles/mongodb_config/vars/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:41,662 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install 2023-04-28 05:57:41,662 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/.yamllint -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install 2023-04-28 05:57:41,662 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install 2023-04-28 05:57:41,662 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/files 2023-04-28 05:57:41,663 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/files/lock_mongodb_packages.sh -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/files 2023-04-28 05:57:41,663 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/meta 2023-04-28 05:57:41,663 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/meta 2023-04-28 05:57:41,663 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule 2023-04-28 05:57:41,663 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:41,663 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:41,664 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:41,664 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:41,664 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests 2023-04-28 05:57:41,664 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests 2023-04-28 05:57:41,664 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:41,665 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:41,665 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:41,665 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:41,665 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:41,665 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests 2023-04-28 05:57:41,666 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests 2023-04-28 05:57:41,666 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:41,666 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:41,666 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:41,666 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:41,667 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:41,667 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests 2023-04-28 05:57:41,667 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests 2023-04-28 05:57:41,667 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:41,667 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:41,668 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:41,668 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:41,668 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests 2023-04-28 05:57:41,668 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests 2023-04-28 05:57:41,668 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:41,669 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:41,669 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:41,669 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:41,669 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests 2023-04-28 05:57:41,669 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests 2023-04-28 05:57:41,670 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_install/tasks 2023-04-28 05:57:41,670 root INFO copying ansible_collections/community/mongodb/roles/mongodb_install/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_install/tasks 2023-04-28 05:57:41,670 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux 2023-04-28 05:57:41,670 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux 2023-04-28 05:57:41,670 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/defaults 2023-04-28 05:57:41,670 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/defaults/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/defaults 2023-04-28 05:57:41,671 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/files 2023-04-28 05:57:41,671 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/files/thp-disable.service -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/files 2023-04-28 05:57:41,671 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/meta 2023-04-28 05:57:41,671 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/meta 2023-04-28 05:57:41,671 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule 2023-04-28 05:57:41,671 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:41,672 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:41,672 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:41,672 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:41,672 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests 2023-04-28 05:57:41,672 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests 2023-04-28 05:57:41,673 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:41,673 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:41,673 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:41,673 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:41,673 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests 2023-04-28 05:57:41,674 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests 2023-04-28 05:57:41,674 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/tasks 2023-04-28 05:57:41,674 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/tasks 2023-04-28 05:57:41,674 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:41,674 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/vars/Debian.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:41,674 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/vars/Fedora.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:41,675 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/vars/RedHat-8.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:41,675 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/vars/RedHat.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:41,675 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/vars/default.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:41,675 root INFO copying ansible_collections/community/mongodb/roles/mongodb_linux/vars/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:41,676 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod 2023-04-28 05:57:41,676 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/.yamllint -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod 2023-04-28 05:57:41,676 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod 2023-04-28 05:57:41,676 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/defaults 2023-04-28 05:57:41,676 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/defaults/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/defaults 2023-04-28 05:57:41,676 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/handlers 2023-04-28 05:57:41,677 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/handlers/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/handlers 2023-04-28 05:57:41,677 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/meta 2023-04-28 05:57:41,677 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/meta 2023-04-28 05:57:41,677 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule 2023-04-28 05:57:41,677 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:41,677 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:41,678 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:41,678 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:41,678 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:41,678 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests 2023-04-28 05:57:41,678 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests 2023-04-28 05:57:41,679 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:41,679 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:41,679 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:41,679 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:41,679 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:41,680 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests 2023-04-28 05:57:41,680 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests 2023-04-28 05:57:41,680 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:41,680 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:41,680 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:41,681 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:41,681 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:41,681 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests 2023-04-28 05:57:41,681 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests 2023-04-28 05:57:41,681 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:41,682 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:41,682 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:41,682 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:41,682 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests 2023-04-28 05:57:41,682 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests 2023-04-28 05:57:41,683 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/tasks 2023-04-28 05:57:41,683 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/tasks 2023-04-28 05:57:41,683 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/templates 2023-04-28 05:57:41,683 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/templates/mongod.conf.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/templates 2023-04-28 05:57:41,683 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:41,683 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/vars/Debian.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:41,684 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/vars/RedHat.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:41,684 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/vars/default.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:41,684 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongod/vars/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:41,684 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos 2023-04-28 05:57:41,684 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/.yamllint -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos 2023-04-28 05:57:41,685 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos 2023-04-28 05:57:41,685 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/defaults 2023-04-28 05:57:41,685 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/defaults/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/defaults 2023-04-28 05:57:41,685 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/handlers 2023-04-28 05:57:41,685 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/handlers/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/handlers 2023-04-28 05:57:41,686 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/meta 2023-04-28 05:57:41,686 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/meta 2023-04-28 05:57:41,686 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule 2023-04-28 05:57:41,686 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:41,686 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:41,686 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:41,687 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:41,687 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:41,687 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests 2023-04-28 05:57:41,687 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests 2023-04-28 05:57:41,687 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:41,688 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:41,688 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:41,688 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/prepare.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:41,688 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests 2023-04-28 05:57:41,688 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests 2023-04-28 05:57:41,689 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/tasks 2023-04-28 05:57:41,689 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/tasks 2023-04-28 05:57:41,689 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:41,689 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos.conf.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:41,689 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos.service.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:41,690 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos_pre.sh.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:41,690 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:41,690 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/vars/Debian.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:41,690 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/vars/RedHat.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:41,690 root INFO copying ansible_collections/community/mongodb/roles/mongodb_mongos/vars/default.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:41,691 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository 2023-04-28 05:57:41,691 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/.yamllint -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository 2023-04-28 05:57:41,691 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository 2023-04-28 05:57:41,691 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/defaults 2023-04-28 05:57:41,691 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/defaults/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/defaults 2023-04-28 05:57:41,691 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/meta 2023-04-28 05:57:41,692 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/meta 2023-04-28 05:57:41,692 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule 2023-04-28 05:57:41,692 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:41,692 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:41,692 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:41,693 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:41,693 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests 2023-04-28 05:57:41,693 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests 2023-04-28 05:57:41,693 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox 2023-04-28 05:57:41,693 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox 2023-04-28 05:57:41,693 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox 2023-04-28 05:57:41,694 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests 2023-04-28 05:57:41,694 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests 2023-04-28 05:57:41,694 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:41,694 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/tasks/Debian.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:41,694 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/tasks/RedHat.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:41,695 root INFO copying ansible_collections/community/mongodb/roles/mongodb_repository/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:41,695 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux 2023-04-28 05:57:41,695 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/.yamllint -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux 2023-04-28 05:57:41,695 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/README.md -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux 2023-04-28 05:57:41,695 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/files 2023-04-28 05:57:41,696 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/files/compile_mongodb_selinux.sh -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/files 2023-04-28 05:57:41,696 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/meta 2023-04-28 05:57:41,696 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/meta/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/meta 2023-04-28 05:57:41,696 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule 2023-04-28 05:57:41,696 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:41,696 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/Dockerfile.j2 -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:41,697 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:41,697 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:41,697 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests 2023-04-28 05:57:41,697 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests 2023-04-28 05:57:41,697 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox 2023-04-28 05:57:41,697 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/molecule.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox 2023-04-28 05:57:41,698 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/playbook.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox 2023-04-28 05:57:41,698 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests 2023-04-28 05:57:41,698 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests/test_default.py -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests 2023-04-28 05:57:41,698 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/tasks 2023-04-28 05:57:41,698 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/tasks/main.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/tasks 2023-04-28 05:57:41,699 root INFO creating build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,699 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Amazon.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,699 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Debian.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,699 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Fedora.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,699 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/vars/RedHat-7.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,700 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/vars/RedHat-8.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,700 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Ubuntu-16.04.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,700 root INFO copying ansible_collections/community/mongodb/roles/mongodb_selinux/vars/default.yml -> build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:41,700 root INFO creating build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,700 root INFO copying ansible_collections/community/mysql/CHANGELOG.rst -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,701 root INFO copying ansible_collections/community/mysql/CONTRIBUTING.md -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,701 root INFO copying ansible_collections/community/mysql/CONTRIBUTORS -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,701 root INFO copying ansible_collections/community/mysql/COPYING -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,701 root INFO copying ansible_collections/community/mysql/FILES.json -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,702 root INFO copying ansible_collections/community/mysql/MAINTAINERS -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,702 root INFO copying ansible_collections/community/mysql/MAINTAINING.md -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,702 root INFO copying ansible_collections/community/mysql/MANIFEST.json -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,702 root INFO copying ansible_collections/community/mysql/PSF-license.txt -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,703 root INFO copying ansible_collections/community/mysql/README.md -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,703 root INFO copying ansible_collections/community/mysql/codecov.yml -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,703 root INFO copying ansible_collections/community/mysql/simplified_bsd.txt -> build/lib/ansible_collections/community/mysql 2023-04-28 05:57:41,703 root INFO creating build/lib/ansible_collections/community/mysql/changelogs 2023-04-28 05:57:41,703 root INFO copying ansible_collections/community/mysql/changelogs/changelog.yaml -> build/lib/ansible_collections/community/mysql/changelogs 2023-04-28 05:57:41,704 root INFO copying ansible_collections/community/mysql/changelogs/config.yaml -> build/lib/ansible_collections/community/mysql/changelogs 2023-04-28 05:57:41,704 root INFO creating build/lib/ansible_collections/community/mysql/changelogs/fragments 2023-04-28 05:57:41,704 root INFO copying ansible_collections/community/mysql/changelogs/fragments/.keep -> build/lib/ansible_collections/community/mysql/changelogs/fragments 2023-04-28 05:57:41,704 root INFO creating build/lib/ansible_collections/community/mysql/meta 2023-04-28 05:57:41,704 root INFO copying ansible_collections/community/mysql/meta/runtime.yml -> build/lib/ansible_collections/community/mysql/meta 2023-04-28 05:57:41,705 root INFO creating build/lib/ansible_collections/community/mysql/plugins 2023-04-28 05:57:41,705 root INFO copying ansible_collections/community/mysql/plugins/README.md -> build/lib/ansible_collections/community/mysql/plugins 2023-04-28 05:57:41,705 root INFO creating build/lib/ansible_collections/community/mysql/plugins/doc_fragments 2023-04-28 05:57:41,705 root INFO copying ansible_collections/community/mysql/plugins/doc_fragments/mysql.py -> build/lib/ansible_collections/community/mysql/plugins/doc_fragments 2023-04-28 05:57:41,705 root INFO creating build/lib/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:41,705 root INFO copying ansible_collections/community/mysql/plugins/module_utils/_version.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:41,706 root INFO copying ansible_collections/community/mysql/plugins/module_utils/database.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:41,706 root INFO copying ansible_collections/community/mysql/plugins/module_utils/mysql.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:41,706 root INFO copying ansible_collections/community/mysql/plugins/module_utils/user.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:41,706 root INFO copying ansible_collections/community/mysql/plugins/module_utils/version.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:41,707 root INFO creating build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations 2023-04-28 05:57:41,707 root INFO creating build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:41,707 root INFO copying ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/replication.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:41,707 root INFO copying ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/role.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:41,707 root INFO copying ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/user.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:41,707 root INFO creating build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:41,708 root INFO copying ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/replication.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:41,708 root INFO copying ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/role.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:41,708 root INFO copying ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/user.py -> build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:41,708 root INFO creating build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,708 root INFO copying ansible_collections/community/mysql/plugins/modules/mysql_db.py -> build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,709 root INFO copying ansible_collections/community/mysql/plugins/modules/mysql_info.py -> build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,709 root INFO copying ansible_collections/community/mysql/plugins/modules/mysql_query.py -> build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,709 root INFO copying ansible_collections/community/mysql/plugins/modules/mysql_replication.py -> build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,709 root INFO copying ansible_collections/community/mysql/plugins/modules/mysql_role.py -> build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,710 root INFO copying ansible_collections/community/mysql/plugins/modules/mysql_user.py -> build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,710 root INFO copying ansible_collections/community/mysql/plugins/modules/mysql_variables.py -> build/lib/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:41,710 root INFO creating build/lib/ansible_collections/community/network 2023-04-28 05:57:41,710 root INFO copying ansible_collections/community/network/103-nclu-check-diff.yaml -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,710 root INFO copying ansible_collections/community/network/CHANGELOG.rst -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,711 root INFO copying ansible_collections/community/network/CONTRIBUTING.md -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,711 root INFO copying ansible_collections/community/network/COPYING -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,711 root INFO copying ansible_collections/community/network/FILES.json -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,712 root INFO copying ansible_collections/community/network/MANIFEST.json -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,712 root INFO copying ansible_collections/community/network/PSF-license.txt -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,712 root INFO copying ansible_collections/community/network/README.md -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,713 root INFO copying ansible_collections/community/network/shippable.yml -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,713 root INFO copying ansible_collections/community/network/simplified_bsd.txt -> build/lib/ansible_collections/community/network 2023-04-28 05:57:41,713 root INFO creating build/lib/ansible_collections/community/network/changelogs 2023-04-28 05:57:41,713 root INFO copying ansible_collections/community/network/changelogs/.gitignore -> build/lib/ansible_collections/community/network/changelogs 2023-04-28 05:57:41,713 root INFO copying ansible_collections/community/network/changelogs/changelog.yaml -> build/lib/ansible_collections/community/network/changelogs 2023-04-28 05:57:41,714 root INFO copying ansible_collections/community/network/changelogs/config.yaml -> build/lib/ansible_collections/community/network/changelogs 2023-04-28 05:57:41,714 root INFO creating build/lib/ansible_collections/community/network/changelogs/fragments 2023-04-28 05:57:41,714 root INFO copying ansible_collections/community/network/changelogs/fragments/.keep -> build/lib/ansible_collections/community/network/changelogs/fragments 2023-04-28 05:57:41,714 root INFO creating build/lib/ansible_collections/community/network/meta 2023-04-28 05:57:41,714 root INFO copying ansible_collections/community/network/meta/runtime.yml -> build/lib/ansible_collections/community/network/meta 2023-04-28 05:57:41,715 root INFO creating build/lib/ansible_collections/community/network/plugins 2023-04-28 05:57:41,715 root INFO creating build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,715 root INFO copying ansible_collections/community/network/plugins/action/__init__.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,715 root INFO copying ansible_collections/community/network/plugins/action/aireos.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,715 root INFO copying ansible_collections/community/network/plugins/action/aruba.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,716 root INFO copying ansible_collections/community/network/plugins/action/ce.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,716 root INFO copying ansible_collections/community/network/plugins/action/ce_template.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,716 root INFO copying ansible_collections/community/network/plugins/action/cnos.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,716 root INFO copying ansible_collections/community/network/plugins/action/edgeos_config.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,716 root INFO copying ansible_collections/community/network/plugins/action/enos.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,717 root INFO copying ansible_collections/community/network/plugins/action/exos.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,717 root INFO copying ansible_collections/community/network/plugins/action/ironware.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,717 root INFO copying ansible_collections/community/network/plugins/action/nos_config.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,717 root INFO copying ansible_collections/community/network/plugins/action/slxos.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,718 root INFO copying ansible_collections/community/network/plugins/action/sros.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,718 root INFO copying ansible_collections/community/network/plugins/action/voss.py -> build/lib/ansible_collections/community/network/plugins/action 2023-04-28 05:57:41,718 root INFO creating build/lib/ansible_collections/community/network/plugins/become 2023-04-28 05:57:41,718 root INFO copying ansible_collections/community/network/plugins/become/__init__.py -> build/lib/ansible_collections/community/network/plugins/become 2023-04-28 05:57:41,718 root INFO creating build/lib/ansible_collections/community/network/plugins/cache 2023-04-28 05:57:41,718 root INFO copying ansible_collections/community/network/plugins/cache/__init__.py -> build/lib/ansible_collections/community/network/plugins/cache 2023-04-28 05:57:41,719 root INFO creating build/lib/ansible_collections/community/network/plugins/callback 2023-04-28 05:57:41,719 root INFO copying ansible_collections/community/network/plugins/callback/__init__.py -> build/lib/ansible_collections/community/network/plugins/callback 2023-04-28 05:57:41,719 root INFO creating build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,719 root INFO copying ansible_collections/community/network/plugins/cliconf/__init__.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,719 root INFO copying ansible_collections/community/network/plugins/cliconf/aireos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,720 root INFO copying ansible_collections/community/network/plugins/cliconf/apconos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,720 root INFO copying ansible_collections/community/network/plugins/cliconf/aruba.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,720 root INFO copying ansible_collections/community/network/plugins/cliconf/ce.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,720 root INFO copying ansible_collections/community/network/plugins/cliconf/cnos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,720 root INFO copying ansible_collections/community/network/plugins/cliconf/edgeos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,721 root INFO copying ansible_collections/community/network/plugins/cliconf/edgeswitch.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,721 root INFO copying ansible_collections/community/network/plugins/cliconf/enos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,721 root INFO copying ansible_collections/community/network/plugins/cliconf/eric_eccli.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,721 root INFO copying ansible_collections/community/network/plugins/cliconf/exos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,722 root INFO copying ansible_collections/community/network/plugins/cliconf/icx.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,722 root INFO copying ansible_collections/community/network/plugins/cliconf/ironware.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,722 root INFO copying ansible_collections/community/network/plugins/cliconf/netvisor.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,722 root INFO copying ansible_collections/community/network/plugins/cliconf/nos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,722 root INFO copying ansible_collections/community/network/plugins/cliconf/slxos.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,723 root INFO copying ansible_collections/community/network/plugins/cliconf/voss.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,723 root INFO copying ansible_collections/community/network/plugins/cliconf/weos4.py -> build/lib/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:41,723 root INFO creating build/lib/ansible_collections/community/network/plugins/connection 2023-04-28 05:57:41,723 root INFO copying ansible_collections/community/network/plugins/connection/__init__.py -> build/lib/ansible_collections/community/network/plugins/connection 2023-04-28 05:57:41,723 root INFO creating build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,724 root INFO copying ansible_collections/community/network/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,724 root INFO copying ansible_collections/community/network/plugins/doc_fragments/a10.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,724 root INFO copying ansible_collections/community/network/plugins/doc_fragments/aireos.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,724 root INFO copying ansible_collections/community/network/plugins/doc_fragments/aruba.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,724 root INFO copying ansible_collections/community/network/plugins/doc_fragments/avi.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,725 root INFO copying ansible_collections/community/network/plugins/doc_fragments/ce.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,725 root INFO copying ansible_collections/community/network/plugins/doc_fragments/cnos.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,725 root INFO copying ansible_collections/community/network/plugins/doc_fragments/enos.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,725 root INFO copying ansible_collections/community/network/plugins/doc_fragments/ingate.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,726 root INFO copying ansible_collections/community/network/plugins/doc_fragments/ironware.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,726 root INFO copying ansible_collections/community/network/plugins/doc_fragments/netscaler.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,726 root INFO copying ansible_collections/community/network/plugins/doc_fragments/sros.py -> build/lib/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:41,726 root INFO creating build/lib/ansible_collections/community/network/plugins/filter 2023-04-28 05:57:41,726 root INFO copying ansible_collections/community/network/plugins/filter/__init__.py -> build/lib/ansible_collections/community/network/plugins/filter 2023-04-28 05:57:41,727 root INFO creating build/lib/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:41,727 root INFO copying ansible_collections/community/network/plugins/httpapi/__init__.py -> build/lib/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:41,727 root INFO copying ansible_collections/community/network/plugins/httpapi/exos.py -> build/lib/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:41,727 root INFO copying ansible_collections/community/network/plugins/httpapi/ftd.py -> build/lib/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:41,727 root INFO creating build/lib/ansible_collections/community/network/plugins/inventory 2023-04-28 05:57:41,728 root INFO copying ansible_collections/community/network/plugins/inventory/__init__.py -> build/lib/ansible_collections/community/network/plugins/inventory 2023-04-28 05:57:41,728 root INFO creating build/lib/ansible_collections/community/network/plugins/lookup 2023-04-28 05:57:41,728 root INFO copying ansible_collections/community/network/plugins/lookup/__init__.py -> build/lib/ansible_collections/community/network/plugins/lookup 2023-04-28 05:57:41,728 root INFO copying ansible_collections/community/network/plugins/lookup/avi.py -> build/lib/ansible_collections/community/network/plugins/lookup 2023-04-28 05:57:41,728 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:41,728 root INFO copying ansible_collections/community/network/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:41,729 root INFO copying ansible_collections/community/network/plugins/module_utils/_version.py -> build/lib/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:41,729 root INFO copying ansible_collections/community/network/plugins/module_utils/version.py -> build/lib/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:41,729 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network 2023-04-28 05:57:41,729 root INFO copying ansible_collections/community/network/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network 2023-04-28 05:57:41,729 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/a10 2023-04-28 05:57:41,730 root INFO copying ansible_collections/community/network/plugins/module_utils/network/a10/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/a10 2023-04-28 05:57:41,730 root INFO copying ansible_collections/community/network/plugins/module_utils/network/a10/a10.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/a10 2023-04-28 05:57:41,730 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/aireos 2023-04-28 05:57:41,730 root INFO copying ansible_collections/community/network/plugins/module_utils/network/aireos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/aireos 2023-04-28 05:57:41,730 root INFO copying ansible_collections/community/network/plugins/module_utils/network/aireos/aireos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/aireos 2023-04-28 05:57:41,731 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/aos 2023-04-28 05:57:41,731 root INFO copying ansible_collections/community/network/plugins/module_utils/network/aos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/aos 2023-04-28 05:57:41,731 root INFO copying ansible_collections/community/network/plugins/module_utils/network/aos/aos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/aos 2023-04-28 05:57:41,731 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/apconos 2023-04-28 05:57:41,731 root INFO copying ansible_collections/community/network/plugins/module_utils/network/apconos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/apconos 2023-04-28 05:57:41,732 root INFO copying ansible_collections/community/network/plugins/module_utils/network/apconos/apconos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/apconos 2023-04-28 05:57:41,732 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/aruba 2023-04-28 05:57:41,732 root INFO copying ansible_collections/community/network/plugins/module_utils/network/aruba/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/aruba 2023-04-28 05:57:41,732 root INFO copying ansible_collections/community/network/plugins/module_utils/network/aruba/aruba.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/aruba 2023-04-28 05:57:41,732 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:41,732 root INFO copying ansible_collections/community/network/plugins/module_utils/network/avi/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:41,733 root INFO copying ansible_collections/community/network/plugins/module_utils/network/avi/ansible_utils.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:41,733 root INFO copying ansible_collections/community/network/plugins/module_utils/network/avi/avi.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:41,733 root INFO copying ansible_collections/community/network/plugins/module_utils/network/avi/avi_api.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:41,733 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/bigswitch 2023-04-28 05:57:41,734 root INFO copying ansible_collections/community/network/plugins/module_utils/network/bigswitch/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/bigswitch 2023-04-28 05:57:41,734 root INFO copying ansible_collections/community/network/plugins/module_utils/network/bigswitch/bigswitch.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/bigswitch 2023-04-28 05:57:41,734 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/cloudengine 2023-04-28 05:57:41,734 root INFO copying ansible_collections/community/network/plugins/module_utils/network/cloudengine/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/cloudengine 2023-04-28 05:57:41,734 root INFO copying ansible_collections/community/network/plugins/module_utils/network/cloudengine/ce.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/cloudengine 2023-04-28 05:57:41,735 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:41,735 root INFO copying ansible_collections/community/network/plugins/module_utils/network/cnos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:41,735 root INFO copying ansible_collections/community/network/plugins/module_utils/network/cnos/cnos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:41,735 root INFO copying ansible_collections/community/network/plugins/module_utils/network/cnos/cnos_devicerules.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:41,736 root INFO copying ansible_collections/community/network/plugins/module_utils/network/cnos/cnos_errorcodes.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:41,736 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeos 2023-04-28 05:57:41,736 root INFO copying ansible_collections/community/network/plugins/module_utils/network/edgeos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeos 2023-04-28 05:57:41,736 root INFO copying ansible_collections/community/network/plugins/module_utils/network/edgeos/edgeos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeos 2023-04-28 05:57:41,736 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:41,736 root INFO copying ansible_collections/community/network/plugins/module_utils/network/edgeswitch/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:41,737 root INFO copying ansible_collections/community/network/plugins/module_utils/network/edgeswitch/edgeswitch.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:41,737 root INFO copying ansible_collections/community/network/plugins/module_utils/network/edgeswitch/edgeswitch_interface.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:41,737 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/enos 2023-04-28 05:57:41,737 root INFO copying ansible_collections/community/network/plugins/module_utils/network/enos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/enos 2023-04-28 05:57:41,737 root INFO copying ansible_collections/community/network/plugins/module_utils/network/enos/enos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/enos 2023-04-28 05:57:41,738 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/eric_eccli 2023-04-28 05:57:41,738 root INFO copying ansible_collections/community/network/plugins/module_utils/network/eric_eccli/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/eric_eccli 2023-04-28 05:57:41,738 root INFO copying ansible_collections/community/network/plugins/module_utils/network/eric_eccli/eric_eccli.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/eric_eccli 2023-04-28 05:57:41,738 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos 2023-04-28 05:57:41,738 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos 2023-04-28 05:57:41,739 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/exos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos 2023-04-28 05:57:41,739 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec 2023-04-28 05:57:41,739 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec 2023-04-28 05:57:41,739 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts 2023-04-28 05:57:41,739 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts 2023-04-28 05:57:41,740 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/facts.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts 2023-04-28 05:57:41,740 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces 2023-04-28 05:57:41,740 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces 2023-04-28 05:57:41,740 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces 2023-04-28 05:57:41,740 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global 2023-04-28 05:57:41,741 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global 2023-04-28 05:57:41,741 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/lldp_global.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global 2023-04-28 05:57:41,741 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces 2023-04-28 05:57:41,741 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces 2023-04-28 05:57:41,741 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces 2023-04-28 05:57:41,742 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans 2023-04-28 05:57:41,742 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans 2023-04-28 05:57:41,742 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/vlans.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans 2023-04-28 05:57:41,742 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config 2023-04-28 05:57:41,742 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config 2023-04-28 05:57:41,742 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces 2023-04-28 05:57:41,743 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces 2023-04-28 05:57:41,743 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces 2023-04-28 05:57:41,743 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global 2023-04-28 05:57:41,743 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global 2023-04-28 05:57:41,743 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/lldp_global.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global 2023-04-28 05:57:41,744 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces 2023-04-28 05:57:41,744 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces 2023-04-28 05:57:41,744 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces 2023-04-28 05:57:41,744 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans 2023-04-28 05:57:41,744 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans 2023-04-28 05:57:41,745 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/vlans.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans 2023-04-28 05:57:41,745 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts 2023-04-28 05:57:41,745 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts 2023-04-28 05:57:41,745 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/facts.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts 2023-04-28 05:57:41,745 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces 2023-04-28 05:57:41,746 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces 2023-04-28 05:57:41,746 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces 2023-04-28 05:57:41,746 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy 2023-04-28 05:57:41,746 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy 2023-04-28 05:57:41,746 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/base.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy 2023-04-28 05:57:41,747 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global 2023-04-28 05:57:41,747 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global 2023-04-28 05:57:41,747 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/lldp_global.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global 2023-04-28 05:57:41,747 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces 2023-04-28 05:57:41,747 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces 2023-04-28 05:57:41,747 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces 2023-04-28 05:57:41,748 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans 2023-04-28 05:57:41,748 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans 2023-04-28 05:57:41,748 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/vlans.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans 2023-04-28 05:57:41,748 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/utils 2023-04-28 05:57:41,748 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/utils/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/utils 2023-04-28 05:57:41,749 root INFO copying ansible_collections/community/network/plugins/module_utils/network/exos/utils/utils.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/utils 2023-04-28 05:57:41,749 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:41,749 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ftd/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:41,749 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ftd/common.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:41,749 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ftd/configuration.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:41,750 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ftd/device.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:41,750 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ftd/fdm_swagger_client.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:41,750 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ftd/operation.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:41,750 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/icx 2023-04-28 05:57:41,751 root INFO copying ansible_collections/community/network/plugins/module_utils/network/icx/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/icx 2023-04-28 05:57:41,751 root INFO copying ansible_collections/community/network/plugins/module_utils/network/icx/icx.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/icx 2023-04-28 05:57:41,751 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/ingate 2023-04-28 05:57:41,751 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ingate/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ingate 2023-04-28 05:57:41,751 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ingate/common.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ingate 2023-04-28 05:57:41,752 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/ironware 2023-04-28 05:57:41,752 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ironware/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ironware 2023-04-28 05:57:41,752 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ironware/ironware.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ironware 2023-04-28 05:57:41,752 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/netscaler 2023-04-28 05:57:41,752 root INFO copying ansible_collections/community/network/plugins/module_utils/network/netscaler/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/netscaler 2023-04-28 05:57:41,752 root INFO copying ansible_collections/community/network/plugins/module_utils/network/netscaler/netscaler.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/netscaler 2023-04-28 05:57:41,753 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:41,753 root INFO copying ansible_collections/community/network/plugins/module_utils/network/netvisor/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:41,753 root INFO copying ansible_collections/community/network/plugins/module_utils/network/netvisor/netvisor.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:41,753 root INFO copying ansible_collections/community/network/plugins/module_utils/network/netvisor/pn_nvos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:41,753 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/nos 2023-04-28 05:57:41,754 root INFO copying ansible_collections/community/network/plugins/module_utils/network/nos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/nos 2023-04-28 05:57:41,754 root INFO copying ansible_collections/community/network/plugins/module_utils/network/nos/nos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/nos 2023-04-28 05:57:41,754 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/ordnance 2023-04-28 05:57:41,755 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ordnance/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ordnance 2023-04-28 05:57:41,755 root INFO copying ansible_collections/community/network/plugins/module_utils/network/ordnance/ordnance.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/ordnance 2023-04-28 05:57:41,755 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/slxos 2023-04-28 05:57:41,755 root INFO copying ansible_collections/community/network/plugins/module_utils/network/slxos/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/slxos 2023-04-28 05:57:41,755 root INFO copying ansible_collections/community/network/plugins/module_utils/network/slxos/slxos.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/slxos 2023-04-28 05:57:41,756 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/sros 2023-04-28 05:57:41,756 root INFO copying ansible_collections/community/network/plugins/module_utils/network/sros/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/sros 2023-04-28 05:57:41,756 root INFO copying ansible_collections/community/network/plugins/module_utils/network/sros/sros.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/sros 2023-04-28 05:57:41,756 root INFO creating build/lib/ansible_collections/community/network/plugins/module_utils/network/voss 2023-04-28 05:57:41,756 root INFO copying ansible_collections/community/network/plugins/module_utils/network/voss/__init__.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/voss 2023-04-28 05:57:41,756 root INFO copying ansible_collections/community/network/plugins/module_utils/network/voss/voss.py -> build/lib/ansible_collections/community/network/plugins/module_utils/network/voss 2023-04-28 05:57:41,757 root INFO creating build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,757 root INFO copying ansible_collections/community/network/plugins/modules/__init__.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,757 root INFO copying ansible_collections/community/network/plugins/modules/a10_server.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,757 root INFO copying ansible_collections/community/network/plugins/modules/a10_server_axapi3.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,757 root INFO copying ansible_collections/community/network/plugins/modules/a10_service_group.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,758 root INFO copying ansible_collections/community/network/plugins/modules/a10_virtual_server.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,758 root INFO copying ansible_collections/community/network/plugins/modules/aireos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,758 root INFO copying ansible_collections/community/network/plugins/modules/aireos_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,758 root INFO copying ansible_collections/community/network/plugins/modules/apconos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,759 root INFO copying ansible_collections/community/network/plugins/modules/aruba_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,759 root INFO copying ansible_collections/community/network/plugins/modules/aruba_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,759 root INFO copying ansible_collections/community/network/plugins/modules/avi_actiongroupconfig.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,759 root INFO copying ansible_collections/community/network/plugins/modules/avi_alertconfig.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,760 root INFO copying ansible_collections/community/network/plugins/modules/avi_alertemailconfig.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,760 root INFO copying ansible_collections/community/network/plugins/modules/avi_alertscriptconfig.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,760 root INFO copying ansible_collections/community/network/plugins/modules/avi_alertsyslogconfig.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,760 root INFO copying ansible_collections/community/network/plugins/modules/avi_analyticsprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,760 root INFO copying ansible_collections/community/network/plugins/modules/avi_api_session.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,761 root INFO copying ansible_collections/community/network/plugins/modules/avi_api_version.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,761 root INFO copying ansible_collections/community/network/plugins/modules/avi_applicationpersistenceprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,761 root INFO copying ansible_collections/community/network/plugins/modules/avi_applicationprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,761 root INFO copying ansible_collections/community/network/plugins/modules/avi_authprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,762 root INFO copying ansible_collections/community/network/plugins/modules/avi_autoscalelaunchconfig.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,762 root INFO copying ansible_collections/community/network/plugins/modules/avi_backup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,762 root INFO copying ansible_collections/community/network/plugins/modules/avi_backupconfiguration.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,762 root INFO copying ansible_collections/community/network/plugins/modules/avi_certificatemanagementprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,762 root INFO copying ansible_collections/community/network/plugins/modules/avi_cloud.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,763 root INFO copying ansible_collections/community/network/plugins/modules/avi_cloudconnectoruser.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,763 root INFO copying ansible_collections/community/network/plugins/modules/avi_cloudproperties.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,763 root INFO copying ansible_collections/community/network/plugins/modules/avi_cluster.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,763 root INFO copying ansible_collections/community/network/plugins/modules/avi_clusterclouddetails.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,764 root INFO copying ansible_collections/community/network/plugins/modules/avi_controllerproperties.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,764 root INFO copying ansible_collections/community/network/plugins/modules/avi_customipamdnsprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,764 root INFO copying ansible_collections/community/network/plugins/modules/avi_dnspolicy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,764 root INFO copying ansible_collections/community/network/plugins/modules/avi_errorpagebody.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,765 root INFO copying ansible_collections/community/network/plugins/modules/avi_errorpageprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,765 root INFO copying ansible_collections/community/network/plugins/modules/avi_gslb.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,765 root INFO copying ansible_collections/community/network/plugins/modules/avi_gslbgeodbprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,765 root INFO copying ansible_collections/community/network/plugins/modules/avi_gslbservice.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,765 root INFO copying ansible_collections/community/network/plugins/modules/avi_gslbservice_patch_member.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,766 root INFO copying ansible_collections/community/network/plugins/modules/avi_hardwaresecuritymodulegroup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,766 root INFO copying ansible_collections/community/network/plugins/modules/avi_healthmonitor.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,766 root INFO copying ansible_collections/community/network/plugins/modules/avi_httppolicyset.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,766 root INFO copying ansible_collections/community/network/plugins/modules/avi_ipaddrgroup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,767 root INFO copying ansible_collections/community/network/plugins/modules/avi_ipamdnsproviderprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,767 root INFO copying ansible_collections/community/network/plugins/modules/avi_l4policyset.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,767 root INFO copying ansible_collections/community/network/plugins/modules/avi_microservicegroup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,767 root INFO copying ansible_collections/community/network/plugins/modules/avi_network.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,767 root INFO copying ansible_collections/community/network/plugins/modules/avi_networkprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,768 root INFO copying ansible_collections/community/network/plugins/modules/avi_networksecuritypolicy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,768 root INFO copying ansible_collections/community/network/plugins/modules/avi_pkiprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,768 root INFO copying ansible_collections/community/network/plugins/modules/avi_pool.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,768 root INFO copying ansible_collections/community/network/plugins/modules/avi_poolgroup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,769 root INFO copying ansible_collections/community/network/plugins/modules/avi_poolgroupdeploymentpolicy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,769 root INFO copying ansible_collections/community/network/plugins/modules/avi_prioritylabels.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,769 root INFO copying ansible_collections/community/network/plugins/modules/avi_role.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,769 root INFO copying ansible_collections/community/network/plugins/modules/avi_scheduler.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,770 root INFO copying ansible_collections/community/network/plugins/modules/avi_seproperties.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,770 root INFO copying ansible_collections/community/network/plugins/modules/avi_serverautoscalepolicy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,770 root INFO copying ansible_collections/community/network/plugins/modules/avi_serviceengine.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,770 root INFO copying ansible_collections/community/network/plugins/modules/avi_serviceenginegroup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,771 root INFO copying ansible_collections/community/network/plugins/modules/avi_snmptrapprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,771 root INFO copying ansible_collections/community/network/plugins/modules/avi_sslkeyandcertificate.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,771 root INFO copying ansible_collections/community/network/plugins/modules/avi_sslprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,771 root INFO copying ansible_collections/community/network/plugins/modules/avi_stringgroup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,771 root INFO copying ansible_collections/community/network/plugins/modules/avi_systemconfiguration.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,772 root INFO copying ansible_collections/community/network/plugins/modules/avi_tenant.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,772 root INFO copying ansible_collections/community/network/plugins/modules/avi_trafficcloneprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,772 root INFO copying ansible_collections/community/network/plugins/modules/avi_user.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,772 root INFO copying ansible_collections/community/network/plugins/modules/avi_useraccount.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,773 root INFO copying ansible_collections/community/network/plugins/modules/avi_useraccountprofile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,773 root INFO copying ansible_collections/community/network/plugins/modules/avi_virtualservice.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,773 root INFO copying ansible_collections/community/network/plugins/modules/avi_vrfcontext.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,773 root INFO copying ansible_collections/community/network/plugins/modules/avi_vsdatascriptset.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,774 root INFO copying ansible_collections/community/network/plugins/modules/avi_vsvip.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,774 root INFO copying ansible_collections/community/network/plugins/modules/avi_webhook.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,774 root INFO copying ansible_collections/community/network/plugins/modules/bcf_switch.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,774 root INFO copying ansible_collections/community/network/plugins/modules/bigmon_chain.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,774 root INFO copying ansible_collections/community/network/plugins/modules/bigmon_policy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,775 root INFO copying ansible_collections/community/network/plugins/modules/ce_aaa_server.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,775 root INFO copying ansible_collections/community/network/plugins/modules/ce_aaa_server_host.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,775 root INFO copying ansible_collections/community/network/plugins/modules/ce_acl.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,776 root INFO copying ansible_collections/community/network/plugins/modules/ce_acl_advance.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,776 root INFO copying ansible_collections/community/network/plugins/modules/ce_acl_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,776 root INFO copying ansible_collections/community/network/plugins/modules/ce_bfd_global.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,776 root INFO copying ansible_collections/community/network/plugins/modules/ce_bfd_session.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,777 root INFO copying ansible_collections/community/network/plugins/modules/ce_bfd_view.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,777 root INFO copying ansible_collections/community/network/plugins/modules/ce_bgp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,777 root INFO copying ansible_collections/community/network/plugins/modules/ce_bgp_af.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,778 root INFO copying ansible_collections/community/network/plugins/modules/ce_bgp_neighbor.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,778 root INFO copying ansible_collections/community/network/plugins/modules/ce_bgp_neighbor_af.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,778 root INFO copying ansible_collections/community/network/plugins/modules/ce_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,779 root INFO copying ansible_collections/community/network/plugins/modules/ce_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,779 root INFO copying ansible_collections/community/network/plugins/modules/ce_dldp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,779 root INFO copying ansible_collections/community/network/plugins/modules/ce_dldp_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,779 root INFO copying ansible_collections/community/network/plugins/modules/ce_eth_trunk.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,780 root INFO copying ansible_collections/community/network/plugins/modules/ce_evpn_bd_vni.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,780 root INFO copying ansible_collections/community/network/plugins/modules/ce_evpn_bgp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,780 root INFO copying ansible_collections/community/network/plugins/modules/ce_evpn_bgp_rr.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,781 root INFO copying ansible_collections/community/network/plugins/modules/ce_evpn_global.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,781 root INFO copying ansible_collections/community/network/plugins/modules/ce_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,781 root INFO copying ansible_collections/community/network/plugins/modules/ce_file_copy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,781 root INFO copying ansible_collections/community/network/plugins/modules/ce_info_center_debug.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,782 root INFO copying ansible_collections/community/network/plugins/modules/ce_info_center_global.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,782 root INFO copying ansible_collections/community/network/plugins/modules/ce_info_center_log.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,782 root INFO copying ansible_collections/community/network/plugins/modules/ce_info_center_trap.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,782 root INFO copying ansible_collections/community/network/plugins/modules/ce_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,783 root INFO copying ansible_collections/community/network/plugins/modules/ce_interface_ospf.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,783 root INFO copying ansible_collections/community/network/plugins/modules/ce_ip_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,783 root INFO copying ansible_collections/community/network/plugins/modules/ce_is_is_instance.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,783 root INFO copying ansible_collections/community/network/plugins/modules/ce_is_is_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,784 root INFO copying ansible_collections/community/network/plugins/modules/ce_is_is_view.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,784 root INFO copying ansible_collections/community/network/plugins/modules/ce_lacp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,784 root INFO copying ansible_collections/community/network/plugins/modules/ce_link_status.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,784 root INFO copying ansible_collections/community/network/plugins/modules/ce_lldp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,785 root INFO copying ansible_collections/community/network/plugins/modules/ce_lldp_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,785 root INFO copying ansible_collections/community/network/plugins/modules/ce_mdn_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,785 root INFO copying ansible_collections/community/network/plugins/modules/ce_mlag_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,786 root INFO copying ansible_collections/community/network/plugins/modules/ce_mlag_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,786 root INFO copying ansible_collections/community/network/plugins/modules/ce_mtu.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,786 root INFO copying ansible_collections/community/network/plugins/modules/ce_multicast_global.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,786 root INFO copying ansible_collections/community/network/plugins/modules/ce_multicast_igmp_enable.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,787 root INFO copying ansible_collections/community/network/plugins/modules/ce_netconf.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,787 root INFO copying ansible_collections/community/network/plugins/modules/ce_netstream_aging.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,787 root INFO copying ansible_collections/community/network/plugins/modules/ce_netstream_export.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,787 root INFO copying ansible_collections/community/network/plugins/modules/ce_netstream_global.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,788 root INFO copying ansible_collections/community/network/plugins/modules/ce_netstream_template.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,788 root INFO copying ansible_collections/community/network/plugins/modules/ce_ntp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,788 root INFO copying ansible_collections/community/network/plugins/modules/ce_ntp_auth.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,788 root INFO copying ansible_collections/community/network/plugins/modules/ce_ospf.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,789 root INFO copying ansible_collections/community/network/plugins/modules/ce_ospf_vrf.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,789 root INFO copying ansible_collections/community/network/plugins/modules/ce_reboot.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,789 root INFO copying ansible_collections/community/network/plugins/modules/ce_rollback.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,789 root INFO copying ansible_collections/community/network/plugins/modules/ce_sflow.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,790 root INFO copying ansible_collections/community/network/plugins/modules/ce_snmp_community.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,790 root INFO copying ansible_collections/community/network/plugins/modules/ce_snmp_contact.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,790 root INFO copying ansible_collections/community/network/plugins/modules/ce_snmp_location.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,791 root INFO copying ansible_collections/community/network/plugins/modules/ce_snmp_target_host.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,791 root INFO copying ansible_collections/community/network/plugins/modules/ce_snmp_traps.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,791 root INFO copying ansible_collections/community/network/plugins/modules/ce_snmp_user.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,791 root INFO copying ansible_collections/community/network/plugins/modules/ce_startup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,792 root INFO copying ansible_collections/community/network/plugins/modules/ce_static_route.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,792 root INFO copying ansible_collections/community/network/plugins/modules/ce_static_route_bfd.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,792 root INFO copying ansible_collections/community/network/plugins/modules/ce_stp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,792 root INFO copying ansible_collections/community/network/plugins/modules/ce_switchport.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,793 root INFO copying ansible_collections/community/network/plugins/modules/ce_vlan.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,793 root INFO copying ansible_collections/community/network/plugins/modules/ce_vrf.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,793 root INFO copying ansible_collections/community/network/plugins/modules/ce_vrf_af.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,794 root INFO copying ansible_collections/community/network/plugins/modules/ce_vrf_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,794 root INFO copying ansible_collections/community/network/plugins/modules/ce_vrrp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,794 root INFO copying ansible_collections/community/network/plugins/modules/ce_vxlan_arp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,794 root INFO copying ansible_collections/community/network/plugins/modules/ce_vxlan_gateway.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,795 root INFO copying ansible_collections/community/network/plugins/modules/ce_vxlan_global.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,795 root INFO copying ansible_collections/community/network/plugins/modules/ce_vxlan_tunnel.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,795 root INFO copying ansible_collections/community/network/plugins/modules/ce_vxlan_vap.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,795 root INFO copying ansible_collections/community/network/plugins/modules/cnos_backup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,796 root INFO copying ansible_collections/community/network/plugins/modules/cnos_banner.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,796 root INFO copying ansible_collections/community/network/plugins/modules/cnos_bgp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,796 root INFO copying ansible_collections/community/network/plugins/modules/cnos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,796 root INFO copying ansible_collections/community/network/plugins/modules/cnos_conditional_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,797 root INFO copying ansible_collections/community/network/plugins/modules/cnos_conditional_template.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,797 root INFO copying ansible_collections/community/network/plugins/modules/cnos_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,797 root INFO copying ansible_collections/community/network/plugins/modules/cnos_factory.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,797 root INFO copying ansible_collections/community/network/plugins/modules/cnos_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,798 root INFO copying ansible_collections/community/network/plugins/modules/cnos_image.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,798 root INFO copying ansible_collections/community/network/plugins/modules/cnos_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,798 root INFO copying ansible_collections/community/network/plugins/modules/cnos_l2_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,798 root INFO copying ansible_collections/community/network/plugins/modules/cnos_l3_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,799 root INFO copying ansible_collections/community/network/plugins/modules/cnos_linkagg.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,799 root INFO copying ansible_collections/community/network/plugins/modules/cnos_lldp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,799 root INFO copying ansible_collections/community/network/plugins/modules/cnos_logging.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,799 root INFO copying ansible_collections/community/network/plugins/modules/cnos_reload.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,800 root INFO copying ansible_collections/community/network/plugins/modules/cnos_rollback.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,800 root INFO copying ansible_collections/community/network/plugins/modules/cnos_save.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,800 root INFO copying ansible_collections/community/network/plugins/modules/cnos_showrun.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,800 root INFO copying ansible_collections/community/network/plugins/modules/cnos_static_route.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,800 root INFO copying ansible_collections/community/network/plugins/modules/cnos_system.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,801 root INFO copying ansible_collections/community/network/plugins/modules/cnos_template.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,801 root INFO copying ansible_collections/community/network/plugins/modules/cnos_user.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,801 root INFO copying ansible_collections/community/network/plugins/modules/cnos_vlag.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,801 root INFO copying ansible_collections/community/network/plugins/modules/cnos_vlan.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,802 root INFO copying ansible_collections/community/network/plugins/modules/cnos_vrf.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,802 root INFO copying ansible_collections/community/network/plugins/modules/cv_server_provision.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,802 root INFO copying ansible_collections/community/network/plugins/modules/dladm_etherstub.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,802 root INFO copying ansible_collections/community/network/plugins/modules/dladm_iptun.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,803 root INFO copying ansible_collections/community/network/plugins/modules/dladm_linkprop.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,803 root INFO copying ansible_collections/community/network/plugins/modules/dladm_vlan.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,803 root INFO copying ansible_collections/community/network/plugins/modules/dladm_vnic.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,803 root INFO copying ansible_collections/community/network/plugins/modules/edgeos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,804 root INFO copying ansible_collections/community/network/plugins/modules/edgeos_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,804 root INFO copying ansible_collections/community/network/plugins/modules/edgeos_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,804 root INFO copying ansible_collections/community/network/plugins/modules/edgeswitch_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,804 root INFO copying ansible_collections/community/network/plugins/modules/edgeswitch_vlan.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,804 root INFO copying ansible_collections/community/network/plugins/modules/enos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,805 root INFO copying ansible_collections/community/network/plugins/modules/enos_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,805 root INFO copying ansible_collections/community/network/plugins/modules/enos_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,805 root INFO copying ansible_collections/community/network/plugins/modules/eric_eccli_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,805 root INFO copying ansible_collections/community/network/plugins/modules/exos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,806 root INFO copying ansible_collections/community/network/plugins/modules/exos_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,806 root INFO copying ansible_collections/community/network/plugins/modules/exos_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,806 root INFO copying ansible_collections/community/network/plugins/modules/exos_l2_interfaces.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,806 root INFO copying ansible_collections/community/network/plugins/modules/exos_lldp_global.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,807 root INFO copying ansible_collections/community/network/plugins/modules/exos_lldp_interfaces.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,807 root INFO copying ansible_collections/community/network/plugins/modules/exos_vlans.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,807 root INFO copying ansible_collections/community/network/plugins/modules/flowadm.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,807 root INFO copying ansible_collections/community/network/plugins/modules/ftd_configuration.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,808 root INFO copying ansible_collections/community/network/plugins/modules/ftd_file_download.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,808 root INFO copying ansible_collections/community/network/plugins/modules/ftd_file_upload.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,808 root INFO copying ansible_collections/community/network/plugins/modules/ftd_install.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,808 root INFO copying ansible_collections/community/network/plugins/modules/iap_start_workflow.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,809 root INFO copying ansible_collections/community/network/plugins/modules/iap_token.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,809 root INFO copying ansible_collections/community/network/plugins/modules/icx_banner.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,809 root INFO copying ansible_collections/community/network/plugins/modules/icx_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,809 root INFO copying ansible_collections/community/network/plugins/modules/icx_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,810 root INFO copying ansible_collections/community/network/plugins/modules/icx_copy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,810 root INFO copying ansible_collections/community/network/plugins/modules/icx_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,810 root INFO copying ansible_collections/community/network/plugins/modules/icx_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,810 root INFO copying ansible_collections/community/network/plugins/modules/icx_l3_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,811 root INFO copying ansible_collections/community/network/plugins/modules/icx_linkagg.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,811 root INFO copying ansible_collections/community/network/plugins/modules/icx_lldp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,811 root INFO copying ansible_collections/community/network/plugins/modules/icx_logging.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,811 root INFO copying ansible_collections/community/network/plugins/modules/icx_ping.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,811 root INFO copying ansible_collections/community/network/plugins/modules/icx_static_route.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,812 root INFO copying ansible_collections/community/network/plugins/modules/icx_system.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,812 root INFO copying ansible_collections/community/network/plugins/modules/icx_user.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,812 root INFO copying ansible_collections/community/network/plugins/modules/icx_vlan.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,812 root INFO copying ansible_collections/community/network/plugins/modules/ig_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,813 root INFO copying ansible_collections/community/network/plugins/modules/ig_unit_information.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,813 root INFO copying ansible_collections/community/network/plugins/modules/ipadm_addr.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,813 root INFO copying ansible_collections/community/network/plugins/modules/ipadm_addrprop.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,813 root INFO copying ansible_collections/community/network/plugins/modules/ipadm_if.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,814 root INFO copying ansible_collections/community/network/plugins/modules/ipadm_ifprop.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,814 root INFO copying ansible_collections/community/network/plugins/modules/ipadm_prop.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,814 root INFO copying ansible_collections/community/network/plugins/modules/ironware_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,814 root INFO copying ansible_collections/community/network/plugins/modules/ironware_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,815 root INFO copying ansible_collections/community/network/plugins/modules/ironware_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,815 root INFO copying ansible_collections/community/network/plugins/modules/nclu.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,815 root INFO copying ansible_collections/community/network/plugins/modules/netact_cm_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,815 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_cs_action.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,816 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_cs_policy.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,816 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_cs_vserver.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,816 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_gslb_service.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,816 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_gslb_site.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,817 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_gslb_vserver.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,817 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_lb_monitor.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,817 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_lb_vserver.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,817 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_nitro_request.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,818 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_save_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,818 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_server.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,818 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_service.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,818 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_servicegroup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,819 root INFO copying ansible_collections/community/network/plugins/modules/netscaler_ssl_certkey.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,819 root INFO copying ansible_collections/community/network/plugins/modules/nos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,819 root INFO copying ansible_collections/community/network/plugins/modules/nos_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,819 root INFO copying ansible_collections/community/network/plugins/modules/nos_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,820 root INFO copying ansible_collections/community/network/plugins/modules/nuage_vspk.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,820 root INFO copying ansible_collections/community/network/plugins/modules/opx_cps.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,820 root INFO copying ansible_collections/community/network/plugins/modules/ordnance_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,820 root INFO copying ansible_collections/community/network/plugins/modules/ordnance_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,821 root INFO copying ansible_collections/community/network/plugins/modules/pn_access_list.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,821 root INFO copying ansible_collections/community/network/plugins/modules/pn_access_list_ip.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,821 root INFO copying ansible_collections/community/network/plugins/modules/pn_admin_service.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,821 root INFO copying ansible_collections/community/network/plugins/modules/pn_admin_session_timeout.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,822 root INFO copying ansible_collections/community/network/plugins/modules/pn_admin_syslog.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,822 root INFO copying ansible_collections/community/network/plugins/modules/pn_connection_stats_settings.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,822 root INFO copying ansible_collections/community/network/plugins/modules/pn_cpu_class.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,822 root INFO copying ansible_collections/community/network/plugins/modules/pn_cpu_mgmt_class.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,823 root INFO copying ansible_collections/community/network/plugins/modules/pn_dhcp_filter.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,823 root INFO copying ansible_collections/community/network/plugins/modules/pn_dscp_map.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,823 root INFO copying ansible_collections/community/network/plugins/modules/pn_dscp_map_pri_map.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,823 root INFO copying ansible_collections/community/network/plugins/modules/pn_fabric_local.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,823 root INFO copying ansible_collections/community/network/plugins/modules/pn_igmp_snooping.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,824 root INFO copying ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,824 root INFO copying ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard_port.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,824 root INFO copying ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard_vlan.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,824 root INFO copying ansible_collections/community/network/plugins/modules/pn_log_audit_exception.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,825 root INFO copying ansible_collections/community/network/plugins/modules/pn_port_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,825 root INFO copying ansible_collections/community/network/plugins/modules/pn_port_cos_bw.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,825 root INFO copying ansible_collections/community/network/plugins/modules/pn_port_cos_rate_setting.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,825 root INFO copying ansible_collections/community/network/plugins/modules/pn_prefix_list.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,826 root INFO copying ansible_collections/community/network/plugins/modules/pn_prefix_list_network.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,826 root INFO copying ansible_collections/community/network/plugins/modules/pn_role.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,826 root INFO copying ansible_collections/community/network/plugins/modules/pn_snmp_community.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,826 root INFO copying ansible_collections/community/network/plugins/modules/pn_snmp_trap_sink.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,827 root INFO copying ansible_collections/community/network/plugins/modules/pn_snmp_vacm.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,827 root INFO copying ansible_collections/community/network/plugins/modules/pn_stp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,827 root INFO copying ansible_collections/community/network/plugins/modules/pn_stp_port.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,827 root INFO copying ansible_collections/community/network/plugins/modules/pn_switch_setup.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,827 root INFO copying ansible_collections/community/network/plugins/modules/pn_user.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,828 root INFO copying ansible_collections/community/network/plugins/modules/pn_vflow_table_profile.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,828 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_bgp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,828 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_bgp_network.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,828 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_interface_ip.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,829 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_loopback_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,829 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_ospf.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,829 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_ospf6.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,829 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_packet_relay.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,830 root INFO copying ansible_collections/community/network/plugins/modules/pn_vrouter_pim_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,830 root INFO copying ansible_collections/community/network/plugins/modules/pn_vtep.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,830 root INFO copying ansible_collections/community/network/plugins/modules/slxos_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,830 root INFO copying ansible_collections/community/network/plugins/modules/slxos_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,831 root INFO copying ansible_collections/community/network/plugins/modules/slxos_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,831 root INFO copying ansible_collections/community/network/plugins/modules/slxos_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,831 root INFO copying ansible_collections/community/network/plugins/modules/slxos_l2_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,831 root INFO copying ansible_collections/community/network/plugins/modules/slxos_l3_interface.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,832 root INFO copying ansible_collections/community/network/plugins/modules/slxos_linkagg.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,832 root INFO copying ansible_collections/community/network/plugins/modules/slxos_lldp.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,832 root INFO copying ansible_collections/community/network/plugins/modules/slxos_vlan.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,832 root INFO copying ansible_collections/community/network/plugins/modules/sros_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,833 root INFO copying ansible_collections/community/network/plugins/modules/sros_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,833 root INFO copying ansible_collections/community/network/plugins/modules/sros_rollback.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,833 root INFO copying ansible_collections/community/network/plugins/modules/vdirect_commit.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,833 root INFO copying ansible_collections/community/network/plugins/modules/vdirect_file.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,834 root INFO copying ansible_collections/community/network/plugins/modules/vdirect_runnable.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,834 root INFO copying ansible_collections/community/network/plugins/modules/voss_command.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,834 root INFO copying ansible_collections/community/network/plugins/modules/voss_config.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,834 root INFO copying ansible_collections/community/network/plugins/modules/voss_facts.py -> build/lib/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:41,835 root INFO creating build/lib/ansible_collections/community/network/plugins/netconf 2023-04-28 05:57:41,835 root INFO copying ansible_collections/community/network/plugins/netconf/__init__.py -> build/lib/ansible_collections/community/network/plugins/netconf 2023-04-28 05:57:41,835 root INFO copying ansible_collections/community/network/plugins/netconf/ce.py -> build/lib/ansible_collections/community/network/plugins/netconf 2023-04-28 05:57:41,835 root INFO creating build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,835 root INFO copying ansible_collections/community/network/plugins/terminal/__init__.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,835 root INFO copying ansible_collections/community/network/plugins/terminal/aireos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,836 root INFO copying ansible_collections/community/network/plugins/terminal/apconos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,836 root INFO copying ansible_collections/community/network/plugins/terminal/aruba.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,836 root INFO copying ansible_collections/community/network/plugins/terminal/ce.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,836 root INFO copying ansible_collections/community/network/plugins/terminal/cnos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,837 root INFO copying ansible_collections/community/network/plugins/terminal/edgeos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,837 root INFO copying ansible_collections/community/network/plugins/terminal/edgeswitch.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,837 root INFO copying ansible_collections/community/network/plugins/terminal/enos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,837 root INFO copying ansible_collections/community/network/plugins/terminal/eric_eccli.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,837 root INFO copying ansible_collections/community/network/plugins/terminal/exos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,838 root INFO copying ansible_collections/community/network/plugins/terminal/icx.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,838 root INFO copying ansible_collections/community/network/plugins/terminal/ironware.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,838 root INFO copying ansible_collections/community/network/plugins/terminal/netvisor.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,838 root INFO copying ansible_collections/community/network/plugins/terminal/nos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,839 root INFO copying ansible_collections/community/network/plugins/terminal/slxos.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,839 root INFO copying ansible_collections/community/network/plugins/terminal/sros.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,839 root INFO copying ansible_collections/community/network/plugins/terminal/voss.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,839 root INFO copying ansible_collections/community/network/plugins/terminal/weos4.py -> build/lib/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:41,839 root INFO creating build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,840 root INFO copying ansible_collections/community/okd/CHANGELOG.rst -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,840 root INFO copying ansible_collections/community/okd/CONTRIBUTING.md -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,840 root INFO copying ansible_collections/community/okd/FILES.json -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,840 root INFO copying ansible_collections/community/okd/LICENSE -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,841 root INFO copying ansible_collections/community/okd/MANIFEST.json -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,841 root INFO copying ansible_collections/community/okd/Makefile -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,841 root INFO copying ansible_collections/community/okd/OWNERS -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,841 root INFO copying ansible_collections/community/okd/OWNERS_ALIASES -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,841 root INFO copying ansible_collections/community/okd/README.md -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,842 root INFO copying ansible_collections/community/okd/codecov.yml -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,842 root INFO copying ansible_collections/community/okd/requirements.txt -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,842 root INFO copying ansible_collections/community/okd/requirements.yml -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,842 root INFO copying ansible_collections/community/okd/setup.cfg -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,843 root INFO copying ansible_collections/community/okd/test-requirements.txt -> build/lib/ansible_collections/community/okd 2023-04-28 05:57:41,843 root INFO creating build/lib/ansible_collections/community/okd/changelogs 2023-04-28 05:57:41,843 root INFO copying ansible_collections/community/okd/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/community/okd/changelogs 2023-04-28 05:57:41,843 root INFO copying ansible_collections/community/okd/changelogs/changelog.yaml -> build/lib/ansible_collections/community/okd/changelogs 2023-04-28 05:57:41,843 root INFO copying ansible_collections/community/okd/changelogs/config.yaml -> build/lib/ansible_collections/community/okd/changelogs 2023-04-28 05:57:41,844 root INFO creating build/lib/ansible_collections/community/okd/ci 2023-04-28 05:57:41,844 root INFO copying ansible_collections/community/okd/ci/Dockerfile -> build/lib/ansible_collections/community/okd/ci 2023-04-28 05:57:41,844 root INFO copying ansible_collections/community/okd/ci/doc_fragment_modules.py -> build/lib/ansible_collections/community/okd/ci 2023-04-28 05:57:41,844 root INFO copying ansible_collections/community/okd/ci/downstream.sh -> build/lib/ansible_collections/community/okd/ci 2023-04-28 05:57:41,844 root INFO copying ansible_collections/community/okd/ci/downstream_fragments.py -> build/lib/ansible_collections/community/okd/ci 2023-04-28 05:57:41,845 root INFO copying ansible_collections/community/okd/ci/incluster_integration.sh -> build/lib/ansible_collections/community/okd/ci 2023-04-28 05:57:41,845 root INFO creating build/lib/ansible_collections/community/okd/meta 2023-04-28 05:57:41,845 root INFO copying ansible_collections/community/okd/meta/runtime.yml -> build/lib/ansible_collections/community/okd/meta 2023-04-28 05:57:41,845 root INFO creating build/lib/ansible_collections/community/okd/molecule 2023-04-28 05:57:41,845 root INFO creating build/lib/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:41,845 root INFO copying ansible_collections/community/okd/molecule/default/README.md -> build/lib/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:41,846 root INFO copying ansible_collections/community/okd/molecule/default/converge.yml -> build/lib/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:41,846 root INFO copying ansible_collections/community/okd/molecule/default/destroy.yml -> build/lib/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:41,846 root INFO copying ansible_collections/community/okd/molecule/default/molecule.yml -> build/lib/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:41,846 root INFO copying ansible_collections/community/okd/molecule/default/prepare.yml -> build/lib/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:41,846 root INFO copying ansible_collections/community/okd/molecule/default/verify.yml -> build/lib/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:41,847 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,847 root INFO copying ansible_collections/community/okd/molecule/default/files/crd-resource.yml -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,847 root INFO copying ansible_collections/community/okd/molecule/default/files/example.env -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,847 root INFO copying ansible_collections/community/okd/molecule/default/files/kuard-extra-property.yml -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,847 root INFO copying ansible_collections/community/okd/molecule/default/files/kuard-invalid-type.yml -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,848 root INFO copying ansible_collections/community/okd/molecule/default/files/nginx.env -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,848 root INFO copying ansible_collections/community/okd/molecule/default/files/pod-template.yaml -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,848 root INFO copying ansible_collections/community/okd/molecule/default/files/setup-crd.yml -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,848 root INFO copying ansible_collections/community/okd/molecule/default/files/simple-template.yaml -> build/lib/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:41,849 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles 2023-04-28 05:57:41,849 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups 2023-04-28 05:57:41,849 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/defaults 2023-04-28 05:57:41,849 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/defaults/main.yml -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/defaults 2023-04-28 05:57:41,849 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library 2023-04-28 05:57:41,849 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/openshift_ldap_entry.py -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library 2023-04-28 05:57:41,850 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/openshift_ldap_entry_info.py -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library 2023-04-28 05:57:41,850 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/meta 2023-04-28 05:57:41,850 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/meta/main.yml -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/meta 2023-04-28 05:57:41,850 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:41,850 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/activeDirectory.yml -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:41,850 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/augmentedActiveDirectory.yml -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:41,851 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/main.yml -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:41,851 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/python-ldap-not-installed.yml -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:41,851 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/rfc2307.yml -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:41,851 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates 2023-04-28 05:57:41,851 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad 2023-04-28 05:57:41,852 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad/definition.j2 -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad 2023-04-28 05:57:41,852 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad/sync-config.j2 -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad 2023-04-28 05:57:41,852 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad 2023-04-28 05:57:41,852 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad/definition.j2 -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad 2023-04-28 05:57:41,852 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad/sync-config.j2 -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad 2023-04-28 05:57:41,853 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307 2023-04-28 05:57:41,853 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307/definition.j2 -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307 2023-04-28 05:57:41,853 root INFO copying ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307/sync-config.j2 -> build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307 2023-04-28 05:57:41,853 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,853 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_auth_clusterroles.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,854 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_auth_roles.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,854 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_deployments.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,854 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_auth.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,854 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_builds.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,855 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_import_images.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,855 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_process.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,855 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_prune_images.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,855 root INFO copying ansible_collections/community/okd/molecule/default/tasks/openshift_route.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,855 root INFO copying ansible_collections/community/okd/molecule/default/tasks/validate_installed.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,856 root INFO copying ansible_collections/community/okd/molecule/default/tasks/validate_not_installed.yml -> build/lib/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:41,856 root INFO creating build/lib/ansible_collections/community/okd/molecule/default/vars 2023-04-28 05:57:41,856 root INFO copying ansible_collections/community/okd/molecule/default/vars/main.yml -> build/lib/ansible_collections/community/okd/molecule/default/vars 2023-04-28 05:57:41,856 root INFO creating build/lib/ansible_collections/community/okd/plugins 2023-04-28 05:57:41,856 root INFO creating build/lib/ansible_collections/community/okd/plugins/connection 2023-04-28 05:57:41,856 root INFO copying ansible_collections/community/okd/plugins/connection/oc.py -> build/lib/ansible_collections/community/okd/plugins/connection 2023-04-28 05:57:41,857 root INFO creating build/lib/ansible_collections/community/okd/plugins/inventory 2023-04-28 05:57:41,857 root INFO copying ansible_collections/community/okd/plugins/inventory/openshift.py -> build/lib/ansible_collections/community/okd/plugins/inventory 2023-04-28 05:57:41,857 root INFO creating build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,857 root INFO copying ansible_collections/community/okd/plugins/module_utils/k8s.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,857 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_auth.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,858 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_deployments.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,858 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_images.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,858 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_builds.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,858 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_common.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,859 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_docker_image.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,859 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_groups.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,859 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_images_common.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,859 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_import_image.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,860 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_ldap.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,860 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_process.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,860 root INFO copying ansible_collections/community/okd/plugins/module_utils/openshift_registry.py -> build/lib/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:41,860 root INFO creating build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,860 root INFO copying ansible_collections/community/okd/plugins/modules/k8s.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,861 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_adm_groups_sync.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,861 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_adm_migrate_template_instances.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,861 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_adm_prune_auth.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,861 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_adm_prune_builds.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,862 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_adm_prune_deployments.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,862 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_adm_prune_images.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,862 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_auth.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,862 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_build.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,862 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_import_image.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,863 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_process.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,863 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_registry_info.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,863 root INFO copying ansible_collections/community/okd/plugins/modules/openshift_route.py -> build/lib/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:41,863 root INFO creating build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,864 root INFO copying ansible_collections/community/postgresql/CHANGELOG.rst -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,864 root INFO copying ansible_collections/community/postgresql/CONTRIBUTING.md -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,864 root INFO copying ansible_collections/community/postgresql/CONTRIBUTORS -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,864 root INFO copying ansible_collections/community/postgresql/COPYING -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,864 root INFO copying ansible_collections/community/postgresql/FILES.json -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,865 root INFO copying ansible_collections/community/postgresql/MAINTAINERS -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,865 root INFO copying ansible_collections/community/postgresql/MAINTAINING.md -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,865 root INFO copying ansible_collections/community/postgresql/MANIFEST.json -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,865 root INFO copying ansible_collections/community/postgresql/PSF-license.txt -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,866 root INFO copying ansible_collections/community/postgresql/README.md -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,866 root INFO copying ansible_collections/community/postgresql/requirements.txt -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,866 root INFO copying ansible_collections/community/postgresql/shippable.yml -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,866 root INFO copying ansible_collections/community/postgresql/simplified_bsd.txt -> build/lib/ansible_collections/community/postgresql 2023-04-28 05:57:41,867 root INFO creating build/lib/ansible_collections/community/postgresql/changelogs 2023-04-28 05:57:41,867 root INFO copying ansible_collections/community/postgresql/changelogs/changelog.yaml -> build/lib/ansible_collections/community/postgresql/changelogs 2023-04-28 05:57:41,867 root INFO copying ansible_collections/community/postgresql/changelogs/config.yaml -> build/lib/ansible_collections/community/postgresql/changelogs 2023-04-28 05:57:41,867 root INFO creating build/lib/ansible_collections/community/postgresql/changelogs/fragments 2023-04-28 05:57:41,867 root INFO copying ansible_collections/community/postgresql/changelogs/fragments/.keep -> build/lib/ansible_collections/community/postgresql/changelogs/fragments 2023-04-28 05:57:41,868 root INFO creating build/lib/ansible_collections/community/postgresql/meta 2023-04-28 05:57:41,868 root INFO copying ansible_collections/community/postgresql/meta/runtime.yml -> build/lib/ansible_collections/community/postgresql/meta 2023-04-28 05:57:41,868 root INFO creating build/lib/ansible_collections/community/postgresql/plugins 2023-04-28 05:57:41,868 root INFO creating build/lib/ansible_collections/community/postgresql/plugins/doc_fragments 2023-04-28 05:57:41,868 root INFO copying ansible_collections/community/postgresql/plugins/doc_fragments/postgres.py -> build/lib/ansible_collections/community/postgresql/plugins/doc_fragments 2023-04-28 05:57:41,868 root INFO creating build/lib/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:41,868 root INFO copying ansible_collections/community/postgresql/plugins/module_utils/_version.py -> build/lib/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:41,869 root INFO copying ansible_collections/community/postgresql/plugins/module_utils/database.py -> build/lib/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:41,869 root INFO copying ansible_collections/community/postgresql/plugins/module_utils/postgres.py -> build/lib/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:41,869 root INFO copying ansible_collections/community/postgresql/plugins/module_utils/saslprep.py -> build/lib/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:41,869 root INFO copying ansible_collections/community/postgresql/plugins/module_utils/version.py -> build/lib/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:41,870 root INFO creating build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,870 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_copy.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,870 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_db.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,870 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_ext.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,871 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_idx.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,871 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_info.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,871 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_lang.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,871 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_membership.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,872 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_owner.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,872 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_pg_hba.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,872 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_ping.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,872 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_privs.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,873 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_publication.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,873 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_query.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,873 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_schema.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,873 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_script.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,873 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_sequence.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,874 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_set.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,874 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_slot.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,874 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_subscription.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,874 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_table.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,875 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_tablespace.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,875 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_user.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,875 root INFO copying ansible_collections/community/postgresql/plugins/modules/postgresql_user_obj_stat_info.py -> build/lib/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:41,875 root INFO creating build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,876 root INFO copying ansible_collections/community/proxysql/CHANGELOG.rst -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,876 root INFO copying ansible_collections/community/proxysql/CONTRIBUTING.md -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,876 root INFO copying ansible_collections/community/proxysql/CONTRIBUTORS -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,876 root INFO copying ansible_collections/community/proxysql/FILES.json -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,877 root INFO copying ansible_collections/community/proxysql/LICENSE -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,877 root INFO copying ansible_collections/community/proxysql/MAINTAINERS -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,877 root INFO copying ansible_collections/community/proxysql/MAINTAINING.md -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,877 root INFO copying ansible_collections/community/proxysql/MANIFEST.json -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,878 root INFO copying ansible_collections/community/proxysql/README.md -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,878 root INFO copying ansible_collections/community/proxysql/REVIEW_CHECKLIST.md -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,878 root INFO copying ansible_collections/community/proxysql/codecov.yml -> build/lib/ansible_collections/community/proxysql 2023-04-28 05:57:41,878 root INFO creating build/lib/ansible_collections/community/proxysql/changelogs 2023-04-28 05:57:41,878 root INFO copying ansible_collections/community/proxysql/changelogs/changelog.yaml -> build/lib/ansible_collections/community/proxysql/changelogs 2023-04-28 05:57:41,879 root INFO copying ansible_collections/community/proxysql/changelogs/config.yaml -> build/lib/ansible_collections/community/proxysql/changelogs 2023-04-28 05:57:41,879 root INFO creating build/lib/ansible_collections/community/proxysql/meta 2023-04-28 05:57:41,879 root INFO copying ansible_collections/community/proxysql/meta/runtime.yml -> build/lib/ansible_collections/community/proxysql/meta 2023-04-28 05:57:41,879 root INFO creating build/lib/ansible_collections/community/proxysql/plugins 2023-04-28 05:57:41,880 root INFO copying ansible_collections/community/proxysql/plugins/README.md -> build/lib/ansible_collections/community/proxysql/plugins 2023-04-28 05:57:41,880 root INFO creating build/lib/ansible_collections/community/proxysql/plugins/doc_fragments 2023-04-28 05:57:41,880 root INFO copying ansible_collections/community/proxysql/plugins/doc_fragments/proxysql.py -> build/lib/ansible_collections/community/proxysql/plugins/doc_fragments 2023-04-28 05:57:41,880 root INFO creating build/lib/ansible_collections/community/proxysql/plugins/module_utils 2023-04-28 05:57:41,880 root INFO copying ansible_collections/community/proxysql/plugins/module_utils/mysql.py -> build/lib/ansible_collections/community/proxysql/plugins/module_utils 2023-04-28 05:57:41,881 root INFO creating build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,881 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_backend_servers.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,881 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_global_variables.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,881 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_info.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,881 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_manage_config.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,882 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_mysql_users.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,882 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_query_rules.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,882 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_query_rules_fast_routing.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,882 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_replication_hostgroups.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,883 root INFO copying ansible_collections/community/proxysql/plugins/modules/proxysql_scheduler.py -> build/lib/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:41,883 root INFO creating build/lib/ansible_collections/community/proxysql/roles 2023-04-28 05:57:41,883 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql 2023-04-28 05:57:41,883 root INFO copying ansible_collections/community/proxysql/roles/proxysql/.yamllint -> build/lib/ansible_collections/community/proxysql/roles/proxysql 2023-04-28 05:57:41,883 root INFO copying ansible_collections/community/proxysql/roles/proxysql/README.md -> build/lib/ansible_collections/community/proxysql/roles/proxysql 2023-04-28 05:57:41,884 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/defaults 2023-04-28 05:57:41,884 root INFO copying ansible_collections/community/proxysql/roles/proxysql/defaults/main.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/defaults 2023-04-28 05:57:41,884 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/handlers 2023-04-28 05:57:41,884 root INFO copying ansible_collections/community/proxysql/roles/proxysql/handlers/main.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/handlers 2023-04-28 05:57:41,884 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/meta 2023-04-28 05:57:41,884 root INFO copying ansible_collections/community/proxysql/roles/proxysql/meta/main.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/meta 2023-04-28 05:57:41,885 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule 2023-04-28 05:57:41,885 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:41,885 root INFO copying ansible_collections/community/proxysql/roles/proxysql/molecule/default/converge.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:41,885 root INFO copying ansible_collections/community/proxysql/roles/proxysql/molecule/default/molecule.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:41,885 root INFO copying ansible_collections/community/proxysql/roles/proxysql/molecule/default/prepare.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:41,885 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests 2023-04-28 05:57:41,886 root INFO copying ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests/test_default.py -> build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests 2023-04-28 05:57:41,886 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:41,886 root INFO copying ansible_collections/community/proxysql/roles/proxysql/tasks/config.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:41,886 root INFO copying ansible_collections/community/proxysql/roles/proxysql/tasks/install.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:41,886 root INFO copying ansible_collections/community/proxysql/roles/proxysql/tasks/main.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:41,887 root INFO copying ansible_collections/community/proxysql/roles/proxysql/tasks/setvars.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:41,887 root INFO copying ansible_collections/community/proxysql/roles/proxysql/tasks/users.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:41,887 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/templates 2023-04-28 05:57:41,887 root INFO copying ansible_collections/community/proxysql/roles/proxysql/templates/client.my.cnf.j2 -> build/lib/ansible_collections/community/proxysql/roles/proxysql/templates 2023-04-28 05:57:41,887 root INFO copying ansible_collections/community/proxysql/roles/proxysql/templates/proxysql.cnf.j2 -> build/lib/ansible_collections/community/proxysql/roles/proxysql/templates 2023-04-28 05:57:41,888 root INFO creating build/lib/ansible_collections/community/proxysql/roles/proxysql/vars 2023-04-28 05:57:41,888 root INFO copying ansible_collections/community/proxysql/roles/proxysql/vars/main.yml -> build/lib/ansible_collections/community/proxysql/roles/proxysql/vars 2023-04-28 05:57:41,888 root INFO creating build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,888 root INFO copying ansible_collections/community/rabbitmq/CHANGELOG.rst -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,888 root INFO copying ansible_collections/community/rabbitmq/CONTRIBUTING.md -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,889 root INFO copying ansible_collections/community/rabbitmq/COPYING -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,889 root INFO copying ansible_collections/community/rabbitmq/FILES.json -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,889 root INFO copying ansible_collections/community/rabbitmq/MAINTAINERS -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,889 root INFO copying ansible_collections/community/rabbitmq/MAINTAINING.md -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,890 root INFO copying ansible_collections/community/rabbitmq/MANIFEST.json -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,890 root INFO copying ansible_collections/community/rabbitmq/PSF-license.txt -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,890 root INFO copying ansible_collections/community/rabbitmq/README.md -> build/lib/ansible_collections/community/rabbitmq 2023-04-28 05:57:41,890 root INFO creating build/lib/ansible_collections/community/rabbitmq/changelogs 2023-04-28 05:57:41,890 root INFO copying ansible_collections/community/rabbitmq/changelogs/changelog.yaml -> build/lib/ansible_collections/community/rabbitmq/changelogs 2023-04-28 05:57:41,891 root INFO copying ansible_collections/community/rabbitmq/changelogs/config.yaml -> build/lib/ansible_collections/community/rabbitmq/changelogs 2023-04-28 05:57:41,891 root INFO creating build/lib/ansible_collections/community/rabbitmq/meta 2023-04-28 05:57:41,891 root INFO copying ansible_collections/community/rabbitmq/meta/runtime.yml -> build/lib/ansible_collections/community/rabbitmq/meta 2023-04-28 05:57:41,891 root INFO creating build/lib/ansible_collections/community/rabbitmq/plugins 2023-04-28 05:57:41,891 root INFO creating build/lib/ansible_collections/community/rabbitmq/plugins/doc_fragments 2023-04-28 05:57:41,892 root INFO copying ansible_collections/community/rabbitmq/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/rabbitmq/plugins/doc_fragments 2023-04-28 05:57:41,892 root INFO copying ansible_collections/community/rabbitmq/plugins/doc_fragments/rabbitmq.py -> build/lib/ansible_collections/community/rabbitmq/plugins/doc_fragments 2023-04-28 05:57:41,892 root INFO creating build/lib/ansible_collections/community/rabbitmq/plugins/lookup 2023-04-28 05:57:41,892 root INFO copying ansible_collections/community/rabbitmq/plugins/lookup/rabbitmq.py -> build/lib/ansible_collections/community/rabbitmq/plugins/lookup 2023-04-28 05:57:41,892 root INFO creating build/lib/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:41,892 root INFO copying ansible_collections/community/rabbitmq/plugins/module_utils/_version.py -> build/lib/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:41,893 root INFO copying ansible_collections/community/rabbitmq/plugins/module_utils/rabbitmq.py -> build/lib/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:41,893 root INFO copying ansible_collections/community/rabbitmq/plugins/module_utils/version.py -> build/lib/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:41,893 root INFO creating build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,893 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_binding.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,893 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_exchange.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,894 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_feature_flag.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,894 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_global_parameter.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,894 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_parameter.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,894 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_plugin.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,895 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_policy.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,895 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_publish.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,895 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_queue.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,895 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_upgrade.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,895 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_user.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,896 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_user_limits.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,896 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_vhost.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,896 root INFO copying ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_vhost_limits.py -> build/lib/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:41,896 root INFO creating build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,897 root INFO copying ansible_collections/community/routeros/CHANGELOG.rst -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,897 root INFO copying ansible_collections/community/routeros/CHANGELOG.rst.license -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,897 root INFO copying ansible_collections/community/routeros/COPYING -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,897 root INFO copying ansible_collections/community/routeros/FILES.json -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,898 root INFO copying ansible_collections/community/routeros/MANIFEST.json -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,898 root INFO copying ansible_collections/community/routeros/README.md -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,898 root INFO copying ansible_collections/community/routeros/codecov.yml -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,898 root INFO copying ansible_collections/community/routeros/update-docs.py -> build/lib/ansible_collections/community/routeros 2023-04-28 05:57:41,898 root INFO creating build/lib/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:41,899 root INFO copying ansible_collections/community/routeros/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:41,899 root INFO copying ansible_collections/community/routeros/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:41,899 root INFO copying ansible_collections/community/routeros/LICENSES/PSF-2.0.txt -> build/lib/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:41,899 root INFO creating build/lib/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:41,899 root INFO copying ansible_collections/community/routeros/changelogs/changelog.yaml -> build/lib/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:41,900 root INFO copying ansible_collections/community/routeros/changelogs/changelog.yaml.license -> build/lib/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:41,900 root INFO copying ansible_collections/community/routeros/changelogs/config.yaml -> build/lib/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:41,900 root INFO creating build/lib/ansible_collections/community/routeros/changelogs/fragments 2023-04-28 05:57:41,900 root INFO copying ansible_collections/community/routeros/changelogs/fragments/.keep -> build/lib/ansible_collections/community/routeros/changelogs/fragments 2023-04-28 05:57:41,900 root INFO creating build/lib/ansible_collections/community/routeros/meta 2023-04-28 05:57:41,901 root INFO copying ansible_collections/community/routeros/meta/ee-requirements.txt -> build/lib/ansible_collections/community/routeros/meta 2023-04-28 05:57:41,901 root INFO copying ansible_collections/community/routeros/meta/execution-environment.yml -> build/lib/ansible_collections/community/routeros/meta 2023-04-28 05:57:41,901 root INFO copying ansible_collections/community/routeros/meta/runtime.yml -> build/lib/ansible_collections/community/routeros/meta 2023-04-28 05:57:41,901 root INFO creating build/lib/ansible_collections/community/routeros/plugins 2023-04-28 05:57:41,901 root INFO creating build/lib/ansible_collections/community/routeros/plugins/cliconf 2023-04-28 05:57:41,902 root INFO copying ansible_collections/community/routeros/plugins/cliconf/routeros.py -> build/lib/ansible_collections/community/routeros/plugins/cliconf 2023-04-28 05:57:41,902 root INFO creating build/lib/ansible_collections/community/routeros/plugins/doc_fragments 2023-04-28 05:57:41,902 root INFO copying ansible_collections/community/routeros/plugins/doc_fragments/api.py -> build/lib/ansible_collections/community/routeros/plugins/doc_fragments 2023-04-28 05:57:41,902 root INFO copying ansible_collections/community/routeros/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/routeros/plugins/doc_fragments 2023-04-28 05:57:41,902 root INFO creating build/lib/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:41,902 root INFO copying ansible_collections/community/routeros/plugins/filter/join.yml -> build/lib/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:41,903 root INFO copying ansible_collections/community/routeros/plugins/filter/list_to_dict.yml -> build/lib/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:41,903 root INFO copying ansible_collections/community/routeros/plugins/filter/quote_argument.yml -> build/lib/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:41,903 root INFO copying ansible_collections/community/routeros/plugins/filter/quote_argument_value.yml -> build/lib/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:41,903 root INFO copying ansible_collections/community/routeros/plugins/filter/quoting.py -> build/lib/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:41,904 root INFO copying ansible_collections/community/routeros/plugins/filter/split.yml -> build/lib/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:41,904 root INFO creating build/lib/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:41,904 root INFO copying ansible_collections/community/routeros/plugins/module_utils/_api_data.py -> build/lib/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:41,904 root INFO copying ansible_collections/community/routeros/plugins/module_utils/_version.py -> build/lib/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:41,905 root INFO copying ansible_collections/community/routeros/plugins/module_utils/api.py -> build/lib/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:41,905 root INFO copying ansible_collections/community/routeros/plugins/module_utils/quoting.py -> build/lib/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:41,905 root INFO copying ansible_collections/community/routeros/plugins/module_utils/routeros.py -> build/lib/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:41,905 root INFO copying ansible_collections/community/routeros/plugins/module_utils/version.py -> build/lib/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:41,905 root INFO creating build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,906 root INFO copying ansible_collections/community/routeros/plugins/modules/api.py -> build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,906 root INFO copying ansible_collections/community/routeros/plugins/modules/api_facts.py -> build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,906 root INFO copying ansible_collections/community/routeros/plugins/modules/api_find_and_modify.py -> build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,906 root INFO copying ansible_collections/community/routeros/plugins/modules/api_info.py -> build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,906 root INFO copying ansible_collections/community/routeros/plugins/modules/api_modify.py -> build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,907 root INFO copying ansible_collections/community/routeros/plugins/modules/command.py -> build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,907 root INFO copying ansible_collections/community/routeros/plugins/modules/facts.py -> build/lib/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:41,907 root INFO creating build/lib/ansible_collections/community/routeros/plugins/terminal 2023-04-28 05:57:41,907 root INFO copying ansible_collections/community/routeros/plugins/terminal/routeros.py -> build/lib/ansible_collections/community/routeros/plugins/terminal 2023-04-28 05:57:41,908 root INFO creating build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,908 root INFO copying ansible_collections/community/sap/CHANGELOG.rst -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,908 root INFO copying ansible_collections/community/sap/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,908 root INFO copying ansible_collections/community/sap/CONTRIBUTING.md -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,908 root INFO copying ansible_collections/community/sap/FILES.json -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,909 root INFO copying ansible_collections/community/sap/LICENSE -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,909 root INFO copying ansible_collections/community/sap/MAINTAINERS -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,909 root INFO copying ansible_collections/community/sap/MAINTAINING.md -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,909 root INFO copying ansible_collections/community/sap/MANIFEST.json -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,910 root INFO copying ansible_collections/community/sap/README.md -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,910 root INFO copying ansible_collections/community/sap/REVIEW_CHECKLIST.md -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,910 root INFO copying ansible_collections/community/sap/codecov.yml -> build/lib/ansible_collections/community/sap 2023-04-28 05:57:41,910 root INFO creating build/lib/ansible_collections/community/sap/changelogs 2023-04-28 05:57:41,910 root INFO copying ansible_collections/community/sap/changelogs/changelog.yaml -> build/lib/ansible_collections/community/sap/changelogs 2023-04-28 05:57:41,911 root INFO copying ansible_collections/community/sap/changelogs/config.yaml -> build/lib/ansible_collections/community/sap/changelogs 2023-04-28 05:57:41,911 root INFO creating build/lib/ansible_collections/community/sap/changelogs/fragments 2023-04-28 05:57:41,911 root INFO copying ansible_collections/community/sap/changelogs/fragments/.keep -> build/lib/ansible_collections/community/sap/changelogs/fragments 2023-04-28 05:57:41,911 root INFO creating build/lib/ansible_collections/community/sap/meta 2023-04-28 05:57:41,911 root INFO copying ansible_collections/community/sap/meta/runtime.yml -> build/lib/ansible_collections/community/sap/meta 2023-04-28 05:57:41,911 root INFO creating build/lib/ansible_collections/community/sap/plugins 2023-04-28 05:57:41,912 root INFO creating build/lib/ansible_collections/community/sap/plugins/doc_fragments 2023-04-28 05:57:41,912 root INFO copying ansible_collections/community/sap/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/sap/plugins/doc_fragments 2023-04-28 05:57:41,912 root INFO creating build/lib/ansible_collections/community/sap/plugins/module_utils 2023-04-28 05:57:41,912 root INFO copying ansible_collections/community/sap/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/sap/plugins/module_utils 2023-04-28 05:57:41,912 root INFO creating build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,912 root INFO copying ansible_collections/community/sap/plugins/modules/hana_query.py -> build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,913 root INFO copying ansible_collections/community/sap/plugins/modules/sap_company.py -> build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,913 root INFO copying ansible_collections/community/sap/plugins/modules/sap_snote.py -> build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,913 root INFO copying ansible_collections/community/sap/plugins/modules/sap_system_facts.py -> build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,913 root INFO copying ansible_collections/community/sap/plugins/modules/sap_task_list_execute.py -> build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,914 root INFO copying ansible_collections/community/sap/plugins/modules/sap_user.py -> build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,914 root INFO copying ansible_collections/community/sap/plugins/modules/sapcar_extract.py -> build/lib/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:41,914 root INFO creating build/lib/ansible_collections/community/sap/plugins/modules/database 2023-04-28 05:57:41,914 root INFO creating build/lib/ansible_collections/community/sap/plugins/modules/database/saphana 2023-04-28 05:57:41,914 root INFO copying ansible_collections/community/sap/plugins/modules/database/saphana/hana_query.py -> build/lib/ansible_collections/community/sap/plugins/modules/database/saphana 2023-04-28 05:57:41,914 root INFO creating build/lib/ansible_collections/community/sap/plugins/modules/files 2023-04-28 05:57:41,915 root INFO copying ansible_collections/community/sap/plugins/modules/files/sapcar_extract.py -> build/lib/ansible_collections/community/sap/plugins/modules/files 2023-04-28 05:57:41,915 root INFO creating build/lib/ansible_collections/community/sap/plugins/modules/identity 2023-04-28 05:57:41,915 root INFO copying ansible_collections/community/sap/plugins/modules/identity/sap_company.py -> build/lib/ansible_collections/community/sap/plugins/modules/identity 2023-04-28 05:57:41,915 root INFO copying ansible_collections/community/sap/plugins/modules/identity/sap_user.py -> build/lib/ansible_collections/community/sap/plugins/modules/identity 2023-04-28 05:57:41,915 root INFO creating build/lib/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:41,916 root INFO copying ansible_collections/community/sap/plugins/modules/system/sap_snote.py -> build/lib/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:41,916 root INFO copying ansible_collections/community/sap/plugins/modules/system/sap_system_facts.py -> build/lib/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:41,916 root INFO copying ansible_collections/community/sap/plugins/modules/system/sap_task_list_execute.py -> build/lib/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:41,916 root INFO creating build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,916 root INFO copying ansible_collections/community/sap_libs/CHANGELOG.rst -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,917 root INFO copying ansible_collections/community/sap_libs/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,917 root INFO copying ansible_collections/community/sap_libs/CONTRIBUTING.md -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,917 root INFO copying ansible_collections/community/sap_libs/FILES.json -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,917 root INFO copying ansible_collections/community/sap_libs/LICENSE -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,918 root INFO copying ansible_collections/community/sap_libs/MAINTAINERS -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,918 root INFO copying ansible_collections/community/sap_libs/MAINTAINING.md -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,918 root INFO copying ansible_collections/community/sap_libs/MANIFEST.json -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,918 root INFO copying ansible_collections/community/sap_libs/README.md -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,918 root INFO copying ansible_collections/community/sap_libs/REVIEW_CHECKLIST.md -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,919 root INFO copying ansible_collections/community/sap_libs/codecov.yml -> build/lib/ansible_collections/community/sap_libs 2023-04-28 05:57:41,919 root INFO creating build/lib/ansible_collections/community/sap_libs/changelogs 2023-04-28 05:57:41,919 root INFO copying ansible_collections/community/sap_libs/changelogs/changelog.yaml -> build/lib/ansible_collections/community/sap_libs/changelogs 2023-04-28 05:57:41,919 root INFO copying ansible_collections/community/sap_libs/changelogs/config.yaml -> build/lib/ansible_collections/community/sap_libs/changelogs 2023-04-28 05:57:41,919 root INFO creating build/lib/ansible_collections/community/sap_libs/changelogs/fragments 2023-04-28 05:57:41,920 root INFO copying ansible_collections/community/sap_libs/changelogs/fragments/.keep -> build/lib/ansible_collections/community/sap_libs/changelogs/fragments 2023-04-28 05:57:41,920 root INFO creating build/lib/ansible_collections/community/sap_libs/meta 2023-04-28 05:57:41,920 root INFO copying ansible_collections/community/sap_libs/meta/runtime.yml -> build/lib/ansible_collections/community/sap_libs/meta 2023-04-28 05:57:41,920 root INFO creating build/lib/ansible_collections/community/sap_libs/plugins 2023-04-28 05:57:41,920 root INFO creating build/lib/ansible_collections/community/sap_libs/plugins/doc_fragments 2023-04-28 05:57:41,920 root INFO copying ansible_collections/community/sap_libs/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/sap_libs/plugins/doc_fragments 2023-04-28 05:57:41,921 root INFO creating build/lib/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:41,921 root INFO copying ansible_collections/community/sap_libs/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:41,921 root INFO copying ansible_collections/community/sap_libs/plugins/module_utils/pyrfc_handler.py -> build/lib/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:41,921 root INFO copying ansible_collections/community/sap_libs/plugins/module_utils/swpm2_parameters_inifile_generate.py -> build/lib/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:41,921 root INFO creating build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,922 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_company.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,922 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_control_exec.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,922 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_hdbsql.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,922 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_pyrfc.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,922 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_snote.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,923 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_system_facts.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,923 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_task_list_execute.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,923 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sap_user.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,923 root INFO copying ansible_collections/community/sap_libs/plugins/modules/sapcar_extract.py -> build/lib/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:41,924 root INFO creating build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,924 root INFO copying ansible_collections/community/skydive/CHANGELOG.rst -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,924 root INFO copying ansible_collections/community/skydive/FILES.json -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,924 root INFO copying ansible_collections/community/skydive/LICENSE -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,924 root INFO copying ansible_collections/community/skydive/MANIFEST.json -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,925 root INFO copying ansible_collections/community/skydive/README.md -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,925 root INFO copying ansible_collections/community/skydive/bindep.txt -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,925 root INFO copying ansible_collections/community/skydive/requirements.txt -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,925 root INFO copying ansible_collections/community/skydive/test-requirements.txt -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,925 root INFO copying ansible_collections/community/skydive/tox.ini -> build/lib/ansible_collections/community/skydive 2023-04-28 05:57:41,926 root INFO creating build/lib/ansible_collections/community/skydive/changelogs 2023-04-28 05:57:41,926 root INFO copying ansible_collections/community/skydive/changelogs/changelog.yaml -> build/lib/ansible_collections/community/skydive/changelogs 2023-04-28 05:57:41,926 root INFO copying ansible_collections/community/skydive/changelogs/config.yaml -> build/lib/ansible_collections/community/skydive/changelogs 2023-04-28 05:57:41,926 root INFO creating build/lib/ansible_collections/community/skydive/meta 2023-04-28 05:57:41,926 root INFO copying ansible_collections/community/skydive/meta/runtime.yml -> build/lib/ansible_collections/community/skydive/meta 2023-04-28 05:57:41,927 root INFO creating build/lib/ansible_collections/community/skydive/plugins 2023-04-28 05:57:41,927 root INFO creating build/lib/ansible_collections/community/skydive/plugins/doc_fragments 2023-04-28 05:57:41,927 root INFO copying ansible_collections/community/skydive/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/skydive/plugins/doc_fragments 2023-04-28 05:57:41,927 root INFO copying ansible_collections/community/skydive/plugins/doc_fragments/skydive.py -> build/lib/ansible_collections/community/skydive/plugins/doc_fragments 2023-04-28 05:57:41,927 root INFO creating build/lib/ansible_collections/community/skydive/plugins/lookup 2023-04-28 05:57:41,927 root INFO copying ansible_collections/community/skydive/plugins/lookup/__init__.py -> build/lib/ansible_collections/community/skydive/plugins/lookup 2023-04-28 05:57:41,928 root INFO copying ansible_collections/community/skydive/plugins/lookup/skydive.py -> build/lib/ansible_collections/community/skydive/plugins/lookup 2023-04-28 05:57:41,928 root INFO creating build/lib/ansible_collections/community/skydive/plugins/module_utils 2023-04-28 05:57:41,928 root INFO copying ansible_collections/community/skydive/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/skydive/plugins/module_utils 2023-04-28 05:57:41,928 root INFO creating build/lib/ansible_collections/community/skydive/plugins/module_utils/network 2023-04-28 05:57:41,928 root INFO creating build/lib/ansible_collections/community/skydive/plugins/module_utils/network/skydive 2023-04-28 05:57:41,928 root INFO copying ansible_collections/community/skydive/plugins/module_utils/network/skydive/__init__.py -> build/lib/ansible_collections/community/skydive/plugins/module_utils/network/skydive 2023-04-28 05:57:41,929 root INFO copying ansible_collections/community/skydive/plugins/module_utils/network/skydive/api.py -> build/lib/ansible_collections/community/skydive/plugins/module_utils/network/skydive 2023-04-28 05:57:41,929 root INFO creating build/lib/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:41,929 root INFO copying ansible_collections/community/skydive/plugins/modules/__init__.py -> build/lib/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:41,929 root INFO copying ansible_collections/community/skydive/plugins/modules/skydive_capture.py -> build/lib/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:41,930 root INFO copying ansible_collections/community/skydive/plugins/modules/skydive_edge.py -> build/lib/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:41,930 root INFO copying ansible_collections/community/skydive/plugins/modules/skydive_node.py -> build/lib/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:41,930 root INFO creating build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,930 root INFO copying ansible_collections/community/sops/CHANGELOG.rst -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,930 root INFO copying ansible_collections/community/sops/CHANGELOG.rst.license -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,931 root INFO copying ansible_collections/community/sops/CONTRIBUTING.md -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,931 root INFO copying ansible_collections/community/sops/COPYING -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,931 root INFO copying ansible_collections/community/sops/FILES.json -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,931 root INFO copying ansible_collections/community/sops/MANIFEST.json -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,932 root INFO copying ansible_collections/community/sops/README.md -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,932 root INFO copying ansible_collections/community/sops/codecov.yml -> build/lib/ansible_collections/community/sops 2023-04-28 05:57:41,932 root INFO creating build/lib/ansible_collections/community/sops/LICENSES 2023-04-28 05:57:41,932 root INFO copying ansible_collections/community/sops/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/community/sops/LICENSES 2023-04-28 05:57:41,932 root INFO copying ansible_collections/community/sops/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/sops/LICENSES 2023-04-28 05:57:41,933 root INFO creating build/lib/ansible_collections/community/sops/changelogs 2023-04-28 05:57:41,933 root INFO copying ansible_collections/community/sops/changelogs/changelog.yaml -> build/lib/ansible_collections/community/sops/changelogs 2023-04-28 05:57:41,933 root INFO copying ansible_collections/community/sops/changelogs/changelog.yaml.license -> build/lib/ansible_collections/community/sops/changelogs 2023-04-28 05:57:41,933 root INFO copying ansible_collections/community/sops/changelogs/config.yaml -> build/lib/ansible_collections/community/sops/changelogs 2023-04-28 05:57:41,933 root INFO creating build/lib/ansible_collections/community/sops/changelogs/fragments 2023-04-28 05:57:41,934 root INFO copying ansible_collections/community/sops/changelogs/fragments/.keep -> build/lib/ansible_collections/community/sops/changelogs/fragments 2023-04-28 05:57:41,934 root INFO creating build/lib/ansible_collections/community/sops/meta 2023-04-28 05:57:41,934 root INFO copying ansible_collections/community/sops/meta/ee-bindep.txt -> build/lib/ansible_collections/community/sops/meta 2023-04-28 05:57:41,934 root INFO copying ansible_collections/community/sops/meta/execution-environment.yml -> build/lib/ansible_collections/community/sops/meta 2023-04-28 05:57:41,934 root INFO copying ansible_collections/community/sops/meta/runtime.yml -> build/lib/ansible_collections/community/sops/meta 2023-04-28 05:57:41,935 root INFO creating build/lib/ansible_collections/community/sops/playbooks 2023-04-28 05:57:41,935 root INFO copying ansible_collections/community/sops/playbooks/install.yml -> build/lib/ansible_collections/community/sops/playbooks 2023-04-28 05:57:41,935 root INFO copying ansible_collections/community/sops/playbooks/install_localhost.yml -> build/lib/ansible_collections/community/sops/playbooks 2023-04-28 05:57:41,935 root INFO creating build/lib/ansible_collections/community/sops/plugins 2023-04-28 05:57:41,935 root INFO creating build/lib/ansible_collections/community/sops/plugins/action 2023-04-28 05:57:41,935 root INFO copying ansible_collections/community/sops/plugins/action/load_vars.py -> build/lib/ansible_collections/community/sops/plugins/action 2023-04-28 05:57:41,936 root INFO creating build/lib/ansible_collections/community/sops/plugins/doc_fragments 2023-04-28 05:57:41,936 root INFO copying ansible_collections/community/sops/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/community/sops/plugins/doc_fragments 2023-04-28 05:57:41,936 root INFO copying ansible_collections/community/sops/plugins/doc_fragments/sops.py -> build/lib/ansible_collections/community/sops/plugins/doc_fragments 2023-04-28 05:57:41,936 root INFO creating build/lib/ansible_collections/community/sops/plugins/filter 2023-04-28 05:57:41,936 root INFO copying ansible_collections/community/sops/plugins/filter/_latest_version.py -> build/lib/ansible_collections/community/sops/plugins/filter 2023-04-28 05:57:41,937 root INFO copying ansible_collections/community/sops/plugins/filter/decrypt.py -> build/lib/ansible_collections/community/sops/plugins/filter 2023-04-28 05:57:41,937 root INFO creating build/lib/ansible_collections/community/sops/plugins/lookup 2023-04-28 05:57:41,937 root INFO copying ansible_collections/community/sops/plugins/lookup/sops.py -> build/lib/ansible_collections/community/sops/plugins/lookup 2023-04-28 05:57:41,937 root INFO creating build/lib/ansible_collections/community/sops/plugins/module_utils 2023-04-28 05:57:41,937 root INFO copying ansible_collections/community/sops/plugins/module_utils/io.py -> build/lib/ansible_collections/community/sops/plugins/module_utils 2023-04-28 05:57:41,938 root INFO copying ansible_collections/community/sops/plugins/module_utils/sops.py -> build/lib/ansible_collections/community/sops/plugins/module_utils 2023-04-28 05:57:41,938 root INFO creating build/lib/ansible_collections/community/sops/plugins/modules 2023-04-28 05:57:41,938 root INFO copying ansible_collections/community/sops/plugins/modules/load_vars.py -> build/lib/ansible_collections/community/sops/plugins/modules 2023-04-28 05:57:41,938 root INFO copying ansible_collections/community/sops/plugins/modules/sops_encrypt.py -> build/lib/ansible_collections/community/sops/plugins/modules 2023-04-28 05:57:41,938 root INFO creating build/lib/ansible_collections/community/sops/plugins/plugin_utils 2023-04-28 05:57:41,939 root INFO copying ansible_collections/community/sops/plugins/plugin_utils/action_module.py -> build/lib/ansible_collections/community/sops/plugins/plugin_utils 2023-04-28 05:57:41,939 root INFO creating build/lib/ansible_collections/community/sops/plugins/vars 2023-04-28 05:57:41,939 root INFO copying ansible_collections/community/sops/plugins/vars/sops.py -> build/lib/ansible_collections/community/sops/plugins/vars 2023-04-28 05:57:41,939 root INFO creating build/lib/ansible_collections/community/sops/roles 2023-04-28 05:57:41,939 root INFO creating build/lib/ansible_collections/community/sops/roles/_install_age 2023-04-28 05:57:41,939 root INFO copying ansible_collections/community/sops/roles/_install_age/README.md -> build/lib/ansible_collections/community/sops/roles/_install_age 2023-04-28 05:57:41,940 root INFO creating build/lib/ansible_collections/community/sops/roles/_install_age/defaults 2023-04-28 05:57:41,940 root INFO copying ansible_collections/community/sops/roles/_install_age/defaults/main.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/defaults 2023-04-28 05:57:41,940 root INFO creating build/lib/ansible_collections/community/sops/roles/_install_age/meta 2023-04-28 05:57:41,940 root INFO copying ansible_collections/community/sops/roles/_install_age/meta/main.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/meta 2023-04-28 05:57:41,940 root INFO creating build/lib/ansible_collections/community/sops/roles/_install_age/tasks 2023-04-28 05:57:41,940 root INFO copying ansible_collections/community/sops/roles/_install_age/tasks/main.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/tasks 2023-04-28 05:57:41,941 root INFO creating build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,941 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/D-Alpine.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,941 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/D-Archlinux.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,941 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/D-Debian-10.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,941 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/D-Fedora.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,942 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-16.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,942 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-18.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,942 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-20.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,942 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/OS-Debian.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,943 root INFO copying ansible_collections/community/sops/roles/_install_age/vars/default.yml -> build/lib/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:41,943 root INFO creating build/lib/ansible_collections/community/sops/roles/install 2023-04-28 05:57:41,943 root INFO copying ansible_collections/community/sops/roles/install/README.md -> build/lib/ansible_collections/community/sops/roles/install 2023-04-28 05:57:41,943 root INFO creating build/lib/ansible_collections/community/sops/roles/install/defaults 2023-04-28 05:57:41,943 root INFO copying ansible_collections/community/sops/roles/install/defaults/main.yml -> build/lib/ansible_collections/community/sops/roles/install/defaults 2023-04-28 05:57:41,944 root INFO creating build/lib/ansible_collections/community/sops/roles/install/meta 2023-04-28 05:57:41,944 root INFO copying ansible_collections/community/sops/roles/install/meta/argument_specs.yml -> build/lib/ansible_collections/community/sops/roles/install/meta 2023-04-28 05:57:41,944 root INFO copying ansible_collections/community/sops/roles/install/meta/main.yml -> build/lib/ansible_collections/community/sops/roles/install/meta 2023-04-28 05:57:41,944 root INFO creating build/lib/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:41,944 root INFO copying ansible_collections/community/sops/roles/install/tasks/detect_source.yml -> build/lib/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:41,944 root INFO copying ansible_collections/community/sops/roles/install/tasks/github.yml -> build/lib/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:41,945 root INFO copying ansible_collections/community/sops/roles/install/tasks/github_api.yml -> build/lib/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:41,945 root INFO copying ansible_collections/community/sops/roles/install/tasks/github_latest_release.yml -> build/lib/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:41,945 root INFO copying ansible_collections/community/sops/roles/install/tasks/main.yml -> build/lib/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:41,945 root INFO copying ansible_collections/community/sops/roles/install/tasks/system.yml -> build/lib/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:41,946 root INFO creating build/lib/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:41,946 root INFO copying ansible_collections/community/sops/roles/install/vars/D-Alpine.yml -> build/lib/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:41,946 root INFO copying ansible_collections/community/sops/roles/install/vars/D-Archlinux.yml -> build/lib/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:41,946 root INFO copying ansible_collections/community/sops/roles/install/vars/OS-Debian.yml -> build/lib/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:41,946 root INFO copying ansible_collections/community/sops/roles/install/vars/OS-RedHat.yml -> build/lib/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:41,947 root INFO copying ansible_collections/community/sops/roles/install/vars/default.yml -> build/lib/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:41,947 root INFO creating build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,947 root INFO copying ansible_collections/community/vmware/CHANGELOG.rst -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,947 root INFO copying ansible_collections/community/vmware/COPYING -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,948 root INFO copying ansible_collections/community/vmware/FILES.json -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,948 root INFO copying ansible_collections/community/vmware/LICENSE -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,948 root INFO copying ansible_collections/community/vmware/MANIFEST.json -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,949 root INFO copying ansible_collections/community/vmware/README.md -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,949 root INFO copying ansible_collections/community/vmware/requirements.txt -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,949 root INFO copying ansible_collections/community/vmware/test-requirements.txt -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,949 root INFO copying ansible_collections/community/vmware/testing.md -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,950 root INFO copying ansible_collections/community/vmware/tox.ini -> build/lib/ansible_collections/community/vmware 2023-04-28 05:57:41,950 root INFO creating build/lib/ansible_collections/community/vmware/LICENSES 2023-04-28 05:57:41,950 root INFO copying ansible_collections/community/vmware/LICENSES/BSD-2-Clause.txt -> build/lib/ansible_collections/community/vmware/LICENSES 2023-04-28 05:57:41,950 root INFO copying ansible_collections/community/vmware/LICENSES/GPL-3.0-or-later.txt -> build/lib/ansible_collections/community/vmware/LICENSES 2023-04-28 05:57:41,950 root INFO creating build/lib/ansible_collections/community/vmware/changelogs 2023-04-28 05:57:41,951 root INFO copying ansible_collections/community/vmware/changelogs/changelog.yaml -> build/lib/ansible_collections/community/vmware/changelogs 2023-04-28 05:57:41,951 root INFO copying ansible_collections/community/vmware/changelogs/config.yaml -> build/lib/ansible_collections/community/vmware/changelogs 2023-04-28 05:57:41,951 root INFO creating build/lib/ansible_collections/community/vmware/meta 2023-04-28 05:57:41,951 root INFO copying ansible_collections/community/vmware/meta/runtime.yml -> build/lib/ansible_collections/community/vmware/meta 2023-04-28 05:57:41,951 root INFO creating build/lib/ansible_collections/community/vmware/plugins 2023-04-28 05:57:41,952 root INFO creating build/lib/ansible_collections/community/vmware/plugins/connection 2023-04-28 05:57:41,952 root INFO copying ansible_collections/community/vmware/plugins/connection/__init__.py -> build/lib/ansible_collections/community/vmware/plugins/connection 2023-04-28 05:57:41,952 root INFO copying ansible_collections/community/vmware/plugins/connection/vmware_tools.py -> build/lib/ansible_collections/community/vmware/plugins/connection 2023-04-28 05:57:41,952 root INFO creating build/lib/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:41,952 root INFO copying ansible_collections/community/vmware/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:41,952 root INFO copying ansible_collections/community/vmware/plugins/doc_fragments/vmware.py -> build/lib/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:41,953 root INFO copying ansible_collections/community/vmware/plugins/doc_fragments/vmware_rest_client.py -> build/lib/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:41,953 root INFO creating build/lib/ansible_collections/community/vmware/plugins/httpapi 2023-04-28 05:57:41,953 root INFO copying ansible_collections/community/vmware/plugins/httpapi/__init__.py -> build/lib/ansible_collections/community/vmware/plugins/httpapi 2023-04-28 05:57:41,953 root INFO copying ansible_collections/community/vmware/plugins/httpapi/vmware.py -> build/lib/ansible_collections/community/vmware/plugins/httpapi 2023-04-28 05:57:41,954 root INFO creating build/lib/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:41,954 root INFO copying ansible_collections/community/vmware/plugins/inventory/__init__.py -> build/lib/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:41,954 root INFO copying ansible_collections/community/vmware/plugins/inventory/vmware_host_inventory.py -> build/lib/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:41,954 root INFO copying ansible_collections/community/vmware/plugins/inventory/vmware_vm_inventory.py -> build/lib/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:41,954 root INFO creating build/lib/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:41,955 root INFO copying ansible_collections/community/vmware/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:41,955 root INFO copying ansible_collections/community/vmware/plugins/module_utils/version.py -> build/lib/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:41,955 root INFO copying ansible_collections/community/vmware/plugins/module_utils/vm_device_helper.py -> build/lib/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:41,955 root INFO copying ansible_collections/community/vmware/plugins/module_utils/vmware.py -> build/lib/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:41,956 root INFO copying ansible_collections/community/vmware/plugins/module_utils/vmware_rest_client.py -> build/lib/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:41,956 root INFO copying ansible_collections/community/vmware/plugins/module_utils/vmware_spbm.py -> build/lib/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:41,956 root INFO creating build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,956 root INFO copying ansible_collections/community/vmware/plugins/modules/__init__.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,956 root INFO copying ansible_collections/community/vmware/plugins/modules/vcenter_domain_user_group_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,957 root INFO copying ansible_collections/community/vmware/plugins/modules/vcenter_extension.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,957 root INFO copying ansible_collections/community/vmware/plugins/modules/vcenter_extension_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,957 root INFO copying ansible_collections/community/vmware/plugins/modules/vcenter_folder.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,957 root INFO copying ansible_collections/community/vmware/plugins/modules/vcenter_license.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,958 root INFO copying ansible_collections/community/vmware/plugins/modules/vcenter_standard_key_provider.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,958 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_about_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,958 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_category.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,958 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_category_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,958 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cfg_backup.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,959 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cluster.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,959 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cluster_dpm.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,959 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cluster_drs.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,959 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cluster_ha.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,960 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cluster_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,960 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cluster_vcls.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,960 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_cluster_vsan.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,960 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_content_deploy_ovf_template.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,961 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_content_deploy_template.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,961 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_content_library_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,961 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_content_library_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,961 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_custom_attribute.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,962 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_custom_attribute_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,962 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_datacenter.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,962 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_datacenter_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,962 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_datastore.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,962 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_datastore_cluster.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,963 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_datastore_cluster_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,963 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_datastore_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,963 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_datastore_maintenancemode.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,963 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_deploy_ovf.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,964 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_drs_group.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,964 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_drs_group_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,964 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_drs_group_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,964 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_drs_rule_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,965 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvs_host.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,965 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,965 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup_find.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,965 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,966 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvswitch.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,966 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,966 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_lacp.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,966 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_nioc.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,967 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_pvlans.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,967 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_uplink_pg.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,967 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_evc_mode.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,967 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_export_ovf.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,968 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_first_class_disk.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,968 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_folder_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,968 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,969 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_boot_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,969 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_boot_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,969 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_controller.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,969 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_cross_vc_clone.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,970 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_custom_attribute_defs.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,970 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_custom_attributes.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,970 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_customization_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,970 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_disk.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,971 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_disk_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,971 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_file_operation.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,971 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_find.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,971 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,972 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_instant_clone.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,972 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_move.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,972 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_network.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,972 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_powerstate.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,973 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_register_operation.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,973 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_screenshot.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,973 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_sendkey.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,973 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_serial_port.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,974 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_snapshot.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,974 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_snapshot_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,974 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_storage_policy.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,974 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,974 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_upgrade.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,975 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_wait.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,975 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_tpm.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,975 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_vgpu.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,975 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_vgpu_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,976 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_guest_video.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,976 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,976 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_acceptance.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,976 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_active_directory.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,977 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_auto_start.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,977 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_capability_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,977 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_config_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,977 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_config_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,978 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_custom_attributes.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,978 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_datastore.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,978 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_disk_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,978 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_dns.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,978 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_dns_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,979 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_facts.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,979 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_feature_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,979 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_firewall_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,979 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_firewall_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,980 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_hyperthreading.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,980 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_ipv6.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,980 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_iscsi.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,980 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_iscsi_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,981 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_kernel_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,981 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_lockdown.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,981 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_lockdown_exceptions.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,981 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_logbundle.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,982 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_logbundle_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,982 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_ntp.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,982 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_ntp_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,982 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_package_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,983 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_passthrough.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,983 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_powermgmt_policy.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,983 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_powerstate.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,983 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_scanhba.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,984 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_scsidisk_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,984 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_service_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,984 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_service_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,984 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_snmp.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,984 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_sriov.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,985 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_ssl_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,985 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_tcpip_stacks.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,985 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_user_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,985 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_vmhba_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,986 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_host_vmnic_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,986 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_local_role_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,986 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_local_role_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,986 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_local_user_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,987 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_local_user_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,987 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_maintenancemode.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,987 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_migrate_vmk.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,987 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_object_custom_attributes_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,988 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_object_rename.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,988 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_object_role_permission.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,988 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_object_role_permission_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,988 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_portgroup.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,989 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_portgroup_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,989 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_recommended_datastore.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,989 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_resource_pool.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,989 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_resource_pool_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,990 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_tag.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,990 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_tag_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,990 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_tag_manager.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,990 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_target_canonical_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,990 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vc_infraprofile_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,991 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vcenter_settings.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,991 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vcenter_settings_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,991 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vcenter_statistics.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,992 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_config_option.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,992 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_host_drs_rule.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,992 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,992 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_shell.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,992 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_storage_policy.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,993 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_storage_policy_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,993 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_vm_drs_rule.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,993 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vm_vss_dvs_migrate.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,993 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vmkernel.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,994 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vmkernel_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,994 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vmotion.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,994 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vsan_cluster.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,994 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vsan_hcl_db.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,995 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vsan_health_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,995 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vspan_session.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,995 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vswitch.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,995 root INFO copying ansible_collections/community/vmware/plugins/modules/vmware_vswitch_info.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,996 root INFO copying ansible_collections/community/vmware/plugins/modules/vsphere_copy.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,996 root INFO copying ansible_collections/community/vmware/plugins/modules/vsphere_file.py -> build/lib/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:41,996 root INFO creating build/lib/ansible_collections/community/vmware/plugins/plugin_utils 2023-04-28 05:57:41,996 root INFO copying ansible_collections/community/vmware/plugins/plugin_utils/inventory.py -> build/lib/ansible_collections/community/vmware/plugins/plugin_utils 2023-04-28 05:57:41,996 root INFO creating build/lib/ansible_collections/community/vmware/scripts 2023-04-28 05:57:41,997 root INFO creating build/lib/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:41,997 root INFO copying ansible_collections/community/vmware/scripts/inventory/__init__.py -> build/lib/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:41,997 root INFO copying ansible_collections/community/vmware/scripts/inventory/vmware.ini -> build/lib/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:41,997 root INFO copying ansible_collections/community/vmware/scripts/inventory/vmware.py -> build/lib/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:41,997 root INFO copying ansible_collections/community/vmware/scripts/inventory/vmware_inventory.ini -> build/lib/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:41,998 root INFO copying ansible_collections/community/vmware/scripts/inventory/vmware_inventory.py -> build/lib/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:41,998 root INFO creating build/lib/ansible_collections/community/vmware/tools 2023-04-28 05:57:41,998 root INFO copying ansible_collections/community/vmware/tools/check-ignores-order -> build/lib/ansible_collections/community/vmware/tools 2023-04-28 05:57:41,998 root INFO copying ansible_collections/community/vmware/tools/create_documentation_tasks.yml -> build/lib/ansible_collections/community/vmware/tools 2023-04-28 05:57:41,998 root INFO copying ansible_collections/community/vmware/tools/prepare_release.yml -> build/lib/ansible_collections/community/vmware/tools 2023-04-28 05:57:41,999 root INFO copying ansible_collections/community/vmware/tools/unset_version.yml -> build/lib/ansible_collections/community/vmware/tools 2023-04-28 05:57:41,999 root INFO copying ansible_collections/community/vmware/tools/update_documentation.yml -> build/lib/ansible_collections/community/vmware/tools 2023-04-28 05:57:41,999 root INFO creating build/lib/ansible_collections/community/windows 2023-04-28 05:57:41,999 root INFO copying ansible_collections/community/windows/CHANGELOG.rst -> build/lib/ansible_collections/community/windows 2023-04-28 05:57:41,999 root INFO copying ansible_collections/community/windows/COPYING -> build/lib/ansible_collections/community/windows 2023-04-28 05:57:42,000 root INFO copying ansible_collections/community/windows/FILES.json -> build/lib/ansible_collections/community/windows 2023-04-28 05:57:42,000 root INFO copying ansible_collections/community/windows/MANIFEST.json -> build/lib/ansible_collections/community/windows 2023-04-28 05:57:42,001 root INFO copying ansible_collections/community/windows/README.md -> build/lib/ansible_collections/community/windows 2023-04-28 05:57:42,001 root INFO creating build/lib/ansible_collections/community/windows/changelogs 2023-04-28 05:57:42,001 root INFO copying ansible_collections/community/windows/changelogs/changelog.yaml -> build/lib/ansible_collections/community/windows/changelogs 2023-04-28 05:57:42,001 root INFO copying ansible_collections/community/windows/changelogs/config.yaml -> build/lib/ansible_collections/community/windows/changelogs 2023-04-28 05:57:42,001 root INFO creating build/lib/ansible_collections/community/windows/changelogs/fragments 2023-04-28 05:57:42,002 root INFO copying ansible_collections/community/windows/changelogs/fragments/.keep -> build/lib/ansible_collections/community/windows/changelogs/fragments 2023-04-28 05:57:42,002 root INFO creating build/lib/ansible_collections/community/windows/meta 2023-04-28 05:57:42,002 root INFO copying ansible_collections/community/windows/meta/runtime.yml -> build/lib/ansible_collections/community/windows/meta 2023-04-28 05:57:42,002 root INFO creating build/lib/ansible_collections/community/windows/plugins 2023-04-28 05:57:42,002 root INFO creating build/lib/ansible_collections/community/windows/plugins/action 2023-04-28 05:57:42,002 root INFO copying ansible_collections/community/windows/plugins/action/win_pssession_configuration.py -> build/lib/ansible_collections/community/windows/plugins/action 2023-04-28 05:57:42,003 root INFO creating build/lib/ansible_collections/community/windows/plugins/lookup 2023-04-28 05:57:42,003 root INFO copying ansible_collections/community/windows/plugins/lookup/__init__.py -> build/lib/ansible_collections/community/windows/plugins/lookup 2023-04-28 05:57:42,003 root INFO copying ansible_collections/community/windows/plugins/lookup/laps_password.py -> build/lib/ansible_collections/community/windows/plugins/lookup 2023-04-28 05:57:42,003 root INFO creating build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,004 root INFO copying ansible_collections/community/windows/plugins/modules/__init__.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,004 root INFO copying ansible_collections/community/windows/plugins/modules/psexec.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,005 root INFO copying ansible_collections/community/windows/plugins/modules/win_audit_policy_system.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,006 root INFO copying ansible_collections/community/windows/plugins/modules/win_audit_policy_system.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,006 root INFO copying ansible_collections/community/windows/plugins/modules/win_audit_rule.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,006 root INFO copying ansible_collections/community/windows/plugins/modules/win_audit_rule.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,006 root INFO copying ansible_collections/community/windows/plugins/modules/win_auto_logon.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,007 root INFO copying ansible_collections/community/windows/plugins/modules/win_auto_logon.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,007 root INFO copying ansible_collections/community/windows/plugins/modules/win_certificate_info.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,007 root INFO copying ansible_collections/community/windows/plugins/modules/win_certificate_info.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,007 root INFO copying ansible_collections/community/windows/plugins/modules/win_computer_description.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,008 root INFO copying ansible_collections/community/windows/plugins/modules/win_computer_description.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,009 root INFO copying ansible_collections/community/windows/plugins/modules/win_credential.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,009 root INFO copying ansible_collections/community/windows/plugins/modules/win_credential.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,009 root INFO copying ansible_collections/community/windows/plugins/modules/win_data_deduplication.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,010 root INFO copying ansible_collections/community/windows/plugins/modules/win_data_deduplication.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,010 root INFO copying ansible_collections/community/windows/plugins/modules/win_defrag.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,010 root INFO copying ansible_collections/community/windows/plugins/modules/win_defrag.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,011 root INFO copying ansible_collections/community/windows/plugins/modules/win_dhcp_lease.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,012 root INFO copying ansible_collections/community/windows/plugins/modules/win_dhcp_lease.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,013 root INFO copying ansible_collections/community/windows/plugins/modules/win_disk_facts.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,013 root INFO copying ansible_collections/community/windows/plugins/modules/win_disk_facts.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,015 root INFO copying ansible_collections/community/windows/plugins/modules/win_disk_image.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,015 root INFO copying ansible_collections/community/windows/plugins/modules/win_disk_image.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,015 root INFO copying ansible_collections/community/windows/plugins/modules/win_dns_record.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,015 root INFO copying ansible_collections/community/windows/plugins/modules/win_dns_record.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,015 root INFO copying ansible_collections/community/windows/plugins/modules/win_dns_zone.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,016 root INFO copying ansible_collections/community/windows/plugins/modules/win_dns_zone.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,016 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_computer.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,016 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_computer.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,016 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_group.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,017 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_group.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,017 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_group_membership.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,017 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_group_membership.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,017 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_object_info.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,018 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_object_info.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,018 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_ou.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,018 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_ou.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,018 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_user.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,019 root INFO copying ansible_collections/community/windows/plugins/modules/win_domain_user.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,019 root INFO copying ansible_collections/community/windows/plugins/modules/win_dotnet_ngen.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,019 root INFO copying ansible_collections/community/windows/plugins/modules/win_dotnet_ngen.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,019 root INFO copying ansible_collections/community/windows/plugins/modules/win_eventlog.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,020 root INFO copying ansible_collections/community/windows/plugins/modules/win_eventlog.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,020 root INFO copying ansible_collections/community/windows/plugins/modules/win_eventlog_entry.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,020 root INFO copying ansible_collections/community/windows/plugins/modules/win_eventlog_entry.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,021 root INFO copying ansible_collections/community/windows/plugins/modules/win_feature_info.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,021 root INFO copying ansible_collections/community/windows/plugins/modules/win_feature_info.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,021 root INFO copying ansible_collections/community/windows/plugins/modules/win_file_compression.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,021 root INFO copying ansible_collections/community/windows/plugins/modules/win_file_compression.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,022 root INFO copying ansible_collections/community/windows/plugins/modules/win_file_version.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,022 root INFO copying ansible_collections/community/windows/plugins/modules/win_file_version.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,022 root INFO copying ansible_collections/community/windows/plugins/modules/win_firewall.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,022 root INFO copying ansible_collections/community/windows/plugins/modules/win_firewall.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,022 root INFO copying ansible_collections/community/windows/plugins/modules/win_firewall_rule.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,023 root INFO copying ansible_collections/community/windows/plugins/modules/win_firewall_rule.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,023 root INFO copying ansible_collections/community/windows/plugins/modules/win_format.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,023 root INFO copying ansible_collections/community/windows/plugins/modules/win_format.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,024 root INFO copying ansible_collections/community/windows/plugins/modules/win_hosts.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,024 root INFO copying ansible_collections/community/windows/plugins/modules/win_hosts.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,024 root INFO copying ansible_collections/community/windows/plugins/modules/win_hotfix.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,024 root INFO copying ansible_collections/community/windows/plugins/modules/win_hotfix.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,024 root INFO copying ansible_collections/community/windows/plugins/modules/win_http_proxy.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,025 root INFO copying ansible_collections/community/windows/plugins/modules/win_http_proxy.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,025 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_virtualdirectory.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,025 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_virtualdirectory.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,025 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_webapplication.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,026 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_webapplication.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,026 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_webapppool.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,026 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_webapppool.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,026 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_webbinding.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,027 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_webbinding.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,027 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_website.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,027 root INFO copying ansible_collections/community/windows/plugins/modules/win_iis_website.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,027 root INFO copying ansible_collections/community/windows/plugins/modules/win_inet_proxy.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,027 root INFO copying ansible_collections/community/windows/plugins/modules/win_inet_proxy.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,028 root INFO copying ansible_collections/community/windows/plugins/modules/win_initialize_disk.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,028 root INFO copying ansible_collections/community/windows/plugins/modules/win_initialize_disk.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,028 root INFO copying ansible_collections/community/windows/plugins/modules/win_lineinfile.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,028 root INFO copying ansible_collections/community/windows/plugins/modules/win_lineinfile.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,029 root INFO copying ansible_collections/community/windows/plugins/modules/win_listen_ports_facts.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,029 root INFO copying ansible_collections/community/windows/plugins/modules/win_listen_ports_facts.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,029 root INFO copying ansible_collections/community/windows/plugins/modules/win_mapped_drive.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,029 root INFO copying ansible_collections/community/windows/plugins/modules/win_mapped_drive.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,030 root INFO copying ansible_collections/community/windows/plugins/modules/win_msg.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,030 root INFO copying ansible_collections/community/windows/plugins/modules/win_msg.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,030 root INFO copying ansible_collections/community/windows/plugins/modules/win_net_adapter_feature.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,030 root INFO copying ansible_collections/community/windows/plugins/modules/win_net_adapter_feature.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,031 root INFO copying ansible_collections/community/windows/plugins/modules/win_netbios.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,031 root INFO copying ansible_collections/community/windows/plugins/modules/win_netbios.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,031 root INFO copying ansible_collections/community/windows/plugins/modules/win_nssm.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,031 root INFO copying ansible_collections/community/windows/plugins/modules/win_nssm.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,031 root INFO copying ansible_collections/community/windows/plugins/modules/win_pagefile.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,032 root INFO copying ansible_collections/community/windows/plugins/modules/win_pagefile.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,032 root INFO copying ansible_collections/community/windows/plugins/modules/win_partition.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,032 root INFO copying ansible_collections/community/windows/plugins/modules/win_partition.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,032 root INFO copying ansible_collections/community/windows/plugins/modules/win_pester.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,033 root INFO copying ansible_collections/community/windows/plugins/modules/win_pester.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,033 root INFO copying ansible_collections/community/windows/plugins/modules/win_power_plan.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,033 root INFO copying ansible_collections/community/windows/plugins/modules/win_power_plan.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,033 root INFO copying ansible_collections/community/windows/plugins/modules/win_product_facts.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,034 root INFO copying ansible_collections/community/windows/plugins/modules/win_product_facts.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,034 root INFO copying ansible_collections/community/windows/plugins/modules/win_psexec.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,034 root INFO copying ansible_collections/community/windows/plugins/modules/win_psexec.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,034 root INFO copying ansible_collections/community/windows/plugins/modules/win_psmodule.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,035 root INFO copying ansible_collections/community/windows/plugins/modules/win_psmodule.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,035 root INFO copying ansible_collections/community/windows/plugins/modules/win_psmodule_info.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,035 root INFO copying ansible_collections/community/windows/plugins/modules/win_psmodule_info.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,035 root INFO copying ansible_collections/community/windows/plugins/modules/win_psrepository.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,035 root INFO copying ansible_collections/community/windows/plugins/modules/win_psrepository.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,036 root INFO copying ansible_collections/community/windows/plugins/modules/win_psrepository_copy.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,036 root INFO copying ansible_collections/community/windows/plugins/modules/win_psrepository_copy.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,036 root INFO copying ansible_collections/community/windows/plugins/modules/win_psrepository_info.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,036 root INFO copying ansible_collections/community/windows/plugins/modules/win_psrepository_info.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,037 root INFO copying ansible_collections/community/windows/plugins/modules/win_psscript.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,037 root INFO copying ansible_collections/community/windows/plugins/modules/win_psscript.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,037 root INFO copying ansible_collections/community/windows/plugins/modules/win_psscript_info.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,038 root INFO copying ansible_collections/community/windows/plugins/modules/win_psscript_info.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,038 root INFO copying ansible_collections/community/windows/plugins/modules/win_pssession_configuration.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,038 root INFO copying ansible_collections/community/windows/plugins/modules/win_pssession_configuration.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,038 root INFO copying ansible_collections/community/windows/plugins/modules/win_rabbitmq_plugin.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,039 root INFO copying ansible_collections/community/windows/plugins/modules/win_rabbitmq_plugin.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,039 root INFO copying ansible_collections/community/windows/plugins/modules/win_rds_cap.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,039 root INFO copying ansible_collections/community/windows/plugins/modules/win_rds_cap.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,039 root INFO copying ansible_collections/community/windows/plugins/modules/win_rds_rap.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,039 root INFO copying ansible_collections/community/windows/plugins/modules/win_rds_rap.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,040 root INFO copying ansible_collections/community/windows/plugins/modules/win_rds_settings.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,040 root INFO copying ansible_collections/community/windows/plugins/modules/win_rds_settings.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,040 root INFO copying ansible_collections/community/windows/plugins/modules/win_region.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,041 root INFO copying ansible_collections/community/windows/plugins/modules/win_region.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,041 root INFO copying ansible_collections/community/windows/plugins/modules/win_regmerge.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,041 root INFO copying ansible_collections/community/windows/plugins/modules/win_regmerge.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,041 root INFO copying ansible_collections/community/windows/plugins/modules/win_robocopy.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,041 root INFO copying ansible_collections/community/windows/plugins/modules/win_robocopy.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,042 root INFO copying ansible_collections/community/windows/plugins/modules/win_route.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,042 root INFO copying ansible_collections/community/windows/plugins/modules/win_route.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,042 root INFO copying ansible_collections/community/windows/plugins/modules/win_say.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,042 root INFO copying ansible_collections/community/windows/plugins/modules/win_say.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,043 root INFO copying ansible_collections/community/windows/plugins/modules/win_scheduled_task.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,043 root INFO copying ansible_collections/community/windows/plugins/modules/win_scheduled_task.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,043 root INFO copying ansible_collections/community/windows/plugins/modules/win_scheduled_task_stat.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,043 root INFO copying ansible_collections/community/windows/plugins/modules/win_scheduled_task_stat.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,044 root INFO copying ansible_collections/community/windows/plugins/modules/win_scoop.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,044 root INFO copying ansible_collections/community/windows/plugins/modules/win_scoop.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,044 root INFO copying ansible_collections/community/windows/plugins/modules/win_scoop_bucket.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,044 root INFO copying ansible_collections/community/windows/plugins/modules/win_scoop_bucket.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,045 root INFO copying ansible_collections/community/windows/plugins/modules/win_security_policy.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,045 root INFO copying ansible_collections/community/windows/plugins/modules/win_security_policy.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,045 root INFO copying ansible_collections/community/windows/plugins/modules/win_shortcut.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,045 root INFO copying ansible_collections/community/windows/plugins/modules/win_shortcut.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,046 root INFO copying ansible_collections/community/windows/plugins/modules/win_snmp.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,046 root INFO copying ansible_collections/community/windows/plugins/modules/win_snmp.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,046 root INFO copying ansible_collections/community/windows/plugins/modules/win_timezone.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,046 root INFO copying ansible_collections/community/windows/plugins/modules/win_timezone.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,047 root INFO copying ansible_collections/community/windows/plugins/modules/win_toast.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,047 root INFO copying ansible_collections/community/windows/plugins/modules/win_toast.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,047 root INFO copying ansible_collections/community/windows/plugins/modules/win_unzip.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,047 root INFO copying ansible_collections/community/windows/plugins/modules/win_unzip.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,047 root INFO copying ansible_collections/community/windows/plugins/modules/win_user_profile.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,048 root INFO copying ansible_collections/community/windows/plugins/modules/win_user_profile.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,048 root INFO copying ansible_collections/community/windows/plugins/modules/win_wait_for_process.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,048 root INFO copying ansible_collections/community/windows/plugins/modules/win_wait_for_process.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,048 root INFO copying ansible_collections/community/windows/plugins/modules/win_wakeonlan.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,049 root INFO copying ansible_collections/community/windows/plugins/modules/win_wakeonlan.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,049 root INFO copying ansible_collections/community/windows/plugins/modules/win_webpicmd.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,049 root INFO copying ansible_collections/community/windows/plugins/modules/win_webpicmd.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,049 root INFO copying ansible_collections/community/windows/plugins/modules/win_xml.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,049 root INFO copying ansible_collections/community/windows/plugins/modules/win_xml.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,050 root INFO copying ansible_collections/community/windows/plugins/modules/win_zip.ps1 -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,050 root INFO copying ansible_collections/community/windows/plugins/modules/win_zip.py -> build/lib/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:42,050 root INFO creating build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,050 root INFO copying ansible_collections/community/zabbix/CHANGELOG.rst -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,051 root INFO copying ansible_collections/community/zabbix/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,051 root INFO copying ansible_collections/community/zabbix/CONTRIBUTING.md -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,051 root INFO copying ansible_collections/community/zabbix/FILES.json -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,051 root INFO copying ansible_collections/community/zabbix/LICENSE -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,052 root INFO copying ansible_collections/community/zabbix/MAINTAINERS -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,052 root INFO copying ansible_collections/community/zabbix/MANIFEST.json -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,052 root INFO copying ansible_collections/community/zabbix/PSF-license.txt -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,052 root INFO copying ansible_collections/community/zabbix/README.md -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,053 root INFO copying ansible_collections/community/zabbix/docker-compose.yml -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,053 root INFO copying ansible_collections/community/zabbix/requirements.txt -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,053 root INFO copying ansible_collections/community/zabbix/tox.ini -> build/lib/ansible_collections/community/zabbix 2023-04-28 05:57:42,053 root INFO creating build/lib/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:42,053 root INFO copying ansible_collections/community/zabbix/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:42,054 root INFO copying ansible_collections/community/zabbix/changelogs/changelog.yaml -> build/lib/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:42,054 root INFO copying ansible_collections/community/zabbix/changelogs/config.yaml -> build/lib/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:42,054 root INFO copying ansible_collections/community/zabbix/changelogs/roles_zabbix64.yml -> build/lib/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:42,054 root INFO creating build/lib/ansible_collections/community/zabbix/changelogs/fragments 2023-04-28 05:57:42,055 root INFO copying ansible_collections/community/zabbix/changelogs/fragments/.gitkeep -> build/lib/ansible_collections/community/zabbix/changelogs/fragments 2023-04-28 05:57:42,055 root INFO creating build/lib/ansible_collections/community/zabbix/meta 2023-04-28 05:57:42,055 root INFO copying ansible_collections/community/zabbix/meta/runtime.yml -> build/lib/ansible_collections/community/zabbix/meta 2023-04-28 05:57:42,055 root INFO creating build/lib/ansible_collections/community/zabbix/molecule 2023-04-28 05:57:42,055 root INFO copying ansible_collections/community/zabbix/molecule/requirements.txt -> build/lib/ansible_collections/community/zabbix/molecule 2023-04-28 05:57:42,056 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests 2023-04-28 05:57:42,056 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common 2023-04-28 05:57:42,056 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common 2023-04-28 05:57:42,056 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks 2023-04-28 05:57:42,056 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks/converge.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks 2023-04-28 05:57:42,056 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks/prepare.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks 2023-04-28 05:57:42,057 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests 2023-04-28 05:57:42,057 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/test_docker.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests 2023-04-28 05:57:42,057 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common 2023-04-28 05:57:42,057 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common/test_agent2.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common 2023-04-28 05:57:42,057 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk 2023-04-28 05:57:42,058 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk/test_auto_psk.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk 2023-04-28 05:57:42,058 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common 2023-04-28 05:57:42,058 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common/test_agent.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common 2023-04-28 05:57:42,058 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk 2023-04-28 05:57:42,058 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk/test_no_auto_psk.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk 2023-04-28 05:57:42,058 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule 2023-04-28 05:57:42,059 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2 2023-04-28 05:57:42,059 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2 2023-04-28 05:57:42,059 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests 2023-04-28 05:57:42,059 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/conftest.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests 2023-04-28 05:57:42,059 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common 2023-04-28 05:57:42,059 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common/test_agent2.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common 2023-04-28 05:57:42,060 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common 2023-04-28 05:57:42,060 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common/test_agent.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common 2023-04-28 05:57:42,060 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk 2023-04-28 05:57:42,060 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk/test_no_auto_psk.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk 2023-04-28 05:57:42,060 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk 2023-04-28 05:57:42,061 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk 2023-04-28 05:57:42,061 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests 2023-04-28 05:57:42,061 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/conftest.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests 2023-04-28 05:57:42,061 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common 2023-04-28 05:57:42,061 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common/test_agent2.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common 2023-04-28 05:57:42,061 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk 2023-04-28 05:57:42,062 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk/test_auto_psk.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk 2023-04-28 05:57:42,062 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common 2023-04-28 05:57:42,062 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common/test_agent.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common 2023-04-28 05:57:42,062 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk 2023-04-28 05:57:42,062 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk 2023-04-28 05:57:42,063 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests 2023-04-28 05:57:42,063 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/conftest.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests 2023-04-28 05:57:42,063 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk 2023-04-28 05:57:42,063 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk/test_auto_psk.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk 2023-04-28 05:57:42,063 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common 2023-04-28 05:57:42,063 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common/test_agent.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common 2023-04-28 05:57:42,064 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default 2023-04-28 05:57:42,064 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default 2023-04-28 05:57:42,064 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests 2023-04-28 05:57:42,064 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/conftest.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests 2023-04-28 05:57:42,064 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common 2023-04-28 05:57:42,064 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common/test_agent.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common 2023-04-28 05:57:42,065 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk 2023-04-28 05:57:42,065 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk/test_no_auto_psk.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk 2023-04-28 05:57:42,065 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:42,065 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_javagateway/converge.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:42,065 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_javagateway/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:42,066 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_javagateway/prepare.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:42,066 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests 2023-04-28 05:57:42,066 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests/test_default.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests 2023-04-28 05:57:42,066 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:42,066 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_proxy/converge.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:42,067 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_proxy/destroy.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:42,067 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_proxy/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:42,067 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_proxy/prepare.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:42,067 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy/tests 2023-04-28 05:57:42,067 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_proxy/tests/test_default.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy/tests 2023-04-28 05:57:42,068 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:42,068 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_server/converge.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:42,068 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_server/destroy.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:42,068 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_server/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:42,068 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_server/prepare.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:42,069 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_server/tests 2023-04-28 05:57:42,069 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_server/tests/test_default.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_server/tests 2023-04-28 05:57:42,069 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:42,069 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_web/converge.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:42,069 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_web/destroy.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:42,070 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_web/molecule.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:42,070 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_web/prepare.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:42,070 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_web/requirements.yml -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:42,070 root INFO creating build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/tests 2023-04-28 05:57:42,070 root INFO copying ansible_collections/community/zabbix/molecule/zabbix_web/tests/test_default.py -> build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/tests 2023-04-28 05:57:42,071 root INFO creating build/lib/ansible_collections/community/zabbix/plugins 2023-04-28 05:57:42,071 root INFO creating build/lib/ansible_collections/community/zabbix/plugins/doc_fragments 2023-04-28 05:57:42,071 root INFO copying ansible_collections/community/zabbix/plugins/doc_fragments/connection_persistent.py -> build/lib/ansible_collections/community/zabbix/plugins/doc_fragments 2023-04-28 05:57:42,071 root INFO copying ansible_collections/community/zabbix/plugins/doc_fragments/zabbix.py -> build/lib/ansible_collections/community/zabbix/plugins/doc_fragments 2023-04-28 05:57:42,071 root INFO creating build/lib/ansible_collections/community/zabbix/plugins/httpapi 2023-04-28 05:57:42,071 root INFO copying ansible_collections/community/zabbix/plugins/httpapi/zabbix.py -> build/lib/ansible_collections/community/zabbix/plugins/httpapi 2023-04-28 05:57:42,072 root INFO creating build/lib/ansible_collections/community/zabbix/plugins/inventory 2023-04-28 05:57:42,072 root INFO copying ansible_collections/community/zabbix/plugins/inventory/zabbix_inventory.py -> build/lib/ansible_collections/community/zabbix/plugins/inventory 2023-04-28 05:57:42,072 root INFO creating build/lib/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:42,072 root INFO copying ansible_collections/community/zabbix/plugins/module_utils/__init__.py -> build/lib/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:42,072 root INFO copying ansible_collections/community/zabbix/plugins/module_utils/_version.py -> build/lib/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:42,073 root INFO copying ansible_collections/community/zabbix/plugins/module_utils/api_request.py -> build/lib/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:42,073 root INFO copying ansible_collections/community/zabbix/plugins/module_utils/base.py -> build/lib/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:42,073 root INFO copying ansible_collections/community/zabbix/plugins/module_utils/helpers.py -> build/lib/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:42,073 root INFO copying ansible_collections/community/zabbix/plugins/module_utils/wrappers.py -> build/lib/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:42,074 root INFO creating build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,074 root INFO copying ansible_collections/community/zabbix/plugins/modules/__init__.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,074 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_action.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,074 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_authentication.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,075 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_autoregister.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,075 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_discovery_rule.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,075 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_globalmacro.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,075 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_group.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,076 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_group_facts.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,076 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_group_info.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,076 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_host.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,076 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_host_events_info.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,077 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_host_facts.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,077 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_host_info.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,077 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_hostmacro.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,077 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_housekeeping.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,077 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_maintenance.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,078 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_map.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,078 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_mediatype.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,078 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_proxy.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,078 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_proxy_info.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,079 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_screen.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,079 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_script.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,079 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_service.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,080 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_template.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,080 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_template_info.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,080 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_user.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,080 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_user_directory.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,081 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_user_info.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,081 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_user_role.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,081 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_usergroup.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,081 root INFO copying ansible_collections/community/zabbix/plugins/modules/zabbix_valuemap.py -> build/lib/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:42,081 root INFO creating build/lib/ansible_collections/community/zabbix/roles 2023-04-28 05:57:42,082 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent 2023-04-28 05:57:42,082 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/README.md -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent 2023-04-28 05:57:42,082 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/defaults 2023-04-28 05:57:42,082 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/defaults/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/defaults 2023-04-28 05:57:42,082 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/files 2023-04-28 05:57:42,083 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/files/sample.conf -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/files 2023-04-28 05:57:42,083 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/files/win_sample 2023-04-28 05:57:42,083 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/files/win_sample/doSomething.ps1 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/files/win_sample 2023-04-28 05:57:42,083 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/handlers 2023-04-28 05:57:42,083 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/handlers/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/handlers 2023-04-28 05:57:42,083 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/meta 2023-04-28 05:57:42,084 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/meta/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/meta 2023-04-28 05:57:42,084 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule 2023-04-28 05:57:42,084 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:42,084 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/Dockerfile.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:42,084 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/INSTALL.rst -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:42,084 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/molecule.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:42,085 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/playbook.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:42,085 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/prepare.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:42,085 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/requirements.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:42,085 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests 2023-04-28 05:57:42,086 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/test_agent.py -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests 2023-04-28 05:57:42,086 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/test_default.py -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests 2023-04-28 05:57:42,086 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,086 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Darwin.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,086 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,087 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Docker.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,087 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Linux.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,087 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,087 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Suse.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,087 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Windows.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,088 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Windows_conf.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,088 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/api.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,088 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/firewall.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,088 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/macOS.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,089 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,089 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/remove.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,089 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/selinux.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,089 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,089 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,090 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_common.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,090 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_linux.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,090 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_windows.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,090 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_common.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,091 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_linux.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,091 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_windows.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,091 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/tasks/userparameter.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:42,091 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates 2023-04-28 05:57:42,091 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/templates/zabbix_agent2.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates 2023-04-28 05:57:42,092 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/templates/zabbix_agentd.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates 2023-04-28 05:57:42,092 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters 2023-04-28 05:57:42,092 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters/mysql.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters 2023-04-28 05:57:42,092 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters/win_sample.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters 2023-04-28 05:57:42,092 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,093 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/Darwin.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,093 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,093 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,093 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/Sangoma.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,093 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/Suse.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,094 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/Windows.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,094 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,094 root INFO copying ansible_collections/community/zabbix/roles/zabbix_agent/vars/zabbix.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:42,094 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway 2023-04-28 05:57:42,094 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/README.md -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway 2023-04-28 05:57:42,095 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/defaults 2023-04-28 05:57:42,095 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/defaults/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/defaults 2023-04-28 05:57:42,095 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/files 2023-04-28 05:57:42,095 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/files/systemd.service -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/files 2023-04-28 05:57:42,095 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/handlers 2023-04-28 05:57:42,096 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/handlers/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/handlers 2023-04-28 05:57:42,096 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/meta 2023-04-28 05:57:42,096 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/meta/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/meta 2023-04-28 05:57:42,096 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:42,096 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:42,097 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:42,097 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:42,097 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/templates 2023-04-28 05:57:42,097 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/templates/zabbix_java_gateway.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/templates 2023-04-28 05:57:42,097 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:42,097 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:42,098 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:42,098 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:42,098 root INFO copying ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/zabbix.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:42,098 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy 2023-04-28 05:57:42,098 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/README.md -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy 2023-04-28 05:57:42,099 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/requirements.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy 2023-04-28 05:57:42,099 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/defaults 2023-04-28 05:57:42,099 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/defaults/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/defaults 2023-04-28 05:57:42,099 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/files 2023-04-28 05:57:42,099 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/files/install_semodule.bsx -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/files 2023-04-28 05:57:42,100 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/handlers 2023-04-28 05:57:42,100 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/handlers/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/handlers 2023-04-28 05:57:42,100 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/meta 2023-04-28 05:57:42,100 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/meta/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/meta 2023-04-28 05:57:42,100 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,101 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,101 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,101 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,101 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/mysql.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,101 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/postgresql.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,102 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/selinux.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,102 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/sqlite3.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:42,102 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/templates 2023-04-28 05:57:42,102 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/templates/zabbix_proxy.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/templates 2023-04-28 05:57:42,102 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:42,103 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/vars/Amazon.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:42,103 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/vars/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:42,103 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/vars/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:42,103 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/vars/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:42,104 root INFO copying ansible_collections/community/zabbix/roles/zabbix_proxy/vars/zabbix.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:42,104 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server 2023-04-28 05:57:42,104 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/README.md -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server 2023-04-28 05:57:42,104 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/requirements.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server 2023-04-28 05:57:42,104 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server/defaults 2023-04-28 05:57:42,105 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/defaults/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/defaults 2023-04-28 05:57:42,105 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server/files 2023-04-28 05:57:42,105 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/files/install_semodule.bsx -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/files 2023-04-28 05:57:42,105 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server/handlers 2023-04-28 05:57:42,105 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/handlers/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/handlers 2023-04-28 05:57:42,105 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server/meta 2023-04-28 05:57:42,106 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/meta/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/meta 2023-04-28 05:57:42,106 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,106 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/tasks/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,106 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/tasks/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,106 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/tasks/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,107 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/tasks/mysql.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,107 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/tasks/postgresql.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,107 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/tasks/scripts.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,107 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/tasks/selinux.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:42,108 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server/templates 2023-04-28 05:57:42,108 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/templates/zabbix_server.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/templates 2023-04-28 05:57:42,108 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:42,108 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/vars/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:42,108 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/vars/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:42,109 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/vars/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:42,109 root INFO copying ansible_collections/community/zabbix/roles/zabbix_server/vars/zabbix.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:42,109 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_web 2023-04-28 05:57:42,109 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/README.md -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web 2023-04-28 05:57:42,109 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_web/defaults 2023-04-28 05:57:42,110 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/defaults/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/defaults 2023-04-28 05:57:42,110 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_web/handlers 2023-04-28 05:57:42,110 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/handlers/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/handlers 2023-04-28 05:57:42,110 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_web/meta 2023-04-28 05:57:42,110 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/meta/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/meta 2023-04-28 05:57:42,110 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,111 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,111 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,111 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/access.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,111 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,112 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache_Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,112 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache_RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,112 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/main.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,112 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/nginx.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,112 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/php_Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,113 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/tasks/selinux.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:42,113 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:42,113 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/templates/apache_vhost.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:42,113 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/templates/nginx_vhost.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:42,113 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/templates/php-fpm.conf.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:42,114 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/templates/zabbix.conf.php.j2 -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:42,114 root INFO creating build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,114 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-10.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,114 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-11.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,114 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-8.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,115 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-9.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,115 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,115 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-7.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,115 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-8.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,116 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-9.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,116 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,116 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-18.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,116 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-20.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,116 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-22.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,117 root INFO copying ansible_collections/community/zabbix/roles/zabbix_web/vars/zabbix.yml -> build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:42,117 root INFO creating build/lib/ansible_collections/community/zabbix/scripts 2023-04-28 05:57:42,117 root INFO creating build/lib/ansible_collections/community/zabbix/scripts/inventory 2023-04-28 05:57:42,117 root INFO copying ansible_collections/community/zabbix/scripts/inventory/zabbix.ini -> build/lib/ansible_collections/community/zabbix/scripts/inventory 2023-04-28 05:57:42,117 root INFO copying ansible_collections/community/zabbix/scripts/inventory/zabbix.py -> build/lib/ansible_collections/community/zabbix/scripts/inventory 2023-04-28 05:57:42,118 root INFO creating build/lib/ansible_collections/containers 2023-04-28 05:57:42,118 root INFO creating build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,118 root INFO copying ansible_collections/containers/podman/CHANGELOG.rst -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,118 root INFO copying ansible_collections/containers/podman/CODE-OF-CONDUCT.md -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,118 root INFO copying ansible_collections/containers/podman/COPYING -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,119 root INFO copying ansible_collections/containers/podman/FILES.json -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,119 root INFO copying ansible_collections/containers/podman/MANIFEST.json -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,119 root INFO copying ansible_collections/containers/podman/Makefile -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,119 root INFO copying ansible_collections/containers/podman/README.md -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,120 root INFO copying ansible_collections/containers/podman/SECURITY.md -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,120 root INFO copying ansible_collections/containers/podman/ansible-collection-containers-podman.spec -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,120 root INFO copying ansible_collections/containers/podman/galaxy.yml.in -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,120 root INFO copying ansible_collections/containers/podman/setup.cfg -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,120 root INFO copying ansible_collections/containers/podman/setup.py -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,121 root INFO copying ansible_collections/containers/podman/test-requirements.txt -> build/lib/ansible_collections/containers/podman 2023-04-28 05:57:42,121 root INFO creating build/lib/ansible_collections/containers/podman/changelogs 2023-04-28 05:57:42,121 root INFO copying ansible_collections/containers/podman/changelogs/changelog.yaml -> build/lib/ansible_collections/containers/podman/changelogs 2023-04-28 05:57:42,121 root INFO copying ansible_collections/containers/podman/changelogs/config.yaml -> build/lib/ansible_collections/containers/podman/changelogs 2023-04-28 05:57:42,121 root INFO creating build/lib/ansible_collections/containers/podman/meta 2023-04-28 05:57:42,122 root INFO copying ansible_collections/containers/podman/meta/runtime.yml -> build/lib/ansible_collections/containers/podman/meta 2023-04-28 05:57:42,122 root INFO creating build/lib/ansible_collections/containers/podman/plugins 2023-04-28 05:57:42,122 root INFO creating build/lib/ansible_collections/containers/podman/plugins/become 2023-04-28 05:57:42,122 root INFO copying ansible_collections/containers/podman/plugins/become/podman_unshare.py -> build/lib/ansible_collections/containers/podman/plugins/become 2023-04-28 05:57:42,122 root INFO creating build/lib/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:42,122 root INFO copying ansible_collections/containers/podman/plugins/connection/__init__.py -> build/lib/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:42,123 root INFO copying ansible_collections/containers/podman/plugins/connection/buildah.py -> build/lib/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:42,123 root INFO copying ansible_collections/containers/podman/plugins/connection/podman.py -> build/lib/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:42,123 root INFO creating build/lib/ansible_collections/containers/podman/plugins/module_utils 2023-04-28 05:57:42,123 root INFO copying ansible_collections/containers/podman/plugins/module_utils/__init__.py -> build/lib/ansible_collections/containers/podman/plugins/module_utils 2023-04-28 05:57:42,123 root INFO creating build/lib/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:42,124 root INFO copying ansible_collections/containers/podman/plugins/module_utils/podman/__init__.py -> build/lib/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:42,124 root INFO copying ansible_collections/containers/podman/plugins/module_utils/podman/common.py -> build/lib/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:42,124 root INFO copying ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py -> build/lib/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:42,124 root INFO copying ansible_collections/containers/podman/plugins/module_utils/podman/podman_pod_lib.py -> build/lib/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:42,125 root INFO creating build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,125 root INFO copying ansible_collections/containers/podman/plugins/modules/__init__.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,125 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_container.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,125 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_container_info.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,125 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_containers.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,126 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_export.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,126 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_generate_systemd.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,126 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_image.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,126 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_image_info.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,127 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_import.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,127 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_load.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,127 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_login.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,127 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_login_info.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,128 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_logout.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,128 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_network.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,128 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_network_info.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,128 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_play.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,128 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_pod.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,129 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_pod_info.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,129 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_save.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,130 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_secret.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,130 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_tag.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,130 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_volume.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,130 root INFO copying ansible_collections/containers/podman/plugins/modules/podman_volume_info.py -> build/lib/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:42,130 root INFO creating build/lib/ansible_collections/cyberark 2023-04-28 05:57:42,131 root INFO creating build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,131 root INFO copying ansible_collections/cyberark/conjur/CHANGELOG.md -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,131 root INFO copying ansible_collections/cyberark/conjur/CONTRIBUTING.md -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,131 root INFO copying ansible_collections/cyberark/conjur/FILES.json -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,131 root INFO copying ansible_collections/cyberark/conjur/Jenkinsfile -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,132 root INFO copying ansible_collections/cyberark/conjur/LICENSE -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,132 root INFO copying ansible_collections/cyberark/conjur/MANIFEST.json -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,132 root INFO copying ansible_collections/cyberark/conjur/README.md -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,132 root INFO copying ansible_collections/cyberark/conjur/SECURITY.md -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,133 root INFO copying ansible_collections/cyberark/conjur/requirements.txt -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,133 root INFO copying ansible_collections/cyberark/conjur/secrets.yml -> build/lib/ansible_collections/cyberark/conjur 2023-04-28 05:57:42,133 root INFO creating build/lib/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:42,133 root INFO copying ansible_collections/cyberark/conjur/ci/build_release -> build/lib/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:42,133 root INFO copying ansible_collections/cyberark/conjur/ci/parse-changelog.sh -> build/lib/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:42,134 root INFO copying ansible_collections/cyberark/conjur/ci/publish_to_galaxy -> build/lib/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:42,134 root INFO copying ansible_collections/cyberark/conjur/ci/test.sh -> build/lib/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:42,134 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:42,134 root INFO copying ansible_collections/cyberark/conjur/dev/Dockerfile -> build/lib/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:42,134 root INFO copying ansible_collections/cyberark/conjur/dev/Dockerfile_nginx -> build/lib/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:42,135 root INFO copying ansible_collections/cyberark/conjur/dev/ansible.cfg -> build/lib/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:42,135 root INFO copying ansible_collections/cyberark/conjur/dev/docker-compose.yml -> build/lib/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:42,135 root INFO copying ansible_collections/cyberark/conjur/dev/start.sh -> build/lib/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:42,135 root INFO copying ansible_collections/cyberark/conjur/dev/test_unit.sh -> build/lib/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:42,135 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev/playbooks 2023-04-28 05:57:42,136 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev/playbooks/conjur-identity-setup 2023-04-28 05:57:42,136 root INFO copying ansible_collections/cyberark/conjur/dev/playbooks/conjur-identity-setup/conjur_role_playbook.yml -> build/lib/ansible_collections/cyberark/conjur/dev/playbooks/conjur-identity-setup 2023-04-28 05:57:42,136 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:42,136 root INFO copying ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-playbook-v2.yml -> build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:42,136 root INFO copying ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-playbook.yml -> build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:42,137 root INFO copying ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-v2.j2 -> build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:42,137 root INFO copying ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory.j2 -> build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:42,137 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev/policy 2023-04-28 05:57:42,137 root INFO copying ansible_collections/cyberark/conjur/dev/policy/root.yml -> build/lib/ansible_collections/cyberark/conjur/dev/policy 2023-04-28 05:57:42,137 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev/proxy 2023-04-28 05:57:42,137 root INFO copying ansible_collections/cyberark/conjur/dev/proxy/default.conf -> build/lib/ansible_collections/cyberark/conjur/dev/proxy 2023-04-28 05:57:42,138 root INFO copying ansible_collections/cyberark/conjur/dev/proxy/ssl.conf -> build/lib/ansible_collections/cyberark/conjur/dev/proxy 2023-04-28 05:57:42,138 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev/test_app_centos 2023-04-28 05:57:42,138 root INFO copying ansible_collections/cyberark/conjur/dev/test_app_centos/Dockerfile -> build/lib/ansible_collections/cyberark/conjur/dev/test_app_centos 2023-04-28 05:57:42,138 root INFO creating build/lib/ansible_collections/cyberark/conjur/dev/test_app_ubuntu 2023-04-28 05:57:42,138 root INFO copying ansible_collections/cyberark/conjur/dev/test_app_ubuntu/Dockerfile -> build/lib/ansible_collections/cyberark/conjur/dev/test_app_ubuntu 2023-04-28 05:57:42,139 root INFO creating build/lib/ansible_collections/cyberark/conjur/examples 2023-04-28 05:57:42,139 root INFO copying ansible_collections/cyberark/conjur/examples/test.yml -> build/lib/ansible_collections/cyberark/conjur/examples 2023-04-28 05:57:42,139 root INFO creating build/lib/ansible_collections/cyberark/conjur/meta 2023-04-28 05:57:42,139 root INFO copying ansible_collections/cyberark/conjur/meta/runtime.yml -> build/lib/ansible_collections/cyberark/conjur/meta 2023-04-28 05:57:42,139 root INFO creating build/lib/ansible_collections/cyberark/conjur/plugins 2023-04-28 05:57:42,139 root INFO creating build/lib/ansible_collections/cyberark/conjur/plugins/lookup 2023-04-28 05:57:42,140 root INFO copying ansible_collections/cyberark/conjur/plugins/lookup/conjur_variable.py -> build/lib/ansible_collections/cyberark/conjur/plugins/lookup 2023-04-28 05:57:42,140 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles 2023-04-28 05:57:42,140 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity 2023-04-28 05:57:42,140 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/README.md -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity 2023-04-28 05:57:42,140 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/defaults 2023-04-28 05:57:42,140 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/defaults/main.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/defaults 2023-04-28 05:57:42,141 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/meta 2023-04-28 05:57:42,141 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/meta/main.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/meta 2023-04-28 05:57:42,141 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,141 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/identity.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,141 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/identity_check.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,142 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/install.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,142 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/main.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,142 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/summon-conjur.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,142 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/summon.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,142 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/uninstall.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:42,143 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates 2023-04-28 05:57:42,143 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates/conjur.conf.j2 -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates 2023-04-28 05:57:42,143 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates/conjur.identity.j2 -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates 2023-04-28 05:57:42,143 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,143 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.dockerignore -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,144 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/Dockerfile -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,144 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/Dockerfile_nginx -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,144 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/ansible.cfg -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,144 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/docker-compose.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,144 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-playbook-v2.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,145 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-playbook.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,145 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-v2.j2 -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,145 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory.j2 -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,145 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test.sh -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:42,146 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:42,146 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/.gitignore -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:42,146 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/CACHEDIR.TAG -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:42,146 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/README.md -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:42,146 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v 2023-04-28 05:57:42,146 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache 2023-04-28 05:57:42,147 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache/nodeids -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache 2023-04-28 05:57:42,147 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache/stepwise -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache 2023-04-28 05:57:42,147 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit 2023-04-28 05:57:42,147 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit/cleanup-conjur-identity -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit 2023-04-28 05:57:42,147 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit/configure-conjur-identity -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit 2023-04-28 05:57:42,148 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/policy 2023-04-28 05:57:42,148 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/policy/root.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/policy 2023-04-28 05:57:42,148 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy 2023-04-28 05:57:42,148 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy/default.conf -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy 2023-04-28 05:57:42,148 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy/ssl.conf -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy 2023-04-28 05:57:42,149 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_centos 2023-04-28 05:57:42,149 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_centos/Dockerfile -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_centos 2023-04-28 05:57:42,149 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_ubuntu 2023-04-28 05:57:42,149 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_ubuntu/Dockerfile -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_ubuntu 2023-04-28 05:57:42,149 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases 2023-04-28 05:57:42,149 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity 2023-04-28 05:57:42,150 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/playbook.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity 2023-04-28 05:57:42,150 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests 2023-04-28 05:57:42,150 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests/test_default.py -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests 2023-04-28 05:57:42,150 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity 2023-04-28 05:57:42,150 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/playbook.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity 2023-04-28 05:57:42,150 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests 2023-04-28 05:57:42,151 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests/test_default.py -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests 2023-04-28 05:57:42,151 root INFO creating build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/misconfig-conjur-identity 2023-04-28 05:57:42,151 root INFO copying ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/misconfig-conjur-identity/playbook.yml -> build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/misconfig-conjur-identity 2023-04-28 05:57:42,151 root INFO creating build/lib/ansible_collections/cyberark/pas 2023-04-28 05:57:42,151 root INFO copying ansible_collections/cyberark/pas/CONTRIBUTING.md -> build/lib/ansible_collections/cyberark/pas 2023-04-28 05:57:42,152 root INFO copying ansible_collections/cyberark/pas/FILES.json -> build/lib/ansible_collections/cyberark/pas 2023-04-28 05:57:42,152 root INFO copying ansible_collections/cyberark/pas/LICENSE -> build/lib/ansible_collections/cyberark/pas 2023-04-28 05:57:42,152 root INFO copying ansible_collections/cyberark/pas/MANIFEST.json -> build/lib/ansible_collections/cyberark/pas 2023-04-28 05:57:42,152 root INFO copying ansible_collections/cyberark/pas/README.md -> build/lib/ansible_collections/cyberark/pas 2023-04-28 05:57:42,153 root INFO creating build/lib/ansible_collections/cyberark/pas/custom-cred-types 2023-04-28 05:57:42,153 root INFO creating build/lib/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:42,153 root INFO copying ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/README.md -> build/lib/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:42,153 root INFO copying ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/injector.yml -> build/lib/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:42,153 root INFO copying ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/input.yml -> build/lib/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:42,153 root INFO creating build/lib/ansible_collections/cyberark/pas/meta 2023-04-28 05:57:42,154 root INFO copying ansible_collections/cyberark/pas/meta/runtime.yml -> build/lib/ansible_collections/cyberark/pas/meta 2023-04-28 05:57:42,154 root INFO creating build/lib/ansible_collections/cyberark/pas/plugins 2023-04-28 05:57:42,154 root INFO creating build/lib/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:42,154 root INFO copying ansible_collections/cyberark/pas/plugins/modules/cyberark_account.py -> build/lib/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:42,154 root INFO copying ansible_collections/cyberark/pas/plugins/modules/cyberark_authentication.py -> build/lib/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:42,155 root INFO copying ansible_collections/cyberark/pas/plugins/modules/cyberark_credential.py -> build/lib/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:42,155 root INFO copying ansible_collections/cyberark/pas/plugins/modules/cyberark_user.py -> build/lib/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:42,155 root INFO creating build/lib/ansible_collections/cyberark/pas/roles 2023-04-28 05:57:42,155 root INFO creating build/lib/ansible_collections/cyberark/pas/roles/aimprovider 2023-04-28 05:57:42,155 root INFO copying ansible_collections/cyberark/pas/roles/aimprovider/README.md -> build/lib/ansible_collections/cyberark/pas/roles/aimprovider 2023-04-28 05:57:42,156 root INFO creating build/lib/ansible_collections/cyberark/pas/roles/aimprovider/defaults 2023-04-28 05:57:42,156 root INFO copying ansible_collections/cyberark/pas/roles/aimprovider/defaults/main.yml -> build/lib/ansible_collections/cyberark/pas/roles/aimprovider/defaults 2023-04-28 05:57:42,156 root INFO creating build/lib/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:42,156 root INFO copying ansible_collections/cyberark/pas/roles/aimprovider/tasks/installAIMProvider.yml -> build/lib/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:42,156 root INFO copying ansible_collections/cyberark/pas/roles/aimprovider/tasks/main.yml -> build/lib/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:42,157 root INFO copying ansible_collections/cyberark/pas/roles/aimprovider/tasks/uninstallAIMProvider.yml -> build/lib/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:42,157 root INFO creating build/lib/ansible_collections/dellemc 2023-04-28 05:57:42,157 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:42,157 root INFO copying ansible_collections/dellemc/enterprise_sonic/FILES.json -> build/lib/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:42,157 root INFO copying ansible_collections/dellemc/enterprise_sonic/LICENSE -> build/lib/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:42,158 root INFO copying ansible_collections/dellemc/enterprise_sonic/MANIFEST.json -> build/lib/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:42,158 root INFO copying ansible_collections/dellemc/enterprise_sonic/README.md -> build/lib/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:42,158 root INFO copying ansible_collections/dellemc/enterprise_sonic/rebuild.sh -> build/lib/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:42,158 root INFO copying ansible_collections/dellemc/enterprise_sonic/requirements.txt -> build/lib/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:42,159 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:42,159 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:42,159 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/CHANGELOG.rst -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:42,159 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/changelog.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:42,159 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/config.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:42,160 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments 2023-04-28 05:57:42,160 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,160 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/100-prefix_lists-resource-module.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,160 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/101-bgp-prefix_lists.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,160 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/102-playbook-example-updates.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,160 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/103-standard-interface-naming-and-other-bugfixes.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,161 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/105-vxlan-regression-test-fix.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,161 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/2.0.0.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,161 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/53-oc-yang-compliance.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,161 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/58-vxlan-primary-ip.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,162 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/60-bgp-regression-test_fixes.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,162 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/62-bgp-vxlan-primary-ip.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,162 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/63-bgp_af-route_advertise_list.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,162 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/67-bgp_neighbors-auth_pwd-and-neighbor_description.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,162 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/72-bgp_neighbors-add-attributes.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,163 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/76-CLI-command-prompt-answer-fix.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,163 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/78-aaa-regression-fix.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,163 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/81-add-bgp-peer-group-attributes.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,163 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/82-static_routes.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,164 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/85-regression-test-fixes.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,164 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/88-port_breakout-and-execution-environment.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,164 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/90-aaa-and-users-bugfix.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,164 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/98-vlans-description.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,164 root INFO copying ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/99-ntp-resource-module.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:42,165 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/meta 2023-04-28 05:57:42,165 root INFO copying ansible_collections/dellemc/enterprise_sonic/meta/execution-environment.yml -> build/lib/ansible_collections/dellemc/enterprise_sonic/meta 2023-04-28 05:57:42,165 root INFO copying ansible_collections/dellemc/enterprise_sonic/meta/runtime.yml -> build/lib/ansible_collections/dellemc/enterprise_sonic/meta 2023-04-28 05:57:42,165 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks 2023-04-28 05:57:42,165 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric 2023-04-28 05:57:42,165 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/clos-fabric.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric 2023-04-28 05:57:42,166 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/inventory.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric 2023-04-28 05:57:42,166 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:42,166 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/all.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:42,166 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/leaf.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:42,167 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/spine.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:42,167 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/templates 2023-04-28 05:57:42,167 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/templates/clos_fabric_cfg.j2 -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/templates 2023-04-28 05:57:42,167 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,167 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/hosts -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,167 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/interface_naming.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,168 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/patch.txt -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,168 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_aaa.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,168 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_api.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,168 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_bgp.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,169 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_bgp_communities.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,169 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_command.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,169 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_config.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,169 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_facts.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,169 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_interfaces_config.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,170 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_system.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,170 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_vxlans_config.yaml -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,170 root INFO copying ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/src.txt -> build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:42,170 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins 2023-04-28 05:57:42,170 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/action 2023-04-28 05:57:42,171 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/action/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/action 2023-04-28 05:57:42,171 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/action/sonic.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/action 2023-04-28 05:57:42,171 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf 2023-04-28 05:57:42,171 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf 2023-04-28 05:57:42,171 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/sonic.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf 2023-04-28 05:57:42,172 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi 2023-04-28 05:57:42,172 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi 2023-04-28 05:57:42,172 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/sonic.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi 2023-04-28 05:57:42,172 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils 2023-04-28 05:57:42,172 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils 2023-04-28 05:57:42,172 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network 2023-04-28 05:57:42,173 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network 2023-04-28 05:57:42,173 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic 2023-04-28 05:57:42,173 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic 2023-04-28 05:57:42,173 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/sonic.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic 2023-04-28 05:57:42,173 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec 2023-04-28 05:57:42,173 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec 2023-04-28 05:57:42,174 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa 2023-04-28 05:57:42,174 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa 2023-04-28 05:57:42,174 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/aaa.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa 2023-04-28 05:57:42,174 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp 2023-04-28 05:57:42,174 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp 2023-04-28 05:57:42,175 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/bgp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp 2023-04-28 05:57:42,175 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af 2023-04-28 05:57:42,175 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af 2023-04-28 05:57:42,175 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/bgp_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af 2023-04-28 05:57:42,175 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths 2023-04-28 05:57:42,176 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths 2023-04-28 05:57:42,176 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/bgp_as_paths.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths 2023-04-28 05:57:42,176 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities 2023-04-28 05:57:42,176 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities 2023-04-28 05:57:42,176 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/bgp_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities 2023-04-28 05:57:42,177 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities 2023-04-28 05:57:42,177 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities 2023-04-28 05:57:42,177 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/bgp_ext_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities 2023-04-28 05:57:42,177 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors 2023-04-28 05:57:42,177 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors 2023-04-28 05:57:42,177 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/bgp_neighbors.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors 2023-04-28 05:57:42,178 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af 2023-04-28 05:57:42,178 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af 2023-04-28 05:57:42,178 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/bgp_neighbors_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af 2023-04-28 05:57:42,178 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts 2023-04-28 05:57:42,178 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts 2023-04-28 05:57:42,179 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/facts.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts 2023-04-28 05:57:42,179 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces 2023-04-28 05:57:42,179 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces 2023-04-28 05:57:42,179 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces 2023-04-28 05:57:42,179 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces 2023-04-28 05:57:42,180 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces 2023-04-28 05:57:42,180 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces 2023-04-28 05:57:42,180 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces 2023-04-28 05:57:42,180 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces 2023-04-28 05:57:42,180 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces 2023-04-28 05:57:42,180 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces 2023-04-28 05:57:42,181 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces 2023-04-28 05:57:42,181 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag 2023-04-28 05:57:42,181 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag/mclag.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag 2023-04-28 05:57:42,181 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp 2023-04-28 05:57:42,181 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp/ntp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp 2023-04-28 05:57:42,182 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout 2023-04-28 05:57:42,182 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout/port_breakout.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout 2023-04-28 05:57:42,182 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists 2023-04-28 05:57:42,182 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists 2023-04-28 05:57:42,182 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists 2023-04-28 05:57:42,183 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server 2023-04-28 05:57:42,183 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server/radius_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server 2023-04-28 05:57:42,183 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes 2023-04-28 05:57:42,183 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes 2023-04-28 05:57:42,183 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/static_routes.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes 2023-04-28 05:57:42,183 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system 2023-04-28 05:57:42,184 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system 2023-04-28 05:57:42,184 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/system.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system 2023-04-28 05:57:42,184 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server 2023-04-28 05:57:42,184 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server/tacacs_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server 2023-04-28 05:57:42,184 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users 2023-04-28 05:57:42,185 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users/users.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users 2023-04-28 05:57:42,185 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans 2023-04-28 05:57:42,185 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans 2023-04-28 05:57:42,185 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/vlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans 2023-04-28 05:57:42,185 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs 2023-04-28 05:57:42,185 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs/vrfs.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs 2023-04-28 05:57:42,186 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans 2023-04-28 05:57:42,186 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans 2023-04-28 05:57:42,186 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/vxlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans 2023-04-28 05:57:42,186 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config 2023-04-28 05:57:42,186 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config 2023-04-28 05:57:42,187 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa 2023-04-28 05:57:42,187 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa 2023-04-28 05:57:42,187 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/aaa.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa 2023-04-28 05:57:42,187 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp 2023-04-28 05:57:42,187 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp/bgp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp 2023-04-28 05:57:42,188 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af 2023-04-28 05:57:42,188 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af/bgp_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af 2023-04-28 05:57:42,188 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths 2023-04-28 05:57:42,188 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths/bgp_as_paths.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths 2023-04-28 05:57:42,188 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities 2023-04-28 05:57:42,189 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities 2023-04-28 05:57:42,189 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/bgp_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities 2023-04-28 05:57:42,189 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities 2023-04-28 05:57:42,189 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities 2023-04-28 05:57:42,189 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/bgp_ext_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities 2023-04-28 05:57:42,190 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors 2023-04-28 05:57:42,190 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors/bgp_neighbors.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors 2023-04-28 05:57:42,190 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af 2023-04-28 05:57:42,190 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af/bgp_neighbors_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af 2023-04-28 05:57:42,190 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces 2023-04-28 05:57:42,191 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces/interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces 2023-04-28 05:57:42,191 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces 2023-04-28 05:57:42,191 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces 2023-04-28 05:57:42,191 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces 2023-04-28 05:57:42,191 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces 2023-04-28 05:57:42,192 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces 2023-04-28 05:57:42,192 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces 2023-04-28 05:57:42,192 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag 2023-04-28 05:57:42,192 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag/mclag.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag 2023-04-28 05:57:42,192 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp 2023-04-28 05:57:42,192 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp/ntp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp 2023-04-28 05:57:42,193 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout 2023-04-28 05:57:42,193 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout/port_breakout.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout 2023-04-28 05:57:42,193 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists 2023-04-28 05:57:42,193 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists 2023-04-28 05:57:42,193 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists 2023-04-28 05:57:42,194 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server 2023-04-28 05:57:42,194 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server/radius_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server 2023-04-28 05:57:42,194 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes 2023-04-28 05:57:42,194 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes 2023-04-28 05:57:42,194 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/static_routes.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes 2023-04-28 05:57:42,195 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system 2023-04-28 05:57:42,195 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system 2023-04-28 05:57:42,195 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/system.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system 2023-04-28 05:57:42,195 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server 2023-04-28 05:57:42,195 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server/tacacs_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server 2023-04-28 05:57:42,196 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users 2023-04-28 05:57:42,196 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users/users.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users 2023-04-28 05:57:42,196 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans 2023-04-28 05:57:42,196 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans/vlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans 2023-04-28 05:57:42,196 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs 2023-04-28 05:57:42,196 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs/vrfs.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs 2023-04-28 05:57:42,197 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans 2023-04-28 05:57:42,197 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans/vxlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans 2023-04-28 05:57:42,197 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts 2023-04-28 05:57:42,197 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts 2023-04-28 05:57:42,197 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/facts.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts 2023-04-28 05:57:42,198 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa 2023-04-28 05:57:42,198 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa 2023-04-28 05:57:42,198 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/aaa.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa 2023-04-28 05:57:42,198 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp 2023-04-28 05:57:42,198 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp 2023-04-28 05:57:42,199 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/bgp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp 2023-04-28 05:57:42,199 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af 2023-04-28 05:57:42,199 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af 2023-04-28 05:57:42,199 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/bgp_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af 2023-04-28 05:57:42,199 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths 2023-04-28 05:57:42,200 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths 2023-04-28 05:57:42,200 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/bgp_as_paths.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths 2023-04-28 05:57:42,200 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities 2023-04-28 05:57:42,200 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities 2023-04-28 05:57:42,200 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/bgp_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities 2023-04-28 05:57:42,201 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities 2023-04-28 05:57:42,201 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities 2023-04-28 05:57:42,201 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/bgp_ext_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities 2023-04-28 05:57:42,201 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors 2023-04-28 05:57:42,201 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors 2023-04-28 05:57:42,201 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/bgp_neighbors.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors 2023-04-28 05:57:42,202 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af 2023-04-28 05:57:42,202 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af 2023-04-28 05:57:42,202 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/bgp_neighbors_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af 2023-04-28 05:57:42,202 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces 2023-04-28 05:57:42,202 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces 2023-04-28 05:57:42,203 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces 2023-04-28 05:57:42,203 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces 2023-04-28 05:57:42,203 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces 2023-04-28 05:57:42,203 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces 2023-04-28 05:57:42,203 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces 2023-04-28 05:57:42,204 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces 2023-04-28 05:57:42,204 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces 2023-04-28 05:57:42,204 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces 2023-04-28 05:57:42,204 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces 2023-04-28 05:57:42,204 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag 2023-04-28 05:57:42,205 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag/mclag.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag 2023-04-28 05:57:42,205 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp 2023-04-28 05:57:42,205 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp 2023-04-28 05:57:42,205 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/ntp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp 2023-04-28 05:57:42,205 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout 2023-04-28 05:57:42,205 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout/port_breakout.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout 2023-04-28 05:57:42,206 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists 2023-04-28 05:57:42,206 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists 2023-04-28 05:57:42,206 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists 2023-04-28 05:57:42,206 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server 2023-04-28 05:57:42,206 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server/radius_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server 2023-04-28 05:57:42,207 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes 2023-04-28 05:57:42,207 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes 2023-04-28 05:57:42,207 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/static_routes.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes 2023-04-28 05:57:42,207 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system 2023-04-28 05:57:42,207 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system 2023-04-28 05:57:42,208 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/system.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system 2023-04-28 05:57:42,208 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server 2023-04-28 05:57:42,208 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server/tacacs_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server 2023-04-28 05:57:42,208 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users 2023-04-28 05:57:42,208 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users/users.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users 2023-04-28 05:57:42,208 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans 2023-04-28 05:57:42,209 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans 2023-04-28 05:57:42,209 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/vlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans 2023-04-28 05:57:42,209 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs 2023-04-28 05:57:42,209 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs/vrfs.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs 2023-04-28 05:57:42,209 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans 2023-04-28 05:57:42,210 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans 2023-04-28 05:57:42,210 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/vxlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans 2023-04-28 05:57:42,210 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:42,210 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:42,210 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/bgp_utils.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:42,211 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/interfaces_util.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:42,211 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/utils.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:42,211 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,211 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,211 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_aaa.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,212 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_api.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,212 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,212 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,212 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_as_paths.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,213 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,213 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_ext_communities.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,213 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_neighbors.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,213 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_neighbors_af.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,214 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_command.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,214 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_config.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,214 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_facts.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,214 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,214 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_l2_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,215 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_l3_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,215 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_lag_interfaces.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,215 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_mclag.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,215 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_ntp.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,216 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_port_breakout.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,216 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_prefix_lists.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,216 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_radius_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,216 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_static_routes.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,216 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_system.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,217 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_tacacs_server.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,217 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_users.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,217 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,217 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vrfs.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,218 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vxlans.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:42,218 root INFO creating build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/terminal 2023-04-28 05:57:42,218 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/terminal/__init__.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/terminal 2023-04-28 05:57:42,218 root INFO copying ansible_collections/dellemc/enterprise_sonic/plugins/terminal/sonic.py -> build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/terminal 2023-04-28 05:57:42,218 root INFO creating build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,219 root INFO copying ansible_collections/dellemc/openmanage/CHANGELOG.rst -> build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,219 root INFO copying ansible_collections/dellemc/openmanage/FILES.json -> build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,219 root INFO copying ansible_collections/dellemc/openmanage/LICENSE -> build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,219 root INFO copying ansible_collections/dellemc/openmanage/MANIFEST.json -> build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,220 root INFO copying ansible_collections/dellemc/openmanage/README.md -> build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,220 root INFO copying ansible_collections/dellemc/openmanage/requirements.txt -> build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,220 root INFO copying ansible_collections/dellemc/openmanage/requirements.yml -> build/lib/ansible_collections/dellemc/openmanage 2023-04-28 05:57:42,220 root INFO creating build/lib/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:42,220 root INFO copying ansible_collections/dellemc/openmanage/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:42,221 root INFO copying ansible_collections/dellemc/openmanage/changelogs/changelog.yaml -> build/lib/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:42,221 root INFO copying ansible_collections/dellemc/openmanage/changelogs/config.yaml -> build/lib/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:42,221 root INFO creating build/lib/ansible_collections/dellemc/openmanage/meta 2023-04-28 05:57:42,221 root INFO copying ansible_collections/dellemc/openmanage/meta/execution-environment.yml -> build/lib/ansible_collections/dellemc/openmanage/meta 2023-04-28 05:57:42,222 root INFO copying ansible_collections/dellemc/openmanage/meta/runtime.yml -> build/lib/ansible_collections/dellemc/openmanage/meta 2023-04-28 05:57:42,222 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks 2023-04-28 05:57:42,222 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,222 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/dellemc_idrac_storage_volume.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,222 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_attributes.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,223 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_bios.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,223 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_boot.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,223 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_boot_virtual_media_workflow.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,223 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_certificates.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,223 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_firmware.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,224 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_firmware_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,224 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_job_status_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,224 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_jobs.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,224 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_logs.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,225 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_status_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,225 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_os_deployment.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,225 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_redfish_storage_controller.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,225 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_redfish_storage_controller_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,225 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_reset.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,226 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_reset_result_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,226 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_server_config_profile.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,226 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_syslog.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,226 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_system_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,226 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_user.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,227 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_virtual_media.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:42,227 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,227 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_configure_idrac_eventing.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,227 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_configure_idrac_services.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,228 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_get_firmware_inventory.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,228 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_get_system_inventory.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,228 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_idrac_lc_attributes.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,228 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_system_lockdown_mode.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,228 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/idrac_network.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,229 root INFO copying ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/idrac_timezone_ntp.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:42,229 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,229 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_active_directory.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,229 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_chassis_slots.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,229 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_group.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,230 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,230 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_local_access_configuration.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,230 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_location.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,230 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_mgmt_network.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,230 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_network_services.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,231 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_power_settings.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,231 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_quick_deploy.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,231 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_devices.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,231 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_diagnostics.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,232 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_discovery.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,232 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_domain_user_groups.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,232 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_group_device_action.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,232 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_groups.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,232 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_identity_pool.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,233 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_job_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,233 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_port_breakout.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,233 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_port_breakout_job_traking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,233 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_vlan.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,234 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_vlan_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,234 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profile_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,234 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profile_workflow.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,234 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profiles.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,234 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_smart_fabric.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,235 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_smart_fabric_uplink.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,235 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/ome_template_identity_pool.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:42,235 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,235 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_alerts_smtp.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,235 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_alerts_syslog.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,236 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_certificate.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,236 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_console_preferences.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,236 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_address.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,236 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_address_with_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,237 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_proxy.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,237 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_settings.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,237 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_time.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,237 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_time_zone_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,237 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_webserver.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,238 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_webserver_port_changed_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,238 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_security_settings.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:42,238 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:42,238 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_baseline.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:42,238 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_baseline_workflow.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:42,239 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:42,239 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware 2023-04-28 05:57:42,239 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/ome_firmware.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware 2023-04-28 05:57:42,239 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/ome_firmware_with_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware 2023-04-28 05:57:42,239 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:42,240 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:42,240 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_compliance_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:42,240 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_compliance_info_filters.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:42,240 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:42,241 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering 2023-04-28 05:57:42,241 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering/component_complaince_report_with_baseline.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering 2023-04-28 05:57:42,241 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering/component_complaince_report_with_devices.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering 2023-04-28 05:57:42,241 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/catalog 2023-04-28 05:57:42,241 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/firmware/catalog/ome_firmware_catalog.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/catalog 2023-04-28 05:57:42,241 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate 2023-04-28 05:57:42,242 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/powerstate/ome_powerstate.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate 2023-04-28 05:57:42,242 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/powerstate/ome_powerstate_with_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate 2023-04-28 05:57:42,242 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:42,242 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:42,242 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_assign_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:42,243 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_migrate_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:42,243 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_unassign_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:42,243 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,243 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,243 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_create_modify_lcd_display.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,244 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,244 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_info_with_filter.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,244 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_lcd_display_string_deploy.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,244 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_network_vlan.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,245 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_with_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:42,245 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/user 2023-04-28 05:57:42,245 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/user/ome_user.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/user 2023-04-28 05:57:42,245 root INFO copying ansible_collections/dellemc/openmanage/playbooks/ome/user/ome_user_info.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/user 2023-04-28 05:57:42,245 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish 2023-04-28 05:57:42,245 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/redfish_event_subscription.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish 2023-04-28 05:57:42,246 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/redfish_powerstate.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish 2023-04-28 05:57:42,246 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:42,246 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:42,246 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware_from_http_jobtracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:42,247 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware_from_local_jobtracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:42,247 root INFO creating build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:42,247 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:42,247 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_create_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:42,247 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_delete_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:42,248 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_initialize_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:42,248 root INFO copying ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_modify_job_tracking.yml -> build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:42,248 root INFO creating build/lib/ansible_collections/dellemc/openmanage/plugins 2023-04-28 05:57:42,248 root INFO copying ansible_collections/dellemc/openmanage/plugins/README.md -> build/lib/ansible_collections/dellemc/openmanage/plugins 2023-04-28 05:57:42,248 root INFO creating build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,248 root INFO copying ansible_collections/dellemc/openmanage/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,249 root INFO copying ansible_collections/dellemc/openmanage/plugins/doc_fragments/idrac_auth_options.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,249 root INFO copying ansible_collections/dellemc/openmanage/plugins/doc_fragments/network_share_options.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,249 root INFO copying ansible_collections/dellemc/openmanage/plugins/doc_fragments/ome_auth_options.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,249 root INFO copying ansible_collections/dellemc/openmanage/plugins/doc_fragments/omem_auth_options.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,250 root INFO copying ansible_collections/dellemc/openmanage/plugins/doc_fragments/oment_auth_options.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,250 root INFO copying ansible_collections/dellemc/openmanage/plugins/doc_fragments/redfish_auth_options.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:42,250 root INFO creating build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:42,250 root INFO copying ansible_collections/dellemc/openmanage/plugins/module_utils/__init__.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:42,250 root INFO copying ansible_collections/dellemc/openmanage/plugins/module_utils/dellemc_idrac.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:42,251 root INFO copying ansible_collections/dellemc/openmanage/plugins/module_utils/idrac_redfish.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:42,251 root INFO copying ansible_collections/dellemc/openmanage/plugins/module_utils/ome.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:42,251 root INFO copying ansible_collections/dellemc/openmanage/plugins/module_utils/redfish.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:42,251 root INFO copying ansible_collections/dellemc/openmanage/plugins/module_utils/utils.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:42,252 root INFO creating build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,252 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/__init__.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,252 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/dellemc_configure_idrac_eventing.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,252 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/dellemc_configure_idrac_services.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,252 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/dellemc_get_firmware_inventory.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,253 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/dellemc_get_system_inventory.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,253 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/dellemc_idrac_lc_attributes.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,253 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/dellemc_idrac_storage_volume.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,253 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/dellemc_system_lockdown_mode.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,253 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_attributes.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,254 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_bios.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,254 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_boot.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,255 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_certificates.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,255 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_firmware.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,255 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_firmware_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,255 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_job_status_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,256 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_jobs.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,256 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_logs.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,256 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_status_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,256 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_network.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,256 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_os_deployment.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,257 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_redfish_storage_controller.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,257 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_reset.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,257 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_server_config_profile.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,257 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_syslog.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,258 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_system_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,258 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_timezone_ntp.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,258 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_user.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,258 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/idrac_virtual_media.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,259 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_active_directory.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,259 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_alerts_smtp.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,259 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_alerts_syslog.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,259 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_certificate.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,260 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_console_preferences.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,260 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_address.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,260 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_proxy.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,260 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_settings.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,261 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_time.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,261 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_webserver.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,261 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_application_security_settings.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,261 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_chassis_slots.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,262 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_configuration_compliance_baseline.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,262 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_configuration_compliance_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,262 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_group.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,262 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,263 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_local_access_configuration.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,263 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_location.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,263 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_mgmt_network.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,263 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_network_services.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,264 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_power_settings.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,264 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_device_quick_deploy.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,264 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_devices.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,264 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_diagnostics.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,264 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_discovery.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,265 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_domain_user_groups.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,265 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,265 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,265 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline_compliance_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,266 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,266 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_catalog.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,266 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_groups.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,266 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_identity_pool.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,267 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_job_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,267 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_network_port_breakout.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,267 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_network_vlan.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,267 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_network_vlan_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,268 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_powerstate.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,268 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_profile.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,268 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_server_interface_profile_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,268 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_server_interface_profiles.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,269 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_smart_fabric.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,269 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_smart_fabric_uplink.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,269 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_template.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,269 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_template_identity_pool.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,270 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_template_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,270 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_template_network_vlan.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,270 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_user.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,270 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/ome_user_info.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,271 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/redfish_event_subscription.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,271 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/redfish_firmware.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,271 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/redfish_powerstate.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,271 root INFO copying ansible_collections/dellemc/openmanage/plugins/modules/redfish_storage_volume.py -> build/lib/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:42,272 root INFO creating build/lib/ansible_collections/dellemc/os10 2023-04-28 05:57:42,272 root INFO copying ansible_collections/dellemc/os10/FILES.json -> build/lib/ansible_collections/dellemc/os10 2023-04-28 05:57:42,272 root INFO copying ansible_collections/dellemc/os10/LICENSE -> build/lib/ansible_collections/dellemc/os10 2023-04-28 05:57:42,273 root INFO copying ansible_collections/dellemc/os10/MANIFEST.json -> build/lib/ansible_collections/dellemc/os10 2023-04-28 05:57:42,273 root INFO copying ansible_collections/dellemc/os10/README.md -> build/lib/ansible_collections/dellemc/os10 2023-04-28 05:57:42,273 root INFO creating build/lib/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:42,273 root INFO copying ansible_collections/dellemc/os10/changelogs/CHANGELOG.rst -> build/lib/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:42,273 root INFO copying ansible_collections/dellemc/os10/changelogs/changelog.yaml -> build/lib/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:42,274 root INFO copying ansible_collections/dellemc/os10/changelogs/config.yaml -> build/lib/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:42,274 root INFO creating build/lib/ansible_collections/dellemc/os10/meta 2023-04-28 05:57:42,274 root INFO copying ansible_collections/dellemc/os10/meta/runtime.yml -> build/lib/ansible_collections/dellemc/os10/meta 2023-04-28 05:57:42,274 root INFO creating build/lib/ansible_collections/dellemc/os10/playbooks 2023-04-28 05:57:42,274 root INFO creating build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,274 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/README.md -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,275 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/datacenter.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,275 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,275 root INFO creating build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:42,275 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars/all -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:42,275 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars/spine.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:42,276 root INFO creating build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,276 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf1.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,276 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf2.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,276 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf3.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,276 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf4.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,277 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/spine1.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,277 root INFO copying ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/spine2.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,277 root INFO creating build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:42,277 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/README.md -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:42,277 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/datacenter.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:42,278 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:42,278 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/vxlan_evpn_topology.png -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:42,278 root INFO creating build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:42,278 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/prim-vtep1.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:42,279 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/prim-vtep2.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:42,279 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/sec-vtep1.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:42,279 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/sec-vtep2.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:42,279 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/spine1.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:42,279 root INFO copying ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/spine2.yaml -> build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:42,280 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins 2023-04-28 05:57:42,280 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins/action 2023-04-28 05:57:42,280 root INFO copying ansible_collections/dellemc/os10/plugins/action/os10.py -> build/lib/ansible_collections/dellemc/os10/plugins/action 2023-04-28 05:57:42,280 root INFO copying ansible_collections/dellemc/os10/plugins/action/textfsm_parser.py -> build/lib/ansible_collections/dellemc/os10/plugins/action 2023-04-28 05:57:42,280 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins/cliconf 2023-04-28 05:57:42,281 root INFO copying ansible_collections/dellemc/os10/plugins/cliconf/os10.py -> build/lib/ansible_collections/dellemc/os10/plugins/cliconf 2023-04-28 05:57:42,281 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins/doc_fragments 2023-04-28 05:57:42,281 root INFO copying ansible_collections/dellemc/os10/plugins/doc_fragments/os10.py -> build/lib/ansible_collections/dellemc/os10/plugins/doc_fragments 2023-04-28 05:57:42,281 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins/module_utils 2023-04-28 05:57:42,281 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:42,281 root INFO copying ansible_collections/dellemc/os10/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:42,282 root INFO copying ansible_collections/dellemc/os10/plugins/module_utils/network/base_network_show.py -> build/lib/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:42,282 root INFO copying ansible_collections/dellemc/os10/plugins/module_utils/network/os10.py -> build/lib/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:42,282 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,282 root INFO copying ansible_collections/dellemc/os10/plugins/modules/__init__.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,282 root INFO copying ansible_collections/dellemc/os10/plugins/modules/base_xml_to_dict.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,283 root INFO copying ansible_collections/dellemc/os10/plugins/modules/bgp_validate.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,283 root INFO copying ansible_collections/dellemc/os10/plugins/modules/mtu_validate.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,283 root INFO copying ansible_collections/dellemc/os10/plugins/modules/os10_command.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,283 root INFO copying ansible_collections/dellemc/os10/plugins/modules/os10_config.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,283 root INFO copying ansible_collections/dellemc/os10/plugins/modules/os10_facts.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,284 root INFO copying ansible_collections/dellemc/os10/plugins/modules/show_system_network_summary.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,284 root INFO copying ansible_collections/dellemc/os10/plugins/modules/vlt_validate.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,284 root INFO copying ansible_collections/dellemc/os10/plugins/modules/wiring_validate.py -> build/lib/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:42,284 root INFO creating build/lib/ansible_collections/dellemc/os10/plugins/terminal 2023-04-28 05:57:42,284 root INFO copying ansible_collections/dellemc/os10/plugins/terminal/os10.py -> build/lib/ansible_collections/dellemc/os10/plugins/terminal 2023-04-28 05:57:42,285 root INFO creating build/lib/ansible_collections/dellemc/os10/roles 2023-04-28 05:57:42,285 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa 2023-04-28 05:57:42,285 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa 2023-04-28 05:57:42,285 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa 2023-04-28 05:57:42,285 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/defaults 2023-04-28 05:57:42,286 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/defaults 2023-04-28 05:57:42,286 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/handlers 2023-04-28 05:57:42,286 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/handlers 2023-04-28 05:57:42,286 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/meta 2023-04-28 05:57:42,286 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/meta 2023-04-28 05:57:42,287 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tasks 2023-04-28 05:57:42,287 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tasks 2023-04-28 05:57:42,287 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/templates 2023-04-28 05:57:42,287 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/templates/os10_aaa.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/templates 2023-04-28 05:57:42,287 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:42,287 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:42,288 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:42,288 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:42,288 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/vars 2023-04-28 05:57:42,288 root INFO copying ansible_collections/dellemc/os10/roles/os10_aaa/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/vars 2023-04-28 05:57:42,288 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl 2023-04-28 05:57:42,288 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl 2023-04-28 05:57:42,289 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl 2023-04-28 05:57:42,289 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl/defaults 2023-04-28 05:57:42,289 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/defaults 2023-04-28 05:57:42,289 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl/handlers 2023-04-28 05:57:42,289 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/handlers 2023-04-28 05:57:42,290 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl/meta 2023-04-28 05:57:42,290 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/meta 2023-04-28 05:57:42,290 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tasks 2023-04-28 05:57:42,290 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tasks 2023-04-28 05:57:42,290 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl/templates 2023-04-28 05:57:42,291 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/templates/os10_acl.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/templates 2023-04-28 05:57:42,291 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:42,291 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:42,291 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:42,291 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:42,292 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_acl/vars 2023-04-28 05:57:42,292 root INFO copying ansible_collections/dellemc/os10/roles/os10_acl/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_acl/vars 2023-04-28 05:57:42,292 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd 2023-04-28 05:57:42,292 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd 2023-04-28 05:57:42,292 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd 2023-04-28 05:57:42,293 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/defaults 2023-04-28 05:57:42,293 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/defaults 2023-04-28 05:57:42,293 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/handlers 2023-04-28 05:57:42,293 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/handlers 2023-04-28 05:57:42,293 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/meta 2023-04-28 05:57:42,293 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/meta 2023-04-28 05:57:42,294 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tasks 2023-04-28 05:57:42,294 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tasks 2023-04-28 05:57:42,294 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/templates 2023-04-28 05:57:42,294 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/templates/os10_bfd.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/templates 2023-04-28 05:57:42,294 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:42,295 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:42,295 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:42,295 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:42,295 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/vars 2023-04-28 05:57:42,295 root INFO copying ansible_collections/dellemc/os10/roles/os10_bfd/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/vars 2023-04-28 05:57:42,296 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp 2023-04-28 05:57:42,296 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp 2023-04-28 05:57:42,296 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp 2023-04-28 05:57:42,296 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/defaults 2023-04-28 05:57:42,296 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/defaults 2023-04-28 05:57:42,297 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/handlers 2023-04-28 05:57:42,297 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/handlers 2023-04-28 05:57:42,297 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/meta 2023-04-28 05:57:42,297 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/meta 2023-04-28 05:57:42,297 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tasks 2023-04-28 05:57:42,297 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tasks 2023-04-28 05:57:42,298 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/templates 2023-04-28 05:57:42,298 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/templates/os10_bgp.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/templates 2023-04-28 05:57:42,298 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:42,298 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:42,298 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:42,299 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:42,299 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/vars 2023-04-28 05:57:42,299 root INFO copying ansible_collections/dellemc/os10/roles/os10_bgp/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/vars 2023-04-28 05:57:42,299 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config 2023-04-28 05:57:42,299 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config 2023-04-28 05:57:42,300 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config 2023-04-28 05:57:42,300 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/defaults 2023-04-28 05:57:42,300 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/defaults 2023-04-28 05:57:42,300 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/handlers 2023-04-28 05:57:42,300 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/handlers 2023-04-28 05:57:42,301 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/meta 2023-04-28 05:57:42,301 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/meta 2023-04-28 05:57:42,301 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tasks 2023-04-28 05:57:42,301 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tasks 2023-04-28 05:57:42,301 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/templates 2023-04-28 05:57:42,301 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/templates/leaf1.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/templates 2023-04-28 05:57:42,302 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:42,302 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/tests/inventory -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:42,302 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/tests/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:42,302 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/tests/test.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:42,302 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/vars 2023-04-28 05:57:42,302 root INFO copying ansible_collections/dellemc/os10/roles/os10_copy_config/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/vars 2023-04-28 05:57:42,303 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns 2023-04-28 05:57:42,303 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns 2023-04-28 05:57:42,303 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns 2023-04-28 05:57:42,303 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns/defaults 2023-04-28 05:57:42,303 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/defaults 2023-04-28 05:57:42,304 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns/handlers 2023-04-28 05:57:42,304 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/handlers 2023-04-28 05:57:42,304 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns/meta 2023-04-28 05:57:42,304 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/meta 2023-04-28 05:57:42,304 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tasks 2023-04-28 05:57:42,305 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tasks 2023-04-28 05:57:42,305 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns/templates 2023-04-28 05:57:42,305 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/templates/os10_dns.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/templates 2023-04-28 05:57:42,305 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:42,305 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:42,305 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:42,306 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:42,306 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_dns/vars 2023-04-28 05:57:42,306 root INFO copying ansible_collections/dellemc/os10/roles/os10_dns/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_dns/vars 2023-04-28 05:57:42,306 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp 2023-04-28 05:57:42,306 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp 2023-04-28 05:57:42,307 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp 2023-04-28 05:57:42,307 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/defaults 2023-04-28 05:57:42,307 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/defaults 2023-04-28 05:57:42,307 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/handlers 2023-04-28 05:57:42,307 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/handlers 2023-04-28 05:57:42,308 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/meta 2023-04-28 05:57:42,308 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/meta 2023-04-28 05:57:42,308 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tasks 2023-04-28 05:57:42,308 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tasks 2023-04-28 05:57:42,308 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/templates 2023-04-28 05:57:42,308 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/templates/os10_ecmp.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/templates 2023-04-28 05:57:42,309 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:42,309 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:42,309 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:42,309 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:42,309 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/vars 2023-04-28 05:57:42,310 root INFO copying ansible_collections/dellemc/os10/roles/os10_ecmp/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/vars 2023-04-28 05:57:42,310 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary 2023-04-28 05:57:42,310 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary 2023-04-28 05:57:42,310 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary 2023-04-28 05:57:42,310 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/meta 2023-04-28 05:57:42,311 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/meta 2023-04-28 05:57:42,311 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tasks 2023-04-28 05:57:42,311 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tasks 2023-04-28 05:57:42,311 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:42,311 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:42,311 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:42,312 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/test.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:42,312 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:42,312 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site1-spine1 -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:42,312 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site1-spine2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:42,312 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site2-spine1 -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:42,313 root INFO copying ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site2-spine2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:42,313 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor 2023-04-28 05:57:42,313 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor 2023-04-28 05:57:42,313 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor 2023-04-28 05:57:42,314 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/defaults 2023-04-28 05:57:42,314 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/defaults 2023-04-28 05:57:42,314 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/handlers 2023-04-28 05:57:42,314 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/handlers 2023-04-28 05:57:42,314 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/meta 2023-04-28 05:57:42,314 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/meta 2023-04-28 05:57:42,315 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tasks 2023-04-28 05:57:42,315 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tasks 2023-04-28 05:57:42,315 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/templates 2023-04-28 05:57:42,315 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/templates/os10_flow_monitor.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/templates 2023-04-28 05:57:42,315 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:42,315 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:42,316 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:42,316 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:42,316 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/vars 2023-04-28 05:57:42,316 root INFO copying ansible_collections/dellemc/os10/roles/os10_flow_monitor/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/vars 2023-04-28 05:57:42,316 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade 2023-04-28 05:57:42,317 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade 2023-04-28 05:57:42,317 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade 2023-04-28 05:57:42,317 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/defaults 2023-04-28 05:57:42,317 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/defaults 2023-04-28 05:57:42,317 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/handlers 2023-04-28 05:57:42,318 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/handlers 2023-04-28 05:57:42,318 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/meta 2023-04-28 05:57:42,318 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/meta 2023-04-28 05:57:42,318 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tasks 2023-04-28 05:57:42,318 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tasks 2023-04-28 05:57:42,318 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:42,319 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/inventory -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:42,319 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:42,319 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/test.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:42,319 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/vars 2023-04-28 05:57:42,319 root INFO copying ansible_collections/dellemc/os10/roles/os10_image_upgrade/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/vars 2023-04-28 05:57:42,320 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface 2023-04-28 05:57:42,320 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface 2023-04-28 05:57:42,320 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface 2023-04-28 05:57:42,320 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface/defaults 2023-04-28 05:57:42,320 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/defaults 2023-04-28 05:57:42,321 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface/handlers 2023-04-28 05:57:42,321 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/handlers 2023-04-28 05:57:42,321 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface/meta 2023-04-28 05:57:42,321 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/meta 2023-04-28 05:57:42,321 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tasks 2023-04-28 05:57:42,321 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tasks 2023-04-28 05:57:42,322 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface/templates 2023-04-28 05:57:42,322 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/templates/os10_interface.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/templates 2023-04-28 05:57:42,322 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:42,322 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:42,322 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:42,323 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:42,323 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_interface/vars 2023-04-28 05:57:42,323 root INFO copying ansible_collections/dellemc/os10/roles/os10_interface/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_interface/vars 2023-04-28 05:57:42,323 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag 2023-04-28 05:57:42,323 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag 2023-04-28 05:57:42,324 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag 2023-04-28 05:57:42,324 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag/defaults 2023-04-28 05:57:42,324 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/defaults 2023-04-28 05:57:42,324 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag/handlers 2023-04-28 05:57:42,324 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/handlers 2023-04-28 05:57:42,325 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag/meta 2023-04-28 05:57:42,325 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/meta 2023-04-28 05:57:42,325 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tasks 2023-04-28 05:57:42,325 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tasks 2023-04-28 05:57:42,325 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag/templates 2023-04-28 05:57:42,325 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/templates/os10_lag.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/templates 2023-04-28 05:57:42,326 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:42,326 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:42,326 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:42,326 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:42,326 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lag/vars 2023-04-28 05:57:42,327 root INFO copying ansible_collections/dellemc/os10/roles/os10_lag/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lag/vars 2023-04-28 05:57:42,327 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp 2023-04-28 05:57:42,327 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp 2023-04-28 05:57:42,327 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp 2023-04-28 05:57:42,327 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/defaults 2023-04-28 05:57:42,327 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/defaults 2023-04-28 05:57:42,328 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/handlers 2023-04-28 05:57:42,328 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/handlers 2023-04-28 05:57:42,328 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/meta 2023-04-28 05:57:42,328 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/meta 2023-04-28 05:57:42,328 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tasks 2023-04-28 05:57:42,329 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tasks 2023-04-28 05:57:42,329 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/templates 2023-04-28 05:57:42,329 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/templates/os10_lldp.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/templates 2023-04-28 05:57:42,329 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:42,329 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:42,329 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:42,330 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:42,330 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/vars 2023-04-28 05:57:42,330 root INFO copying ansible_collections/dellemc/os10/roles/os10_lldp/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/vars 2023-04-28 05:57:42,330 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging 2023-04-28 05:57:42,330 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging 2023-04-28 05:57:42,331 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging 2023-04-28 05:57:42,331 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging/defaults 2023-04-28 05:57:42,331 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/defaults 2023-04-28 05:57:42,331 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging/handlers 2023-04-28 05:57:42,331 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/handlers 2023-04-28 05:57:42,332 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging/meta 2023-04-28 05:57:42,332 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/meta 2023-04-28 05:57:42,332 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tasks 2023-04-28 05:57:42,332 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tasks 2023-04-28 05:57:42,332 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging/templates 2023-04-28 05:57:42,332 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/templates/os10_logging.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/templates 2023-04-28 05:57:42,333 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:42,333 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:42,333 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:42,333 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:42,333 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_logging/vars 2023-04-28 05:57:42,334 root INFO copying ansible_collections/dellemc/os10/roles/os10_logging/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_logging/vars 2023-04-28 05:57:42,334 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation 2023-04-28 05:57:42,334 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation 2023-04-28 05:57:42,334 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation 2023-04-28 05:57:42,334 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/meta 2023-04-28 05:57:42,335 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/meta 2023-04-28 05:57:42,335 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:42,335 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/bgp_validation.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:42,335 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:42,335 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/mtu_validation.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:42,336 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/vlt_validation.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:42,336 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/wiring_validation.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:42,336 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:42,336 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:42,336 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:42,337 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:42,337 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/group_vars 2023-04-28 05:57:42,337 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/group_vars/all -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/group_vars 2023-04-28 05:57:42,337 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:42,337 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site1-spine1 -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:42,338 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site1-spine2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:42,338 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site2-spine1 -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:42,338 root INFO copying ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site2-spine2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:42,338 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp 2023-04-28 05:57:42,338 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp 2023-04-28 05:57:42,339 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp 2023-04-28 05:57:42,339 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/defaults 2023-04-28 05:57:42,339 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/defaults 2023-04-28 05:57:42,339 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/handlers 2023-04-28 05:57:42,339 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/handlers 2023-04-28 05:57:42,340 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/meta 2023-04-28 05:57:42,340 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/meta 2023-04-28 05:57:42,340 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tasks 2023-04-28 05:57:42,340 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tasks 2023-04-28 05:57:42,340 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/templates 2023-04-28 05:57:42,340 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/templates/os10_ntp.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/templates 2023-04-28 05:57:42,341 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/templates/os10_ntp_vrf.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/templates 2023-04-28 05:57:42,341 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:42,341 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/tests/inventory -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:42,341 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:42,341 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/tests/test.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:42,342 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/vars 2023-04-28 05:57:42,342 root INFO copying ansible_collections/dellemc/os10/roles/os10_ntp/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/vars 2023-04-28 05:57:42,342 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list 2023-04-28 05:57:42,342 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list 2023-04-28 05:57:42,342 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list 2023-04-28 05:57:42,343 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/defaults 2023-04-28 05:57:42,343 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/defaults 2023-04-28 05:57:42,343 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/handlers 2023-04-28 05:57:42,343 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/handlers 2023-04-28 05:57:42,343 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta 2023-04-28 05:57:42,343 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/meta/.galaxy_install_info -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta 2023-04-28 05:57:42,344 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta 2023-04-28 05:57:42,344 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tasks 2023-04-28 05:57:42,344 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tasks 2023-04-28 05:57:42,344 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/templates 2023-04-28 05:57:42,344 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/templates/os10_prefix_list.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/templates 2023-04-28 05:57:42,345 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:42,345 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:42,345 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:42,345 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:42,345 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/vars 2023-04-28 05:57:42,345 root INFO copying ansible_collections/dellemc/os10/roles/os10_prefix_list/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/vars 2023-04-28 05:57:42,346 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos 2023-04-28 05:57:42,346 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos 2023-04-28 05:57:42,346 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos 2023-04-28 05:57:42,346 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos/defaults 2023-04-28 05:57:42,346 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/defaults 2023-04-28 05:57:42,347 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos/handlers 2023-04-28 05:57:42,347 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/handlers 2023-04-28 05:57:42,347 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos/meta 2023-04-28 05:57:42,347 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/meta 2023-04-28 05:57:42,347 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tasks 2023-04-28 05:57:42,347 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tasks 2023-04-28 05:57:42,348 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos/templates 2023-04-28 05:57:42,348 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/templates/os10_qos.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/templates 2023-04-28 05:57:42,348 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:42,348 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/tests/inventory -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:42,348 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:42,349 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/tests/test.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:42,349 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_qos/vars 2023-04-28 05:57:42,349 root INFO copying ansible_collections/dellemc/os10/roles/os10_qos/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_qos/vars 2023-04-28 05:57:42,349 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard 2023-04-28 05:57:42,349 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard 2023-04-28 05:57:42,350 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard 2023-04-28 05:57:42,350 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/defaults 2023-04-28 05:57:42,350 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/defaults 2023-04-28 05:57:42,350 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/handlers 2023-04-28 05:57:42,350 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/handlers 2023-04-28 05:57:42,351 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/meta 2023-04-28 05:57:42,351 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/meta 2023-04-28 05:57:42,351 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tasks 2023-04-28 05:57:42,351 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tasks 2023-04-28 05:57:42,351 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/templates 2023-04-28 05:57:42,351 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/templates/os10_raguard.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/templates 2023-04-28 05:57:42,352 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:42,352 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:42,352 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:42,352 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:42,352 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/vars 2023-04-28 05:57:42,353 root INFO copying ansible_collections/dellemc/os10/roles/os10_raguard/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/vars 2023-04-28 05:57:42,353 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map 2023-04-28 05:57:42,353 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map 2023-04-28 05:57:42,353 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map 2023-04-28 05:57:42,353 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/defaults 2023-04-28 05:57:42,354 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/defaults 2023-04-28 05:57:42,354 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/handlers 2023-04-28 05:57:42,354 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/handlers 2023-04-28 05:57:42,354 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/meta 2023-04-28 05:57:42,354 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/meta 2023-04-28 05:57:42,354 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tasks 2023-04-28 05:57:42,355 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tasks 2023-04-28 05:57:42,355 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/templates 2023-04-28 05:57:42,355 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/templates/os10_route_map.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/templates 2023-04-28 05:57:42,355 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:42,355 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/tests/inventory -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:42,356 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:42,356 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/tests/test.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:42,356 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/vars 2023-04-28 05:57:42,356 root INFO copying ansible_collections/dellemc/os10/roles/os10_route_map/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/vars 2023-04-28 05:57:42,356 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp 2023-04-28 05:57:42,356 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp 2023-04-28 05:57:42,357 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp 2023-04-28 05:57:42,357 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/defaults 2023-04-28 05:57:42,357 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/defaults 2023-04-28 05:57:42,357 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/handlers 2023-04-28 05:57:42,357 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/handlers 2023-04-28 05:57:42,358 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/meta 2023-04-28 05:57:42,358 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/meta 2023-04-28 05:57:42,358 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tasks 2023-04-28 05:57:42,358 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tasks 2023-04-28 05:57:42,358 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/templates 2023-04-28 05:57:42,359 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/templates/os10_snmp.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/templates 2023-04-28 05:57:42,359 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:42,359 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:42,359 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:42,359 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:42,360 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/vars 2023-04-28 05:57:42,360 root INFO copying ansible_collections/dellemc/os10/roles/os10_snmp/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/vars 2023-04-28 05:57:42,360 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system 2023-04-28 05:57:42,360 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_system 2023-04-28 05:57:42,360 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_system 2023-04-28 05:57:42,361 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system/defaults 2023-04-28 05:57:42,361 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/defaults 2023-04-28 05:57:42,361 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system/handlers 2023-04-28 05:57:42,361 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/handlers 2023-04-28 05:57:42,361 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system/meta 2023-04-28 05:57:42,361 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/meta 2023-04-28 05:57:42,362 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system/tasks 2023-04-28 05:57:42,362 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/tasks 2023-04-28 05:57:42,362 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system/templates 2023-04-28 05:57:42,362 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/templates/os10_system.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/templates 2023-04-28 05:57:42,362 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:42,362 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:42,363 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:42,363 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:42,363 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_system/vars 2023-04-28 05:57:42,363 root INFO copying ansible_collections/dellemc/os10/roles/os10_system/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_system/vars 2023-04-28 05:57:42,363 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_template 2023-04-28 05:57:42,364 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_template 2023-04-28 05:57:42,364 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_template 2023-04-28 05:57:42,364 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_template/meta 2023-04-28 05:57:42,364 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/meta 2023-04-28 05:57:42,364 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,365 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,365 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_bgp_summary.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,365 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_interface_brief.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,365 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_vrf.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,365 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_lldp_neighbors.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,366 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_port-channel_summary.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,366 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_spanning_tree_compatibility_mode.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,366 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_vlan.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,366 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/show_vlt_err_disabled_ports.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,367 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tasks/textfsm.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:42,367 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,367 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_bgp_summary.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,367 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_interface_brief.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,367 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_vrf.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,368 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_lldp_neighbors.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,368 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_port-channel_summary.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,368 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_spanning_tree_compatibility_mode.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,368 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_vlan.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,368 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_vlt_err_disabled_ports.template -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:42,369 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:42,369 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:42,369 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:42,369 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:42,369 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests/group_vars 2023-04-28 05:57:42,370 root INFO copying ansible_collections/dellemc/os10/roles/os10_template/tests/group_vars/all -> build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests/group_vars 2023-04-28 05:57:42,370 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink 2023-04-28 05:57:42,370 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink 2023-04-28 05:57:42,370 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink 2023-04-28 05:57:42,370 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/defaults 2023-04-28 05:57:42,371 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/defaults 2023-04-28 05:57:42,371 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/handlers 2023-04-28 05:57:42,371 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/handlers 2023-04-28 05:57:42,371 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/meta 2023-04-28 05:57:42,371 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/meta 2023-04-28 05:57:42,371 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tasks 2023-04-28 05:57:42,372 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tasks 2023-04-28 05:57:42,372 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/templates 2023-04-28 05:57:42,372 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/templates/os10_uplink.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/templates 2023-04-28 05:57:42,372 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:42,372 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:42,373 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:42,373 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:42,373 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/vars 2023-04-28 05:57:42,373 root INFO copying ansible_collections/dellemc/os10/roles/os10_uplink/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/vars 2023-04-28 05:57:42,373 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users 2023-04-28 05:57:42,373 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_users 2023-04-28 05:57:42,374 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_users 2023-04-28 05:57:42,374 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users/defaults 2023-04-28 05:57:42,374 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/defaults 2023-04-28 05:57:42,374 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users/handlers 2023-04-28 05:57:42,374 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/handlers 2023-04-28 05:57:42,375 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users/meta 2023-04-28 05:57:42,375 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/meta 2023-04-28 05:57:42,375 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users/tasks 2023-04-28 05:57:42,375 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/tasks 2023-04-28 05:57:42,375 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users/templates 2023-04-28 05:57:42,375 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/templates/os10_users.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/templates 2023-04-28 05:57:42,376 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:42,376 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:42,376 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:42,376 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:42,376 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_users/vars 2023-04-28 05:57:42,377 root INFO copying ansible_collections/dellemc/os10/roles/os10_users/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_users/vars 2023-04-28 05:57:42,377 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan 2023-04-28 05:57:42,377 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan 2023-04-28 05:57:42,377 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan 2023-04-28 05:57:42,377 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/defaults 2023-04-28 05:57:42,378 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/defaults 2023-04-28 05:57:42,378 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/handlers 2023-04-28 05:57:42,378 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/handlers 2023-04-28 05:57:42,378 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/meta 2023-04-28 05:57:42,378 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/meta 2023-04-28 05:57:42,379 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tasks 2023-04-28 05:57:42,379 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tasks 2023-04-28 05:57:42,379 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/templates 2023-04-28 05:57:42,379 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/templates/os10_vlan.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/templates 2023-04-28 05:57:42,380 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:42,380 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:42,380 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:42,380 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:42,380 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/vars 2023-04-28 05:57:42,381 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlan/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/vars 2023-04-28 05:57:42,381 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt 2023-04-28 05:57:42,381 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt 2023-04-28 05:57:42,381 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt 2023-04-28 05:57:42,381 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/defaults 2023-04-28 05:57:42,382 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/defaults 2023-04-28 05:57:42,382 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/handlers 2023-04-28 05:57:42,382 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/handlers 2023-04-28 05:57:42,382 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/meta 2023-04-28 05:57:42,382 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/meta 2023-04-28 05:57:42,382 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tasks 2023-04-28 05:57:42,383 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tasks 2023-04-28 05:57:42,383 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/templates 2023-04-28 05:57:42,383 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/templates/os10_vlt.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/templates 2023-04-28 05:57:42,383 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:42,383 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:42,383 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:42,384 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:42,384 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/vars 2023-04-28 05:57:42,384 root INFO copying ansible_collections/dellemc/os10/roles/os10_vlt/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/vars 2023-04-28 05:57:42,384 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf 2023-04-28 05:57:42,384 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf 2023-04-28 05:57:42,385 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf 2023-04-28 05:57:42,385 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/defaults 2023-04-28 05:57:42,385 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/defaults 2023-04-28 05:57:42,385 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/handlers 2023-04-28 05:57:42,385 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/handlers 2023-04-28 05:57:42,386 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/meta 2023-04-28 05:57:42,386 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/meta 2023-04-28 05:57:42,386 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tasks 2023-04-28 05:57:42,386 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tasks 2023-04-28 05:57:42,386 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/templates 2023-04-28 05:57:42,386 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/templates/os10_vrf.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/templates 2023-04-28 05:57:42,387 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:42,387 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:42,387 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:42,387 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:42,387 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/vars 2023-04-28 05:57:42,388 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrf/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/vars 2023-04-28 05:57:42,388 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp 2023-04-28 05:57:42,388 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp 2023-04-28 05:57:42,388 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp 2023-04-28 05:57:42,388 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/defaults 2023-04-28 05:57:42,389 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/defaults 2023-04-28 05:57:42,389 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/handlers 2023-04-28 05:57:42,389 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/handlers 2023-04-28 05:57:42,389 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/meta 2023-04-28 05:57:42,389 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/meta 2023-04-28 05:57:42,390 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tasks 2023-04-28 05:57:42,390 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tasks 2023-04-28 05:57:42,390 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/templates 2023-04-28 05:57:42,390 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/templates/os10_vrrp.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/templates 2023-04-28 05:57:42,390 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:42,390 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:42,391 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/tests/main.os10.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:42,391 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:42,391 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/vars 2023-04-28 05:57:42,391 root INFO copying ansible_collections/dellemc/os10/roles/os10_vrrp/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/vars 2023-04-28 05:57:42,391 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan 2023-04-28 05:57:42,392 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan 2023-04-28 05:57:42,392 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan 2023-04-28 05:57:42,392 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/defaults 2023-04-28 05:57:42,392 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/defaults 2023-04-28 05:57:42,392 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/handlers 2023-04-28 05:57:42,393 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/handlers 2023-04-28 05:57:42,393 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/meta 2023-04-28 05:57:42,393 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/meta 2023-04-28 05:57:42,393 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tasks 2023-04-28 05:57:42,393 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tasks 2023-04-28 05:57:42,393 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/templates 2023-04-28 05:57:42,394 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/templates/os10_vxlan.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/templates 2023-04-28 05:57:42,394 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:42,394 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:42,394 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:42,394 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/tests/test.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:42,395 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/vars 2023-04-28 05:57:42,395 root INFO copying ansible_collections/dellemc/os10/roles/os10_vxlan/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/vars 2023-04-28 05:57:42,395 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp 2023-04-28 05:57:42,395 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/LICENSE -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp 2023-04-28 05:57:42,395 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/README.md -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp 2023-04-28 05:57:42,396 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/defaults 2023-04-28 05:57:42,396 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/defaults 2023-04-28 05:57:42,396 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/handlers 2023-04-28 05:57:42,396 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/handlers 2023-04-28 05:57:42,396 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/meta 2023-04-28 05:57:42,396 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/meta/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/meta 2023-04-28 05:57:42,397 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tasks 2023-04-28 05:57:42,397 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tasks 2023-04-28 05:57:42,397 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/templates 2023-04-28 05:57:42,397 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/templates/os10_xstp.j2 -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/templates 2023-04-28 05:57:42,397 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:42,397 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:42,398 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/tests/main.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:42,398 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:42,398 root INFO creating build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/vars 2023-04-28 05:57:42,398 root INFO copying ansible_collections/dellemc/os10/roles/os10_xstp/vars/main.yml -> build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/vars 2023-04-28 05:57:42,398 root INFO creating build/lib/ansible_collections/dellemc/os6 2023-04-28 05:57:42,399 root INFO copying ansible_collections/dellemc/os6/COPYING -> build/lib/ansible_collections/dellemc/os6 2023-04-28 05:57:42,399 root INFO copying ansible_collections/dellemc/os6/FILES.json -> build/lib/ansible_collections/dellemc/os6 2023-04-28 05:57:42,399 root INFO copying ansible_collections/dellemc/os6/LICENSE -> build/lib/ansible_collections/dellemc/os6 2023-04-28 05:57:42,400 root INFO copying ansible_collections/dellemc/os6/MANIFEST.json -> build/lib/ansible_collections/dellemc/os6 2023-04-28 05:57:42,400 root INFO copying ansible_collections/dellemc/os6/README.md -> build/lib/ansible_collections/dellemc/os6 2023-04-28 05:57:42,400 root INFO creating build/lib/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:42,400 root INFO copying ansible_collections/dellemc/os6/changelogs/CHANGELOG.rst -> build/lib/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:42,400 root INFO copying ansible_collections/dellemc/os6/changelogs/changelog.yaml -> build/lib/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:42,401 root INFO copying ansible_collections/dellemc/os6/changelogs/config.yaml -> build/lib/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:42,401 root INFO creating build/lib/ansible_collections/dellemc/os6/meta 2023-04-28 05:57:42,401 root INFO copying ansible_collections/dellemc/os6/meta/runtime.yml -> build/lib/ansible_collections/dellemc/os6/meta 2023-04-28 05:57:42,401 root INFO creating build/lib/ansible_collections/dellemc/os6/playbooks 2023-04-28 05:57:42,401 root INFO creating build/lib/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:42,401 root INFO copying ansible_collections/dellemc/os6/playbooks/ibgp/README.md -> build/lib/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:42,402 root INFO copying ansible_collections/dellemc/os6/playbooks/ibgp/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:42,402 root INFO copying ansible_collections/dellemc/os6/playbooks/ibgp/os6switch.yaml -> build/lib/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:42,402 root INFO creating build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/group_vars 2023-04-28 05:57:42,402 root INFO copying ansible_collections/dellemc/os6/playbooks/ibgp/group_vars/all -> build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/group_vars 2023-04-28 05:57:42,402 root INFO creating build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars 2023-04-28 05:57:42,403 root INFO copying ansible_collections/dellemc/os6/playbooks/ibgp/host_vars/switch1.yaml -> build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars 2023-04-28 05:57:42,403 root INFO copying ansible_collections/dellemc/os6/playbooks/ibgp/host_vars/switch2.yaml -> build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars 2023-04-28 05:57:42,403 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins 2023-04-28 05:57:42,403 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins/action 2023-04-28 05:57:42,403 root INFO copying ansible_collections/dellemc/os6/plugins/action/__init__.py -> build/lib/ansible_collections/dellemc/os6/plugins/action 2023-04-28 05:57:42,403 root INFO copying ansible_collections/dellemc/os6/plugins/action/os6.py -> build/lib/ansible_collections/dellemc/os6/plugins/action 2023-04-28 05:57:42,404 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins/cliconf 2023-04-28 05:57:42,404 root INFO copying ansible_collections/dellemc/os6/plugins/cliconf/__init__.py -> build/lib/ansible_collections/dellemc/os6/plugins/cliconf 2023-04-28 05:57:42,404 root INFO copying ansible_collections/dellemc/os6/plugins/cliconf/os6.py -> build/lib/ansible_collections/dellemc/os6/plugins/cliconf 2023-04-28 05:57:42,404 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins/doc_fragments 2023-04-28 05:57:42,404 root INFO copying ansible_collections/dellemc/os6/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/dellemc/os6/plugins/doc_fragments 2023-04-28 05:57:42,405 root INFO copying ansible_collections/dellemc/os6/plugins/doc_fragments/os6.py -> build/lib/ansible_collections/dellemc/os6/plugins/doc_fragments 2023-04-28 05:57:42,405 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins/module_utils 2023-04-28 05:57:42,405 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins/module_utils/network 2023-04-28 05:57:42,405 root INFO copying ansible_collections/dellemc/os6/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/dellemc/os6/plugins/module_utils/network 2023-04-28 05:57:42,405 root INFO copying ansible_collections/dellemc/os6/plugins/module_utils/network/os6.py -> build/lib/ansible_collections/dellemc/os6/plugins/module_utils/network 2023-04-28 05:57:42,405 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:42,406 root INFO copying ansible_collections/dellemc/os6/plugins/modules/__init__.py -> build/lib/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:42,406 root INFO copying ansible_collections/dellemc/os6/plugins/modules/os6_command.py -> build/lib/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:42,406 root INFO copying ansible_collections/dellemc/os6/plugins/modules/os6_config.py -> build/lib/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:42,406 root INFO copying ansible_collections/dellemc/os6/plugins/modules/os6_facts.py -> build/lib/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:42,406 root INFO creating build/lib/ansible_collections/dellemc/os6/plugins/terminal 2023-04-28 05:57:42,407 root INFO copying ansible_collections/dellemc/os6/plugins/terminal/__init__.py -> build/lib/ansible_collections/dellemc/os6/plugins/terminal 2023-04-28 05:57:42,407 root INFO copying ansible_collections/dellemc/os6/plugins/terminal/os6.py -> build/lib/ansible_collections/dellemc/os6/plugins/terminal 2023-04-28 05:57:42,407 root INFO creating build/lib/ansible_collections/dellemc/os6/roles 2023-04-28 05:57:42,407 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa 2023-04-28 05:57:42,407 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa 2023-04-28 05:57:42,408 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa 2023-04-28 05:57:42,408 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/defaults 2023-04-28 05:57:42,408 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/defaults 2023-04-28 05:57:42,408 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/handlers 2023-04-28 05:57:42,408 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/handlers 2023-04-28 05:57:42,408 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/meta 2023-04-28 05:57:42,409 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/meta 2023-04-28 05:57:42,409 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tasks 2023-04-28 05:57:42,409 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tasks 2023-04-28 05:57:42,409 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/templates 2023-04-28 05:57:42,409 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/templates/os6_aaa.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/templates 2023-04-28 05:57:42,410 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:42,410 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:42,410 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:42,410 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:42,410 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/vars 2023-04-28 05:57:42,410 root INFO copying ansible_collections/dellemc/os6/roles/os6_aaa/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/vars 2023-04-28 05:57:42,411 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl 2023-04-28 05:57:42,411 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl 2023-04-28 05:57:42,411 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl 2023-04-28 05:57:42,411 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl/defaults 2023-04-28 05:57:42,411 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/defaults 2023-04-28 05:57:42,412 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl/handlers 2023-04-28 05:57:42,412 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/handlers 2023-04-28 05:57:42,412 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl/meta 2023-04-28 05:57:42,412 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/meta 2023-04-28 05:57:42,412 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tasks 2023-04-28 05:57:42,412 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tasks 2023-04-28 05:57:42,413 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl/templates 2023-04-28 05:57:42,413 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/templates/os6_acl.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/templates 2023-04-28 05:57:42,413 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:42,413 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:42,413 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:42,414 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:42,414 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_acl/vars 2023-04-28 05:57:42,414 root INFO copying ansible_collections/dellemc/os6/roles/os6_acl/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_acl/vars 2023-04-28 05:57:42,414 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp 2023-04-28 05:57:42,414 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp 2023-04-28 05:57:42,415 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp 2023-04-28 05:57:42,415 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/defaults 2023-04-28 05:57:42,415 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/defaults 2023-04-28 05:57:42,415 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/handlers 2023-04-28 05:57:42,415 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/handlers 2023-04-28 05:57:42,416 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/meta 2023-04-28 05:57:42,416 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/meta 2023-04-28 05:57:42,416 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tasks 2023-04-28 05:57:42,416 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tasks 2023-04-28 05:57:42,416 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/templates 2023-04-28 05:57:42,416 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/templates/os6_bgp.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/templates 2023-04-28 05:57:42,417 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:42,417 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:42,417 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:42,417 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:42,417 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/vars 2023-04-28 05:57:42,418 root INFO copying ansible_collections/dellemc/os6/roles/os6_bgp/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/vars 2023-04-28 05:57:42,418 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface 2023-04-28 05:57:42,418 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface 2023-04-28 05:57:42,418 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface 2023-04-28 05:57:42,418 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface/defaults 2023-04-28 05:57:42,419 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/defaults 2023-04-28 05:57:42,419 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface/handlers 2023-04-28 05:57:42,419 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/handlers 2023-04-28 05:57:42,419 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface/meta 2023-04-28 05:57:42,419 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/meta 2023-04-28 05:57:42,419 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tasks 2023-04-28 05:57:42,420 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tasks 2023-04-28 05:57:42,420 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface/templates 2023-04-28 05:57:42,420 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/templates/os6_interface.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/templates 2023-04-28 05:57:42,420 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:42,420 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:42,421 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:42,421 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:42,421 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_interface/vars 2023-04-28 05:57:42,421 root INFO copying ansible_collections/dellemc/os6/roles/os6_interface/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_interface/vars 2023-04-28 05:57:42,421 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag 2023-04-28 05:57:42,421 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag 2023-04-28 05:57:42,422 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag 2023-04-28 05:57:42,422 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag/defaults 2023-04-28 05:57:42,422 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/defaults 2023-04-28 05:57:42,422 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag/handlers 2023-04-28 05:57:42,422 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/handlers 2023-04-28 05:57:42,423 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag/meta 2023-04-28 05:57:42,423 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/meta 2023-04-28 05:57:42,423 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tasks 2023-04-28 05:57:42,423 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tasks 2023-04-28 05:57:42,423 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag/templates 2023-04-28 05:57:42,424 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/templates/os6_lag.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/templates 2023-04-28 05:57:42,424 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:42,424 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:42,424 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:42,424 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:42,424 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lag/vars 2023-04-28 05:57:42,425 root INFO copying ansible_collections/dellemc/os6/roles/os6_lag/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lag/vars 2023-04-28 05:57:42,425 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp 2023-04-28 05:57:42,425 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp 2023-04-28 05:57:42,425 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp 2023-04-28 05:57:42,425 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/defaults 2023-04-28 05:57:42,426 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/defaults 2023-04-28 05:57:42,426 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/handlers 2023-04-28 05:57:42,426 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/handlers 2023-04-28 05:57:42,426 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/meta 2023-04-28 05:57:42,426 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/meta 2023-04-28 05:57:42,427 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tasks 2023-04-28 05:57:42,427 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tasks 2023-04-28 05:57:42,427 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/templates 2023-04-28 05:57:42,427 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/templates/os6_lldp.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/templates 2023-04-28 05:57:42,427 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:42,427 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:42,428 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:42,428 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:42,428 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/vars 2023-04-28 05:57:42,428 root INFO copying ansible_collections/dellemc/os6/roles/os6_lldp/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/vars 2023-04-28 05:57:42,428 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging 2023-04-28 05:57:42,428 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging 2023-04-28 05:57:42,429 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging 2023-04-28 05:57:42,429 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging/defaults 2023-04-28 05:57:42,429 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/defaults 2023-04-28 05:57:42,429 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging/handlers 2023-04-28 05:57:42,430 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/handlers 2023-04-28 05:57:42,430 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging/meta 2023-04-28 05:57:42,430 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/meta 2023-04-28 05:57:42,430 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tasks 2023-04-28 05:57:42,430 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tasks 2023-04-28 05:57:42,430 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging/templates 2023-04-28 05:57:42,431 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/templates/os6_logging.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/templates 2023-04-28 05:57:42,431 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:42,431 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:42,431 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:42,431 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:42,432 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_logging/vars 2023-04-28 05:57:42,432 root INFO copying ansible_collections/dellemc/os6/roles/os6_logging/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_logging/vars 2023-04-28 05:57:42,432 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp 2023-04-28 05:57:42,432 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp 2023-04-28 05:57:42,432 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp 2023-04-28 05:57:42,433 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/defaults 2023-04-28 05:57:42,433 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/defaults 2023-04-28 05:57:42,433 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/handlers 2023-04-28 05:57:42,433 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/handlers 2023-04-28 05:57:42,433 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/meta 2023-04-28 05:57:42,433 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/meta 2023-04-28 05:57:42,434 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tasks 2023-04-28 05:57:42,434 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tasks 2023-04-28 05:57:42,434 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/templates 2023-04-28 05:57:42,434 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/templates/os6_ntp.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/templates 2023-04-28 05:57:42,434 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:42,434 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/tests/inventory -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:42,435 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:42,435 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/tests/test.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:42,435 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/vars 2023-04-28 05:57:42,435 root INFO copying ansible_collections/dellemc/os6/roles/os6_ntp/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/vars 2023-04-28 05:57:42,435 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos 2023-04-28 05:57:42,436 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos 2023-04-28 05:57:42,436 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos 2023-04-28 05:57:42,436 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos/defaults 2023-04-28 05:57:42,436 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/defaults 2023-04-28 05:57:42,436 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos/handlers 2023-04-28 05:57:42,437 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/handlers 2023-04-28 05:57:42,437 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos/meta 2023-04-28 05:57:42,437 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/meta 2023-04-28 05:57:42,437 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tasks 2023-04-28 05:57:42,437 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tasks 2023-04-28 05:57:42,437 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos/templates 2023-04-28 05:57:42,438 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/templates/os6_qos.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/templates 2023-04-28 05:57:42,438 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:42,438 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/tests/inventory -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:42,438 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:42,438 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/tests/test.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:42,439 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_qos/vars 2023-04-28 05:57:42,439 root INFO copying ansible_collections/dellemc/os6/roles/os6_qos/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_qos/vars 2023-04-28 05:57:42,439 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp 2023-04-28 05:57:42,439 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp 2023-04-28 05:57:42,439 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp 2023-04-28 05:57:42,440 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/defaults 2023-04-28 05:57:42,440 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/defaults 2023-04-28 05:57:42,440 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/handlers 2023-04-28 05:57:42,440 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/handlers 2023-04-28 05:57:42,440 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/meta 2023-04-28 05:57:42,440 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/meta 2023-04-28 05:57:42,441 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tasks 2023-04-28 05:57:42,441 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tasks 2023-04-28 05:57:42,441 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/templates 2023-04-28 05:57:42,441 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/templates/os6_snmp.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/templates 2023-04-28 05:57:42,441 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:42,441 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:42,442 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:42,442 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:42,442 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/vars 2023-04-28 05:57:42,442 root INFO copying ansible_collections/dellemc/os6/roles/os6_snmp/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/vars 2023-04-28 05:57:42,442 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system 2023-04-28 05:57:42,443 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_system 2023-04-28 05:57:42,443 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_system 2023-04-28 05:57:42,443 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system/defaults 2023-04-28 05:57:42,443 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/defaults 2023-04-28 05:57:42,444 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system/handlers 2023-04-28 05:57:42,444 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/handlers 2023-04-28 05:57:42,444 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system/meta 2023-04-28 05:57:42,444 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/meta 2023-04-28 05:57:42,444 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system/tasks 2023-04-28 05:57:42,444 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/tasks 2023-04-28 05:57:42,445 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system/templates 2023-04-28 05:57:42,445 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/templates/os6_system.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/templates 2023-04-28 05:57:42,445 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:42,445 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:42,445 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:42,445 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:42,446 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_system/vars 2023-04-28 05:57:42,446 root INFO copying ansible_collections/dellemc/os6/roles/os6_system/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_system/vars 2023-04-28 05:57:42,446 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users 2023-04-28 05:57:42,446 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_users 2023-04-28 05:57:42,446 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_users 2023-04-28 05:57:42,447 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users/defaults 2023-04-28 05:57:42,447 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/defaults 2023-04-28 05:57:42,447 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users/handlers 2023-04-28 05:57:42,447 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/handlers 2023-04-28 05:57:42,447 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users/meta 2023-04-28 05:57:42,448 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/meta 2023-04-28 05:57:42,448 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users/tasks 2023-04-28 05:57:42,448 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/tasks 2023-04-28 05:57:42,448 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users/templates 2023-04-28 05:57:42,448 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/templates/os6_users.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/templates 2023-04-28 05:57:42,448 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:42,449 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:42,449 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:42,449 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:42,449 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_users/vars 2023-04-28 05:57:42,449 root INFO copying ansible_collections/dellemc/os6/roles/os6_users/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_users/vars 2023-04-28 05:57:42,450 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan 2023-04-28 05:57:42,450 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan 2023-04-28 05:57:42,450 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan 2023-04-28 05:57:42,450 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/defaults 2023-04-28 05:57:42,450 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/defaults 2023-04-28 05:57:42,451 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/handlers 2023-04-28 05:57:42,451 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/handlers 2023-04-28 05:57:42,451 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/meta 2023-04-28 05:57:42,451 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/meta 2023-04-28 05:57:42,451 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tasks 2023-04-28 05:57:42,451 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tasks 2023-04-28 05:57:42,452 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/templates 2023-04-28 05:57:42,452 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/templates/os6_vlan.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/templates 2023-04-28 05:57:42,452 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:42,452 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:42,452 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:42,453 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:42,453 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/vars 2023-04-28 05:57:42,453 root INFO copying ansible_collections/dellemc/os6/roles/os6_vlan/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/vars 2023-04-28 05:57:42,453 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp 2023-04-28 05:57:42,453 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp 2023-04-28 05:57:42,454 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp 2023-04-28 05:57:42,454 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/defaults 2023-04-28 05:57:42,454 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/defaults 2023-04-28 05:57:42,454 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/handlers 2023-04-28 05:57:42,454 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/handlers 2023-04-28 05:57:42,454 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/meta 2023-04-28 05:57:42,455 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/meta 2023-04-28 05:57:42,455 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tasks 2023-04-28 05:57:42,455 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tasks 2023-04-28 05:57:42,455 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/templates 2023-04-28 05:57:42,455 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/templates/os6_vrrp.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/templates 2023-04-28 05:57:42,455 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:42,456 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:42,456 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:42,456 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:42,456 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/vars 2023-04-28 05:57:42,456 root INFO copying ansible_collections/dellemc/os6/roles/os6_vrrp/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/vars 2023-04-28 05:57:42,457 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp 2023-04-28 05:57:42,457 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/LICENSE -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp 2023-04-28 05:57:42,457 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/README.md -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp 2023-04-28 05:57:42,457 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/defaults 2023-04-28 05:57:42,457 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/defaults 2023-04-28 05:57:42,458 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/handlers 2023-04-28 05:57:42,458 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/handlers 2023-04-28 05:57:42,458 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/meta 2023-04-28 05:57:42,458 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/meta/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/meta 2023-04-28 05:57:42,458 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tasks 2023-04-28 05:57:42,458 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tasks 2023-04-28 05:57:42,459 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/templates 2023-04-28 05:57:42,459 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/templates/os6_xstp.j2 -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/templates 2023-04-28 05:57:42,459 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:42,459 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:42,459 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:42,460 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:42,460 root INFO creating build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/vars 2023-04-28 05:57:42,460 root INFO copying ansible_collections/dellemc/os6/roles/os6_xstp/vars/main.yml -> build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/vars 2023-04-28 05:57:42,460 root INFO creating build/lib/ansible_collections/dellemc/os9 2023-04-28 05:57:42,460 root INFO copying ansible_collections/dellemc/os9/COPYING -> build/lib/ansible_collections/dellemc/os9 2023-04-28 05:57:42,461 root INFO copying ansible_collections/dellemc/os9/FILES.json -> build/lib/ansible_collections/dellemc/os9 2023-04-28 05:57:42,461 root INFO copying ansible_collections/dellemc/os9/LICENSE -> build/lib/ansible_collections/dellemc/os9 2023-04-28 05:57:42,461 root INFO copying ansible_collections/dellemc/os9/MANIFEST.json -> build/lib/ansible_collections/dellemc/os9 2023-04-28 05:57:42,461 root INFO copying ansible_collections/dellemc/os9/README.md -> build/lib/ansible_collections/dellemc/os9 2023-04-28 05:57:42,462 root INFO creating build/lib/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:42,462 root INFO copying ansible_collections/dellemc/os9/changelogs/CHANGELOG.rst -> build/lib/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:42,462 root INFO copying ansible_collections/dellemc/os9/changelogs/changelog.yaml -> build/lib/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:42,462 root INFO copying ansible_collections/dellemc/os9/changelogs/config.yaml -> build/lib/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:42,462 root INFO creating build/lib/ansible_collections/dellemc/os9/meta 2023-04-28 05:57:42,463 root INFO copying ansible_collections/dellemc/os9/meta/runtime.yml -> build/lib/ansible_collections/dellemc/os9/meta 2023-04-28 05:57:42,463 root INFO creating build/lib/ansible_collections/dellemc/os9/playbooks 2023-04-28 05:57:42,463 root INFO creating build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,463 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/README.md -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,463 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/datacenter.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,463 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:42,464 root INFO creating build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:42,464 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars/all -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:42,464 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars/spine.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:42,464 root INFO creating build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,464 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf1.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,465 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf2.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,465 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf3.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,465 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf4.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,465 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/spine1.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,465 root INFO copying ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/spine2.yaml -> build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:42,466 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins 2023-04-28 05:57:42,466 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins/action 2023-04-28 05:57:42,466 root INFO copying ansible_collections/dellemc/os9/plugins/action/__init__.py -> build/lib/ansible_collections/dellemc/os9/plugins/action 2023-04-28 05:57:42,466 root INFO copying ansible_collections/dellemc/os9/plugins/action/os9.py -> build/lib/ansible_collections/dellemc/os9/plugins/action 2023-04-28 05:57:42,466 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins/cliconf 2023-04-28 05:57:42,467 root INFO copying ansible_collections/dellemc/os9/plugins/cliconf/__init__.py -> build/lib/ansible_collections/dellemc/os9/plugins/cliconf 2023-04-28 05:57:42,467 root INFO copying ansible_collections/dellemc/os9/plugins/cliconf/os9.py -> build/lib/ansible_collections/dellemc/os9/plugins/cliconf 2023-04-28 05:57:42,467 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins/doc_fragments 2023-04-28 05:57:42,467 root INFO copying ansible_collections/dellemc/os9/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/dellemc/os9/plugins/doc_fragments 2023-04-28 05:57:42,467 root INFO copying ansible_collections/dellemc/os9/plugins/doc_fragments/os9.py -> build/lib/ansible_collections/dellemc/os9/plugins/doc_fragments 2023-04-28 05:57:42,467 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins/module_utils 2023-04-28 05:57:42,468 root INFO copying ansible_collections/dellemc/os9/plugins/module_utils/__init__.py -> build/lib/ansible_collections/dellemc/os9/plugins/module_utils 2023-04-28 05:57:42,468 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins/module_utils/network 2023-04-28 05:57:42,468 root INFO copying ansible_collections/dellemc/os9/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/dellemc/os9/plugins/module_utils/network 2023-04-28 05:57:42,468 root INFO copying ansible_collections/dellemc/os9/plugins/module_utils/network/os9.py -> build/lib/ansible_collections/dellemc/os9/plugins/module_utils/network 2023-04-28 05:57:42,468 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:42,469 root INFO copying ansible_collections/dellemc/os9/plugins/modules/__init__.py -> build/lib/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:42,469 root INFO copying ansible_collections/dellemc/os9/plugins/modules/os9_command.py -> build/lib/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:42,469 root INFO copying ansible_collections/dellemc/os9/plugins/modules/os9_config.py -> build/lib/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:42,469 root INFO copying ansible_collections/dellemc/os9/plugins/modules/os9_facts.py -> build/lib/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:42,469 root INFO creating build/lib/ansible_collections/dellemc/os9/plugins/terminal 2023-04-28 05:57:42,470 root INFO copying ansible_collections/dellemc/os9/plugins/terminal/__init__.py -> build/lib/ansible_collections/dellemc/os9/plugins/terminal 2023-04-28 05:57:42,470 root INFO copying ansible_collections/dellemc/os9/plugins/terminal/os9.py -> build/lib/ansible_collections/dellemc/os9/plugins/terminal 2023-04-28 05:57:42,470 root INFO creating build/lib/ansible_collections/dellemc/os9/roles 2023-04-28 05:57:42,470 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa 2023-04-28 05:57:42,470 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa 2023-04-28 05:57:42,471 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa 2023-04-28 05:57:42,471 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/defaults 2023-04-28 05:57:42,471 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/defaults 2023-04-28 05:57:42,471 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/handlers 2023-04-28 05:57:42,471 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/handlers 2023-04-28 05:57:42,472 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/meta 2023-04-28 05:57:42,472 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/meta 2023-04-28 05:57:42,472 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tasks 2023-04-28 05:57:42,472 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tasks 2023-04-28 05:57:42,472 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/templates 2023-04-28 05:57:42,472 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/templates/os9_aaa.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/templates 2023-04-28 05:57:42,473 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:42,473 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:42,473 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/tests/main.os6.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:42,473 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:42,473 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/vars 2023-04-28 05:57:42,474 root INFO copying ansible_collections/dellemc/os9/roles/os9_aaa/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/vars 2023-04-28 05:57:42,474 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl 2023-04-28 05:57:42,474 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl 2023-04-28 05:57:42,474 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl 2023-04-28 05:57:42,474 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl/defaults 2023-04-28 05:57:42,475 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/defaults 2023-04-28 05:57:42,475 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl/handlers 2023-04-28 05:57:42,475 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/handlers 2023-04-28 05:57:42,475 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl/meta 2023-04-28 05:57:42,475 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/meta 2023-04-28 05:57:42,475 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tasks 2023-04-28 05:57:42,476 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tasks 2023-04-28 05:57:42,476 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl/templates 2023-04-28 05:57:42,476 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/templates/os9_acl.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/templates 2023-04-28 05:57:42,476 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:42,476 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:42,477 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:42,477 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:42,477 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_acl/vars 2023-04-28 05:57:42,477 root INFO copying ansible_collections/dellemc/os9/roles/os9_acl/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_acl/vars 2023-04-28 05:57:42,477 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp 2023-04-28 05:57:42,477 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp 2023-04-28 05:57:42,478 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp 2023-04-28 05:57:42,478 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/defaults 2023-04-28 05:57:42,478 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/defaults 2023-04-28 05:57:42,478 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/handlers 2023-04-28 05:57:42,478 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/handlers 2023-04-28 05:57:42,479 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/meta 2023-04-28 05:57:42,479 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/meta 2023-04-28 05:57:42,479 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tasks 2023-04-28 05:57:42,479 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tasks 2023-04-28 05:57:42,479 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/templates 2023-04-28 05:57:42,479 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/templates/os9_bgp.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/templates 2023-04-28 05:57:42,480 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:42,480 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:42,480 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:42,480 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:42,480 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/vars 2023-04-28 05:57:42,481 root INFO copying ansible_collections/dellemc/os9/roles/os9_bgp/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/vars 2023-04-28 05:57:42,481 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config 2023-04-28 05:57:42,481 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config 2023-04-28 05:57:42,481 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config 2023-04-28 05:57:42,481 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/defaults 2023-04-28 05:57:42,482 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/defaults 2023-04-28 05:57:42,482 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/handlers 2023-04-28 05:57:42,482 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/handlers 2023-04-28 05:57:42,482 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/meta 2023-04-28 05:57:42,482 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/meta 2023-04-28 05:57:42,483 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tasks 2023-04-28 05:57:42,483 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tasks 2023-04-28 05:57:42,483 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/templates 2023-04-28 05:57:42,483 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/templates/os9_copy_config.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/templates 2023-04-28 05:57:42,483 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:42,483 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:42,484 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:42,484 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:42,484 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/vars 2023-04-28 05:57:42,484 root INFO copying ansible_collections/dellemc/os9/roles/os9_copy_config/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/vars 2023-04-28 05:57:42,484 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb 2023-04-28 05:57:42,484 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb 2023-04-28 05:57:42,485 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb 2023-04-28 05:57:42,485 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/defaults 2023-04-28 05:57:42,485 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/defaults 2023-04-28 05:57:42,485 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/handlers 2023-04-28 05:57:42,486 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/handlers 2023-04-28 05:57:42,486 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/meta 2023-04-28 05:57:42,486 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/meta 2023-04-28 05:57:42,486 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tasks 2023-04-28 05:57:42,486 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tasks 2023-04-28 05:57:42,486 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/templates 2023-04-28 05:57:42,487 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/templates/os9_dcb.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/templates 2023-04-28 05:57:42,487 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:42,487 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:42,487 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:42,487 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:42,488 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/vars 2023-04-28 05:57:42,488 root INFO copying ansible_collections/dellemc/os9/roles/os9_dcb/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/vars 2023-04-28 05:57:42,488 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns 2023-04-28 05:57:42,488 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns 2023-04-28 05:57:42,488 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns 2023-04-28 05:57:42,489 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns/defaults 2023-04-28 05:57:42,489 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/defaults 2023-04-28 05:57:42,489 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns/handlers 2023-04-28 05:57:42,489 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/handlers 2023-04-28 05:57:42,489 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns/meta 2023-04-28 05:57:42,489 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/meta 2023-04-28 05:57:42,490 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tasks 2023-04-28 05:57:42,490 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tasks 2023-04-28 05:57:42,490 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns/templates 2023-04-28 05:57:42,490 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/templates/os9_dns.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/templates 2023-04-28 05:57:42,490 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:42,490 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:42,491 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:42,491 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:42,491 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_dns/vars 2023-04-28 05:57:42,491 root INFO copying ansible_collections/dellemc/os9/roles/os9_dns/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_dns/vars 2023-04-28 05:57:42,491 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp 2023-04-28 05:57:42,492 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp 2023-04-28 05:57:42,492 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp 2023-04-28 05:57:42,492 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/defaults 2023-04-28 05:57:42,492 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/defaults 2023-04-28 05:57:42,492 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/handlers 2023-04-28 05:57:42,493 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/handlers 2023-04-28 05:57:42,493 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/meta 2023-04-28 05:57:42,493 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/meta 2023-04-28 05:57:42,493 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tasks 2023-04-28 05:57:42,493 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tasks 2023-04-28 05:57:42,494 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/templates 2023-04-28 05:57:42,494 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/templates/os9_ecmp.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/templates 2023-04-28 05:57:42,494 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:42,494 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:42,494 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:42,494 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:42,495 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/vars 2023-04-28 05:57:42,495 root INFO copying ansible_collections/dellemc/os9/roles/os9_ecmp/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/vars 2023-04-28 05:57:42,495 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface 2023-04-28 05:57:42,495 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface 2023-04-28 05:57:42,495 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface 2023-04-28 05:57:42,496 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface/defaults 2023-04-28 05:57:42,496 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/defaults 2023-04-28 05:57:42,496 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface/handlers 2023-04-28 05:57:42,496 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/handlers 2023-04-28 05:57:42,496 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface/meta 2023-04-28 05:57:42,496 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/meta 2023-04-28 05:57:42,497 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tasks 2023-04-28 05:57:42,497 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tasks 2023-04-28 05:57:42,497 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface/templates 2023-04-28 05:57:42,497 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/templates/os9_interface.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/templates 2023-04-28 05:57:42,497 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:42,498 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:42,498 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:42,498 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:42,498 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_interface/vars 2023-04-28 05:57:42,498 root INFO copying ansible_collections/dellemc/os9/roles/os9_interface/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_interface/vars 2023-04-28 05:57:42,499 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag 2023-04-28 05:57:42,499 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag 2023-04-28 05:57:42,499 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag 2023-04-28 05:57:42,499 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag/defaults 2023-04-28 05:57:42,499 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/defaults 2023-04-28 05:57:42,500 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag/handlers 2023-04-28 05:57:42,500 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/handlers 2023-04-28 05:57:42,500 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag/meta 2023-04-28 05:57:42,500 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/meta 2023-04-28 05:57:42,500 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tasks 2023-04-28 05:57:42,500 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tasks 2023-04-28 05:57:42,501 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag/templates 2023-04-28 05:57:42,501 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/templates/os9_lag.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/templates 2023-04-28 05:57:42,501 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:42,501 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:42,501 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:42,502 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:42,502 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lag/vars 2023-04-28 05:57:42,502 root INFO copying ansible_collections/dellemc/os9/roles/os9_lag/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lag/vars 2023-04-28 05:57:42,502 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp 2023-04-28 05:57:42,502 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp 2023-04-28 05:57:42,503 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp 2023-04-28 05:57:42,503 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/defaults 2023-04-28 05:57:42,503 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/defaults 2023-04-28 05:57:42,503 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/handlers 2023-04-28 05:57:42,503 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/handlers 2023-04-28 05:57:42,503 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/meta 2023-04-28 05:57:42,504 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/meta 2023-04-28 05:57:42,504 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tasks 2023-04-28 05:57:42,504 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tasks 2023-04-28 05:57:42,505 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/templates 2023-04-28 05:57:42,505 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/templates/os9_lldp.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/templates 2023-04-28 05:57:42,505 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:42,505 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:42,505 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:42,505 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:42,506 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/vars 2023-04-28 05:57:42,506 root INFO copying ansible_collections/dellemc/os9/roles/os9_lldp/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/vars 2023-04-28 05:57:42,506 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging 2023-04-28 05:57:42,506 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging 2023-04-28 05:57:42,506 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging 2023-04-28 05:57:42,507 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging/defaults 2023-04-28 05:57:42,507 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/defaults 2023-04-28 05:57:42,507 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging/handlers 2023-04-28 05:57:42,507 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/handlers 2023-04-28 05:57:42,507 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging/meta 2023-04-28 05:57:42,508 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/meta 2023-04-28 05:57:42,508 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tasks 2023-04-28 05:57:42,508 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tasks 2023-04-28 05:57:42,508 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging/templates 2023-04-28 05:57:42,508 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/templates/os9_logging.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/templates 2023-04-28 05:57:42,508 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:42,509 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:42,509 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:42,509 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:42,509 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_logging/vars 2023-04-28 05:57:42,509 root INFO copying ansible_collections/dellemc/os9/roles/os9_logging/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_logging/vars 2023-04-28 05:57:42,510 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp 2023-04-28 05:57:42,510 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp 2023-04-28 05:57:42,510 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp 2023-04-28 05:57:42,510 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/defaults 2023-04-28 05:57:42,510 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/defaults 2023-04-28 05:57:42,511 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/handlers 2023-04-28 05:57:42,511 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/handlers 2023-04-28 05:57:42,511 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/meta 2023-04-28 05:57:42,511 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/meta 2023-04-28 05:57:42,511 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tasks 2023-04-28 05:57:42,511 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tasks 2023-04-28 05:57:42,512 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/templates 2023-04-28 05:57:42,512 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/templates/os9_ntp.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/templates 2023-04-28 05:57:42,512 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:42,512 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:42,512 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:42,513 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:42,513 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/vars 2023-04-28 05:57:42,513 root INFO copying ansible_collections/dellemc/os9/roles/os9_ntp/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/vars 2023-04-28 05:57:42,513 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list 2023-04-28 05:57:42,513 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list 2023-04-28 05:57:42,514 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list 2023-04-28 05:57:42,514 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/defaults 2023-04-28 05:57:42,514 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/defaults 2023-04-28 05:57:42,514 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/handlers 2023-04-28 05:57:42,514 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/handlers 2023-04-28 05:57:42,515 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/meta 2023-04-28 05:57:42,515 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/meta 2023-04-28 05:57:42,515 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tasks 2023-04-28 05:57:42,515 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tasks 2023-04-28 05:57:42,515 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/templates 2023-04-28 05:57:42,515 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/templates/os9_prefix_list.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/templates 2023-04-28 05:57:42,516 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:42,516 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:42,516 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:42,516 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:42,516 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/vars 2023-04-28 05:57:42,517 root INFO copying ansible_collections/dellemc/os9/roles/os9_prefix_list/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/vars 2023-04-28 05:57:42,517 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow 2023-04-28 05:57:42,517 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow 2023-04-28 05:57:42,517 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow 2023-04-28 05:57:42,517 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/defaults 2023-04-28 05:57:42,517 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/defaults 2023-04-28 05:57:42,518 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/handlers 2023-04-28 05:57:42,518 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/handlers 2023-04-28 05:57:42,518 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/meta 2023-04-28 05:57:42,518 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/meta 2023-04-28 05:57:42,518 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tasks 2023-04-28 05:57:42,519 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tasks 2023-04-28 05:57:42,519 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/templates 2023-04-28 05:57:42,519 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/templates/os9_sflow.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/templates 2023-04-28 05:57:42,519 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:42,519 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:42,519 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:42,520 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:42,520 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/vars 2023-04-28 05:57:42,520 root INFO copying ansible_collections/dellemc/os9/roles/os9_sflow/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/vars 2023-04-28 05:57:42,520 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp 2023-04-28 05:57:42,520 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp 2023-04-28 05:57:42,521 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp 2023-04-28 05:57:42,521 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/defaults 2023-04-28 05:57:42,521 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/defaults 2023-04-28 05:57:42,521 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/handlers 2023-04-28 05:57:42,521 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/handlers 2023-04-28 05:57:42,522 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/meta 2023-04-28 05:57:42,522 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/meta 2023-04-28 05:57:42,522 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tasks 2023-04-28 05:57:42,522 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tasks 2023-04-28 05:57:42,522 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/templates 2023-04-28 05:57:42,522 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/templates/os9_snmp.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/templates 2023-04-28 05:57:42,523 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:42,523 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:42,523 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:42,523 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:42,523 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/vars 2023-04-28 05:57:42,524 root INFO copying ansible_collections/dellemc/os9/roles/os9_snmp/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/vars 2023-04-28 05:57:42,524 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system 2023-04-28 05:57:42,524 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_system 2023-04-28 05:57:42,524 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_system 2023-04-28 05:57:42,524 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system/defaults 2023-04-28 05:57:42,525 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/defaults 2023-04-28 05:57:42,525 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system/handlers 2023-04-28 05:57:42,525 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/handlers 2023-04-28 05:57:42,525 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system/meta 2023-04-28 05:57:42,525 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/meta 2023-04-28 05:57:42,526 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system/tasks 2023-04-28 05:57:42,526 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/tasks 2023-04-28 05:57:42,526 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system/templates 2023-04-28 05:57:42,526 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/templates/os9_system.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/templates 2023-04-28 05:57:42,526 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:42,526 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:42,527 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:42,527 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:42,527 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_system/vars 2023-04-28 05:57:42,527 root INFO copying ansible_collections/dellemc/os9/roles/os9_system/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_system/vars 2023-04-28 05:57:42,527 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users 2023-04-28 05:57:42,528 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_users 2023-04-28 05:57:42,528 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_users 2023-04-28 05:57:42,528 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users/defaults 2023-04-28 05:57:42,528 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/defaults 2023-04-28 05:57:42,528 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users/handlers 2023-04-28 05:57:42,529 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/handlers 2023-04-28 05:57:42,529 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users/meta 2023-04-28 05:57:42,529 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/meta 2023-04-28 05:57:42,529 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users/tasks 2023-04-28 05:57:42,529 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/tasks 2023-04-28 05:57:42,529 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users/templates 2023-04-28 05:57:42,530 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/templates/os9_users.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/templates 2023-04-28 05:57:42,530 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:42,530 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:42,530 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:42,530 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:42,531 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_users/vars 2023-04-28 05:57:42,531 root INFO copying ansible_collections/dellemc/os9/roles/os9_users/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_users/vars 2023-04-28 05:57:42,531 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan 2023-04-28 05:57:42,531 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan 2023-04-28 05:57:42,531 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan 2023-04-28 05:57:42,532 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/defaults 2023-04-28 05:57:42,532 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/defaults 2023-04-28 05:57:42,532 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/handlers 2023-04-28 05:57:42,532 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/handlers 2023-04-28 05:57:42,532 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/meta 2023-04-28 05:57:42,532 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/meta 2023-04-28 05:57:42,533 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tasks 2023-04-28 05:57:42,533 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tasks 2023-04-28 05:57:42,533 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/templates 2023-04-28 05:57:42,533 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/templates/os9_vlan.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/templates 2023-04-28 05:57:42,533 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:42,533 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:42,534 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:42,534 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:42,534 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/vars 2023-04-28 05:57:42,534 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlan/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/vars 2023-04-28 05:57:42,534 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt 2023-04-28 05:57:42,535 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt 2023-04-28 05:57:42,535 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt 2023-04-28 05:57:42,535 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/defaults 2023-04-28 05:57:42,535 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/defaults 2023-04-28 05:57:42,535 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/handlers 2023-04-28 05:57:42,536 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/handlers 2023-04-28 05:57:42,536 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/meta 2023-04-28 05:57:42,536 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/meta 2023-04-28 05:57:42,536 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tasks 2023-04-28 05:57:42,536 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tasks 2023-04-28 05:57:42,537 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/templates 2023-04-28 05:57:42,537 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/templates/os9_vlt.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/templates 2023-04-28 05:57:42,537 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:42,537 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:42,537 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:42,537 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:42,538 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/vars 2023-04-28 05:57:42,538 root INFO copying ansible_collections/dellemc/os9/roles/os9_vlt/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/vars 2023-04-28 05:57:42,538 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf 2023-04-28 05:57:42,538 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf 2023-04-28 05:57:42,538 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf 2023-04-28 05:57:42,539 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/defaults 2023-04-28 05:57:42,539 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/defaults 2023-04-28 05:57:42,539 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/handlers 2023-04-28 05:57:42,539 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/handlers 2023-04-28 05:57:42,539 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/meta 2023-04-28 05:57:42,539 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/meta 2023-04-28 05:57:42,540 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tasks 2023-04-28 05:57:42,540 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tasks 2023-04-28 05:57:42,540 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/templates 2023-04-28 05:57:42,540 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/templates/os9_vrf.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/templates 2023-04-28 05:57:42,540 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:42,541 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:42,541 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:42,541 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:42,541 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/vars 2023-04-28 05:57:42,541 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrf/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/vars 2023-04-28 05:57:42,542 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp 2023-04-28 05:57:42,542 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp 2023-04-28 05:57:42,542 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp 2023-04-28 05:57:42,542 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/defaults 2023-04-28 05:57:42,542 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/defaults 2023-04-28 05:57:42,543 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/handlers 2023-04-28 05:57:42,543 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/handlers 2023-04-28 05:57:42,543 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/meta 2023-04-28 05:57:42,543 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/meta 2023-04-28 05:57:42,543 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tasks 2023-04-28 05:57:42,543 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tasks 2023-04-28 05:57:42,544 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/templates 2023-04-28 05:57:42,544 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/templates/os9_vrrp.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/templates 2023-04-28 05:57:42,544 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:42,544 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:42,544 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:42,545 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:42,545 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/vars 2023-04-28 05:57:42,545 root INFO copying ansible_collections/dellemc/os9/roles/os9_vrrp/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/vars 2023-04-28 05:57:42,545 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp 2023-04-28 05:57:42,545 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/LICENSE -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp 2023-04-28 05:57:42,546 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/README.md -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp 2023-04-28 05:57:42,546 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/defaults 2023-04-28 05:57:42,546 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/defaults/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/defaults 2023-04-28 05:57:42,546 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/handlers 2023-04-28 05:57:42,546 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/handlers/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/handlers 2023-04-28 05:57:42,546 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/meta 2023-04-28 05:57:42,547 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/meta/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/meta 2023-04-28 05:57:42,547 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tasks 2023-04-28 05:57:42,547 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/tasks/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tasks 2023-04-28 05:57:42,547 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/templates 2023-04-28 05:57:42,547 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/templates/os9_xstp.j2 -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/templates 2023-04-28 05:57:42,548 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:42,548 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/tests/inventory.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:42,548 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/tests/main.os9.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:42,548 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/tests/test.yaml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:42,548 root INFO creating build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/vars 2023-04-28 05:57:42,548 root INFO copying ansible_collections/dellemc/os9/roles/os9_xstp/vars/main.yml -> build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/vars 2023-04-28 05:57:42,549 root INFO creating build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,549 root INFO copying ansible_collections/dellemc/powerflex/CHANGELOG.rst -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,549 root INFO copying ansible_collections/dellemc/powerflex/FILES.json -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,549 root INFO copying ansible_collections/dellemc/powerflex/LICENSE -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,550 root INFO copying ansible_collections/dellemc/powerflex/MANIFEST.json -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,550 root INFO copying ansible_collections/dellemc/powerflex/MODULE-LICENSE -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,550 root INFO copying ansible_collections/dellemc/powerflex/README.md -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,550 root INFO copying ansible_collections/dellemc/powerflex/ansible.cfg -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,550 root INFO copying ansible_collections/dellemc/powerflex/requirements.txt -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,551 root INFO copying ansible_collections/dellemc/powerflex/requirements.yml -> build/lib/ansible_collections/dellemc/powerflex 2023-04-28 05:57:42,551 root INFO creating build/lib/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:42,551 root INFO copying ansible_collections/dellemc/powerflex/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:42,551 root INFO copying ansible_collections/dellemc/powerflex/changelogs/changelog.yaml -> build/lib/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:42,551 root INFO copying ansible_collections/dellemc/powerflex/changelogs/config.yaml -> build/lib/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:42,552 root INFO creating build/lib/ansible_collections/dellemc/powerflex/meta 2023-04-28 05:57:42,552 root INFO copying ansible_collections/dellemc/powerflex/meta/execution-environment.yml -> build/lib/ansible_collections/dellemc/powerflex/meta 2023-04-28 05:57:42,552 root INFO copying ansible_collections/dellemc/powerflex/meta/runtime.yml -> build/lib/ansible_collections/dellemc/powerflex/meta 2023-04-28 05:57:42,552 root INFO creating build/lib/ansible_collections/dellemc/powerflex/plugins 2023-04-28 05:57:42,552 root INFO creating build/lib/ansible_collections/dellemc/powerflex/plugins/doc_fragments 2023-04-28 05:57:42,552 root INFO copying ansible_collections/dellemc/powerflex/plugins/doc_fragments/powerflex.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/doc_fragments 2023-04-28 05:57:42,553 root INFO creating build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils 2023-04-28 05:57:42,553 root INFO creating build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage 2023-04-28 05:57:42,553 root INFO creating build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:42,553 root INFO copying ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/__init__.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:42,553 root INFO copying ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/logging_handler.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:42,553 root INFO copying ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/utils.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:42,554 root INFO creating build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,554 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/device.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,554 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/info.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,554 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/mdm_cluster.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,555 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/protection_domain.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,555 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/replication_consistency_group.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,555 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/replication_pair.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,556 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/sdc.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,556 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/sds.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,556 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/snapshot.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,556 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/storagepool.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,557 root INFO copying ansible_collections/dellemc/powerflex/plugins/modules/volume.py -> build/lib/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:42,557 root INFO creating build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,557 root INFO copying ansible_collections/dellemc/unity/CHANGELOG.rst -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,557 root INFO copying ansible_collections/dellemc/unity/FILES.json -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,558 root INFO copying ansible_collections/dellemc/unity/LICENSE -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,558 root INFO copying ansible_collections/dellemc/unity/MANIFEST.json -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,558 root INFO copying ansible_collections/dellemc/unity/MODULE-LICENSE -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,558 root INFO copying ansible_collections/dellemc/unity/README.md -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,558 root INFO copying ansible_collections/dellemc/unity/ansible.cfg -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,559 root INFO copying ansible_collections/dellemc/unity/requirements.txt -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,559 root INFO copying ansible_collections/dellemc/unity/requirements.yml -> build/lib/ansible_collections/dellemc/unity 2023-04-28 05:57:42,559 root INFO creating build/lib/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:42,559 root INFO copying ansible_collections/dellemc/unity/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:42,559 root INFO copying ansible_collections/dellemc/unity/changelogs/changelog.yaml -> build/lib/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:42,560 root INFO copying ansible_collections/dellemc/unity/changelogs/config.yaml -> build/lib/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:42,560 root INFO creating build/lib/ansible_collections/dellemc/unity/meta 2023-04-28 05:57:42,560 root INFO copying ansible_collections/dellemc/unity/meta/execution-environment.yml -> build/lib/ansible_collections/dellemc/unity/meta 2023-04-28 05:57:42,560 root INFO copying ansible_collections/dellemc/unity/meta/runtime.yml -> build/lib/ansible_collections/dellemc/unity/meta 2023-04-28 05:57:42,561 root INFO creating build/lib/ansible_collections/dellemc/unity/plugins 2023-04-28 05:57:42,561 root INFO creating build/lib/ansible_collections/dellemc/unity/plugins/doc_fragments 2023-04-28 05:57:42,561 root INFO copying ansible_collections/dellemc/unity/plugins/doc_fragments/unity.py -> build/lib/ansible_collections/dellemc/unity/plugins/doc_fragments 2023-04-28 05:57:42,561 root INFO creating build/lib/ansible_collections/dellemc/unity/plugins/module_utils 2023-04-28 05:57:42,561 root INFO creating build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage 2023-04-28 05:57:42,561 root INFO creating build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:42,561 root INFO copying ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/__init__.py -> build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:42,562 root INFO copying ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/logging_handler.py -> build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:42,562 root INFO copying ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/utils.py -> build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:42,562 root INFO creating build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,562 root INFO copying ansible_collections/dellemc/unity/plugins/modules/cifsserver.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,562 root INFO copying ansible_collections/dellemc/unity/plugins/modules/consistencygroup.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,563 root INFO copying ansible_collections/dellemc/unity/plugins/modules/filesystem.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,563 root INFO copying ansible_collections/dellemc/unity/plugins/modules/filesystem_snapshot.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,563 root INFO copying ansible_collections/dellemc/unity/plugins/modules/host.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,564 root INFO copying ansible_collections/dellemc/unity/plugins/modules/info.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,564 root INFO copying ansible_collections/dellemc/unity/plugins/modules/interface.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,564 root INFO copying ansible_collections/dellemc/unity/plugins/modules/nasserver.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,564 root INFO copying ansible_collections/dellemc/unity/plugins/modules/nfs.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,565 root INFO copying ansible_collections/dellemc/unity/plugins/modules/nfsserver.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,565 root INFO copying ansible_collections/dellemc/unity/plugins/modules/smbshare.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,565 root INFO copying ansible_collections/dellemc/unity/plugins/modules/snapshot.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,565 root INFO copying ansible_collections/dellemc/unity/plugins/modules/snapshotschedule.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,566 root INFO copying ansible_collections/dellemc/unity/plugins/modules/storagepool.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,566 root INFO copying ansible_collections/dellemc/unity/plugins/modules/tree_quota.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,566 root INFO copying ansible_collections/dellemc/unity/plugins/modules/user_quota.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,567 root INFO copying ansible_collections/dellemc/unity/plugins/modules/volume.py -> build/lib/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:42,567 root INFO creating build/lib/ansible_collections/f5networks 2023-04-28 05:57:42,567 root INFO creating build/lib/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:42,567 root INFO copying ansible_collections/f5networks/f5_modules/CHANGELOG.rst -> build/lib/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:42,567 root INFO copying ansible_collections/f5networks/f5_modules/FILES.json -> build/lib/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:42,568 root INFO copying ansible_collections/f5networks/f5_modules/MANIFEST.json -> build/lib/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:42,568 root INFO copying ansible_collections/f5networks/f5_modules/README.md -> build/lib/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:42,568 root INFO copying ansible_collections/f5networks/f5_modules/requirements.txt -> build/lib/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:42,569 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:42,569 root INFO copying ansible_collections/f5networks/f5_modules/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:42,569 root INFO copying ansible_collections/f5networks/f5_modules/changelogs/changelog.yaml -> build/lib/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:42,569 root INFO copying ansible_collections/f5networks/f5_modules/changelogs/config.yaml -> build/lib/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:42,569 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/changelogs/fragments 2023-04-28 05:57:42,570 root INFO copying ansible_collections/f5networks/f5_modules/changelogs/fragments/.gitkeep -> build/lib/ansible_collections/f5networks/f5_modules/changelogs/fragments 2023-04-28 05:57:42,570 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/meta 2023-04-28 05:57:42,570 root INFO copying ansible_collections/f5networks/f5_modules/meta/runtime.yml -> build/lib/ansible_collections/f5networks/f5_modules/meta 2023-04-28 05:57:42,570 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins 2023-04-28 05:57:42,570 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:42,570 root INFO copying ansible_collections/f5networks/f5_modules/plugins/action/__init__.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:42,571 root INFO copying ansible_collections/f5networks/f5_modules/plugins/action/bigip.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:42,571 root INFO copying ansible_collections/f5networks/f5_modules/plugins/action/bigip_imish_config.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:42,571 root INFO copying ansible_collections/f5networks/f5_modules/plugins/action/bigiq.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:42,571 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:42,571 root INFO copying ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:42,572 root INFO copying ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5_rest_cli.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:42,572 root INFO copying ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5ssh.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:42,572 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:42,572 root INFO copying ansible_collections/f5networks/f5_modules/plugins/filter/__init__.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:42,572 root INFO copying ansible_collections/f5networks/f5_modules/plugins/filter/abspath.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:42,573 root INFO copying ansible_collections/f5networks/f5_modules/plugins/filter/markdev.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:42,573 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:42,573 root INFO copying ansible_collections/f5networks/f5_modules/plugins/lookup/__init__.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:42,573 root INFO copying ansible_collections/f5networks/f5_modules/plugins/lookup/bigiq_license.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:42,573 root INFO copying ansible_collections/f5networks/f5_modules/plugins/lookup/license_hopper.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:42,574 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,574 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/__init__.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,574 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/bigip.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,574 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/bigiq.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,574 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/common.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,575 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/compare.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,575 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/constants.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,575 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/icontrol.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,575 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/ipaddress.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,576 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/teem.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,576 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/urls.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,576 root INFO copying ansible_collections/f5networks/f5_modules/plugins/module_utils/version.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:42,576 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,576 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/__init__.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,577 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_acl.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,577 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_network_access.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,577 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_policy_fetch.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,577 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_policy_import.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,578 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_advanced_settings.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,578 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_dos_application.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,578 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_fetch.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,578 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_import.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,579 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_manage.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,579 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_server_technology.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,579 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_signature_set.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,579 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cgnat_lsn_pool.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,580 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cli_alias.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,580 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cli_script.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,580 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_command.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,580 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_config.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,581 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_configsync_action.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,581 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_data_group.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,581 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,581 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_ldap.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,582 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_radius.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,582 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_radius_server.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,582 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_certificate.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,582 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_connectivity.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,583 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_dns.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,583 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_group.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,583 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_group_member.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,583 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_ha_group.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,584 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_httpd.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,584 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_info.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,585 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_license.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,585 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_ntp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,585 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_sshd.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,586 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_syslog.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,586 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_traffic_group.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,586 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_trust.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,587 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_cache_resolver.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,587 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_nameserver.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,587 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_resolver.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,587 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_zone.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,588 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_file_copy.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,588 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_address_list.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,588 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_dos_profile.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,588 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_dos_vector.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,589 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_global_rules.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,589 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_log_profile.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,589 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_log_profile_network.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,589 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_policy.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,590 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_port_list.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,590 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_rule.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,590 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_rule_list.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,590 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_schedule.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,591 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_datacenter.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,591 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_dns_listener.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,591 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_global.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,591 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_bigip.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,592 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_external.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,592 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_firepass.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,592 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_http.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,592 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_https.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,593 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_tcp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,593 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_tcp_half_open.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,593 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_pool.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,593 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_pool_member.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,594 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_server.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,594 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_topology_record.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,594 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_topology_region.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,595 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_virtual_server.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,595 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_wide_ip.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,595 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_hostname.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,595 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_iapp_service.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,596 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_iapp_template.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,596 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ike_peer.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,596 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_imish_config.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,596 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_interface.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,597 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ipsec_policy.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,597 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_irule.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,597 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_log_destination.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,597 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_log_publisher.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,598 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ltm_global.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,598 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_lx_package.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,598 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_management_route.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,598 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_peer.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,599 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_protocol.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,599 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_route.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,599 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_router.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,599 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_transport_config.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,600 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_dns.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,600 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_external.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,600 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_ftp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,600 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_gateway_icmp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,601 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_http.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,601 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_https.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,601 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_icmp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,601 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_ldap.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,602 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_mysql.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,602 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_oracle.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,602 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_smtp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,602 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_snmp_dca.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,603 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,603 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp_echo.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,603 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp_half_open.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,603 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_udp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,604 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_network_globals.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,604 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_node.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,604 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_partition.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,605 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_password_policy.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,605 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_policy.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,605 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_policy_rule.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,605 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_pool.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,606 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_pool_member.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,606 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_analytics.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,606 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_client_ssl.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,607 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_dns.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,607 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_fastl4.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,607 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_ftp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,607 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,608 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http2.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,608 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http_compression.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,608 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_oneconnect.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,608 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_cookie.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,609 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_src_addr.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,609 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_universal.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,609 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_server_ssl.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,610 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_sip.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,610 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_tcp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,610 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_udp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,610 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_provision.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,611 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_qkview.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,611 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_role.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,611 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_syslog.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,611 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_user.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,612 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_routedomain.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,612 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_selfip.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,612 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_service_policy.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,612 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_smtp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,613 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snat_pool.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,613 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snat_translation.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,613 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,613 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp_community.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,614 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp_trap.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,614 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_image.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,614 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_install.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,614 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_update.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,615 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_certificate.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,615 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_csr.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,615 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_key.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,615 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_key_cert.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,616 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_ocsp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,616 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_static_route.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,616 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_daemon_log_tmm.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,616 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_db.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,616 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_global.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,617 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_timer_policy.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,617 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_traffic_selector.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,617 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_trunk.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,617 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_tunnel.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,618 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ucs.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,618 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ucs_fetch.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,618 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_user.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,618 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_vcmp_guest.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,619 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_virtual_address.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,619 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_virtual_server.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,619 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_vlan.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,620 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigip_wait.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,620 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fasthttp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,620 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fastl4_tcp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,621 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fastl4_udp.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,621 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_http.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,621 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_https_offload.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,621 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_https_waf.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,622 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_device_discovery.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,622 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_device_info.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,622 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_license.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,622 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_license_assignment.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,623 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_pool.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,623 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_utility_license.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,623 root INFO copying ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_utility_license_assignment.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:42,623 root INFO creating build/lib/ansible_collections/f5networks/f5_modules/plugins/terminal 2023-04-28 05:57:42,624 root INFO copying ansible_collections/f5networks/f5_modules/plugins/terminal/bigip.py -> build/lib/ansible_collections/f5networks/f5_modules/plugins/terminal 2023-04-28 05:57:42,624 root INFO creating build/lib/ansible_collections/fortinet 2023-04-28 05:57:42,624 root INFO creating build/lib/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:42,624 root INFO copying ansible_collections/fortinet/fortimanager/CHANGELOG.rst -> build/lib/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:42,624 root INFO copying ansible_collections/fortinet/fortimanager/FILES.json -> build/lib/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:42,625 root INFO copying ansible_collections/fortinet/fortimanager/MANIFEST.json -> build/lib/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:42,625 root INFO copying ansible_collections/fortinet/fortimanager/README.md -> build/lib/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:42,625 root INFO creating build/lib/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:42,625 root INFO copying ansible_collections/fortinet/fortimanager/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:42,626 root INFO copying ansible_collections/fortinet/fortimanager/changelogs/changelog.yaml -> build/lib/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:42,626 root INFO copying ansible_collections/fortinet/fortimanager/changelogs/config.yaml -> build/lib/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:42,626 root INFO creating build/lib/ansible_collections/fortinet/fortimanager/meta 2023-04-28 05:57:42,626 root INFO copying ansible_collections/fortinet/fortimanager/meta/runtime.yml -> build/lib/ansible_collections/fortinet/fortimanager/meta 2023-04-28 05:57:42,627 root INFO creating build/lib/ansible_collections/fortinet/fortimanager/plugins 2023-04-28 05:57:42,627 root INFO copying ansible_collections/fortinet/fortimanager/plugins/README.md -> build/lib/ansible_collections/fortinet/fortimanager/plugins 2023-04-28 05:57:42,627 root INFO creating build/lib/ansible_collections/fortinet/fortimanager/plugins/httpapi 2023-04-28 05:57:42,627 root INFO copying ansible_collections/fortinet/fortimanager/plugins/httpapi/fortimanager.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/httpapi 2023-04-28 05:57:42,627 root INFO creating build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:42,628 root INFO copying ansible_collections/fortinet/fortimanager/plugins/module_utils/__init__.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:42,628 root INFO copying ansible_collections/fortinet/fortimanager/plugins/module_utils/common.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:42,628 root INFO copying ansible_collections/fortinet/fortimanager/plugins/module_utils/exported_schema.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:42,641 root INFO copying ansible_collections/fortinet/fortimanager/plugins/module_utils/fortimanager.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:42,641 root INFO copying ansible_collections/fortinet/fortimanager/plugins/module_utils/napi.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:42,642 root INFO creating build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,642 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_adom_options.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,642 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_mmschecksum.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,642 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_mmschecksum_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,643 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_notification.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,643 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_notification_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,643 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,644 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_cifs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,644 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_contentdisarm.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,644 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_ftp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,645 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_http.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,645 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_imap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,645 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_mapi.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,645 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_nacquar.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,646 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_nntp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,646 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_outbreakprevention.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,646 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_pop3.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,647 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_smb.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,647 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_smtp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,647 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_ssh.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,648 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_apcfgprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,648 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_apcfgprofile_commandlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,648 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_categories.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,648 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_custom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,649 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,649 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,649 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_defaultnetworkservices.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,650 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,650 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries_parameters.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,650 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries_parameters_members.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,650 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_arrpprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,651 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_authentication_scheme.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,651 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bleprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,651 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bonjourprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,652 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bonjourprofile_policylist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,652 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_certificate_template.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,652 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_domaincontroller.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,652 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,653 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_filefilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,653 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_filefilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,653 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_serverkeytab.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,653 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_clone.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,654 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_credentialstore_domaincontroller.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,654 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_device_profile_fortianalyzer.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,655 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_device_profile_fortiguard.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,655 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_import.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,655 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_fortianalyzer_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,655 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_fortianalyzercloud_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,656 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_syslogd_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,656 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_syslogd_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,656 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_centralmanagement.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,656 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_centralmanagement_serverlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,656 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_dns.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,657 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_emailserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,657 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_global.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,657 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_ntp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,658 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_ntp_ntpserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,658 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_admin.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,658 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_alertmail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,658 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_auth.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,658 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_devicedetectionportal.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,659 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_ec.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,659 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_fortiguardwf.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,659 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_ftp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,659 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_http.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,660 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_mail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,660 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_mms.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,660 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_nacquar.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,660 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_nntp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,661 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_spam.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,661 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_sslvpn.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,661 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_trafficquota.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,661 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_utm.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,662 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_webproxy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,662 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,662 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community_hosts.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,662 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community_hosts6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,663 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_sysinfo.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,663 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_user.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,663 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_datatype.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,663 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_dictionary.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,663 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_dictionary_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,664 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_filepattern.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,664 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_filepattern_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,664 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_fpsensitivity.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,664 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,665 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_profile_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,665 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensitivity.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,665 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,665 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,666 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,666 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_domainfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,666 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_domainfilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,666 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,667 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_dnstranslation.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,667 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_domainfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,667 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_ftgddns.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,667 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_ftgddns_filters.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,668 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_add_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,668 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_add_devlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,668 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_changehaseq.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,668 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_del_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,669 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_del_devlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,669 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_discover_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,669 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_import_devlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,670 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_reload_devlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,670 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_update_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,670 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_update_devlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,670 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,671 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_adom_objectmember.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,671 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,671 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device_replace_sn.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,671 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device_vdom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,672 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_folder.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,672 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,672 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_group_objectmember.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,672 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,673 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,673 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,673 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_revision.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,673 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,673 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_execute.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,674 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_objectmember.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,674 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_scriptschedule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,674 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_approve.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,674 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_discard.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,675 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_drop.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,675 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_reject.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,675 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_repair.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,675 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_revert.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,676 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_review.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,676 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_save.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,676 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_start.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,676 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_submit.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,677 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,677 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_dev.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,677 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_obj.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,677 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_pkg.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,677 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,678 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_dev.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,678 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_obj.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,678 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_pkg.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,678 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,679 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_dev.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,679 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_obj.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,679 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_pkg.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,679 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_address.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,680 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_address_dynamicaddrmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,680 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_certificate_local.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,680 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_certificate_local_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,680 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_input_interface.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,681 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_input_interface_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,681 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,681 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,681 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface_platformmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,682 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_ippool.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,682 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_multicast_interface.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,682 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_multicast_interface_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,682 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,682 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_members.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,683 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_members_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,683 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_neighbor.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,683 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_neighbor_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,684 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_server.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,684 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_server_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,684 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vpntunnel.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,684 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vpntunnel_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,684 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_blockallowlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,685 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_blockallowlist_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,685 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bwl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,685 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bwl_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,685 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bword.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,686 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bword_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,686 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_dnsbl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,686 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_dnsbl_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,686 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_fortishield.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,687 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_iptrust.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,687 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_iptrust_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,687 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_mheader.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,687 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_mheader_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,688 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_options.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,688 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,688 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_filefilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,688 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_filefilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,689 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_gmail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,689 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_imap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,689 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_mapi.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,689 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_msnhotmail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,690 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_otherwebmails.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,690 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_pop3.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,690 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_smtp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,690 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_endpointcontrol_fctems.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,691 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_exec_fgfm_reclaimdevtunnel.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,691 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_export_playbooks.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,692 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_dataplan.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,692 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,692 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,693 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_controllerreport.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,693 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem1.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,693 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem1_autoswitch.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,694 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem2.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,694 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem2_autoswitch.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,694 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,694 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification_alert.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,695 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification_receiver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,695 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_lanextension.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,695 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_lanextension_backhaul.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,695 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_simprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,696 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_simprofile_autoswitchprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,696 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_template.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,696 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fact.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,697 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_filefilter_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,698 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_filefilter_profile_rules.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,698 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,698 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,698 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,699 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,699 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6_sslciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,699 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,700 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway_sslciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,700 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,700 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_serverpubkeyauthsettings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,700 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_serverpubkeyauthsettings_certextension.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,700 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxyvirtualhost.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,701 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,701 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,701 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,702 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_dynamicmapping_subnetsegment.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,702 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_list.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,702 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_subnetsegment.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,702 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,703 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,703 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template_subnetsegment.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,703 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template_subnetsegment_values.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,703 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,704 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_list.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,704 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,704 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,704 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,705 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,705 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,705 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,705 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,706 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_carrierendpointbwl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,706 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_carrierendpointbwl_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,706 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_decryptedtrafficmirror.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,706 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,707 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_apn.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,707 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ieremovepolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,707 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ievalidation.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,707 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_imsi.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,708 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ippolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,708 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimit.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,708 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv0.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,708 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv1.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,709 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv2.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,709 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_noippolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,709 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_perapnshaper.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,709 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,710 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_policyv2.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,710 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_identitybasedroute.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,710 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_identitybasedroute_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,710 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservice.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,711 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservice_entry.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,711 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,711 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition_entry.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,711 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition_entry_portrange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,712 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,712 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_disableentry.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,712 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_disableentry_iprange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,712 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_entry.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,713 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_entry_portrange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,713 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustomgroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,713 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicegroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,713 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicename.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,714 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,714 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,714 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool6_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,714 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,715 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ldbmonitor.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,715 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,715 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_dupe.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,715 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_flood.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,716 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_notification.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,716 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_notifmsisdn.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,716 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_outbreakprevention.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,716 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,717 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,717 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress6_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,717 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,717 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profilegroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,718 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,718 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,718 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_filefilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,718 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_filefilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,719 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_serverkeytab.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,719 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_dns.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,719 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_ftp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,719 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_http.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,720 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_imap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,720 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_mailsignature.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,720 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_mapi.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,721 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_nntp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,721 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_pop3.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,721 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_smtp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,721 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_ssh.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,722 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,722 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress_headergroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,722 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,722 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddrgrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,722 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddrgrp_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,723 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,723 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_onetime.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,723 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_recurring.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,723 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_category.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,724 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_custom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,724 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,724 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shaper_peripshaper.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,724 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shaper_trafficshaper.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,725 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shapingprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,725 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shapingprofile_shapingentries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,725 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ssh_localca.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,725 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,726 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_dot.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,726 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ftps.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,726 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_https.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,727 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_imaps.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,727 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_pop3s.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,727 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_smtps.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,727 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ssh.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,728 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ssl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,728 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_sslexempt.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,728 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_sslserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,728 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_trafficclass.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,729 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,729 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,729 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,730 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,730 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,730 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,731 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,731 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,731 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,732 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,732 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping_sslciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,732 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,732 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_sslciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,733 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_sslserverciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,733 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,733 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,733 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping_sslciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,734 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_realservers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,734 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_sslciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,734 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_sslserverciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,734 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,735 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp46.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,735 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,735 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp64.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,735 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,736 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_wildcardfqdn_custom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,736 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_wildcardfqdn_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,736 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_device_blueprint.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,736 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_variable.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,737 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_variable_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,737 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_analyzer_virusreport.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,737 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_avips_advancedlog.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,737 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_avips_webproxy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,738 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_customurllist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,738 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_diskquota.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,738 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fctservices.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,738 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,739 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverride.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,739 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverridetoclient.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,739 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverridetoclient_announceip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,739 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_serveroverride.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,740 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_serveroverride_servlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,740 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_updateschedule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,740 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fwmsetting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,740 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_multilayer.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,741 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_publicnetwork.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,741 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveraccesspriorities.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,741 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveraccesspriorities_privateserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,741 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveroverridestatus.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,742 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_service.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,742 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,742 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting_serveroverride.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,742 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting_serveroverride_servlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,743 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_webproxy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,743 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,744 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,744 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_excluderange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,744 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_iprange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,744 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_options.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,745 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_reservedaddress.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,745 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,745 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,746 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_excluderange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,746 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_iprange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,746 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_options.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,746 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_reservedaddress.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,747 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,747 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,747 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6delegatedprefixlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,748 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6extraaddr.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,748 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6prefixlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,748 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_vrrp6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,748 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_secondaryip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,749 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,749 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,750 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6delegatedprefixlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,750 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6extraaddr.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,750 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6prefixlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,750 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_vrrp6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,751 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_secondaryip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,751 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_vrrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,751 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_generic.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,751 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_apn.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,752 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_apngrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,752 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_iewhitelist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,752 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_iewhitelist_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,752 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_messagefilterv0v1.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,753 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_messagefilterv2.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,753 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_tunnellimit.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,753 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqp3gppcellular.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,753 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqp3gppcellular_mccmnclist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,754 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpipaddresstype.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,754 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,754 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,755 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist_eapmethod.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,755 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist_eapmethod_authparam.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,755 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnetworkauthtype.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,755 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqproamingconsortium.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,756 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqproamingconsortium_oilist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,756 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenuename.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,756 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenuename_valuelist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,756 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenueurl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,757 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenueurl_valuelist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,757 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,757 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge_aoclist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,757 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge_aoclist_planinfo.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,758 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpconncapability.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,758 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpoperatorname.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,758 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpoperatorname_valuelist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,758 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,759 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider_friendlyname.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,759 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider_servicedescription.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,759 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovidernai.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,759 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovidernai_nailist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,759 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qptermsandconditions.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,760 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpwanmetric.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,760 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_hsprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,760 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_icon.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,760 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_icon_iconlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,761 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,761 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap_dscpexcept.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,761 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap_dscprange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,761 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,762 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_icapheaders.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,762 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_respmodforwardrules.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,762 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_respmodforwardrules_headergroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,762 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_server.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,763 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_custom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,763 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,763 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,764 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor_entries_exemptip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,764 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_log_customfield.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,764 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_metafields_system_admin_user.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,764 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_move.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,765 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,765 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile_mpskgroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,765 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile_mpskgroup_mpskkey.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,765 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_nacprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,765 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_authentication_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,766 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_authentication_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,766 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_central_dnat.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,766 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_central_dnat6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,766 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_acl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,767 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_acl6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,767 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_centralsnatmap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,767 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_consolidated_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,767 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_consolidated_policy_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,768 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,768 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,768 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy6_anomaly.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,769 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy_anomaly.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,769 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,769 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,769 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy6_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,770 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,770 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_localinpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,770 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_localinpolicy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,770 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_multicastpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,771 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_multicastpolicy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,771 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,771 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy46.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,771 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,772 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy64.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,772 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy6_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,772 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,773 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_vpndstnode.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,773 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_vpnsrcnode.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,773 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_proxypolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,773 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_proxypolicy_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,774 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_securitypolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,774 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_securitypolicy_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,774 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_shapingpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,774 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,775 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_policy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,775 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_shapingpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,776 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,776 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_policy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,777 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_shapingpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,777 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_address.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,777 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_addrgrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,778 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_centralsnatmap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,778 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,778 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_service_custom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,778 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_service_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,778 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,779 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_policy_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,779 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_securitypolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,779 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_securitypolicy_sectionvalue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,780 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_reset_database.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,780 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_upgrade.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,780 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_commit.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,780 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_lock.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,780 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_unlock.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,781 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_devprof_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,781 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_devprof_pkg.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,781 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pblock_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,781 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pblock_obj.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,782 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,782 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,782 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg_global.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,782 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_wanprof_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,783 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_wanprof_pkg.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,783 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_qosprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,783 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_region.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,783 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_rename.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,784 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,784 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,785 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist6_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,785 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,785 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_aspathlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,785 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_aspathlist_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,786 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_communitylist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,786 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_communitylist_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,786 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,786 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,787 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist6_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,787 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,787 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_routemap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,787 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_routemap_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,788 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_abort.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,788 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_assign_package.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,788 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_cliprof_check.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,788 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_import_dev_objs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,789 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,789 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_package.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,789 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_preview.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,789 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_cancel_install.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,789 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_clone.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,790 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_commit.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,790 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_move.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,790 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_pblock_clone.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,790 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_preview_result.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,791 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_reinstall_package.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,791 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_sign_certificate_template.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,791 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bwl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,791 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bwl_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,792 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bword.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,792 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bword_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,792 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_dnsbl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,792 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_dnsbl_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,793 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_iptrust.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,793 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_iptrust_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,793 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_mheader.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,793 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_mheader_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,794 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,794 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_gmail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,794 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_imap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,794 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_mapi.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,794 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_msnhotmail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,795 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_pop3.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,795 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_smtp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,795 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_yahoomail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,795 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,796 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_filefilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,796 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_filefilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,796 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_shellcommands.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,796 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_customcommand.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,797 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_dsl_policy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,797 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,797 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_customtlvs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,797 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_medlocationservice.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,798 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_mednetworkpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,798 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,798 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_8021xsettings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,799 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_customcommand.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,799 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_igmpsnooping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,799 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ipsourceguard.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,799 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ipsourceguard_bindingentry.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,800 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_mirror.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,800 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ports.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,800 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_remotelog.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,800 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpcommunity.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,801 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpcommunity_hosts.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,801 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpsysinfo.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,801 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmptrapthreshold.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,801 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpuser.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,802 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_stormcontrol.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,802 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_stpsettings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,802 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_switchlog.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,802 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_switchstpsettings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,803 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_dot1pmap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,803 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_ipdscpmap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,803 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_ipdscpmap_map.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,803 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_qospolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,804 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_queuepolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,804 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_queuepolicy_cosqueue.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,804 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_securitypolicy_8021x.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,804 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_securitypolicy_captiveportal.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,805 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_api_sdnconnector.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,805 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_generate_wsdl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,805 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_hitcount.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,805 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_login_challenge.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,806 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_login_user.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,806 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_logout.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,806 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_proxy_json.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,806 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_reboot.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,806 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_task_result.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,807 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,807 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_group_member.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,807 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_ldap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,807 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_ldap_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,808 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,808 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_profile_datamaskcustomfields.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,808 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_radius.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,809 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,809 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_tacacs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,809 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,809 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_adom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,810 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_adomexclude.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,810 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_appfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,810 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_dashboard.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,810 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_dashboardtabs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,811 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_ipsfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,811 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_metadata.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,811 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_policypackage.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,811 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_restrictdevvdom.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,812 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_webfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,812 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertconsole.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,812 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertemail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,812 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertevent.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,813 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertevent_alertdestination.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,813 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,813 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_dlpfilesautodeletion.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,813 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_logautodeletion.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,814 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_quarantinefilesautodeletion.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,814 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_reportautodeletion.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,814 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_backup_allsettings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,814 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_ca.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,814 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_crl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,815 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_local.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,815 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_oftp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,815 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_remote.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,815 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_ssh.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,816 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_connector.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,816 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_customlanguage.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,816 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,817 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_excluderange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,817 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_iprange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,817 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_options.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,817 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_reservedaddress.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,817 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dm.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,818 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dns.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,818 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_docker.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,818 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_externalresource.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,818 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fips.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,819 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiguard.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,819 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiview_autocache.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,819 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiview_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,819 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipcountry.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,820 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,820 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride_ip6range.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,820 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride_iprange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,820 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_global.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,821 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_guiact.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,821 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,821 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_monitoredinterfaces.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,821 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_monitoredips.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,822 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_peer.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,822 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_hascheduledcheck.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,822 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,822 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface_ipv6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,823 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface_member.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,823 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_localinpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,823 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_localinpolicy6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,823 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_disk_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,824 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_disk_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,824 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer2_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,824 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer2_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,824 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer3_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,825 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer3_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,825 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,825 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,826 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_memory_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,826 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_memory_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,826 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,826 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd2_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,827 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd2_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,827 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd3_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,827 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd3_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,827 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd_filter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,828 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,828 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_alert.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,828 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_devicedisable.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,828 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_fospolicystats.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,829 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_interfacestats.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,829 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ioc.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,829 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_maildomain.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,829 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,830 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,830 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit_ratelimits.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,830 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,830 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollinganalyzer.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,831 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollinglocal.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,831 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollingregular.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,831 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_topology.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,831 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,832 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile_devicefilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,832 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile_logfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,832 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_serversettings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,832 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_mail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,833 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_mcpolicydisabledadoms.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,833 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_meta.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,833 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_meta_sysmetafields.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,833 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_metadata_admins.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,834 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,834 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_fpanomaly.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,834 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_isfnpqueues.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,834 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_portcpumap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,835 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_portnpumap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,835 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_priorityprotocol.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,835 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_swehhash.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,835 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ntp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,836 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ntp_ntpserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,836 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_objecttagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,836 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_passwordpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,836 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,837 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_admin.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,837 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_alertmail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,837 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_auth.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,838 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_automation.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,838 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_custommessage.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,838 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_devicedetectionportal.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,838 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_ec.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,838 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_fortiguardwf.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,839 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_ftp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,839 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_http.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,839 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_icap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,839 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mail.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,840 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm1.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,840 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm3.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,840 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm4.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,841 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm7.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,841 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mms.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,841 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_nacquar.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,841 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_nntp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,841 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_spam.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,842 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_sslvpn.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,842 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_trafficquota.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,842 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_utm.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,842 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_webproxy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,843 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsgimage.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,843 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_autocache.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,843 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_estbrowsetime.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,843 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,844 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group_chartalternative.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,844 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group_groupby.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,844 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_setting.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,844 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_route.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,845 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_route6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,845 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_saml.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,845 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_saml_fabricidp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,845 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,846 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_externalaccountlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,846 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_externalip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,846 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_forwardingrule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,846 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_gcpprojectlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,847 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_nic.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,847 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_nic_ip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,847 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_route.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,847 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_routetable.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,848 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_routetable_route.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,848 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_smsserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,848 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sniffer.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,848 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,848 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community_hosts.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,849 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community_hosts6.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,849 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_sysinfo.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,849 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_user.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,849 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_socfabric.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,850 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,850 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_customindex.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,850 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_customskipidx.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,851 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_tsindexfield.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,851 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sslciphersuites.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,851 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_syslog.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,851 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_virtualwirepair.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,852 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_webproxy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,852 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_workflow_approvalmatrix.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,852 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_workflow_approvalmatrix_approver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,852 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_template.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,852 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_templategroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,853 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_adgrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,853 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_clearpass.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,853 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_connector.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,853 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,854 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,854 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,854 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicecategory.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,854 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,855 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,855 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup_tagging.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,855 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_domaincontroller.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,855 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_domaincontroller_extraserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,856 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_exchange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,856 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fortitoken.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,856 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fsso.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,856 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fsso_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,857 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fssopolling.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,857 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fssopolling_adgrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,857 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,857 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,858 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_guest.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,858 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_match.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,858 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_sslvpnoschecklist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,858 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_guest.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,859 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_match.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,859 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_krbkeytab.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,859 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_ldap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,860 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_ldap_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,860 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_local.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,860 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_nsx.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,860 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_nsx_service.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,861 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_passwordpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,861 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_peer.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,861 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_peergrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,861 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_pop3.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,862 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_pxgrid.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,862 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,862 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_accountingserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,862 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,863 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_dynamicmapping_accountingserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,863 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_saml.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,863 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_securityexemptlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,864 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_securityexemptlist_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,864 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_tacacs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,864 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_tacacs_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,864 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_vcenter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,865 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_vcenter_rule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,865 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_utmprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,865 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,866 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_dynamicmapping.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,866 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_macfilterlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,866 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_mpskkey.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,867 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_portalmessageoverrides.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,867 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_vlanname.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,867 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_vlanpool.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,867 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vapgroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,868 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,868 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile_fortiguardcategory.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,868 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile_fortiguardcategory_filters.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,868 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_youtubechannelfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,869 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_youtubechannelfilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,869 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,869 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_msrp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,870 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_sccp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,870 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_sip.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,870 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_ca.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,871 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_ocspserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,871 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_remote.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,871 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ipsec_fec.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,871 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ipsec_fec_mappings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,871 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ssl_settings.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,872 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ssl_settings_authenticationrule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,872 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,872 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_iprange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,873 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_ipv4excluderange.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,873 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_protectedsubnet.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,873 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_summaryaddr.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,873 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_vpntable.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,874 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_hostchecksoftware.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,874 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_hostchecksoftware_checkitemlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,874 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,874 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,875 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup_bookmarks.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,875 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup_bookmarks_formdata.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,875 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_macaddrcheckrule.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,875 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_oschecklist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,876 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_splitdns.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,876 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_realm.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,876 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_mainclass.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,876 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,877 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_addresslist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,877 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,878 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_contentlength.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,878 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_exception.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,878 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_headerlength.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,878 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_hostname.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,878 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_linelength.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,879 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_malformed.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,879 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxcookie.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,880 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxheaderline.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,880 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxrangesegment.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,880 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxurlparam.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,880 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_method.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,881 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_paramlength.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,881 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_urlparamlength.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,881 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_version.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,881 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_method.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,882 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_method_methodpolicy.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,882 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,882 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature_customsignature.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,882 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature_mainclass.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,883 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_urlaccess.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,883 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_urlaccess_accesspattern.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,883 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_signature.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,883 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_subclass.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,883 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wagprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,884 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_authgroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,884 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_peer.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,884 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,884 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_cifs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,885 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_ftp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,885 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_http.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,885 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_mapi.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,885 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_tcp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,886 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,886 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_duplication.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,886 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_healthcheck.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,887 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_healthcheck_sla.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,887 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_members.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,887 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_neighbor.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,887 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_service.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,888 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_service_sla.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,888 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_zone.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,888 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,888 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_healthcheck.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,889 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_healthcheck_sla.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,889 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_members.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,889 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_neighbor.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,889 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_service.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,890 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_service_sla.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,890 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_categories.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,890 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_content.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,891 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_content_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,891 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_contentheader.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,891 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_contentheader_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,891 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_ftgdlocalcat.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,891 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_ftgdlocalrating.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,892 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,892 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,892 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish_custompatterns.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,893 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish_inspectionentries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,893 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_filefilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,893 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_filefilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,893 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,894 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf_filters.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,894 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf_quota.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,894 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_override.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,894 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_urlextraction.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,895 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_web.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,895 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_youtubechannelfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,895 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_urlfilter.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,895 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_urlfilter_entries.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,896 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardserver.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,896 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardservergroup.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,896 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardservergroup_serverlist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,896 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_profile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,897 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_profile_headers.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,897 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_wisp.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,897 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_widsprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,897 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,898 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_denymaclist.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,898 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_eslsesdongle.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,899 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_lan.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,899 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_lbs.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,899 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_platform.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,899 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio1.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,900 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio2.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,900 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio3.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,900 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio4.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,901 root INFO copying ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_splittunnelingacl.py -> build/lib/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:42,901 root INFO creating build/lib/ansible_collections/fortinet/fortios 2023-04-28 05:57:42,901 root INFO copying ansible_collections/fortinet/fortios/CHANGELOG.rst -> build/lib/ansible_collections/fortinet/fortios 2023-04-28 05:57:42,901 root INFO copying ansible_collections/fortinet/fortios/FILES.json -> build/lib/ansible_collections/fortinet/fortios 2023-04-28 05:57:42,902 root INFO copying ansible_collections/fortinet/fortios/LICENSE -> build/lib/ansible_collections/fortinet/fortios 2023-04-28 05:57:42,902 root INFO copying ansible_collections/fortinet/fortios/MANIFEST.json -> build/lib/ansible_collections/fortinet/fortios 2023-04-28 05:57:42,902 root INFO copying ansible_collections/fortinet/fortios/README.md -> build/lib/ansible_collections/fortinet/fortios 2023-04-28 05:57:42,902 root INFO creating build/lib/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:42,903 root INFO copying ansible_collections/fortinet/fortios/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:42,903 root INFO copying ansible_collections/fortinet/fortios/changelogs/changelog.yaml -> build/lib/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:42,903 root INFO copying ansible_collections/fortinet/fortios/changelogs/config.yaml -> build/lib/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:42,903 root INFO creating build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,903 root INFO copying ansible_collections/fortinet/fortios/examples/set_firewall_address.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,904 root INFO copying ansible_collections/fortinet/fortios/examples/set_firewall_address_group.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,904 root INFO copying ansible_collections/fortinet/fortios/examples/set_firewall_vip.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,904 root INFO copying ansible_collections/fortinet/fortios/examples/set_system_alias.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,904 root INFO copying ansible_collections/fortinet/fortios/examples/set_system_dns.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,904 root INFO copying ansible_collections/fortinet/fortios/examples/set_system_global.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,905 root INFO copying ansible_collections/fortinet/fortios/examples/set_system_ha.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,905 root INFO copying ansible_collections/fortinet/fortios/examples/set_system_ha_monitor.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,905 root INFO copying ansible_collections/fortinet/fortios/examples/set_system_ntp.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,905 root INFO copying ansible_collections/fortinet/fortios/examples/set_system_zone.yml -> build/lib/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:42,906 root INFO creating build/lib/ansible_collections/fortinet/fortios/examples/httpapi 2023-04-28 05:57:42,906 root INFO copying ansible_collections/fortinet/fortios/examples/httpapi/readme -> build/lib/ansible_collections/fortinet/fortios/examples/httpapi 2023-04-28 05:57:42,906 root INFO copying ansible_collections/fortinet/fortios/examples/httpapi/set_system_global.yml -> build/lib/ansible_collections/fortinet/fortios/examples/httpapi 2023-04-28 05:57:42,906 root INFO creating build/lib/ansible_collections/fortinet/fortios/examples/httpapi/inventory 2023-04-28 05:57:42,906 root INFO copying ansible_collections/fortinet/fortios/examples/httpapi/inventory/hosts -> build/lib/ansible_collections/fortinet/fortios/examples/httpapi/inventory 2023-04-28 05:57:42,907 root INFO creating build/lib/ansible_collections/fortinet/fortios/meta 2023-04-28 05:57:42,907 root INFO copying ansible_collections/fortinet/fortios/meta/runtime.yml -> build/lib/ansible_collections/fortinet/fortios/meta 2023-04-28 05:57:42,907 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins 2023-04-28 05:57:42,907 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/doc_fragments 2023-04-28 05:57:42,907 root INFO copying ansible_collections/fortinet/fortios/plugins/doc_fragments/fortios.py -> build/lib/ansible_collections/fortinet/fortios/plugins/doc_fragments 2023-04-28 05:57:42,907 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/httpapi 2023-04-28 05:57:42,907 root INFO copying ansible_collections/fortinet/fortios/plugins/httpapi/fortios.py -> build/lib/ansible_collections/fortinet/fortios/plugins/httpapi 2023-04-28 05:57:42,908 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils 2023-04-28 05:57:42,908 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/common 2023-04-28 05:57:42,908 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/common/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/common 2023-04-28 05:57:42,908 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/common/type_utils.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/common 2023-04-28 05:57:42,908 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:42,909 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:42,909 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/common.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:42,909 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/fortimanager.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:42,909 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:42,909 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:42,910 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/comparison.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:42,910 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/data_post_processor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:42,910 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/fortios.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:42,910 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/secret_field.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:42,911 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec 2023-04-28 05:57:42,911 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec 2023-04-28 05:57:42,911 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts 2023-04-28 05:57:42,911 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts 2023-04-28 05:57:42,911 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/facts.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts 2023-04-28 05:57:42,911 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system 2023-04-28 05:57:42,912 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system 2023-04-28 05:57:42,912 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/system.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system 2023-04-28 05:57:42,912 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts 2023-04-28 05:57:42,912 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts 2023-04-28 05:57:42,912 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/facts.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts 2023-04-28 05:57:42,913 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system 2023-04-28 05:57:42,913 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system 2023-04-28 05:57:42,913 root INFO copying ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/system.py -> build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system 2023-04-28 05:57:42,913 root INFO creating build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,913 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/__init__.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,913 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_alertemail_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,914 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_heuristic.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,914 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_mms_checksum.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,914 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_notification.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,915 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,916 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_quarantine.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,916 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,917 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_application_custom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,917 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_application_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,917 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_application_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,918 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_application_name.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,918 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_application_rule_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,918 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_rule.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,919 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_scheme.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,919 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,919 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_automation_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,919 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_ca.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,920 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_crl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,920 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_local.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,920 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_remote.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,921 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_cifs_domain_controller.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,921 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_cifs_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,921 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_configuration_fact.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,922 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_credential_store_domain_controller.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,922 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_data_type.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,922 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_dictionary.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,922 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_filepattern.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,923 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_fp_doc_source.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,923 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_fp_sensitivity.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,923 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,923 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_sensitivity.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,924 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_sensor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,924 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,924 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dnsfilter_domain_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,925 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dnsfilter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,925 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dpdk_cpus.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,925 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_dpdk_global.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,925 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_block_allow_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,926 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_bwl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,926 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_bword.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,926 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_dnsbl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,926 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_fortishield.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,927 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_iptrust.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,927 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_mheader.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,927 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_options.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,928 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,928 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_client.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,928 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_fctems.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,928 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_forticlient_ems.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,929 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_forticlient_registration_sync.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,929 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,929 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_registered_forticlient.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,930 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,930 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_export_config_playbook.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,930 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_dataplan.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,931 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_extender.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,931 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_extender_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,932 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_extender_info.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,932 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_lte_carrier_by_mcc_mnc.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,932 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_lte_carrier_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,932 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_modem_status.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,933 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_sys_info.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,933 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_dataplan.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,933 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_extender.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,933 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_extender_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,934 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_fortigate.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,934 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_fortigate_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,934 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_file_filter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,934 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,935 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,936 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy_ssh_client_cert.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,936 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy_virtual_host.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,936 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_acl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,937 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_acl6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,937 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,937 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,938 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address6_template.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,938 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_addrgrp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,938 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_addrgrp6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,939 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_auth_portal.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,939 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_carrier_endpoint_bwl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,939 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_central_snat_map.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,939 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_city.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,940 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_consolidated_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,940 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_country.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,940 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_decrypted_traffic_mirror.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,941 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dnstranslation.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,941 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dos_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,941 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dos_policy6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,941 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_global.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,942 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_gtp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,942 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_identity_based_route.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,943 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_interface_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,943 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_interface_policy6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,944 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,944 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_addition.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,944 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_append.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,944 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_botnet.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,945 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_custom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,945 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_custom_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,945 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_definition.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,945 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_extension.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,946 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,946 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_ipbl_reason.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,946 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_ipbl_vendor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,946 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,947 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_name.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,947 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_owner.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,947 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_reputation.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,947 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_sld.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,948 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ip_translation.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,948 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipmacbinding_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,948 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipmacbinding_table.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,948 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ippool.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,949 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ippool6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,949 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_iprope_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,949 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipv6_eh_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,949 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ldb_monitor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,950 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_local_in_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,950 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_local_in_policy6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,950 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_mms_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,951 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_address.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,951 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_address6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,951 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,952 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_policy6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,952 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_network_service_dynamic.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,952 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_pfcp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,952 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,953 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy46.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,953 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,954 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy64.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,954 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_profile_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,954 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_profile_protocol_options.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,955 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proute.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,955 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_address.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,956 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_addrgrp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,956 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,956 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_region.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,957 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,957 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_onetime.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,957 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_recurring.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,958 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_security_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,958 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_category.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,958 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_custom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,959 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,959 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaper_per_ip_shaper.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,959 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaper_traffic_shaper.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,959 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaping_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,960 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaping_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,960 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_sniffer.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,961 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_host_key.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,961 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_local_ca.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,961 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_local_key.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,961 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,962 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,962 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,962 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_ssh_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,963 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_traffic_class.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,963 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ttl_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,964 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vendor_mac.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,964 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,965 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip46.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,965 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,967 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip64.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,967 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,967 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp46.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,967 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,968 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp64.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,968 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_wildcard_fqdn_custom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,968 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_wildcard_fqdn_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,968 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ftp_proxy_explicit.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,969 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apn.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,969 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apn_shaper.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,969 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apngrp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,969 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_ie_allow_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,970 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_ie_white_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,970 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_message_filter_v0v1.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,970 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_message_filter_v2.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,971 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_rat_timeout_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,971 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_tunnel_limit.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,971 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_nic.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,971 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_dce.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,972 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_session_stats.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,972 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_sse_stats.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,972 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,972 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,973 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_server_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,973 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_custom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,973 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_decoder.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,974 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_global.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,974 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_rule.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,974 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_rule_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,974 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_sensor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,975 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,975 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_view_map.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,975 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_json_generic.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,975 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_custom_field.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,976 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_disk_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,976 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_disk_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,976 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_eventfilter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,977 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fact.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,977 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,978 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,978 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,978 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,979 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,979 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,979 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,979 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,980 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,980 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,980 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,981 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,981 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,981 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,982 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,982 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,982 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,983 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,983 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,983 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,984 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_gui_display.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,984 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,984 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_global_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,984 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,985 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_null_device_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,985 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_null_device_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,985 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,986 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,986 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,986 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,987 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,987 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,987 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,988 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,988 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,988 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,989 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,989 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,989 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,990 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,990 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_override_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,990 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_override_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,991 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,991 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting2_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,991 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting2_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,991 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting3_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,992 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting3_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,992 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,992 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,992 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_threat_weight.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,993 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_webtrends_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,993 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_log_webtrends_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,993 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_monitor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,994 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_monitor_fact.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,994 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_monitoring_np6_ipsec_engine.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,995 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_monitoring_npu_hpe.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,995 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_nsxt_service_chain.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,995 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_nsxt_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,995 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_pfcp_message_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,996 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_report_chart.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,996 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_report_dataset.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,996 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_report_layout.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,997 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_report_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,997 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_report_style.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,997 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_report_theme.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,998 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_access_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,998 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_access_list6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,998 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_aspath_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,998 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_auth_path.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,999 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bfd.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,999 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bfd6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:42,999 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bgp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,000 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_community_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,001 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_isis.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,002 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_key_chain.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,002 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,002 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,003 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast_flow.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,003 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ospf.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,004 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ospf6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,005 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,005 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_policy6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,005 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_prefix_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,005 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_prefix_list6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,006 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_rip.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,006 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ripng.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,006 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_route_map.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,007 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,007 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,007 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,008 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_sctp_filter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,008 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_bwl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,008 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_bword.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,009 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_dnsbl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,009 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_fortishield.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,009 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_iptrust.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,009 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_mheader.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,009 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_options.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,010 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,010 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_ssh_filter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,010 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_802_1x_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,011 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_custom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,011 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_default.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,011 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,011 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_custom_command.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,012 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_dynamic_port_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,012 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_flow_tracking.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,012 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_fortilink_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,012 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_global.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,013 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_igmp_snooping.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,013 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_initial_config_template.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,013 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_initial_config_vlans.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,014 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_lldp_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,014 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_lldp_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,014 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_location.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,014 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_mac_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,015 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_mac_sync_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,015 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_managed_switch.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,016 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_nac_device.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,016 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_nac_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,017 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_network_monitor_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,017 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_poe.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,017 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_port_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,018 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_ptp_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,018 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_ptp_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,018 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_dot1p_map.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,018 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_ip_dscp_map.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,019 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_qos_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,019 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_queue_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,019 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_quarantine.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,019 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_remote_log.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,020 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_802_1x.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,020 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_captive_portal.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,020 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_local_access.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,021 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_sflow.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,021 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_community.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,021 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_sysinfo.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,021 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_trap_threshold.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,022 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_user.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,022 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_storm_control.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,022 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_storm_control_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,022 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_stp_instance.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,023 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_stp_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,023 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,023 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_interface_tag.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,023 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_log.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,024 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,024 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_system.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,024 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_traffic_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,025 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_traffic_sniffer.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,025 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_virtual_port_pool.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,025 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_vlan.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,025 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_vlan_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,026 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_3g_modem_custom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,026 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_accprofile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,026 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_acme.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,027 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_admin.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,027 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_affinity_interrupt.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,027 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_affinity_packet_redistribution.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,028 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_alarm.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,028 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_alias.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,028 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_api_user.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,028 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_arp_table.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,029 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_auto_install.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,029 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_auto_script.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,029 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_action.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,030 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_destination.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,030 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_stitch.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,030 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_trigger.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,030 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_push_update.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,031 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_schedule.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,031 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_tunneling.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,031 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_central_management.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,032 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_cluster_sync.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,032 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_console.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,032 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_csf.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,032 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_custom_language.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,033 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ddns.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,033 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dedicated_mgmt.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,033 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dhcp6_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,034 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dhcp_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,034 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,034 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns64.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,035 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns_database.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,035 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,035 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dscp_based_priority.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,035 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_email_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,036 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_external_resource.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,036 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_federated_upgrade.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,036 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fips_cc.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,037 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fm.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,037 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortiai.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,037 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortiguard.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,037 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortimanager.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,038 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortindr.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,038 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortisandbox.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,038 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fsso_polling.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,039 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ftm_push.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,039 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geneve.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,039 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geoip_country.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,039 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geoip_override.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,040 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_gi_gk.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,040 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_global.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,041 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_gre_tunnel.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,041 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ha.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,042 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ha_monitor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,042 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ike.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,043 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_interface.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,044 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipam.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,044 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipip_tunnel.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,044 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,045 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips_urlfilter_dns.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,045 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips_urlfilter_dns6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,045 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipsec_aggregate.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,046 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipv6_neighbor_cache.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,046 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipv6_tunnel.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,046 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_isf_queue_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,047 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_link_monitor.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,047 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_lldp_network_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,047 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_lte_modem.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,048 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mac_address_table.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,048 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_management_tunnel.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,048 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mem_mgr.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,048 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mobile_tunnel.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,049 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_modem.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,049 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_nat64.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,049 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_nd_proxy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,049 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_netflow.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,050 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_network_visibility.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,050 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_np6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,050 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_npu.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,051 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ntp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,051 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_object_tagging.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,051 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_password_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,052 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_password_policy_guest_admin.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,052 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_performance_top.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,052 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_physical_switch.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,052 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_pppoe_interface.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,053 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_probe_response.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,053 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_proxy_arp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,053 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ptp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,053 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_admin.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,054 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_alertmail.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,054 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_auth.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,054 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_automation.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,054 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_device_detection_portal.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,055 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_ec.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,055 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_fortiguard_wf.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,055 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_ftp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,055 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,056 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_http.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,057 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_icap.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,057 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_image.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,057 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mail.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,058 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm1.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,058 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm3.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,058 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm4.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,058 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm7.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,059 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mms.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,059 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_nac_quar.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,059 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_nntp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,059 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_spam.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,060 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_sslvpn.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,060 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_traffic_quota.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,060 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_utm.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,061 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_webproxy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,061 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_resource_limits.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,061 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_saml.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,061 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sdn_connector.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,062 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sdwan.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,062 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_session_helper.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,063 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_session_ttl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,063 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,064 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sflow.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,064 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sit_tunnel.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,064 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_smc_ntp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,065 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sms_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,065 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_community.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,065 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_mib_view.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,065 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_sysinfo.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,066 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_user.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,066 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_speed_test_schedule.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,066 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_speed_test_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,067 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sso_admin.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,067 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sso_forticloud_admin.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,067 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_standalone_cluster.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,067 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_storage.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,068 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_stp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,068 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_switch_interface.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,068 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_tos_based_priority.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,069 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,069 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_dns.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,069 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_exception.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,069 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_link.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,070 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_netflow.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,070 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_property.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,070 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_radius_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,070 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_sflow.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,071 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_switch.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,071 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_wan_link.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,071 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_wire_pair.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,072 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vne_tunnel.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,072 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vxlan.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,072 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_wccp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,073 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_system_zone.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,073 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_adgrp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,073 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_certificate.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,073 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,074 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_access_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,074 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_category.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,074 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,074 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_domain_controller.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,075 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_exchange.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,075 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fortitoken.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,075 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fsso.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,075 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fsso_polling.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,076 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,076 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_krb_keytab.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,076 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_ldap.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,077 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_local.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,077 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_nac_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,077 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_password_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,078 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_peer.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,078 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_peergrp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,078 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_pop3.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,078 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_quarantine.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,079 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_radius.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,079 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_saml.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,079 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_security_exempt_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,080 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,080 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_user_tacacsplus.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,080 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,081 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_youtube_channel_filter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,081 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_youtube_key.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,081 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_voip_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,082 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_ca.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,082 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_crl.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,083 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_local.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,083 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_ocsp_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,083 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_remote.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,084 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,084 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ike_gateway.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,084 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_concentrator.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,085 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_fec.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,085 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_forticlient.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,085 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_manualkey.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,085 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_manualkey_interface.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,086 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase1.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,086 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase1_interface.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,087 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase2.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,088 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase2_interface.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,089 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_l2tp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,089 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ocvpn.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,089 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_pptp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,089 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_client.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,090 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,090 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_host_check_software.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,091 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_portal.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,091 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_realm.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,092 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_user_bookmark.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,092 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_user_group_bookmark.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,093 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_main_class.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,093 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,094 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_signature.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,094 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_sub_class.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,094 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_auth_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,095 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_cache_service.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,095 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_content_delivery_network_rule.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,095 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_peer.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,096 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,096 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_remote_storage.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,096 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_settings.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,097 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_webcache.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,097 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_debug_url.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,097 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_explicit.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,097 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_forward_server.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,098 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_forward_server_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,098 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_global.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,098 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,099 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_url_match.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,099 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_wisp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,099 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_content.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,100 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_content_header.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,100 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_fortiguard.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,100 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ftgd_local_cat.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,100 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ftgd_local_rating.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,101 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_cache_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,101 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,101 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_setting6.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,101 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_override.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,102 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,102 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_search_engine.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,103 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_status.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,103 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_urlfilter.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,103 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_access_control_list.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,103 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_address.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,104 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_addrgrp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,104 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ap_status.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,104 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_apcfg_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,104 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_arrp_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,105 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ble_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,105 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_bonjour_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,105 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_client_info.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,106 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_global.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,106 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_3gpp_cellular.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,106 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_ip_address_type.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,106 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_nai_realm.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,107 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_network_auth_type.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,107 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_roaming_consortium.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,107 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_venue_name.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,108 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_venue_url.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,108 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_advice_of_charge.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,108 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_conn_capability.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,108 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_operator_name.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,109 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_osu_provider.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,109 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_osu_provider_nai.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,109 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_terms_and_conditions.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,109 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_wan_metric.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,110 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_hs_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,110 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_icon.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,110 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_qos_map.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,111 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_inter_controller.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,111 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_log.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,111 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_mpsk_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,112 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_nac_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,112 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_qos_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,112 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_region.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,112 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_rf_analysis.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,113 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_setting.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,113 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_snmp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,114 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_spectral_info.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,114 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ssid_policy.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,114 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_status.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,114 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_syslog_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,115 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_timers.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,115 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_utm_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,115 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,116 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,116 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap_status.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,117 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wag_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,117 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wids_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,117 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,118 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_group.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,119 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_profile.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,121 root INFO copying ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_status.py -> build/lib/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:43,121 root INFO creating build/lib/ansible_collections/frr 2023-04-28 05:57:43,121 root INFO creating build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,121 root INFO copying ansible_collections/frr/frr/CHANGELOG.rst -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,122 root INFO copying ansible_collections/frr/frr/FILES.json -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,122 root INFO copying ansible_collections/frr/frr/LICENSE -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,122 root INFO copying ansible_collections/frr/frr/MANIFEST.json -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,123 root INFO copying ansible_collections/frr/frr/README.md -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,123 root INFO copying ansible_collections/frr/frr/bindep.txt -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,123 root INFO copying ansible_collections/frr/frr/codecov.yml -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,123 root INFO copying ansible_collections/frr/frr/pyproject.toml -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,124 root INFO copying ansible_collections/frr/frr/requirements.txt -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,124 root INFO copying ansible_collections/frr/frr/test-requirements.txt -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,124 root INFO copying ansible_collections/frr/frr/tox.ini -> build/lib/ansible_collections/frr/frr 2023-04-28 05:57:43,124 root INFO creating build/lib/ansible_collections/frr/frr/changelogs 2023-04-28 05:57:43,124 root INFO copying ansible_collections/frr/frr/changelogs/changelog.yaml -> build/lib/ansible_collections/frr/frr/changelogs 2023-04-28 05:57:43,125 root INFO copying ansible_collections/frr/frr/changelogs/config.yaml -> build/lib/ansible_collections/frr/frr/changelogs 2023-04-28 05:57:43,125 root INFO creating build/lib/ansible_collections/frr/frr/meta 2023-04-28 05:57:43,125 root INFO copying ansible_collections/frr/frr/meta/runtime.yml -> build/lib/ansible_collections/frr/frr/meta 2023-04-28 05:57:43,125 root INFO creating build/lib/ansible_collections/frr/frr/plugins 2023-04-28 05:57:43,125 root INFO creating build/lib/ansible_collections/frr/frr/plugins/cliconf 2023-04-28 05:57:43,126 root INFO copying ansible_collections/frr/frr/plugins/cliconf/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/cliconf 2023-04-28 05:57:43,126 root INFO copying ansible_collections/frr/frr/plugins/cliconf/frr.py -> build/lib/ansible_collections/frr/frr/plugins/cliconf 2023-04-28 05:57:43,126 root INFO creating build/lib/ansible_collections/frr/frr/plugins/module_utils 2023-04-28 05:57:43,126 root INFO copying ansible_collections/frr/frr/plugins/module_utils/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils 2023-04-28 05:57:43,126 root INFO creating build/lib/ansible_collections/frr/frr/plugins/module_utils/network 2023-04-28 05:57:43,127 root INFO creating build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr 2023-04-28 05:57:43,127 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr 2023-04-28 05:57:43,127 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/frr.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr 2023-04-28 05:57:43,127 root INFO creating build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:43,127 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:43,128 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/module.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:43,128 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/providers.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:43,128 root INFO creating build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli 2023-04-28 05:57:43,128 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli 2023-04-28 05:57:43,128 root INFO creating build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config 2023-04-28 05:57:43,129 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config 2023-04-28 05:57:43,129 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/base.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config 2023-04-28 05:57:43,129 root INFO creating build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:43,130 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:43,130 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/address_family.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:43,130 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/neighbors.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:43,130 root INFO copying ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/process.py -> build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:43,131 root INFO creating build/lib/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:43,131 root INFO copying ansible_collections/frr/frr/plugins/modules/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:43,131 root INFO copying ansible_collections/frr/frr/plugins/modules/frr_bgp.py -> build/lib/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:43,131 root INFO copying ansible_collections/frr/frr/plugins/modules/frr_facts.py -> build/lib/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:43,132 root INFO creating build/lib/ansible_collections/frr/frr/plugins/terminal 2023-04-28 05:57:43,132 root INFO copying ansible_collections/frr/frr/plugins/terminal/__init__.py -> build/lib/ansible_collections/frr/frr/plugins/terminal 2023-04-28 05:57:43,132 root INFO copying ansible_collections/frr/frr/plugins/terminal/frr.py -> build/lib/ansible_collections/frr/frr/plugins/terminal 2023-04-28 05:57:43,132 root INFO creating build/lib/ansible_collections/gluster 2023-04-28 05:57:43,132 root INFO creating build/lib/ansible_collections/gluster/gluster 2023-04-28 05:57:43,132 root INFO copying ansible_collections/gluster/gluster/CHANGELOG.rst -> build/lib/ansible_collections/gluster/gluster 2023-04-28 05:57:43,133 root INFO copying ansible_collections/gluster/gluster/FILES.json -> build/lib/ansible_collections/gluster/gluster 2023-04-28 05:57:43,133 root INFO copying ansible_collections/gluster/gluster/LICENSE -> build/lib/ansible_collections/gluster/gluster 2023-04-28 05:57:43,133 root INFO copying ansible_collections/gluster/gluster/MANIFEST.json -> build/lib/ansible_collections/gluster/gluster 2023-04-28 05:57:43,133 root INFO copying ansible_collections/gluster/gluster/README.md -> build/lib/ansible_collections/gluster/gluster 2023-04-28 05:57:43,134 root INFO creating build/lib/ansible_collections/gluster/gluster/changelogs 2023-04-28 05:57:43,134 root INFO copying ansible_collections/gluster/gluster/changelogs/changelog.yaml -> build/lib/ansible_collections/gluster/gluster/changelogs 2023-04-28 05:57:43,134 root INFO copying ansible_collections/gluster/gluster/changelogs/config.yaml -> build/lib/ansible_collections/gluster/gluster/changelogs 2023-04-28 05:57:43,134 root INFO creating build/lib/ansible_collections/gluster/gluster/meta 2023-04-28 05:57:43,134 root INFO copying ansible_collections/gluster/gluster/meta/runtime.yml -> build/lib/ansible_collections/gluster/gluster/meta 2023-04-28 05:57:43,135 root INFO creating build/lib/ansible_collections/gluster/gluster/plugins 2023-04-28 05:57:43,135 root INFO creating build/lib/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:43,135 root INFO copying ansible_collections/gluster/gluster/plugins/modules/geo_rep.py -> build/lib/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:43,135 root INFO copying ansible_collections/gluster/gluster/plugins/modules/gluster_heal_info.py -> build/lib/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:43,135 root INFO copying ansible_collections/gluster/gluster/plugins/modules/gluster_peer.py -> build/lib/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:43,136 root INFO copying ansible_collections/gluster/gluster/plugins/modules/gluster_volume.py -> build/lib/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:43,136 root INFO creating build/lib/ansible_collections/google 2023-04-28 05:57:43,136 root INFO creating build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,136 root INFO copying ansible_collections/google/cloud/CHANGELOG.rst -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,136 root INFO copying ansible_collections/google/cloud/CONTRIBUTING.md -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,137 root INFO copying ansible_collections/google/cloud/FILES.json -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,137 root INFO copying ansible_collections/google/cloud/LICENSE -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,137 root INFO copying ansible_collections/google/cloud/MAINTAINING.md -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,138 root INFO copying ansible_collections/google/cloud/MANIFEST.json -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,138 root INFO copying ansible_collections/google/cloud/README.md -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,138 root INFO copying ansible_collections/google/cloud/requirements-test.txt -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,138 root INFO copying ansible_collections/google/cloud/requirements.txt -> build/lib/ansible_collections/google/cloud 2023-04-28 05:57:43,138 root INFO creating build/lib/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:43,139 root INFO copying ansible_collections/google/cloud/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:43,139 root INFO copying ansible_collections/google/cloud/changelogs/changelog.yaml -> build/lib/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:43,139 root INFO copying ansible_collections/google/cloud/changelogs/config.yaml -> build/lib/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:43,139 root INFO creating build/lib/ansible_collections/google/cloud/meta 2023-04-28 05:57:43,139 root INFO copying ansible_collections/google/cloud/meta/runtime.yml -> build/lib/ansible_collections/google/cloud/meta 2023-04-28 05:57:43,140 root INFO creating build/lib/ansible_collections/google/cloud/molecule 2023-04-28 05:57:43,140 root INFO creating build/lib/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:43,140 root INFO copying ansible_collections/google/cloud/molecule/gcloud/Dockerfile.j2 -> build/lib/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:43,140 root INFO copying ansible_collections/google/cloud/molecule/gcloud/archive_playbook.yml -> build/lib/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:43,140 root INFO copying ansible_collections/google/cloud/molecule/gcloud/converge.yml -> build/lib/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:43,141 root INFO copying ansible_collections/google/cloud/molecule/gcloud/molecule.yml -> build/lib/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:43,141 root INFO copying ansible_collections/google/cloud/molecule/gcloud/package_playbook.yml -> build/lib/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:43,141 root INFO copying ansible_collections/google/cloud/molecule/gcloud/verify.yml -> build/lib/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:43,141 root INFO creating build/lib/ansible_collections/google/cloud/molecule/gcloud/files 2023-04-28 05:57:43,141 root INFO copying ansible_collections/google/cloud/molecule/gcloud/files/override.conf -> build/lib/ansible_collections/google/cloud/molecule/gcloud/files 2023-04-28 05:57:43,142 root INFO creating build/lib/ansible_collections/google/cloud/molecule/gcloud/tests 2023-04-28 05:57:43,142 root INFO copying ansible_collections/google/cloud/molecule/gcloud/tests/test_default.py -> build/lib/ansible_collections/google/cloud/molecule/gcloud/tests 2023-04-28 05:57:43,142 root INFO creating build/lib/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:43,142 root INFO copying ansible_collections/google/cloud/molecule/gcsfuse/Dockerfile.j2 -> build/lib/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:43,142 root INFO copying ansible_collections/google/cloud/molecule/gcsfuse/converge.yml -> build/lib/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:43,142 root INFO copying ansible_collections/google/cloud/molecule/gcsfuse/molecule.yml -> build/lib/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:43,143 root INFO copying ansible_collections/google/cloud/molecule/gcsfuse/verify.yml -> build/lib/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:43,143 root INFO creating build/lib/ansible_collections/google/cloud/molecule/gcsfuse/files 2023-04-28 05:57:43,143 root INFO copying ansible_collections/google/cloud/molecule/gcsfuse/files/override.conf -> build/lib/ansible_collections/google/cloud/molecule/gcsfuse/files 2023-04-28 05:57:43,143 root INFO creating build/lib/ansible_collections/google/cloud/molecule/gcsfuse/tests 2023-04-28 05:57:43,143 root INFO copying ansible_collections/google/cloud/molecule/gcsfuse/tests/test_default.py -> build/lib/ansible_collections/google/cloud/molecule/gcsfuse/tests 2023-04-28 05:57:43,144 root INFO creating build/lib/ansible_collections/google/cloud/plugins 2023-04-28 05:57:43,144 root INFO copying ansible_collections/google/cloud/plugins/README.md -> build/lib/ansible_collections/google/cloud/plugins 2023-04-28 05:57:43,144 root INFO creating build/lib/ansible_collections/google/cloud/plugins/doc_fragments 2023-04-28 05:57:43,144 root INFO copying ansible_collections/google/cloud/plugins/doc_fragments/gcp.py -> build/lib/ansible_collections/google/cloud/plugins/doc_fragments 2023-04-28 05:57:43,144 root INFO creating build/lib/ansible_collections/google/cloud/plugins/filter 2023-04-28 05:57:43,144 root INFO copying ansible_collections/google/cloud/plugins/filter/gcp_kms_filters.py -> build/lib/ansible_collections/google/cloud/plugins/filter 2023-04-28 05:57:43,145 root INFO creating build/lib/ansible_collections/google/cloud/plugins/inventory 2023-04-28 05:57:43,145 root INFO copying ansible_collections/google/cloud/plugins/inventory/gcp_compute.py -> build/lib/ansible_collections/google/cloud/plugins/inventory 2023-04-28 05:57:43,145 root INFO creating build/lib/ansible_collections/google/cloud/plugins/module_utils 2023-04-28 05:57:43,145 root INFO copying ansible_collections/google/cloud/plugins/module_utils/gcp_utils.py -> build/lib/ansible_collections/google/cloud/plugins/module_utils 2023-04-28 05:57:43,145 root INFO creating build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,146 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_appengine_firewall_rule.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,146 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_appengine_firewall_rule_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,146 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_bigquery_dataset.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,146 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_bigquery_dataset_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,147 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_bigquery_table.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,147 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_bigquery_table_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,147 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_bigtable_instance.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,147 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_bigtable_instance_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,148 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudbuild_trigger.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,148 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudbuild_trigger_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,148 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudfunctions_cloud_function.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,148 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudfunctions_cloud_function_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,149 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudscheduler_job.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,149 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudscheduler_job_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,149 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudtasks_queue.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,149 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_cloudtasks_queue_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,150 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_address.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,150 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_address_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,150 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_autoscaler.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,150 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_autoscaler_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,151 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_bucket.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,151 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_bucket_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,151 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_service.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,151 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_service_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,152 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_disk.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,152 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_disk_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,152 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_external_vpn_gateway.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,152 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_external_vpn_gateway_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,153 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_firewall.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,153 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_firewall_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,153 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_forwarding_rule.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,153 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_forwarding_rule_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,154 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_global_address.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,154 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_global_address_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,154 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_global_forwarding_rule.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,154 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_global_forwarding_rule_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,155 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_health_check.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,155 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_health_check_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,155 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_http_health_check.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,155 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_http_health_check_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,156 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_https_health_check.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,156 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_https_health_check_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,156 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_image.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,156 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_image_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,157 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,157 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,157 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,157 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_manager.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,158 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_manager_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,158 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,158 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_template.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,158 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_template_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,159 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_interconnect_attachment.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,159 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_interconnect_attachment_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,159 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_network.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,159 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_network_endpoint_group.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,160 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_network_endpoint_group_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,160 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_network_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,160 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_node_group.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,160 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_node_group_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,161 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_node_template.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,161 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_node_template_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,161 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_autoscaler.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,161 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_autoscaler_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,162 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_backend_service.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,162 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_backend_service_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,162 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_disk.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,163 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_disk_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,163 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_health_check.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,163 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_health_check_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,163 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_instance_group_manager.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,164 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_instance_group_manager_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,164 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_http_proxy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,164 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_http_proxy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,164 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_https_proxy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,164 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_https_proxy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,165 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_url_map.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,165 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_region_url_map_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,166 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_reservation.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,166 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_reservation_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,166 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_resource_policy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,167 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_resource_policy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,167 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_route.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,167 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_route_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,167 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_router.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,168 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_router_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,168 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_snapshot.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,168 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_snapshot_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,168 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_certificate.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,168 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_certificate_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,169 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_policy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,169 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_policy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,169 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_subnetwork.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,169 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_subnetwork_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,170 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_http_proxy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,170 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_http_proxy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,170 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_https_proxy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,170 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_https_proxy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,171 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_instance.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,171 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_instance_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,171 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_pool.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,171 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_pool_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,172 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_ssl_proxy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,172 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_ssl_proxy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,172 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_tcp_proxy.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,172 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_tcp_proxy_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,173 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_vpn_gateway.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,173 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_target_vpn_gateway_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,173 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_url_map.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,174 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_url_map_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,174 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_vpn_tunnel.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,175 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_compute_vpn_tunnel_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,175 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_container_cluster.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,175 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_container_cluster_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,176 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_container_node_pool.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,176 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_container_node_pool_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,176 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_dns_managed_zone.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,176 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_dns_managed_zone_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,177 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_dns_resource_record_set.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,177 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_dns_resource_record_set_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,177 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_filestore_instance.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,177 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_filestore_instance_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,178 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_iam_role.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,178 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_iam_role_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,178 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,178 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,178 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account_key.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,179 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_kms_crypto_key.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,179 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_kms_crypto_key_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,179 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_kms_key_ring.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,179 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_kms_key_ring_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,180 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_logging_metric.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,180 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_logging_metric_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,180 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_mlengine_model.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,180 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_mlengine_model_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,181 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_mlengine_version.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,181 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_mlengine_version_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,181 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_pubsub_subscription.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,181 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_pubsub_subscription_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,182 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_pubsub_topic.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,182 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_pubsub_topic_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,182 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_redis_instance.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,182 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_redis_instance_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,183 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_resourcemanager_project.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,183 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_resourcemanager_project_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,183 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_config.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,183 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_config_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,183 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_variable.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,184 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_variable_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,184 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_serviceusage_service.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,184 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_serviceusage_service_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,184 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sourcerepo_repository.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,185 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sourcerepo_repository_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,185 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_spanner_database.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,185 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_spanner_database_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,185 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_spanner_instance.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,186 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_spanner_instance_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,186 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sql_database.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,186 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sql_database_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,186 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sql_instance.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,187 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sql_instance_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,187 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sql_ssl_cert.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,187 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sql_user.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,187 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_sql_user_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,188 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_storage_bucket.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,188 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_storage_bucket_access_control.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,188 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_storage_default_object_acl.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,188 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_storage_object.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,189 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_tpu_node.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,189 root INFO copying ansible_collections/google/cloud/plugins/modules/gcp_tpu_node_info.py -> build/lib/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:43,189 root INFO creating build/lib/ansible_collections/google/cloud/roles 2023-04-28 05:57:43,189 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcloud 2023-04-28 05:57:43,189 root INFO copying ansible_collections/google/cloud/roles/gcloud/README.md -> build/lib/ansible_collections/google/cloud/roles/gcloud 2023-04-28 05:57:43,190 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcloud/defaults 2023-04-28 05:57:43,190 root INFO copying ansible_collections/google/cloud/roles/gcloud/defaults/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/defaults 2023-04-28 05:57:43,190 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcloud/meta 2023-04-28 05:57:43,190 root INFO copying ansible_collections/google/cloud/roles/gcloud/meta/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/meta 2023-04-28 05:57:43,190 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcloud/tasks 2023-04-28 05:57:43,190 root INFO copying ansible_collections/google/cloud/roles/gcloud/tasks/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/tasks 2023-04-28 05:57:43,191 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:43,191 root INFO copying ansible_collections/google/cloud/roles/gcloud/tasks/archive/archive_install.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:43,191 root INFO copying ansible_collections/google/cloud/roles/gcloud/tasks/archive/command_completion.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:43,191 root INFO copying ansible_collections/google/cloud/roles/gcloud/tasks/archive/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:43,191 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:43,192 root INFO copying ansible_collections/google/cloud/roles/gcloud/tasks/package/debian.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:43,192 root INFO copying ansible_collections/google/cloud/roles/gcloud/tasks/package/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:43,192 root INFO copying ansible_collections/google/cloud/roles/gcloud/tasks/package/redhat.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:43,192 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcloud/vars 2023-04-28 05:57:43,192 root INFO copying ansible_collections/google/cloud/roles/gcloud/vars/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcloud/vars 2023-04-28 05:57:43,193 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcp_http_lb 2023-04-28 05:57:43,193 root INFO copying ansible_collections/google/cloud/roles/gcp_http_lb/README.md -> build/lib/ansible_collections/google/cloud/roles/gcp_http_lb 2023-04-28 05:57:43,193 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/defaults 2023-04-28 05:57:43,193 root INFO copying ansible_collections/google/cloud/roles/gcp_http_lb/defaults/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/defaults 2023-04-28 05:57:43,193 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/meta 2023-04-28 05:57:43,193 root INFO copying ansible_collections/google/cloud/roles/gcp_http_lb/meta/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/meta 2023-04-28 05:57:43,194 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tasks 2023-04-28 05:57:43,194 root INFO copying ansible_collections/google/cloud/roles/gcp_http_lb/tasks/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tasks 2023-04-28 05:57:43,194 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tests 2023-04-28 05:57:43,194 root INFO copying ansible_collections/google/cloud/roles/gcp_http_lb/tests/inventory -> build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tests 2023-04-28 05:57:43,194 root INFO copying ansible_collections/google/cloud/roles/gcp_http_lb/tests/test.yml -> build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tests 2023-04-28 05:57:43,194 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/vars 2023-04-28 05:57:43,195 root INFO copying ansible_collections/google/cloud/roles/gcp_http_lb/vars/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/vars 2023-04-28 05:57:43,195 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcsfuse 2023-04-28 05:57:43,195 root INFO copying ansible_collections/google/cloud/roles/gcsfuse/README.md -> build/lib/ansible_collections/google/cloud/roles/gcsfuse 2023-04-28 05:57:43,195 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcsfuse/defaults 2023-04-28 05:57:43,195 root INFO copying ansible_collections/google/cloud/roles/gcsfuse/defaults/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcsfuse/defaults 2023-04-28 05:57:43,196 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcsfuse/handlers 2023-04-28 05:57:43,196 root INFO copying ansible_collections/google/cloud/roles/gcsfuse/handlers/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcsfuse/handlers 2023-04-28 05:57:43,196 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcsfuse/meta 2023-04-28 05:57:43,196 root INFO copying ansible_collections/google/cloud/roles/gcsfuse/meta/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcsfuse/meta 2023-04-28 05:57:43,196 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcsfuse/tasks 2023-04-28 05:57:43,196 root INFO copying ansible_collections/google/cloud/roles/gcsfuse/tasks/debian.yml -> build/lib/ansible_collections/google/cloud/roles/gcsfuse/tasks 2023-04-28 05:57:43,197 root INFO copying ansible_collections/google/cloud/roles/gcsfuse/tasks/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcsfuse/tasks 2023-04-28 05:57:43,197 root INFO creating build/lib/ansible_collections/google/cloud/roles/gcsfuse/vars 2023-04-28 05:57:43,197 root INFO copying ansible_collections/google/cloud/roles/gcsfuse/vars/main.yml -> build/lib/ansible_collections/google/cloud/roles/gcsfuse/vars 2023-04-28 05:57:43,197 root INFO creating build/lib/ansible_collections/google/cloud/scripts 2023-04-28 05:57:43,197 root INFO copying ansible_collections/google/cloud/scripts/bootstrap-project.sh -> build/lib/ansible_collections/google/cloud/scripts 2023-04-28 05:57:43,198 root INFO copying ansible_collections/google/cloud/scripts/cleanup-project.sh -> build/lib/ansible_collections/google/cloud/scripts 2023-04-28 05:57:43,198 root INFO creating build/lib/ansible_collections/google/cloud/test-fixtures 2023-04-28 05:57:43,198 root INFO copying ansible_collections/google/cloud/test-fixtures/cloud-function.zip -> build/lib/ansible_collections/google/cloud/test-fixtures 2023-04-28 05:57:43,198 root INFO creating build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:43,198 root INFO copying ansible_collections/google/cloud/test-fixtures/cloud-function-source/build-function-zip.sh -> build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:43,198 root INFO copying ansible_collections/google/cloud/test-fixtures/cloud-function-source/main.py -> build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:43,199 root INFO copying ansible_collections/google/cloud/test-fixtures/cloud-function-source/requirements.txt -> build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:43,199 root INFO creating build/lib/ansible_collections/grafana 2023-04-28 05:57:43,199 root INFO creating build/lib/ansible_collections/grafana/grafana 2023-04-28 05:57:43,199 root INFO copying ansible_collections/grafana/grafana/CHANGELOG.rst -> build/lib/ansible_collections/grafana/grafana 2023-04-28 05:57:43,199 root INFO copying ansible_collections/grafana/grafana/FILES.json -> build/lib/ansible_collections/grafana/grafana 2023-04-28 05:57:43,200 root INFO copying ansible_collections/grafana/grafana/LICENSE -> build/lib/ansible_collections/grafana/grafana 2023-04-28 05:57:43,200 root INFO copying ansible_collections/grafana/grafana/MANIFEST.json -> build/lib/ansible_collections/grafana/grafana 2023-04-28 05:57:43,200 root INFO copying ansible_collections/grafana/grafana/README.md -> build/lib/ansible_collections/grafana/grafana 2023-04-28 05:57:43,200 root INFO creating build/lib/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:43,200 root INFO copying ansible_collections/grafana/grafana/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:43,201 root INFO copying ansible_collections/grafana/grafana/changelogs/changelog.yaml -> build/lib/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:43,201 root INFO copying ansible_collections/grafana/grafana/changelogs/config.yaml -> build/lib/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:43,201 root INFO creating build/lib/ansible_collections/grafana/grafana/meta 2023-04-28 05:57:43,201 root INFO copying ansible_collections/grafana/grafana/meta/runtime.yml -> build/lib/ansible_collections/grafana/grafana/meta 2023-04-28 05:57:43,201 root INFO creating build/lib/ansible_collections/grafana/grafana/plugins 2023-04-28 05:57:43,202 root INFO creating build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,202 root INFO copying ansible_collections/grafana/grafana/plugins/modules/alert_contact_point.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,202 root INFO copying ansible_collections/grafana/grafana/plugins/modules/alert_notification_policy.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,202 root INFO copying ansible_collections/grafana/grafana/plugins/modules/cloud_api_key.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,202 root INFO copying ansible_collections/grafana/grafana/plugins/modules/cloud_plugin.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,203 root INFO copying ansible_collections/grafana/grafana/plugins/modules/cloud_stack.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,203 root INFO copying ansible_collections/grafana/grafana/plugins/modules/dashboard.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,203 root INFO copying ansible_collections/grafana/grafana/plugins/modules/datasource.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,203 root INFO copying ansible_collections/grafana/grafana/plugins/modules/folder.py -> build/lib/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:43,204 root INFO creating build/lib/ansible_collections/grafana/grafana/roles 2023-04-28 05:57:43,204 root INFO creating build/lib/ansible_collections/grafana/grafana/roles/grafana_agent 2023-04-28 05:57:43,204 root INFO copying ansible_collections/grafana/grafana/roles/grafana_agent/README.md -> build/lib/ansible_collections/grafana/grafana/roles/grafana_agent 2023-04-28 05:57:43,204 root INFO creating build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/defaults 2023-04-28 05:57:43,204 root INFO copying ansible_collections/grafana/grafana/roles/grafana_agent/defaults/main.yml -> build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/defaults 2023-04-28 05:57:43,204 root INFO creating build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/meta 2023-04-28 05:57:43,204 root INFO copying ansible_collections/grafana/grafana/roles/grafana_agent/meta/main.yml -> build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/meta 2023-04-28 05:57:43,205 root INFO creating build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/tasks 2023-04-28 05:57:43,205 root INFO copying ansible_collections/grafana/grafana/roles/grafana_agent/tasks/main.yml -> build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/tasks 2023-04-28 05:57:43,205 root INFO creating build/lib/ansible_collections/hetzner 2023-04-28 05:57:43,205 root INFO creating build/lib/ansible_collections/hetzner/hcloud 2023-04-28 05:57:43,205 root INFO copying ansible_collections/hetzner/hcloud/CHANGELOG.rst -> build/lib/ansible_collections/hetzner/hcloud 2023-04-28 05:57:43,206 root INFO copying ansible_collections/hetzner/hcloud/COPYING -> build/lib/ansible_collections/hetzner/hcloud 2023-04-28 05:57:43,206 root INFO copying ansible_collections/hetzner/hcloud/FILES.json -> build/lib/ansible_collections/hetzner/hcloud 2023-04-28 05:57:43,206 root INFO copying ansible_collections/hetzner/hcloud/MANIFEST.json -> build/lib/ansible_collections/hetzner/hcloud 2023-04-28 05:57:43,206 root INFO copying ansible_collections/hetzner/hcloud/README.md -> build/lib/ansible_collections/hetzner/hcloud 2023-04-28 05:57:43,207 root INFO creating build/lib/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:43,207 root INFO copying ansible_collections/hetzner/hcloud/changelogs/.gitignore -> build/lib/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:43,207 root INFO copying ansible_collections/hetzner/hcloud/changelogs/changelog.yaml -> build/lib/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:43,207 root INFO copying ansible_collections/hetzner/hcloud/changelogs/config.yaml -> build/lib/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:43,207 root INFO creating build/lib/ansible_collections/hetzner/hcloud/changelogs/fragments 2023-04-28 05:57:43,207 root INFO copying ansible_collections/hetzner/hcloud/changelogs/fragments/.keep -> build/lib/ansible_collections/hetzner/hcloud/changelogs/fragments 2023-04-28 05:57:43,208 root INFO creating build/lib/ansible_collections/hetzner/hcloud/meta 2023-04-28 05:57:43,208 root INFO copying ansible_collections/hetzner/hcloud/meta/runtime.yml -> build/lib/ansible_collections/hetzner/hcloud/meta 2023-04-28 05:57:43,208 root INFO creating build/lib/ansible_collections/hetzner/hcloud/plugins 2023-04-28 05:57:43,208 root INFO creating build/lib/ansible_collections/hetzner/hcloud/plugins/doc_fragments 2023-04-28 05:57:43,208 root INFO copying ansible_collections/hetzner/hcloud/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/doc_fragments 2023-04-28 05:57:43,208 root INFO copying ansible_collections/hetzner/hcloud/plugins/doc_fragments/hcloud.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/doc_fragments 2023-04-28 05:57:43,209 root INFO creating build/lib/ansible_collections/hetzner/hcloud/plugins/inventory 2023-04-28 05:57:43,209 root INFO copying ansible_collections/hetzner/hcloud/plugins/inventory/__init__.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/inventory 2023-04-28 05:57:43,209 root INFO copying ansible_collections/hetzner/hcloud/plugins/inventory/hcloud.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/inventory 2023-04-28 05:57:43,209 root INFO creating build/lib/ansible_collections/hetzner/hcloud/plugins/module_utils 2023-04-28 05:57:43,209 root INFO copying ansible_collections/hetzner/hcloud/plugins/module_utils/__init__.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/module_utils 2023-04-28 05:57:43,210 root INFO copying ansible_collections/hetzner/hcloud/plugins/module_utils/hcloud.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/module_utils 2023-04-28 05:57:43,210 root INFO creating build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,210 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/__init__.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,210 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_certificate.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,210 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_certificate_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,211 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_datacenter_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,211 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_datacenter_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,211 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_firewall.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,211 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,212 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,212 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,212 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_image_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,212 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_image_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,212 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,213 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,213 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_network.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,213 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_service.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,213 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_target.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,214 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_type_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,214 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_location_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,214 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_location_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,214 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_network.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,215 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_network_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,215 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_placement_group.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,215 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_primary_ip.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,215 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_rdns.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,215 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_route.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,216 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,216 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,216 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,216 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_network.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,217 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_type_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,217 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_type_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,217 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,217 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,218 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,218 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_subnetwork.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,218 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,218 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume_facts.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,218 root INFO copying ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume_info.py -> build/lib/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:43,219 root INFO creating build/lib/ansible_collections/hpe 2023-04-28 05:57:43,219 root INFO creating build/lib/ansible_collections/hpe/nimble 2023-04-28 05:57:43,219 root INFO copying ansible_collections/hpe/nimble/CHANGELOG.rst -> build/lib/ansible_collections/hpe/nimble 2023-04-28 05:57:43,219 root INFO copying ansible_collections/hpe/nimble/FILES.json -> build/lib/ansible_collections/hpe/nimble 2023-04-28 05:57:43,219 root INFO copying ansible_collections/hpe/nimble/MANIFEST.json -> build/lib/ansible_collections/hpe/nimble 2023-04-28 05:57:43,220 root INFO copying ansible_collections/hpe/nimble/README.md -> build/lib/ansible_collections/hpe/nimble 2023-04-28 05:57:43,220 root INFO copying ansible_collections/hpe/nimble/bindep.txt -> build/lib/ansible_collections/hpe/nimble 2023-04-28 05:57:43,220 root INFO copying ansible_collections/hpe/nimble/requirements.txt -> build/lib/ansible_collections/hpe/nimble 2023-04-28 05:57:43,220 root INFO creating build/lib/ansible_collections/hpe/nimble/changelogs 2023-04-28 05:57:43,220 root INFO copying ansible_collections/hpe/nimble/changelogs/changelog.yaml -> build/lib/ansible_collections/hpe/nimble/changelogs 2023-04-28 05:57:43,221 root INFO copying ansible_collections/hpe/nimble/changelogs/config.yaml -> build/lib/ansible_collections/hpe/nimble/changelogs 2023-04-28 05:57:43,221 root INFO creating build/lib/ansible_collections/hpe/nimble/meta 2023-04-28 05:57:43,221 root INFO copying ansible_collections/hpe/nimble/meta/runtime.yml -> build/lib/ansible_collections/hpe/nimble/meta 2023-04-28 05:57:43,221 root INFO creating build/lib/ansible_collections/hpe/nimble/plugins 2023-04-28 05:57:43,221 root INFO creating build/lib/ansible_collections/hpe/nimble/plugins/doc_fragments 2023-04-28 05:57:43,221 root INFO copying ansible_collections/hpe/nimble/plugins/doc_fragments/hpe_nimble.py -> build/lib/ansible_collections/hpe/nimble/plugins/doc_fragments 2023-04-28 05:57:43,222 root INFO creating build/lib/ansible_collections/hpe/nimble/plugins/module_utils 2023-04-28 05:57:43,222 root INFO copying ansible_collections/hpe/nimble/plugins/module_utils/hpe_nimble.py -> build/lib/ansible_collections/hpe/nimble/plugins/module_utils 2023-04-28 05:57:43,222 root INFO creating build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,222 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_access_control_record.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,222 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_array.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,223 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_chap_user.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,223 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_disk.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,223 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_encryption.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,223 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_fc.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,223 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_group.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,224 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_info.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,224 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_initiator_group.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,224 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_network.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,225 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_partner.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,225 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_performance_policy.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,225 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_pool.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,225 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_protection_schedule.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,226 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_protection_template.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,226 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_shelf.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,226 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_snapshot.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,226 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_snapshot_collection.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,226 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_user.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,227 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_user_policy.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,227 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_volume.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,227 root INFO copying ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_volume_collection.py -> build/lib/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:43,227 root INFO creating build/lib/ansible_collections/ibm 2023-04-28 05:57:43,228 root INFO creating build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,228 root INFO copying ansible_collections/ibm/qradar/CHANGELOG.rst -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,228 root INFO copying ansible_collections/ibm/qradar/FILES.json -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,228 root INFO copying ansible_collections/ibm/qradar/LICENSE -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,228 root INFO copying ansible_collections/ibm/qradar/MANIFEST.json -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,229 root INFO copying ansible_collections/ibm/qradar/README.md -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,229 root INFO copying ansible_collections/ibm/qradar/bindep.txt -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,229 root INFO copying ansible_collections/ibm/qradar/pyproject.toml -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,229 root INFO copying ansible_collections/ibm/qradar/requirements.txt -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,229 root INFO copying ansible_collections/ibm/qradar/test-requirements.txt -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,230 root INFO copying ansible_collections/ibm/qradar/tox.ini -> build/lib/ansible_collections/ibm/qradar 2023-04-28 05:57:43,230 root INFO creating build/lib/ansible_collections/ibm/qradar/changelogs 2023-04-28 05:57:43,230 root INFO copying ansible_collections/ibm/qradar/changelogs/changelog.yaml -> build/lib/ansible_collections/ibm/qradar/changelogs 2023-04-28 05:57:43,230 root INFO copying ansible_collections/ibm/qradar/changelogs/config.yaml -> build/lib/ansible_collections/ibm/qradar/changelogs 2023-04-28 05:57:43,230 root INFO creating build/lib/ansible_collections/ibm/qradar/meta 2023-04-28 05:57:43,231 root INFO copying ansible_collections/ibm/qradar/meta/runtime.yml -> build/lib/ansible_collections/ibm/qradar/meta 2023-04-28 05:57:43,231 root INFO creating build/lib/ansible_collections/ibm/qradar/plugins 2023-04-28 05:57:43,231 root INFO creating build/lib/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:43,231 root INFO copying ansible_collections/ibm/qradar/plugins/action/__init__.py -> build/lib/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:43,231 root INFO copying ansible_collections/ibm/qradar/plugins/action/qradar_analytics_rules.py -> build/lib/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:43,232 root INFO copying ansible_collections/ibm/qradar/plugins/action/qradar_log_sources_management.py -> build/lib/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:43,232 root INFO creating build/lib/ansible_collections/ibm/qradar/plugins/httpapi 2023-04-28 05:57:43,232 root INFO copying ansible_collections/ibm/qradar/plugins/httpapi/qradar.py -> build/lib/ansible_collections/ibm/qradar/plugins/httpapi 2023-04-28 05:57:43,232 root INFO creating build/lib/ansible_collections/ibm/qradar/plugins/module_utils 2023-04-28 05:57:43,232 root INFO copying ansible_collections/ibm/qradar/plugins/module_utils/qradar.py -> build/lib/ansible_collections/ibm/qradar/plugins/module_utils 2023-04-28 05:57:43,232 root INFO creating build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,233 root INFO copying ansible_collections/ibm/qradar/plugins/modules/deploy.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,233 root INFO copying ansible_collections/ibm/qradar/plugins/modules/log_source_management.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,233 root INFO copying ansible_collections/ibm/qradar/plugins/modules/offense_action.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,233 root INFO copying ansible_collections/ibm/qradar/plugins/modules/offense_info.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,234 root INFO copying ansible_collections/ibm/qradar/plugins/modules/offense_note.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,234 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_analytics_rules.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,234 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_deploy.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,234 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_log_source_management.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,234 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_log_sources_management.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,235 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_offense_action.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,235 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_offense_info.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,235 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_offense_note.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,235 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_rule.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,236 root INFO copying ansible_collections/ibm/qradar/plugins/modules/qradar_rule_info.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,236 root INFO copying ansible_collections/ibm/qradar/plugins/modules/rule.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,236 root INFO copying ansible_collections/ibm/qradar/plugins/modules/rule_info.py -> build/lib/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:43,236 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:43,236 root INFO copying ansible_collections/ibm/spectrum_virtualize/FILES.json -> build/lib/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:43,237 root INFO copying ansible_collections/ibm/spectrum_virtualize/LICENSE -> build/lib/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:43,237 root INFO copying ansible_collections/ibm/spectrum_virtualize/MANIFEST.json -> build/lib/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:43,237 root INFO copying ansible_collections/ibm/spectrum_virtualize/README.md -> build/lib/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:43,237 root INFO copying ansible_collections/ibm/spectrum_virtualize/requirements.txt -> build/lib/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:43,238 root INFO copying ansible_collections/ibm/spectrum_virtualize/requirements.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:43,238 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize/changelogs 2023-04-28 05:57:43,238 root INFO copying ansible_collections/ibm/spectrum_virtualize/changelogs/changelog.yaml -> build/lib/ansible_collections/ibm/spectrum_virtualize/changelogs 2023-04-28 05:57:43,238 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize/meta 2023-04-28 05:57:43,238 root INFO copying ansible_collections/ibm/spectrum_virtualize/meta/execution-environment.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/meta 2023-04-28 05:57:43,239 root INFO copying ansible_collections/ibm/spectrum_virtualize/meta/runtime.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/meta 2023-04-28 05:57:43,239 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,239 root INFO copying ansible_collections/ibm/spectrum_virtualize/playbooks/create_GMCV_in_CG.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,239 root INFO copying ansible_collections/ibm/spectrum_virtualize/playbooks/generic_ansible_sample.yaml -> build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,239 root INFO copying ansible_collections/ibm/spectrum_virtualize/playbooks/generic_info.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,240 root INFO copying ansible_collections/ibm/spectrum_virtualize/playbooks/initial_setup_system_complete.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,240 root INFO copying ansible_collections/ibm/spectrum_virtualize/playbooks/map_volume_to_host.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,240 root INFO copying ansible_collections/ibm/spectrum_virtualize/playbooks/volume_migrate.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,240 root INFO copying ansible_collections/ibm/spectrum_virtualize/playbooks/volumegrp_create.yml -> build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:43,240 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize/plugins 2023-04-28 05:57:43,241 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/README.md -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins 2023-04-28 05:57:43,241 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils 2023-04-28 05:57:43,241 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/ibm_svc_ssh.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils 2023-04-28 05:57:43,241 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/ibm_svc_utils.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils 2023-04-28 05:57:43,241 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,241 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/__init__.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,242 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_awss3_cloudaccount.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,242 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_cloud_backups.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,242 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_ip_partnership.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,242 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_provisioning_policy.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,243 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_replication_policy.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,243 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_snapshot.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,243 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_snapshotpolicy.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,243 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_ssl_certificate.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,244 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_truststore_for_replication.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,244 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_restore_cloud_backup.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,244 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_switch_replication_direction.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,244 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_auth.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,244 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_complete_initial_setup.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,245 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_host.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,245 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_hostcluster.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,245 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_info.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,245 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_initial_setup.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,246 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_callhome.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,246 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_consistgrp_flashcopy.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,246 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_cv.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,246 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_flashcopy.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,247 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_ip.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,247 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_migration.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,247 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_mirrored_volume.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,247 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_ownershipgroup.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,248 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_portset.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,248 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_replication.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,248 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_replicationgroup.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,248 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_safeguarded_policy.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,249 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_sra.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,249 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_user.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,249 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_usergroup.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,249 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_volume.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,250 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_volumegroup.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,250 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_mdisk.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,250 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_mdiskgrp.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,250 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_start_stop_flashcopy.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,251 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_start_stop_replication.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,251 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_vdisk.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,251 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_vol_map.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,251 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svcinfo_command.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,251 root INFO copying ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svctask_command.py -> build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:43,252 root INFO creating build/lib/ansible_collections/ibm/spectrum_virtualize/roles 2023-04-28 05:57:43,252 root INFO copying ansible_collections/ibm/spectrum_virtualize/roles/place_holder -> build/lib/ansible_collections/ibm/spectrum_virtualize/roles 2023-04-28 05:57:43,252 root INFO creating build/lib/ansible_collections/infinidat 2023-04-28 05:57:43,252 root INFO creating build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,252 root INFO copying ansible_collections/infinidat/infinibox/CHANGELOG.rst -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,252 root INFO copying ansible_collections/infinidat/infinibox/FILES.json -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,253 root INFO copying ansible_collections/infinidat/infinibox/LICENSE -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,253 root INFO copying ansible_collections/infinidat/infinibox/MANIFEST.json -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,253 root INFO copying ansible_collections/infinidat/infinibox/Makefile -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,253 root INFO copying ansible_collections/infinidat/infinibox/Makefile-help -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,254 root INFO copying ansible_collections/infinidat/infinibox/README.md -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,254 root INFO copying ansible_collections/infinidat/infinibox/requirements-dev.txt -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,254 root INFO copying ansible_collections/infinidat/infinibox/requirements.txt -> build/lib/ansible_collections/infinidat/infinibox 2023-04-28 05:57:43,255 root INFO creating build/lib/ansible_collections/infinidat/infinibox/ibox_vars 2023-04-28 05:57:43,255 root INFO copying ansible_collections/infinidat/infinibox/ibox_vars/iboxCICD.yaml -> build/lib/ansible_collections/infinidat/infinibox/ibox_vars 2023-04-28 05:57:43,255 root INFO copying ansible_collections/infinidat/infinibox/ibox_vars/iboxNNNN_example.yaml -> build/lib/ansible_collections/infinidat/infinibox/ibox_vars 2023-04-28 05:57:43,255 root INFO creating build/lib/ansible_collections/infinidat/infinibox/meta 2023-04-28 05:57:43,255 root INFO copying ansible_collections/infinidat/infinibox/meta/execution-environment.yml -> build/lib/ansible_collections/infinidat/infinibox/meta 2023-04-28 05:57:43,256 root INFO copying ansible_collections/infinidat/infinibox/meta/runtime.yml -> build/lib/ansible_collections/infinidat/infinibox/meta 2023-04-28 05:57:43,256 root INFO creating build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,256 root INFO copying ansible_collections/infinidat/infinibox/playbooks/ansible.cfg -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,256 root INFO copying ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_runtest.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,256 root INFO copying ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_setup.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,257 root INFO copying ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_teardown.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,257 root INFO copying ansible_collections/infinidat/infinibox/playbooks/inventory -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,257 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_create_map_cluster.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,257 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_create_network_spaces.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,258 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_create_resources.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,258 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_create_snapshots.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,258 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_remove_map_cluster.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,258 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_remove_network_spaces.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,258 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_remove_resources.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,259 root INFO copying ansible_collections/infinidat/infinibox/playbooks/test_remove_snapshots.yml -> build/lib/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:43,259 root INFO creating build/lib/ansible_collections/infinidat/infinibox/plugins 2023-04-28 05:57:43,259 root INFO creating build/lib/ansible_collections/infinidat/infinibox/plugins/doc_fragments 2023-04-28 05:57:43,259 root INFO copying ansible_collections/infinidat/infinibox/plugins/doc_fragments/infinibox.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/doc_fragments 2023-04-28 05:57:43,259 root INFO creating build/lib/ansible_collections/infinidat/infinibox/plugins/filter 2023-04-28 05:57:43,259 root INFO copying ansible_collections/infinidat/infinibox/plugins/filter/delta_time.yml -> build/lib/ansible_collections/infinidat/infinibox/plugins/filter 2023-04-28 05:57:43,260 root INFO copying ansible_collections/infinidat/infinibox/plugins/filter/psus_filters.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/filter 2023-04-28 05:57:43,260 root INFO creating build/lib/ansible_collections/infinidat/infinibox/plugins/module_utils 2023-04-28 05:57:43,260 root INFO copying ansible_collections/infinidat/infinibox/plugins/module_utils/infinibox.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/module_utils 2023-04-28 05:57:43,260 root INFO creating build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,260 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/__init__.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,261 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_cluster.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,261 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_export.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,261 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_export_client.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,261 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_fs.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,262 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_host.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,262 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_map.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,262 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_network_space.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,262 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_pool.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,262 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_port.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,263 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_user.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,263 root INFO copying ansible_collections/infinidat/infinibox/plugins/modules/infini_vol.py -> build/lib/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:43,263 root INFO creating build/lib/ansible_collections/infoblox 2023-04-28 05:57:43,263 root INFO creating build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,263 root INFO copying ansible_collections/infoblox/nios_modules/CHANGELOG.rst -> build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,264 root INFO copying ansible_collections/infoblox/nios_modules/CONTRIBUTING.md -> build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,264 root INFO copying ansible_collections/infoblox/nios_modules/COPYING -> build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,264 root INFO copying ansible_collections/infoblox/nios_modules/FILES.json -> build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,264 root INFO copying ansible_collections/infoblox/nios_modules/MANIFEST.json -> build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,265 root INFO copying ansible_collections/infoblox/nios_modules/README.md -> build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,265 root INFO copying ansible_collections/infoblox/nios_modules/requirements.txt -> build/lib/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:43,265 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:43,265 root INFO copying ansible_collections/infoblox/nios_modules/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:43,265 root INFO copying ansible_collections/infoblox/nios_modules/changelogs/changelog.yaml -> build/lib/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:43,266 root INFO copying ansible_collections/infoblox/nios_modules/changelogs/config.yaml -> build/lib/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:43,266 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/meta 2023-04-28 05:57:43,266 root INFO copying ansible_collections/infoblox/nios_modules/meta/runtime.yml -> build/lib/ansible_collections/infoblox/nios_modules/meta 2023-04-28 05:57:43,266 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,266 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_a_record.yaml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,267 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_cname_record.yaml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,267 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_dns_view.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,267 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_dtc_lbdn.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,267 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_dtc_pool.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,267 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_dtc_server.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,268 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_mx_record.yaml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,268 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_network.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,268 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_network_view.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,268 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_txt_record.yaml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,269 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/create_zone.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,269 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/delete_cname_record.yaml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,269 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/delete_dnsview.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,269 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/delete_mx_record.yaml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,269 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/delete_network.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,270 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/delete_network_view.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,270 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/delete_txt_record.yaml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,270 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/delete_zone.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,270 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/restart_services.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,270 root INFO copying ansible_collections/infoblox/nios_modules/playbooks/update_a_record.yml -> build/lib/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:43,271 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/plugins 2023-04-28 05:57:43,271 root INFO copying ansible_collections/infoblox/nios_modules/plugins/README.md -> build/lib/ansible_collections/infoblox/nios_modules/plugins 2023-04-28 05:57:43,271 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/plugins/doc_fragments 2023-04-28 05:57:43,271 root INFO copying ansible_collections/infoblox/nios_modules/plugins/doc_fragments/nios.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/doc_fragments 2023-04-28 05:57:43,271 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/plugins/inventory 2023-04-28 05:57:43,272 root INFO copying ansible_collections/infoblox/nios_modules/plugins/inventory/nios_inventory.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/inventory 2023-04-28 05:57:43,272 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:43,272 root INFO copying ansible_collections/infoblox/nios_modules/plugins/lookup/nios_lookup.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:43,272 root INFO copying ansible_collections/infoblox/nios_modules/plugins/lookup/nios_next_ip.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:43,272 root INFO copying ansible_collections/infoblox/nios_modules/plugins/lookup/nios_next_network.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:43,273 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/plugins/module_utils 2023-04-28 05:57:43,273 root INFO copying ansible_collections/infoblox/nios_modules/plugins/module_utils/api.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/module_utils 2023-04-28 05:57:43,273 root INFO copying ansible_collections/infoblox/nios_modules/plugins/module_utils/network.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/module_utils 2023-04-28 05:57:43,273 root INFO creating build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,273 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_a_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,274 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_aaaa_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,274 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_cname_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,274 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_dns_view.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,274 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_lbdn.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,274 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_pool.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,275 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_server.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,275 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_fixed_address.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,275 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_host_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,275 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_member.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,276 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_mx_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,276 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_naptr_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,276 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_network.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,276 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_network_view.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,276 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_nsgroup.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,277 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_ptr_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,277 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_restartservices.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,277 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_srv_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,277 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_txt_record.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,278 root INFO copying ansible_collections/infoblox/nios_modules/plugins/modules/nios_zone.py -> build/lib/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:43,278 root INFO creating build/lib/ansible_collections/inspur 2023-04-28 05:57:43,278 root INFO creating build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,278 root INFO copying ansible_collections/inspur/ispim/CHANGELOG.rst -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,278 root INFO copying ansible_collections/inspur/ispim/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,279 root INFO copying ansible_collections/inspur/ispim/FILES.json -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,279 root INFO copying ansible_collections/inspur/ispim/LICENSE -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,279 root INFO copying ansible_collections/inspur/ispim/MANIFEST.json -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,279 root INFO copying ansible_collections/inspur/ispim/README.md -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,279 root INFO copying ansible_collections/inspur/ispim/__init__.py -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,280 root INFO copying ansible_collections/inspur/ispim/requirements.txt -> build/lib/ansible_collections/inspur/ispim 2023-04-28 05:57:43,280 root INFO creating build/lib/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:43,280 root INFO copying ansible_collections/inspur/ispim/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:43,280 root INFO copying ansible_collections/inspur/ispim/changelogs/changelog.yaml -> build/lib/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:43,281 root INFO copying ansible_collections/inspur/ispim/changelogs/config.yaml -> build/lib/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:43,281 root INFO creating build/lib/ansible_collections/inspur/ispim/changelogs/fragments 2023-04-28 05:57:43,281 root INFO copying ansible_collections/inspur/ispim/changelogs/fragments/.keep -> build/lib/ansible_collections/inspur/ispim/changelogs/fragments 2023-04-28 05:57:43,281 root INFO creating build/lib/ansible_collections/inspur/ispim/meta 2023-04-28 05:57:43,281 root INFO copying ansible_collections/inspur/ispim/meta/runtime.yml -> build/lib/ansible_collections/inspur/ispim/meta 2023-04-28 05:57:43,281 root INFO creating build/lib/ansible_collections/inspur/ispim/plugins 2023-04-28 05:57:43,282 root INFO creating build/lib/ansible_collections/inspur/ispim/plugins/doc_fragments 2023-04-28 05:57:43,282 root INFO copying ansible_collections/inspur/ispim/plugins/doc_fragments/ism.py -> build/lib/ansible_collections/inspur/ispim/plugins/doc_fragments 2023-04-28 05:57:43,282 root INFO creating build/lib/ansible_collections/inspur/ispim/plugins/module_utils 2023-04-28 05:57:43,282 root INFO copying ansible_collections/inspur/ispim/plugins/module_utils/__init__.py -> build/lib/ansible_collections/inspur/ispim/plugins/module_utils 2023-04-28 05:57:43,282 root INFO copying ansible_collections/inspur/ispim/plugins/module_utils/ism.py -> build/lib/ansible_collections/inspur/ispim/plugins/module_utils 2023-04-28 05:57:43,282 root INFO creating build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,283 root INFO copying ansible_collections/inspur/ispim/plugins/modules/__init__.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,283 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ad_group.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,283 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ad_group_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,283 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ad_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,283 root INFO copying ansible_collections/inspur/ispim/plugins/modules/adapter_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,284 root INFO copying ansible_collections/inspur/ispim/plugins/modules/add_ldisk.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,284 root INFO copying ansible_collections/inspur/ispim/plugins/modules/alert_policy_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,284 root INFO copying ansible_collections/inspur/ispim/plugins/modules/audit_log_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,284 root INFO copying ansible_collections/inspur/ispim/plugins/modules/auto_capture_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,285 root INFO copying ansible_collections/inspur/ispim/plugins/modules/backplane_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,285 root INFO copying ansible_collections/inspur/ispim/plugins/modules/backup.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,285 root INFO copying ansible_collections/inspur/ispim/plugins/modules/bios_export.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,285 root INFO copying ansible_collections/inspur/ispim/plugins/modules/bios_import.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,285 root INFO copying ansible_collections/inspur/ispim/plugins/modules/bios_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,286 root INFO copying ansible_collections/inspur/ispim/plugins/modules/bmc_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,286 root INFO copying ansible_collections/inspur/ispim/plugins/modules/boot_image_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,286 root INFO copying ansible_collections/inspur/ispim/plugins/modules/boot_option_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,286 root INFO copying ansible_collections/inspur/ispim/plugins/modules/clear_audit_log.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,287 root INFO copying ansible_collections/inspur/ispim/plugins/modules/clear_event_log.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,287 root INFO copying ansible_collections/inspur/ispim/plugins/modules/clear_system_log.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,287 root INFO copying ansible_collections/inspur/ispim/plugins/modules/collect_blackbox.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,287 root INFO copying ansible_collections/inspur/ispim/plugins/modules/collect_log.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,287 root INFO copying ansible_collections/inspur/ispim/plugins/modules/connect_media_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,288 root INFO copying ansible_collections/inspur/ispim/plugins/modules/cpu_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,288 root INFO copying ansible_collections/inspur/ispim/plugins/modules/del_session.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,288 root INFO copying ansible_collections/inspur/ispim/plugins/modules/dns_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,288 root INFO copying ansible_collections/inspur/ispim/plugins/modules/download_auto_screenshot.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,288 root INFO copying ansible_collections/inspur/ispim/plugins/modules/download_manual_screenshot.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,289 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_ad.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,289 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_alert_policy.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,289 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_auto_capture.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,289 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_bios.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,290 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_boot_image.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,290 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_boot_option.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,290 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_connect_media.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,290 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_dns.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,291 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_event_log_policy.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,291 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_fan.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,291 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_fru.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,291 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_ipv4.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,291 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_ipv6.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,292 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_kvm.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,292 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_ldap.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,292 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_ldisk.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,292 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_log_setting.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,292 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_m6_log_setting.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,293 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_manual_capture.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,293 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_media_instance.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,293 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_ncsi.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,293 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_network.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,294 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_network_bond.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,294 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_network_link.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,294 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_ntp.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,294 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_pdisk.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,294 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_power_budget.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,295 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_power_restore.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,295 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_power_status.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,295 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_preserve_config.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,295 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_psu_config.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,296 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_psu_peak.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,296 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_restore_factory_default.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,296 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_service.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,296 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_smtp.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,297 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_smtp_com.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,297 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_smtp_dest.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,297 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_snmp.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,297 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_snmp_trap.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,297 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_threshold.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,298 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_uid.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,298 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_virtual_media.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,298 root INFO copying ansible_collections/inspur/ispim/plugins/modules/edit_vlan.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,298 root INFO copying ansible_collections/inspur/ispim/plugins/modules/event_log_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,298 root INFO copying ansible_collections/inspur/ispim/plugins/modules/event_log_policy_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,299 root INFO copying ansible_collections/inspur/ispim/plugins/modules/fan_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,299 root INFO copying ansible_collections/inspur/ispim/plugins/modules/fru_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,299 root INFO copying ansible_collections/inspur/ispim/plugins/modules/fw_version_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,299 root INFO copying ansible_collections/inspur/ispim/plugins/modules/gpu_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,300 root INFO copying ansible_collections/inspur/ispim/plugins/modules/hard_disk_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,300 root INFO copying ansible_collections/inspur/ispim/plugins/modules/kvm_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,300 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ldap_group.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,300 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ldap_group_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,300 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ldap_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,301 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ldisk_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,301 root INFO copying ansible_collections/inspur/ispim/plugins/modules/log_setting_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,301 root INFO copying ansible_collections/inspur/ispim/plugins/modules/media_instance_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,301 root INFO copying ansible_collections/inspur/ispim/plugins/modules/mem_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,302 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ncsi_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,302 root INFO copying ansible_collections/inspur/ispim/plugins/modules/network_bond_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,302 root INFO copying ansible_collections/inspur/ispim/plugins/modules/network_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,302 root INFO copying ansible_collections/inspur/ispim/plugins/modules/network_link_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,302 root INFO copying ansible_collections/inspur/ispim/plugins/modules/ntp_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,303 root INFO copying ansible_collections/inspur/ispim/plugins/modules/onboard_disk_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,303 root INFO copying ansible_collections/inspur/ispim/plugins/modules/pcie_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,303 root INFO copying ansible_collections/inspur/ispim/plugins/modules/pdisk_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,303 root INFO copying ansible_collections/inspur/ispim/plugins/modules/power_budget_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,304 root INFO copying ansible_collections/inspur/ispim/plugins/modules/power_consumption_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,304 root INFO copying ansible_collections/inspur/ispim/plugins/modules/power_restore_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,304 root INFO copying ansible_collections/inspur/ispim/plugins/modules/power_status_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,304 root INFO copying ansible_collections/inspur/ispim/plugins/modules/preserve_config_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,304 root INFO copying ansible_collections/inspur/ispim/plugins/modules/psu_config_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,305 root INFO copying ansible_collections/inspur/ispim/plugins/modules/psu_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,305 root INFO copying ansible_collections/inspur/ispim/plugins/modules/psu_peak_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,305 root INFO copying ansible_collections/inspur/ispim/plugins/modules/raid_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,305 root INFO copying ansible_collections/inspur/ispim/plugins/modules/reset_bmc.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,306 root INFO copying ansible_collections/inspur/ispim/plugins/modules/reset_kvm.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,306 root INFO copying ansible_collections/inspur/ispim/plugins/modules/restore.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,306 root INFO copying ansible_collections/inspur/ispim/plugins/modules/self_test_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,306 root INFO copying ansible_collections/inspur/ispim/plugins/modules/sensor_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,306 root INFO copying ansible_collections/inspur/ispim/plugins/modules/server_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,307 root INFO copying ansible_collections/inspur/ispim/plugins/modules/service_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,307 root INFO copying ansible_collections/inspur/ispim/plugins/modules/session_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,307 root INFO copying ansible_collections/inspur/ispim/plugins/modules/smtp_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,307 root INFO copying ansible_collections/inspur/ispim/plugins/modules/snmp_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,308 root INFO copying ansible_collections/inspur/ispim/plugins/modules/snmp_trap_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,308 root INFO copying ansible_collections/inspur/ispim/plugins/modules/support_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,308 root INFO copying ansible_collections/inspur/ispim/plugins/modules/system_log_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,308 root INFO copying ansible_collections/inspur/ispim/plugins/modules/temp_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,308 root INFO copying ansible_collections/inspur/ispim/plugins/modules/threshold_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,309 root INFO copying ansible_collections/inspur/ispim/plugins/modules/uid_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,309 root INFO copying ansible_collections/inspur/ispim/plugins/modules/update_cpld.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,309 root INFO copying ansible_collections/inspur/ispim/plugins/modules/update_fw.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,309 root INFO copying ansible_collections/inspur/ispim/plugins/modules/user.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,310 root INFO copying ansible_collections/inspur/ispim/plugins/modules/user_group.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,310 root INFO copying ansible_collections/inspur/ispim/plugins/modules/user_group_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,310 root INFO copying ansible_collections/inspur/ispim/plugins/modules/user_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,310 root INFO copying ansible_collections/inspur/ispim/plugins/modules/virtual_media_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,311 root INFO copying ansible_collections/inspur/ispim/plugins/modules/volt_info.py -> build/lib/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:43,311 root INFO creating build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,311 root INFO copying ansible_collections/inspur/sm/CHANGELOG.rst -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,311 root INFO copying ansible_collections/inspur/sm/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,311 root INFO copying ansible_collections/inspur/sm/FILES.json -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,312 root INFO copying ansible_collections/inspur/sm/LICENSE -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,312 root INFO copying ansible_collections/inspur/sm/MANIFEST.json -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,312 root INFO copying ansible_collections/inspur/sm/README.md -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,312 root INFO copying ansible_collections/inspur/sm/__init__.py -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,313 root INFO copying ansible_collections/inspur/sm/bindep.txt -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,313 root INFO copying ansible_collections/inspur/sm/requirements.txt -> build/lib/ansible_collections/inspur/sm 2023-04-28 05:57:43,313 root INFO creating build/lib/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:43,313 root INFO copying ansible_collections/inspur/sm/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:43,313 root INFO copying ansible_collections/inspur/sm/changelogs/changelog.yaml -> build/lib/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:43,314 root INFO copying ansible_collections/inspur/sm/changelogs/config.yaml -> build/lib/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:43,314 root INFO creating build/lib/ansible_collections/inspur/sm/meta 2023-04-28 05:57:43,314 root INFO copying ansible_collections/inspur/sm/meta/runtime.yml -> build/lib/ansible_collections/inspur/sm/meta 2023-04-28 05:57:43,314 root INFO creating build/lib/ansible_collections/inspur/sm/playbooks 2023-04-28 05:57:43,314 root INFO creating build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,314 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ad_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,315 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ad_group_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,315 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ad_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,315 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-adapter_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,315 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-add_ad_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,316 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-add_ldap_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,316 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-add_ldisk.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,316 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-add_user.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,316 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-add_user_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,316 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-alert_policy_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,317 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-audit_log_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,317 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-auto_capture_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,317 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-backplane_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,317 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-backup.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,317 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-bios_export.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,318 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-bios_import.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,318 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-bios_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,318 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-bmc_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,318 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-boot_image_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,319 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-boot_option_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,319 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-clear_audit_log.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,319 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-clear_event_log.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,319 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-clear_system_log.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,319 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-collect_blackbox.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,320 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-collect_log.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,320 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-connect_media_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,320 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-cpu_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,320 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-del_ad_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,320 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-del_ldap_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,321 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-del_session.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,321 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-del_user.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,321 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-del_user_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,321 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-dns_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,322 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-download_auto_screenshot.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,322 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-download_manual_screenshot.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,322 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ad.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,322 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ad_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,322 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_alert_policy.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,323 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_auto_capture.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,323 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_bios.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,323 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_boot_image.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,323 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_boot_option.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,324 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_connect_media.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,324 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_dns.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,324 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_event_log_policy.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,324 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_fan.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,324 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_fru.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,325 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ipv4.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,325 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ipv6.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,325 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_kvm.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,325 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldap.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,326 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldap_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,326 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldisk.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,326 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_log_setting.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,326 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_manual_capture.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,326 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_media_instance.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,327 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ncsi.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,327 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_network.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,327 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_network_bond.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,327 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_network_link.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,328 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_ntp.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,328 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_pass_user.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,328 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_pdisk.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,328 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_budget.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,328 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_restore.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,329 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_status.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,329 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_preserve_config.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,329 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_priv_user.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,329 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_psu_config.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,330 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_psu_peak.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,330 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_restore_factory_default.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,330 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_service.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,330 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,330 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp_com.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,331 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp_dest.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,331 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_snmp.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,331 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_snmp_trap.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,331 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_threshold.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,332 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_uid.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,332 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_user_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,332 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_virtual_media.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,332 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-edit_vlan.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,332 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-event_log_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,333 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-event_log_policy_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,333 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-fan_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,333 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-fru_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,333 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-fw_verison_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,334 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-gpu_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,334 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-hard_disk_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,334 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-kvm_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,334 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ldap_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,334 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ldap_group_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,335 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ldap_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,335 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ldisk_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,335 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-log_setting_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,335 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-media_instance_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,335 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-mem_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,336 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ncsi_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,336 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-network_bond_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,336 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-network_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,336 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-network_link_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,337 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-ntp_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,337 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-onboard_disk_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,337 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-pcie_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,337 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-pdisk_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,337 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-power_budget_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,338 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-power_consumption_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,338 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-power_restore_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,338 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-power_status_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,338 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-preserver_config_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,339 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-psu_config_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,339 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-psu_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,339 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-psu_peak_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,339 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-raid_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,340 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-reset_bmc.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,340 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-reset_kvm.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,340 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-restore.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,340 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-self_test_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,340 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-sensor_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,341 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-server_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,341 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-service_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,341 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-session_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,341 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-smtp_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,342 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-snmp_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,342 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-snmp_trap_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,342 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-system_log_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,342 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-temp_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,342 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-threshold_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,343 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-uid_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,343 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-update_cpld.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,343 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-update_fw.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,343 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-user.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,344 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-user_group.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,344 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-user_group_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,344 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-user_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,344 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-virtual_media_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,344 root INFO copying ansible_collections/inspur/sm/playbooks/modules/examples-volt_info.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:43,345 root INFO creating build/lib/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:43,345 root INFO copying ansible_collections/inspur/sm/playbooks/modules/overall/examples-ad_overall.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:43,345 root INFO copying ansible_collections/inspur/sm/playbooks/modules/overall/examples-ldap_overall.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:43,345 root INFO copying ansible_collections/inspur/sm/playbooks/modules/overall/examples-system_info_overall.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:43,345 root INFO copying ansible_collections/inspur/sm/playbooks/modules/overall/examples-user_overall.yml -> build/lib/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:43,346 root INFO creating build/lib/ansible_collections/inspur/sm/plugins 2023-04-28 05:57:43,346 root INFO creating build/lib/ansible_collections/inspur/sm/plugins/doc_fragments 2023-04-28 05:57:43,346 root INFO copying ansible_collections/inspur/sm/plugins/doc_fragments/ism.py -> build/lib/ansible_collections/inspur/sm/plugins/doc_fragments 2023-04-28 05:57:43,346 root INFO creating build/lib/ansible_collections/inspur/sm/plugins/module_utils 2023-04-28 05:57:43,346 root INFO copying ansible_collections/inspur/sm/plugins/module_utils/__init__.py -> build/lib/ansible_collections/inspur/sm/plugins/module_utils 2023-04-28 05:57:43,347 root INFO copying ansible_collections/inspur/sm/plugins/module_utils/ism.py -> build/lib/ansible_collections/inspur/sm/plugins/module_utils 2023-04-28 05:57:43,347 root INFO creating build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,347 root INFO copying ansible_collections/inspur/sm/plugins/modules/__init__.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,347 root INFO copying ansible_collections/inspur/sm/plugins/modules/ad_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,347 root INFO copying ansible_collections/inspur/sm/plugins/modules/ad_group_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,347 root INFO copying ansible_collections/inspur/sm/plugins/modules/ad_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,348 root INFO copying ansible_collections/inspur/sm/plugins/modules/adapter_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,348 root INFO copying ansible_collections/inspur/sm/plugins/modules/add_ad_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,348 root INFO copying ansible_collections/inspur/sm/plugins/modules/add_ldap_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,348 root INFO copying ansible_collections/inspur/sm/plugins/modules/add_ldisk.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,349 root INFO copying ansible_collections/inspur/sm/plugins/modules/add_user.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,349 root INFO copying ansible_collections/inspur/sm/plugins/modules/add_user_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,349 root INFO copying ansible_collections/inspur/sm/plugins/modules/alert_policy_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,349 root INFO copying ansible_collections/inspur/sm/plugins/modules/audit_log_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,349 root INFO copying ansible_collections/inspur/sm/plugins/modules/auto_capture_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,350 root INFO copying ansible_collections/inspur/sm/plugins/modules/backplane_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,350 root INFO copying ansible_collections/inspur/sm/plugins/modules/backup.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,350 root INFO copying ansible_collections/inspur/sm/plugins/modules/bios_export.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,350 root INFO copying ansible_collections/inspur/sm/plugins/modules/bios_import.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,351 root INFO copying ansible_collections/inspur/sm/plugins/modules/bios_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,351 root INFO copying ansible_collections/inspur/sm/plugins/modules/bmc_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,351 root INFO copying ansible_collections/inspur/sm/plugins/modules/boot_image_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,351 root INFO copying ansible_collections/inspur/sm/plugins/modules/boot_option_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,351 root INFO copying ansible_collections/inspur/sm/plugins/modules/clear_audit_log.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,352 root INFO copying ansible_collections/inspur/sm/plugins/modules/clear_event_log.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,352 root INFO copying ansible_collections/inspur/sm/plugins/modules/clear_system_log.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,352 root INFO copying ansible_collections/inspur/sm/plugins/modules/collect_blackbox.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,352 root INFO copying ansible_collections/inspur/sm/plugins/modules/collect_log.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,352 root INFO copying ansible_collections/inspur/sm/plugins/modules/connect_media_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,353 root INFO copying ansible_collections/inspur/sm/plugins/modules/cpu_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,353 root INFO copying ansible_collections/inspur/sm/plugins/modules/del_ad_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,353 root INFO copying ansible_collections/inspur/sm/plugins/modules/del_ldap_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,353 root INFO copying ansible_collections/inspur/sm/plugins/modules/del_session.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,354 root INFO copying ansible_collections/inspur/sm/plugins/modules/del_user.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,354 root INFO copying ansible_collections/inspur/sm/plugins/modules/del_user_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,354 root INFO copying ansible_collections/inspur/sm/plugins/modules/dns_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,354 root INFO copying ansible_collections/inspur/sm/plugins/modules/download_auto_screenshot.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,354 root INFO copying ansible_collections/inspur/sm/plugins/modules/download_manual_screenshot.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,355 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ad.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,355 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ad_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,355 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_alert_policy.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,355 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_auto_capture.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,356 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_bios.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,356 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_boot_image.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,356 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_boot_option.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,356 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_connect_media.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,356 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_dns.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,357 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_event_log_policy.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,357 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_fan.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,357 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_fru.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,357 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ipv4.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,358 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ipv6.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,358 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_kvm.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,358 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ldap.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,358 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ldap_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,358 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ldisk.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,359 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_log_setting.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,359 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_manual_capture.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,359 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_media_instance.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,359 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ncsi.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,360 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_network.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,360 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_network_bond.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,360 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_network_link.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,360 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_ntp.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,360 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_pass_user.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,361 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_pdisk.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,361 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_power_budget.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,361 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_power_restore.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,361 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_power_status.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,362 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_preserve_config.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,362 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_priv_user.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,362 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_psu_config.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,362 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_psu_peak.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,362 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_restore_factory_default.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,363 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_service.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,363 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_smtp.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,363 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_smtp_com.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,363 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_smtp_dest.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,364 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_snmp.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,364 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_snmp_trap.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,364 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_threshold.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,364 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_uid.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,365 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_user_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,365 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_virtual_media.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,365 root INFO copying ansible_collections/inspur/sm/plugins/modules/edit_vlan.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,365 root INFO copying ansible_collections/inspur/sm/plugins/modules/event_log_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,365 root INFO copying ansible_collections/inspur/sm/plugins/modules/event_log_policy_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,366 root INFO copying ansible_collections/inspur/sm/plugins/modules/fan_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,366 root INFO copying ansible_collections/inspur/sm/plugins/modules/fru_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,366 root INFO copying ansible_collections/inspur/sm/plugins/modules/fw_version_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,366 root INFO copying ansible_collections/inspur/sm/plugins/modules/gpu_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,367 root INFO copying ansible_collections/inspur/sm/plugins/modules/hard_disk_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,367 root INFO copying ansible_collections/inspur/sm/plugins/modules/kvm_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,367 root INFO copying ansible_collections/inspur/sm/plugins/modules/ldap_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,367 root INFO copying ansible_collections/inspur/sm/plugins/modules/ldap_group_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,367 root INFO copying ansible_collections/inspur/sm/plugins/modules/ldap_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,368 root INFO copying ansible_collections/inspur/sm/plugins/modules/ldisk_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,368 root INFO copying ansible_collections/inspur/sm/plugins/modules/log_setting_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,368 root INFO copying ansible_collections/inspur/sm/plugins/modules/media_instance_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,368 root INFO copying ansible_collections/inspur/sm/plugins/modules/mem_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,369 root INFO copying ansible_collections/inspur/sm/plugins/modules/ncsi_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,369 root INFO copying ansible_collections/inspur/sm/plugins/modules/network_bond_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,369 root INFO copying ansible_collections/inspur/sm/plugins/modules/network_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,369 root INFO copying ansible_collections/inspur/sm/plugins/modules/network_link_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,369 root INFO copying ansible_collections/inspur/sm/plugins/modules/ntp_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,370 root INFO copying ansible_collections/inspur/sm/plugins/modules/onboard_disk_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,370 root INFO copying ansible_collections/inspur/sm/plugins/modules/pcie_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,370 root INFO copying ansible_collections/inspur/sm/plugins/modules/pdisk_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,370 root INFO copying ansible_collections/inspur/sm/plugins/modules/power_budget_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,371 root INFO copying ansible_collections/inspur/sm/plugins/modules/power_consumption_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,371 root INFO copying ansible_collections/inspur/sm/plugins/modules/power_restore_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,371 root INFO copying ansible_collections/inspur/sm/plugins/modules/power_status_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,371 root INFO copying ansible_collections/inspur/sm/plugins/modules/preserve_config_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,371 root INFO copying ansible_collections/inspur/sm/plugins/modules/psu_config_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,372 root INFO copying ansible_collections/inspur/sm/plugins/modules/psu_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,372 root INFO copying ansible_collections/inspur/sm/plugins/modules/psu_peak_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,372 root INFO copying ansible_collections/inspur/sm/plugins/modules/raid_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,372 root INFO copying ansible_collections/inspur/sm/plugins/modules/reset_bmc.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,373 root INFO copying ansible_collections/inspur/sm/plugins/modules/reset_kvm.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,373 root INFO copying ansible_collections/inspur/sm/plugins/modules/restore.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,373 root INFO copying ansible_collections/inspur/sm/plugins/modules/self_test_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,373 root INFO copying ansible_collections/inspur/sm/plugins/modules/sensor_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,373 root INFO copying ansible_collections/inspur/sm/plugins/modules/server_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,374 root INFO copying ansible_collections/inspur/sm/plugins/modules/service_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,374 root INFO copying ansible_collections/inspur/sm/plugins/modules/session_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,374 root INFO copying ansible_collections/inspur/sm/plugins/modules/smtp_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,374 root INFO copying ansible_collections/inspur/sm/plugins/modules/snmp_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,375 root INFO copying ansible_collections/inspur/sm/plugins/modules/snmp_trap_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,375 root INFO copying ansible_collections/inspur/sm/plugins/modules/system_log_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,375 root INFO copying ansible_collections/inspur/sm/plugins/modules/temp_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,375 root INFO copying ansible_collections/inspur/sm/plugins/modules/threshold_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,375 root INFO copying ansible_collections/inspur/sm/plugins/modules/uid_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,376 root INFO copying ansible_collections/inspur/sm/plugins/modules/update_cpld.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,376 root INFO copying ansible_collections/inspur/sm/plugins/modules/update_fw.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,376 root INFO copying ansible_collections/inspur/sm/plugins/modules/user.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,376 root INFO copying ansible_collections/inspur/sm/plugins/modules/user_group.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,377 root INFO copying ansible_collections/inspur/sm/plugins/modules/user_group_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,377 root INFO copying ansible_collections/inspur/sm/plugins/modules/user_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,377 root INFO copying ansible_collections/inspur/sm/plugins/modules/virtual_media_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,377 root INFO copying ansible_collections/inspur/sm/plugins/modules/volt_info.py -> build/lib/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:43,377 root INFO creating build/lib/ansible_collections/junipernetworks 2023-04-28 05:57:43,378 root INFO creating build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,378 root INFO copying ansible_collections/junipernetworks/junos/CHANGELOG.rst -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,378 root INFO copying ansible_collections/junipernetworks/junos/FILES.json -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,379 root INFO copying ansible_collections/junipernetworks/junos/LICENSE -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,379 root INFO copying ansible_collections/junipernetworks/junos/MANIFEST.json -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,379 root INFO copying ansible_collections/junipernetworks/junos/README.md -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,380 root INFO copying ansible_collections/junipernetworks/junos/bindep.txt -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,380 root INFO copying ansible_collections/junipernetworks/junos/pyproject.toml -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,380 root INFO copying ansible_collections/junipernetworks/junos/requirements.txt -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,380 root INFO copying ansible_collections/junipernetworks/junos/test-requirements.txt -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,381 root INFO copying ansible_collections/junipernetworks/junos/tox.ini -> build/lib/ansible_collections/junipernetworks/junos 2023-04-28 05:57:43,381 root INFO creating build/lib/ansible_collections/junipernetworks/junos/changelogs 2023-04-28 05:57:43,381 root INFO copying ansible_collections/junipernetworks/junos/changelogs/changelog.yaml -> build/lib/ansible_collections/junipernetworks/junos/changelogs 2023-04-28 05:57:43,381 root INFO copying ansible_collections/junipernetworks/junos/changelogs/config.yaml -> build/lib/ansible_collections/junipernetworks/junos/changelogs 2023-04-28 05:57:43,381 root INFO creating build/lib/ansible_collections/junipernetworks/junos/changelogs/fragments 2023-04-28 05:57:43,381 root INFO copying ansible_collections/junipernetworks/junos/changelogs/fragments/.keep -> build/lib/ansible_collections/junipernetworks/junos/changelogs/fragments 2023-04-28 05:57:43,382 root INFO creating build/lib/ansible_collections/junipernetworks/junos/meta 2023-04-28 05:57:43,382 root INFO copying ansible_collections/junipernetworks/junos/meta/runtime.yml -> build/lib/ansible_collections/junipernetworks/junos/meta 2023-04-28 05:57:43,382 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins 2023-04-28 05:57:43,382 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/action 2023-04-28 05:57:43,382 root INFO copying ansible_collections/junipernetworks/junos/plugins/action/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/action 2023-04-28 05:57:43,383 root INFO copying ansible_collections/junipernetworks/junos/plugins/action/junos.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/action 2023-04-28 05:57:43,383 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/cliconf 2023-04-28 05:57:43,383 root INFO copying ansible_collections/junipernetworks/junos/plugins/cliconf/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/cliconf 2023-04-28 05:57:43,383 root INFO copying ansible_collections/junipernetworks/junos/plugins/cliconf/junos.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/cliconf 2023-04-28 05:57:43,383 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/doc_fragments 2023-04-28 05:57:43,383 root INFO copying ansible_collections/junipernetworks/junos/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/doc_fragments 2023-04-28 05:57:43,384 root INFO copying ansible_collections/junipernetworks/junos/plugins/doc_fragments/junos.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/doc_fragments 2023-04-28 05:57:43,384 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils 2023-04-28 05:57:43,384 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils 2023-04-28 05:57:43,384 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network 2023-04-28 05:57:43,384 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network 2023-04-28 05:57:43,385 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos 2023-04-28 05:57:43,385 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos 2023-04-28 05:57:43,385 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/junos.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos 2023-04-28 05:57:43,385 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec 2023-04-28 05:57:43,385 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec 2023-04-28 05:57:43,385 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces 2023-04-28 05:57:43,386 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces 2023-04-28 05:57:43,386 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces 2023-04-28 05:57:43,386 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls 2023-04-28 05:57:43,386 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls 2023-04-28 05:57:43,386 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/acls.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls 2023-04-28 05:57:43,387 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family 2023-04-28 05:57:43,387 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family 2023-04-28 05:57:43,387 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family 2023-04-28 05:57:43,387 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global 2023-04-28 05:57:43,387 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global 2023-04-28 05:57:43,388 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/bgp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global 2023-04-28 05:57:43,388 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts 2023-04-28 05:57:43,388 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts 2023-04-28 05:57:43,388 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/facts.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts 2023-04-28 05:57:43,389 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname 2023-04-28 05:57:43,389 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname 2023-04-28 05:57:43,389 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/hostname.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname 2023-04-28 05:57:43,389 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces 2023-04-28 05:57:43,389 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces 2023-04-28 05:57:43,389 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces 2023-04-28 05:57:43,390 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces 2023-04-28 05:57:43,390 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces 2023-04-28 05:57:43,390 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces 2023-04-28 05:57:43,390 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces 2023-04-28 05:57:43,390 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces 2023-04-28 05:57:43,391 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces 2023-04-28 05:57:43,391 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp 2023-04-28 05:57:43,391 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp 2023-04-28 05:57:43,391 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/lacp.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp 2023-04-28 05:57:43,391 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces 2023-04-28 05:57:43,392 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces 2023-04-28 05:57:43,392 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces 2023-04-28 05:57:43,392 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces 2023-04-28 05:57:43,392 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces 2023-04-28 05:57:43,392 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces 2023-04-28 05:57:43,393 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global 2023-04-28 05:57:43,393 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global 2023-04-28 05:57:43,393 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/lldp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global 2023-04-28 05:57:43,393 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces 2023-04-28 05:57:43,393 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces 2023-04-28 05:57:43,393 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces 2023-04-28 05:57:43,394 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global 2023-04-28 05:57:43,394 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global 2023-04-28 05:57:43,394 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/logging_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global 2023-04-28 05:57:43,394 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global 2023-04-28 05:57:43,394 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global 2023-04-28 05:57:43,395 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/ntp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global 2023-04-28 05:57:43,395 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces 2023-04-28 05:57:43,395 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces 2023-04-28 05:57:43,395 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces 2023-04-28 05:57:43,396 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2 2023-04-28 05:57:43,396 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2 2023-04-28 05:57:43,396 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/ospfv2.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2 2023-04-28 05:57:43,396 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3 2023-04-28 05:57:43,396 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3 2023-04-28 05:57:43,396 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/ospfv3.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3 2023-04-28 05:57:43,397 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists 2023-04-28 05:57:43,397 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists 2023-04-28 05:57:43,397 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists 2023-04-28 05:57:43,397 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances 2023-04-28 05:57:43,397 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances 2023-04-28 05:57:43,398 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/routing_instances.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances 2023-04-28 05:57:43,398 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options 2023-04-28 05:57:43,398 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options 2023-04-28 05:57:43,398 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/routing_options.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options 2023-04-28 05:57:43,398 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies 2023-04-28 05:57:43,398 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies 2023-04-28 05:57:43,399 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/security_policies.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies 2023-04-28 05:57:43,399 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global 2023-04-28 05:57:43,399 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global 2023-04-28 05:57:43,399 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/security_policies_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global 2023-04-28 05:57:43,400 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones 2023-04-28 05:57:43,400 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones 2023-04-28 05:57:43,400 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/security_zones.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones 2023-04-28 05:57:43,400 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server 2023-04-28 05:57:43,400 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server 2023-04-28 05:57:43,401 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/snmp_server.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server 2023-04-28 05:57:43,401 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes 2023-04-28 05:57:43,401 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes 2023-04-28 05:57:43,401 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/static_routes.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes 2023-04-28 05:57:43,401 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans 2023-04-28 05:57:43,401 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans 2023-04-28 05:57:43,402 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/vlans.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans 2023-04-28 05:57:43,402 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config 2023-04-28 05:57:43,402 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config 2023-04-28 05:57:43,402 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces 2023-04-28 05:57:43,402 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces 2023-04-28 05:57:43,403 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces 2023-04-28 05:57:43,403 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls 2023-04-28 05:57:43,403 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls 2023-04-28 05:57:43,403 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/acls.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls 2023-04-28 05:57:43,403 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family 2023-04-28 05:57:43,404 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family 2023-04-28 05:57:43,404 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family 2023-04-28 05:57:43,404 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global 2023-04-28 05:57:43,404 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global 2023-04-28 05:57:43,404 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/bgp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global 2023-04-28 05:57:43,405 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname 2023-04-28 05:57:43,405 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname 2023-04-28 05:57:43,405 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/hostname.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname 2023-04-28 05:57:43,405 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces 2023-04-28 05:57:43,405 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces 2023-04-28 05:57:43,406 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces 2023-04-28 05:57:43,406 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces 2023-04-28 05:57:43,406 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces 2023-04-28 05:57:43,406 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces 2023-04-28 05:57:43,406 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces 2023-04-28 05:57:43,407 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces 2023-04-28 05:57:43,407 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces 2023-04-28 05:57:43,407 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp 2023-04-28 05:57:43,407 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp 2023-04-28 05:57:43,407 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/lacp.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp 2023-04-28 05:57:43,408 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces 2023-04-28 05:57:43,408 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces 2023-04-28 05:57:43,408 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces 2023-04-28 05:57:43,408 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces 2023-04-28 05:57:43,408 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces 2023-04-28 05:57:43,408 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces 2023-04-28 05:57:43,409 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global 2023-04-28 05:57:43,409 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global 2023-04-28 05:57:43,409 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/lldp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global 2023-04-28 05:57:43,409 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces 2023-04-28 05:57:43,409 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces 2023-04-28 05:57:43,410 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces 2023-04-28 05:57:43,410 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global 2023-04-28 05:57:43,410 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global 2023-04-28 05:57:43,410 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/logging_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global 2023-04-28 05:57:43,410 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global 2023-04-28 05:57:43,411 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global 2023-04-28 05:57:43,411 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/ntp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global 2023-04-28 05:57:43,411 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces 2023-04-28 05:57:43,411 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces 2023-04-28 05:57:43,411 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces 2023-04-28 05:57:43,412 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2 2023-04-28 05:57:43,412 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2 2023-04-28 05:57:43,412 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/ospfv2.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2 2023-04-28 05:57:43,412 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3 2023-04-28 05:57:43,412 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3 2023-04-28 05:57:43,413 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/ospfv3.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3 2023-04-28 05:57:43,413 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists 2023-04-28 05:57:43,413 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists 2023-04-28 05:57:43,413 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists 2023-04-28 05:57:43,413 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances 2023-04-28 05:57:43,414 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances 2023-04-28 05:57:43,414 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/routing_instances.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances 2023-04-28 05:57:43,414 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options 2023-04-28 05:57:43,414 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options 2023-04-28 05:57:43,414 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/routing_options.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options 2023-04-28 05:57:43,415 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies 2023-04-28 05:57:43,415 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies 2023-04-28 05:57:43,415 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/security_policies.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies 2023-04-28 05:57:43,415 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global 2023-04-28 05:57:43,415 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global 2023-04-28 05:57:43,416 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/security_policies_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global 2023-04-28 05:57:43,416 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones 2023-04-28 05:57:43,416 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones 2023-04-28 05:57:43,416 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/security_zones.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones 2023-04-28 05:57:43,416 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server 2023-04-28 05:57:43,417 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server 2023-04-28 05:57:43,417 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/snmp_server.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server 2023-04-28 05:57:43,417 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes 2023-04-28 05:57:43,417 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes 2023-04-28 05:57:43,417 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/static_routes.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes 2023-04-28 05:57:43,418 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans 2023-04-28 05:57:43,418 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans 2023-04-28 05:57:43,418 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/vlans.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans 2023-04-28 05:57:43,418 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts 2023-04-28 05:57:43,418 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts 2023-04-28 05:57:43,419 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/facts.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts 2023-04-28 05:57:43,419 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces 2023-04-28 05:57:43,419 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces 2023-04-28 05:57:43,419 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/acl_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces 2023-04-28 05:57:43,419 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls 2023-04-28 05:57:43,419 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls 2023-04-28 05:57:43,420 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/acls.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls 2023-04-28 05:57:43,420 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family 2023-04-28 05:57:43,420 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family 2023-04-28 05:57:43,420 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family 2023-04-28 05:57:43,421 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global 2023-04-28 05:57:43,421 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global 2023-04-28 05:57:43,421 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/bgp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global 2023-04-28 05:57:43,421 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname 2023-04-28 05:57:43,421 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname 2023-04-28 05:57:43,422 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/hostname.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname 2023-04-28 05:57:43,422 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces 2023-04-28 05:57:43,422 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces 2023-04-28 05:57:43,422 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces 2023-04-28 05:57:43,422 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces 2023-04-28 05:57:43,422 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces 2023-04-28 05:57:43,423 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/l2_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces 2023-04-28 05:57:43,423 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces 2023-04-28 05:57:43,423 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces 2023-04-28 05:57:43,423 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces 2023-04-28 05:57:43,424 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp 2023-04-28 05:57:43,424 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp 2023-04-28 05:57:43,424 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/lacp.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp 2023-04-28 05:57:43,424 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces 2023-04-28 05:57:43,424 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces 2023-04-28 05:57:43,424 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/lacp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces 2023-04-28 05:57:43,425 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces 2023-04-28 05:57:43,425 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces 2023-04-28 05:57:43,425 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces 2023-04-28 05:57:43,425 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy 2023-04-28 05:57:43,425 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy 2023-04-28 05:57:43,426 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/base.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy 2023-04-28 05:57:43,426 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global 2023-04-28 05:57:43,426 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global 2023-04-28 05:57:43,426 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/lldp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global 2023-04-28 05:57:43,426 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces 2023-04-28 05:57:43,427 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces 2023-04-28 05:57:43,427 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces 2023-04-28 05:57:43,427 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global 2023-04-28 05:57:43,427 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global 2023-04-28 05:57:43,427 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/logging_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global 2023-04-28 05:57:43,428 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global 2023-04-28 05:57:43,428 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global 2023-04-28 05:57:43,428 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/ntp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global 2023-04-28 05:57:43,428 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces 2023-04-28 05:57:43,428 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces 2023-04-28 05:57:43,429 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces 2023-04-28 05:57:43,429 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2 2023-04-28 05:57:43,429 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2 2023-04-28 05:57:43,429 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/ospfv2.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2 2023-04-28 05:57:43,429 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3 2023-04-28 05:57:43,429 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3 2023-04-28 05:57:43,430 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/ospfv3.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3 2023-04-28 05:57:43,430 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists 2023-04-28 05:57:43,430 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists 2023-04-28 05:57:43,430 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists 2023-04-28 05:57:43,430 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances 2023-04-28 05:57:43,431 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances 2023-04-28 05:57:43,431 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/routing_instances.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances 2023-04-28 05:57:43,431 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options 2023-04-28 05:57:43,431 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options 2023-04-28 05:57:43,431 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/routing_options.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options 2023-04-28 05:57:43,432 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies 2023-04-28 05:57:43,432 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies 2023-04-28 05:57:43,432 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/security_policies.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies 2023-04-28 05:57:43,432 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global 2023-04-28 05:57:43,432 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global 2023-04-28 05:57:43,433 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/security_policies_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global 2023-04-28 05:57:43,433 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones 2023-04-28 05:57:43,433 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones 2023-04-28 05:57:43,433 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/security_zones.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones 2023-04-28 05:57:43,433 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server 2023-04-28 05:57:43,434 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server 2023-04-28 05:57:43,434 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/snmp_server.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server 2023-04-28 05:57:43,434 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes 2023-04-28 05:57:43,434 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes 2023-04-28 05:57:43,434 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/static_routes.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes 2023-04-28 05:57:43,435 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans 2023-04-28 05:57:43,435 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans 2023-04-28 05:57:43,435 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/vlans.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans 2023-04-28 05:57:43,435 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils 2023-04-28 05:57:43,435 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils 2023-04-28 05:57:43,435 root INFO copying ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/utils.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils 2023-04-28 05:57:43,436 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,436 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,436 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_acl_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,436 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_acls.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,437 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_banner.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,437 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_bgp_address_family.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,437 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_bgp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,437 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_command.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,438 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_config.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,438 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_facts.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,438 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_hostname.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,438 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,439 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_l2_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,439 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_l3_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,439 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_lacp.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,439 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_lacp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,440 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_lag_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,440 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_lldp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,440 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_lldp_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,440 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_logging.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,440 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_logging_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,441 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_netconf.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,441 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_ntp_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,441 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_ospf_interfaces.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,441 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_ospfv2.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,442 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_ospfv3.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,442 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_package.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,442 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_ping.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,442 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_prefix_lists.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,443 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_routing_instances.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,443 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_routing_options.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,443 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_rpc.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,443 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_scp.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,444 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_security_policies.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,444 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_security_policies_global.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,444 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_security_zones.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,445 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_snmp_server.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,445 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_static_routes.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,445 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_system.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,445 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_user.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,446 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_vlans.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,446 root INFO copying ansible_collections/junipernetworks/junos/plugins/modules/junos_vrf.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:43,446 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/netconf 2023-04-28 05:57:43,446 root INFO copying ansible_collections/junipernetworks/junos/plugins/netconf/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/netconf 2023-04-28 05:57:43,446 root INFO copying ansible_collections/junipernetworks/junos/plugins/netconf/junos.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/netconf 2023-04-28 05:57:43,447 root INFO creating build/lib/ansible_collections/junipernetworks/junos/plugins/terminal 2023-04-28 05:57:43,447 root INFO copying ansible_collections/junipernetworks/junos/plugins/terminal/__init__.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/terminal 2023-04-28 05:57:43,447 root INFO copying ansible_collections/junipernetworks/junos/plugins/terminal/junos.py -> build/lib/ansible_collections/junipernetworks/junos/plugins/terminal 2023-04-28 05:57:43,447 root INFO creating build/lib/ansible_collections/kubernetes 2023-04-28 05:57:43,447 root INFO creating build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,447 root INFO copying ansible_collections/kubernetes/core/CHANGELOG.rst -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,448 root INFO copying ansible_collections/kubernetes/core/CONTRIBUTING.md -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,448 root INFO copying ansible_collections/kubernetes/core/FILES.json -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,448 root INFO copying ansible_collections/kubernetes/core/LICENSE -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,449 root INFO copying ansible_collections/kubernetes/core/MANIFEST.json -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,449 root INFO copying ansible_collections/kubernetes/core/Makefile -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,449 root INFO copying ansible_collections/kubernetes/core/PSF-license.txt -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,449 root INFO copying ansible_collections/kubernetes/core/README.md -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,449 root INFO copying ansible_collections/kubernetes/core/bindep.txt -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,450 root INFO copying ansible_collections/kubernetes/core/codecov.yml -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,450 root INFO copying ansible_collections/kubernetes/core/requirements.txt -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,450 root INFO copying ansible_collections/kubernetes/core/setup.cfg -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,450 root INFO copying ansible_collections/kubernetes/core/test-requirements.txt -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,451 root INFO copying ansible_collections/kubernetes/core/tox.ini -> build/lib/ansible_collections/kubernetes/core 2023-04-28 05:57:43,451 root INFO creating build/lib/ansible_collections/kubernetes/core/changelogs 2023-04-28 05:57:43,451 root INFO copying ansible_collections/kubernetes/core/changelogs/changelog.yaml -> build/lib/ansible_collections/kubernetes/core/changelogs 2023-04-28 05:57:43,451 root INFO copying ansible_collections/kubernetes/core/changelogs/config.yaml -> build/lib/ansible_collections/kubernetes/core/changelogs 2023-04-28 05:57:43,451 root INFO creating build/lib/ansible_collections/kubernetes/core/meta 2023-04-28 05:57:43,452 root INFO copying ansible_collections/kubernetes/core/meta/runtime.yml -> build/lib/ansible_collections/kubernetes/core/meta 2023-04-28 05:57:43,452 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins 2023-04-28 05:57:43,452 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,452 root INFO copying ansible_collections/kubernetes/core/plugins/action/helm.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,452 root INFO copying ansible_collections/kubernetes/core/plugins/action/helm_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,452 root INFO copying ansible_collections/kubernetes/core/plugins/action/helm_plugin.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,453 root INFO copying ansible_collections/kubernetes/core/plugins/action/helm_plugin_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,453 root INFO copying ansible_collections/kubernetes/core/plugins/action/helm_repository.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,453 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,453 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_cluster_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,454 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_cp.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,454 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_drain.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,454 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_exec.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,454 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,455 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_log.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,455 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_rollback.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,455 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_scale.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,455 root INFO copying ansible_collections/kubernetes/core/plugins/action/k8s_service.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,456 root INFO copying ansible_collections/kubernetes/core/plugins/action/ks8_json_patch.py -> build/lib/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:43,456 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/connection 2023-04-28 05:57:43,456 root INFO copying ansible_collections/kubernetes/core/plugins/connection/kubectl.py -> build/lib/ansible_collections/kubernetes/core/plugins/connection 2023-04-28 05:57:43,456 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,456 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,456 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/helm_common_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,457 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_auth_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,457 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_delete_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,457 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_name_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,457 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_resource_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,458 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_scale_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,458 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_state_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,458 root INFO copying ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_wait_options.py -> build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:43,458 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/filter 2023-04-28 05:57:43,458 root INFO copying ansible_collections/kubernetes/core/plugins/filter/k8s.py -> build/lib/ansible_collections/kubernetes/core/plugins/filter 2023-04-28 05:57:43,459 root INFO copying ansible_collections/kubernetes/core/plugins/filter/k8s_config_resource_name.yml -> build/lib/ansible_collections/kubernetes/core/plugins/filter 2023-04-28 05:57:43,459 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/inventory 2023-04-28 05:57:43,459 root INFO copying ansible_collections/kubernetes/core/plugins/inventory/k8s.py -> build/lib/ansible_collections/kubernetes/core/plugins/inventory 2023-04-28 05:57:43,459 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/lookup 2023-04-28 05:57:43,459 root INFO copying ansible_collections/kubernetes/core/plugins/lookup/k8s.py -> build/lib/ansible_collections/kubernetes/core/plugins/lookup 2023-04-28 05:57:43,460 root INFO copying ansible_collections/kubernetes/core/plugins/lookup/kustomize.py -> build/lib/ansible_collections/kubernetes/core/plugins/lookup 2023-04-28 05:57:43,460 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,460 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/__init__.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,460 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/_version.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,460 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/ansiblemodule.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,461 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/apply.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,461 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/args_common.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,461 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/common.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,461 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/copy.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,462 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/exceptions.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,462 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/hashes.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,462 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/helm.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,462 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/helm_args_common.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,462 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8sdynamicclient.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,463 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/selector.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,463 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/version.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:43,463 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/module_utils/client 2023-04-28 05:57:43,463 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/client/discovery.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/client 2023-04-28 05:57:43,463 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/client/resource.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/client 2023-04-28 05:57:43,464 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,464 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8s/client.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,464 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8s/core.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,464 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8s/exceptions.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,464 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8s/resource.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,465 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8s/runner.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,465 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8s/service.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,465 root INFO copying ansible_collections/kubernetes/core/plugins/module_utils/k8s/waiter.py -> build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:43,465 root INFO creating build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,465 root INFO copying ansible_collections/kubernetes/core/plugins/modules/__init__.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,466 root INFO copying ansible_collections/kubernetes/core/plugins/modules/helm.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,466 root INFO copying ansible_collections/kubernetes/core/plugins/modules/helm_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,466 root INFO copying ansible_collections/kubernetes/core/plugins/modules/helm_plugin.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,466 root INFO copying ansible_collections/kubernetes/core/plugins/modules/helm_plugin_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,467 root INFO copying ansible_collections/kubernetes/core/plugins/modules/helm_pull.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,467 root INFO copying ansible_collections/kubernetes/core/plugins/modules/helm_repository.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,467 root INFO copying ansible_collections/kubernetes/core/plugins/modules/helm_template.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,467 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,468 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_cluster_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,468 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_cp.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,468 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_drain.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,468 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_exec.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,469 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_info.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,469 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_json_patch.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,469 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_log.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,469 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_rollback.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,469 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_scale.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,470 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_service.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,470 root INFO copying ansible_collections/kubernetes/core/plugins/modules/k8s_taint.py -> build/lib/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:43,470 root INFO creating build/lib/ansible_collections/lowlydba 2023-04-28 05:57:43,470 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,470 root INFO copying ansible_collections/lowlydba/sqlserver/CHANGELOG.rst -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,471 root INFO copying ansible_collections/lowlydba/sqlserver/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,471 root INFO copying ansible_collections/lowlydba/sqlserver/CONTRIBUTING.md -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,471 root INFO copying ansible_collections/lowlydba/sqlserver/FILES.json -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,471 root INFO copying ansible_collections/lowlydba/sqlserver/LICENSE -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,472 root INFO copying ansible_collections/lowlydba/sqlserver/MAINTAINERS -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,472 root INFO copying ansible_collections/lowlydba/sqlserver/MANIFEST.json -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,472 root INFO copying ansible_collections/lowlydba/sqlserver/README.md -> build/lib/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:43,472 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver/changelogs 2023-04-28 05:57:43,472 root INFO copying ansible_collections/lowlydba/sqlserver/changelogs/changelog.yaml -> build/lib/ansible_collections/lowlydba/sqlserver/changelogs 2023-04-28 05:57:43,473 root INFO copying ansible_collections/lowlydba/sqlserver/changelogs/config.yaml -> build/lib/ansible_collections/lowlydba/sqlserver/changelogs 2023-04-28 05:57:43,473 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver/changelogs/fragments 2023-04-28 05:57:43,473 root INFO copying ansible_collections/lowlydba/sqlserver/changelogs/fragments/.keep -> build/lib/ansible_collections/lowlydba/sqlserver/changelogs/fragments 2023-04-28 05:57:43,473 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver/meta 2023-04-28 05:57:43,473 root INFO copying ansible_collections/lowlydba/sqlserver/meta/runtime.yml -> build/lib/ansible_collections/lowlydba/sqlserver/meta 2023-04-28 05:57:43,474 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver/plugins 2023-04-28 05:57:43,474 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:43,474 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/attributes.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:43,474 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/sql_credentials.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:43,474 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/state.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:43,474 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver/plugins/module_utils 2023-04-28 05:57:43,475 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/module_utils/_SqlServerUtils.psm1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/module_utils 2023-04-28 05:57:43,475 root INFO creating build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,475 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/ag_listener.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,475 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/ag_listener.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,475 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/ag_replica.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,476 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/ag_replica.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,476 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,476 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,476 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_category.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,476 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_category.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,477 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_schedule.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,477 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_schedule.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,477 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_step.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,477 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_step.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,478 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/availability_group.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,478 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/availability_group.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,478 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/backup.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,478 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/backup.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,479 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/credential.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,479 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/credential.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,479 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/database.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,479 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/database.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,479 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/dba_multitool.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,480 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/dba_multitool.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,480 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/first_responder_kit.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,480 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/first_responder_kit.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,480 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/hadr.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,480 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/hadr.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,481 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/install_script.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,481 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/install_script.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,481 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/instance_info.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,481 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/instance_info.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,482 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/login.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,482 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/login.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,482 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/maintenance_solution.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,482 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/maintenance_solution.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,482 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/memory.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,483 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/memory.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,483 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/nonquery.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,483 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/nonquery.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,483 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/resource_governor.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,484 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/resource_governor.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,484 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/restore.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,484 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/restore.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,484 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/rg_resource_pool.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,484 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/rg_resource_pool.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,485 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/rg_workload_group.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,485 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/rg_workload_group.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,485 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/sa.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,485 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/sa.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,486 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/sp_configure.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,486 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/sp_configure.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,486 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/sp_whoisactive.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,486 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/sp_whoisactive.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,486 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/spn.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,487 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/spn.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,487 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/tcp_port.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,487 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/tcp_port.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,487 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/traceflag.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,488 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/traceflag.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,488 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/user.ps1 -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,488 root INFO copying ansible_collections/lowlydba/sqlserver/plugins/modules/user.py -> build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:43,488 root INFO creating build/lib/ansible_collections/mellanox 2023-04-28 05:57:43,488 root INFO creating build/lib/ansible_collections/mellanox/onyx 2023-04-28 05:57:43,488 root INFO copying ansible_collections/mellanox/onyx/FILES.json -> build/lib/ansible_collections/mellanox/onyx 2023-04-28 05:57:43,489 root INFO copying ansible_collections/mellanox/onyx/LICENSE -> build/lib/ansible_collections/mellanox/onyx 2023-04-28 05:57:43,489 root INFO copying ansible_collections/mellanox/onyx/MANIFEST.json -> build/lib/ansible_collections/mellanox/onyx 2023-04-28 05:57:43,489 root INFO copying ansible_collections/mellanox/onyx/README.md -> build/lib/ansible_collections/mellanox/onyx 2023-04-28 05:57:43,489 root INFO creating build/lib/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:43,490 root INFO copying ansible_collections/mellanox/onyx/changelogs/CHANGELOG.rst -> build/lib/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:43,490 root INFO copying ansible_collections/mellanox/onyx/changelogs/changelog.yaml -> build/lib/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:43,490 root INFO copying ansible_collections/mellanox/onyx/changelogs/config.yaml -> build/lib/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:43,490 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins 2023-04-28 05:57:43,490 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/action 2023-04-28 05:57:43,490 root INFO copying ansible_collections/mellanox/onyx/plugins/action/__init__.py -> build/lib/ansible_collections/mellanox/onyx/plugins/action 2023-04-28 05:57:43,491 root INFO copying ansible_collections/mellanox/onyx/plugins/action/onyx_config.py -> build/lib/ansible_collections/mellanox/onyx/plugins/action 2023-04-28 05:57:43,491 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/cliconf 2023-04-28 05:57:43,491 root INFO copying ansible_collections/mellanox/onyx/plugins/cliconf/__init__.py -> build/lib/ansible_collections/mellanox/onyx/plugins/cliconf 2023-04-28 05:57:43,491 root INFO copying ansible_collections/mellanox/onyx/plugins/cliconf/onyx.py -> build/lib/ansible_collections/mellanox/onyx/plugins/cliconf 2023-04-28 05:57:43,491 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/doc_fragments 2023-04-28 05:57:43,492 root INFO copying ansible_collections/mellanox/onyx/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/mellanox/onyx/plugins/doc_fragments 2023-04-28 05:57:43,492 root INFO copying ansible_collections/mellanox/onyx/plugins/doc_fragments/onyx.py -> build/lib/ansible_collections/mellanox/onyx/plugins/doc_fragments 2023-04-28 05:57:43,492 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/module_utils 2023-04-28 05:57:43,492 root INFO copying ansible_collections/mellanox/onyx/plugins/module_utils/__init__.py -> build/lib/ansible_collections/mellanox/onyx/plugins/module_utils 2023-04-28 05:57:43,492 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/module_utils/network 2023-04-28 05:57:43,492 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx 2023-04-28 05:57:43,493 root INFO copying ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/__init__.py -> build/lib/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx 2023-04-28 05:57:43,493 root INFO copying ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/onyx.py -> build/lib/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx 2023-04-28 05:57:43,493 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,493 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/__init__.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,493 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_aaa.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,494 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_bfd.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,494 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_bgp.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,494 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_buffer_pool.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,494 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_command.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,494 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_config.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,495 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_facts.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,495 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,495 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp_interface.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,495 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp_vlan.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,496 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_interface.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,496 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_l2_interface.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,496 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_l3_interface.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,496 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_linkagg.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,497 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_lldp.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,497 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_lldp_interface.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,497 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_magp.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,497 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_mlag_ipl.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,497 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_mlag_vip.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,498 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_ntp.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,498 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_ntp_servers_peers.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,498 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_ospf.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,498 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_pfc_interface.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,499 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_protocol.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,499 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_ptp_global.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,499 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_ptp_interface.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,499 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_qos.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,499 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,500 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp_hosts.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,500 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp_users.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,500 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_syslog_files.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,500 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_syslog_remote.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,501 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_traffic_class.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,501 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_username.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,501 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_vlan.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,501 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_vxlan.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,502 root INFO copying ansible_collections/mellanox/onyx/plugins/modules/onyx_wjh.py -> build/lib/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:43,502 root INFO creating build/lib/ansible_collections/mellanox/onyx/plugins/terminal 2023-04-28 05:57:43,502 root INFO copying ansible_collections/mellanox/onyx/plugins/terminal/__init__.py -> build/lib/ansible_collections/mellanox/onyx/plugins/terminal 2023-04-28 05:57:43,502 root INFO copying ansible_collections/mellanox/onyx/plugins/terminal/onyx.py -> build/lib/ansible_collections/mellanox/onyx/plugins/terminal 2023-04-28 05:57:43,502 root INFO creating build/lib/ansible_collections/microsoft 2023-04-28 05:57:43,502 root INFO creating build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,503 root INFO copying ansible_collections/microsoft/ad/CHANGELOG.rst -> build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,503 root INFO copying ansible_collections/microsoft/ad/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,503 root INFO copying ansible_collections/microsoft/ad/COPYING -> build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,503 root INFO copying ansible_collections/microsoft/ad/FILES.json -> build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,504 root INFO copying ansible_collections/microsoft/ad/MANIFEST.json -> build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,504 root INFO copying ansible_collections/microsoft/ad/README.md -> build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,504 root INFO copying ansible_collections/microsoft/ad/codecov.yml -> build/lib/ansible_collections/microsoft/ad 2023-04-28 05:57:43,505 root INFO creating build/lib/ansible_collections/microsoft/ad/changelogs 2023-04-28 05:57:43,505 root INFO copying ansible_collections/microsoft/ad/changelogs/changelog.yaml -> build/lib/ansible_collections/microsoft/ad/changelogs 2023-04-28 05:57:43,505 root INFO copying ansible_collections/microsoft/ad/changelogs/config.yaml -> build/lib/ansible_collections/microsoft/ad/changelogs 2023-04-28 05:57:43,505 root INFO creating build/lib/ansible_collections/microsoft/ad/changelogs/fragments 2023-04-28 05:57:43,505 root INFO copying ansible_collections/microsoft/ad/changelogs/fragments/.keep -> build/lib/ansible_collections/microsoft/ad/changelogs/fragments 2023-04-28 05:57:43,506 root INFO creating build/lib/ansible_collections/microsoft/ad/meta 2023-04-28 05:57:43,506 root INFO copying ansible_collections/microsoft/ad/meta/runtime.yml -> build/lib/ansible_collections/microsoft/ad/meta 2023-04-28 05:57:43,506 root INFO creating build/lib/ansible_collections/microsoft/ad/plugins 2023-04-28 05:57:43,506 root INFO creating build/lib/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:43,506 root INFO copying ansible_collections/microsoft/ad/plugins/action/__init__.py -> build/lib/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:43,506 root INFO copying ansible_collections/microsoft/ad/plugins/action/domain.py -> build/lib/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:43,507 root INFO copying ansible_collections/microsoft/ad/plugins/action/domain_controller.py -> build/lib/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:43,507 root INFO copying ansible_collections/microsoft/ad/plugins/action/membership.py -> build/lib/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:43,507 root INFO creating build/lib/ansible_collections/microsoft/ad/plugins/doc_fragments 2023-04-28 05:57:43,507 root INFO copying ansible_collections/microsoft/ad/plugins/doc_fragments/ad_object.py -> build/lib/ansible_collections/microsoft/ad/plugins/doc_fragments 2023-04-28 05:57:43,507 root INFO creating build/lib/ansible_collections/microsoft/ad/plugins/module_utils 2023-04-28 05:57:43,507 root INFO copying ansible_collections/microsoft/ad/plugins/module_utils/_ADObject.psm1 -> build/lib/ansible_collections/microsoft/ad/plugins/module_utils 2023-04-28 05:57:43,508 root INFO creating build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,508 root INFO copying ansible_collections/microsoft/ad/plugins/modules/computer.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,508 root INFO copying ansible_collections/microsoft/ad/plugins/modules/computer.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,508 root INFO copying ansible_collections/microsoft/ad/plugins/modules/domain.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,509 root INFO copying ansible_collections/microsoft/ad/plugins/modules/domain.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,509 root INFO copying ansible_collections/microsoft/ad/plugins/modules/domain_controller.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,509 root INFO copying ansible_collections/microsoft/ad/plugins/modules/domain_controller.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,509 root INFO copying ansible_collections/microsoft/ad/plugins/modules/group.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,509 root INFO copying ansible_collections/microsoft/ad/plugins/modules/group.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,510 root INFO copying ansible_collections/microsoft/ad/plugins/modules/membership.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,510 root INFO copying ansible_collections/microsoft/ad/plugins/modules/membership.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,510 root INFO copying ansible_collections/microsoft/ad/plugins/modules/object.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,510 root INFO copying ansible_collections/microsoft/ad/plugins/modules/object.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,511 root INFO copying ansible_collections/microsoft/ad/plugins/modules/object_info.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,511 root INFO copying ansible_collections/microsoft/ad/plugins/modules/object_info.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,511 root INFO copying ansible_collections/microsoft/ad/plugins/modules/offline_join.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,511 root INFO copying ansible_collections/microsoft/ad/plugins/modules/offline_join.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,511 root INFO copying ansible_collections/microsoft/ad/plugins/modules/ou.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,512 root INFO copying ansible_collections/microsoft/ad/plugins/modules/ou.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,512 root INFO copying ansible_collections/microsoft/ad/plugins/modules/user.ps1 -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,512 root INFO copying ansible_collections/microsoft/ad/plugins/modules/user.py -> build/lib/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:43,512 root INFO creating build/lib/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:43,512 root INFO copying ansible_collections/microsoft/ad/plugins/plugin_utils/__init__.py -> build/lib/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:43,513 root INFO copying ansible_collections/microsoft/ad/plugins/plugin_utils/_module_with_reboot.py -> build/lib/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:43,513 root INFO copying ansible_collections/microsoft/ad/plugins/plugin_utils/_reboot.py -> build/lib/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:43,513 root INFO creating build/lib/ansible_collections/netapp 2023-04-28 05:57:43,513 root INFO creating build/lib/ansible_collections/netapp/aws 2023-04-28 05:57:43,513 root INFO copying ansible_collections/netapp/aws/CHANGELOG.rst -> build/lib/ansible_collections/netapp/aws 2023-04-28 05:57:43,514 root INFO copying ansible_collections/netapp/aws/COPYING -> build/lib/ansible_collections/netapp/aws 2023-04-28 05:57:43,514 root INFO copying ansible_collections/netapp/aws/FILES.json -> build/lib/ansible_collections/netapp/aws 2023-04-28 05:57:43,514 root INFO copying ansible_collections/netapp/aws/MANIFEST.json -> build/lib/ansible_collections/netapp/aws 2023-04-28 05:57:43,514 root INFO copying ansible_collections/netapp/aws/README.md -> build/lib/ansible_collections/netapp/aws 2023-04-28 05:57:43,515 root INFO copying ansible_collections/netapp/aws/requirements.txt -> build/lib/ansible_collections/netapp/aws 2023-04-28 05:57:43,515 root INFO creating build/lib/ansible_collections/netapp/aws/changelogs 2023-04-28 05:57:43,515 root INFO copying ansible_collections/netapp/aws/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp/aws/changelogs 2023-04-28 05:57:43,515 root INFO copying ansible_collections/netapp/aws/changelogs/config.yaml -> build/lib/ansible_collections/netapp/aws/changelogs 2023-04-28 05:57:43,515 root INFO creating build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,516 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/20.2.0.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,516 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/20.6.0.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,516 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/20.8.0.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,516 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/20.9.0.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,516 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/2019.10.0.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,517 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-3569.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,517 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-3644.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,517 root INFO copying ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-4416.yaml -> build/lib/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:43,517 root INFO creating build/lib/ansible_collections/netapp/aws/meta 2023-04-28 05:57:43,517 root INFO copying ansible_collections/netapp/aws/meta/runtime.yml -> build/lib/ansible_collections/netapp/aws/meta 2023-04-28 05:57:43,518 root INFO creating build/lib/ansible_collections/netapp/aws/plugins 2023-04-28 05:57:43,518 root INFO creating build/lib/ansible_collections/netapp/aws/plugins/doc_fragments 2023-04-28 05:57:43,518 root INFO copying ansible_collections/netapp/aws/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp/aws/plugins/doc_fragments 2023-04-28 05:57:43,518 root INFO creating build/lib/ansible_collections/netapp/aws/plugins/module_utils 2023-04-28 05:57:43,518 root INFO copying ansible_collections/netapp/aws/plugins/module_utils/netapp.py -> build/lib/ansible_collections/netapp/aws/plugins/module_utils 2023-04-28 05:57:43,518 root INFO copying ansible_collections/netapp/aws/plugins/module_utils/netapp_module.py -> build/lib/ansible_collections/netapp/aws/plugins/module_utils 2023-04-28 05:57:43,519 root INFO creating build/lib/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:43,519 root INFO copying ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_active_directory.py -> build/lib/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:43,519 root INFO copying ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_filesystems.py -> build/lib/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:43,519 root INFO copying ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_pool.py -> build/lib/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:43,520 root INFO copying ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_snapshots.py -> build/lib/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:43,520 root INFO creating build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,520 root INFO copying ansible_collections/netapp/azure/CHANGELOG.rst -> build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,520 root INFO copying ansible_collections/netapp/azure/COPYING -> build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,520 root INFO copying ansible_collections/netapp/azure/FILES.json -> build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,521 root INFO copying ansible_collections/netapp/azure/HACK.md -> build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,521 root INFO copying ansible_collections/netapp/azure/MANIFEST.json -> build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,521 root INFO copying ansible_collections/netapp/azure/README.md -> build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,521 root INFO copying ansible_collections/netapp/azure/requirements.txt -> build/lib/ansible_collections/netapp/azure 2023-04-28 05:57:43,521 root INFO creating build/lib/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:43,522 root INFO copying ansible_collections/netapp/azure/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:43,522 root INFO copying ansible_collections/netapp/azure/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:43,522 root INFO copying ansible_collections/netapp/azure/changelogs/config.yaml -> build/lib/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:43,522 root INFO creating build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,522 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/20.2.0.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,523 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/20.4.0.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,523 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/20.5.0.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,523 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/20.6.0.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,523 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/20.7.0.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,523 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/20.8.0.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,524 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3505.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,524 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3526.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,524 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3663.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,524 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3704.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,525 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3849.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,525 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3935.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,525 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3949.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,525 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4001.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,525 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4070.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,526 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4135.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,526 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4246.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,526 root INFO copying ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4416.yaml -> build/lib/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:43,526 root INFO creating build/lib/ansible_collections/netapp/azure/meta 2023-04-28 05:57:43,526 root INFO copying ansible_collections/netapp/azure/meta/runtime.yml -> build/lib/ansible_collections/netapp/azure/meta 2023-04-28 05:57:43,527 root INFO creating build/lib/ansible_collections/netapp/azure/plugins 2023-04-28 05:57:43,527 root INFO creating build/lib/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:43,527 root INFO copying ansible_collections/netapp/azure/plugins/doc_fragments/azure.py -> build/lib/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:43,527 root INFO copying ansible_collections/netapp/azure/plugins/doc_fragments/azure_tags.py -> build/lib/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:43,527 root INFO copying ansible_collections/netapp/azure/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:43,528 root INFO creating build/lib/ansible_collections/netapp/azure/plugins/module_utils 2023-04-28 05:57:43,528 root INFO copying ansible_collections/netapp/azure/plugins/module_utils/azure_rm_netapp_common.py -> build/lib/ansible_collections/netapp/azure/plugins/module_utils 2023-04-28 05:57:43,528 root INFO copying ansible_collections/netapp/azure/plugins/module_utils/netapp_module.py -> build/lib/ansible_collections/netapp/azure/plugins/module_utils 2023-04-28 05:57:43,528 root INFO creating build/lib/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:43,528 root INFO copying ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_account.py -> build/lib/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:43,529 root INFO copying ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_capacity_pool.py -> build/lib/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:43,529 root INFO copying ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_snapshot.py -> build/lib/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:43,529 root INFO copying ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_volume.py -> build/lib/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:43,529 root INFO creating build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,529 root INFO copying ansible_collections/netapp/cloudmanager/CHANGELOG.rst -> build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,530 root INFO copying ansible_collections/netapp/cloudmanager/COPYING -> build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,530 root INFO copying ansible_collections/netapp/cloudmanager/FILES.json -> build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,530 root INFO copying ansible_collections/netapp/cloudmanager/MANIFEST.json -> build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,530 root INFO copying ansible_collections/netapp/cloudmanager/README.md -> build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,531 root INFO copying ansible_collections/netapp/cloudmanager/kubectl.sha256 -> build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,531 root INFO copying ansible_collections/netapp/cloudmanager/requirements.txt -> build/lib/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:43,531 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:43,531 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:43,531 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:43,532 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/config.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:43,532 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,532 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3803.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,532 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3844.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,532 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3909.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,533 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3910.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,533 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3911.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,533 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3912.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,533 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3913.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,533 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3922.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,534 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3946.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,534 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3947.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,534 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3948.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,534 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3965.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,535 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3967.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,535 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3975.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,535 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3984.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,535 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3985.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,535 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3995.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,536 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4021.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,536 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4065.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,536 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4105.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,536 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4118.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,536 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4136.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,537 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4164.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,537 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4200.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,537 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4201.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,537 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4205.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,538 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4223.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,538 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4264.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,538 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4267.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,538 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4271.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,538 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4281.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,539 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4292.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,539 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4298.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,539 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4303.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,539 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4321.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,540 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4327.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,540 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4328.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,540 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4358.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,540 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4386.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,540 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4416.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,541 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4458.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,541 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4492.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,541 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4500.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,541 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4513.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,541 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4516.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,542 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4542.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,542 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4563.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,542 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4567.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,542 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4647.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,543 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4703.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,543 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4758.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,543 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4820.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,543 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5002.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,543 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5151.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,544 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5252.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,544 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5307.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,544 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5342.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,544 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5366.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,545 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5437.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,545 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5452.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,545 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5472.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,545 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5527.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,545 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5540.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,546 root INFO copying ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5562.yaml -> build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:43,546 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/execution_environments 2023-04-28 05:57:43,546 root INFO copying ansible_collections/netapp/cloudmanager/execution_environments/README.md -> build/lib/ansible_collections/netapp/cloudmanager/execution_environments 2023-04-28 05:57:43,546 root INFO copying ansible_collections/netapp/cloudmanager/execution_environments/requirements.txt -> build/lib/ansible_collections/netapp/cloudmanager/execution_environments 2023-04-28 05:57:43,546 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy 2023-04-28 05:57:43,547 root INFO copying ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy/execution-environment.yml -> build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy 2023-04-28 05:57:43,547 root INFO copying ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy/requirements.yml -> build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy 2023-04-28 05:57:43,547 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_github 2023-04-28 05:57:43,547 root INFO copying ansible_collections/netapp/cloudmanager/execution_environments/from_github/execution-environment.yml -> build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_github 2023-04-28 05:57:43,547 root INFO copying ansible_collections/netapp/cloudmanager/execution_environments/from_github/requirements.yml -> build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_github 2023-04-28 05:57:43,548 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/meta 2023-04-28 05:57:43,548 root INFO copying ansible_collections/netapp/cloudmanager/meta/execution-environment.yml -> build/lib/ansible_collections/netapp/cloudmanager/meta 2023-04-28 05:57:43,548 root INFO copying ansible_collections/netapp/cloudmanager/meta/runtime.yml -> build/lib/ansible_collections/netapp/cloudmanager/meta 2023-04-28 05:57:43,548 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/plugins 2023-04-28 05:57:43,548 root INFO copying ansible_collections/netapp/cloudmanager/plugins/README.md -> build/lib/ansible_collections/netapp/cloudmanager/plugins 2023-04-28 05:57:43,548 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/plugins/doc_fragments 2023-04-28 05:57:43,549 root INFO copying ansible_collections/netapp/cloudmanager/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/doc_fragments 2023-04-28 05:57:43,549 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/plugins/module_utils 2023-04-28 05:57:43,549 root INFO copying ansible_collections/netapp/cloudmanager/plugins/module_utils/netapp.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/module_utils 2023-04-28 05:57:43,549 root INFO copying ansible_collections/netapp/cloudmanager/plugins/module_utils/netapp_module.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/module_utils 2023-04-28 05:57:43,550 root INFO creating build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,550 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_aggregate.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,550 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_aws_fsx.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,550 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cifs_server.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,550 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_aws.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,551 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_azure.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,551 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_gcp.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,551 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_aws.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,551 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_azure.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,552 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_gcp.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,552 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_info.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,552 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_nss_account.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,552 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_snapmirror.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,553 root INFO copying ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_volume.py -> build/lib/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:43,553 root INFO creating build/lib/ansible_collections/netapp/elementsw 2023-04-28 05:57:43,553 root INFO copying ansible_collections/netapp/elementsw/CHANGELOG.rst -> build/lib/ansible_collections/netapp/elementsw 2023-04-28 05:57:43,553 root INFO copying ansible_collections/netapp/elementsw/FILES.json -> build/lib/ansible_collections/netapp/elementsw 2023-04-28 05:57:43,553 root INFO copying ansible_collections/netapp/elementsw/MANIFEST.json -> build/lib/ansible_collections/netapp/elementsw 2023-04-28 05:57:43,554 root INFO copying ansible_collections/netapp/elementsw/README.md -> build/lib/ansible_collections/netapp/elementsw 2023-04-28 05:57:43,554 root INFO copying ansible_collections/netapp/elementsw/requirements.txt -> build/lib/ansible_collections/netapp/elementsw 2023-04-28 05:57:43,554 root INFO creating build/lib/ansible_collections/netapp/elementsw/changelogs 2023-04-28 05:57:43,554 root INFO copying ansible_collections/netapp/elementsw/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs 2023-04-28 05:57:43,554 root INFO copying ansible_collections/netapp/elementsw/changelogs/config.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs 2023-04-28 05:57:43,555 root INFO creating build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,555 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/20.2.0.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,555 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/20.6.0.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,555 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/20.8.0.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,555 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/20.9.0.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,556 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/2019.10.0.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,556 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3117.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,556 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3174.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,556 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3188.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,557 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3196.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,557 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3235.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,557 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3310.yml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,557 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3324.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,557 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3731.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,558 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3733.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,558 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3734.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,558 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3800.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,558 root INFO copying ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-4416.yaml -> build/lib/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:43,559 root INFO creating build/lib/ansible_collections/netapp/elementsw/meta 2023-04-28 05:57:43,559 root INFO copying ansible_collections/netapp/elementsw/meta/runtime.yml -> build/lib/ansible_collections/netapp/elementsw/meta 2023-04-28 05:57:43,559 root INFO creating build/lib/ansible_collections/netapp/elementsw/plugins 2023-04-28 05:57:43,559 root INFO creating build/lib/ansible_collections/netapp/elementsw/plugins/doc_fragments 2023-04-28 05:57:43,559 root INFO copying ansible_collections/netapp/elementsw/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp/elementsw/plugins/doc_fragments 2023-04-28 05:57:43,559 root INFO creating build/lib/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:43,559 root INFO copying ansible_collections/netapp/elementsw/plugins/module_utils/netapp.py -> build/lib/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:43,560 root INFO copying ansible_collections/netapp/elementsw/plugins/module_utils/netapp_elementsw_module.py -> build/lib/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:43,560 root INFO copying ansible_collections/netapp/elementsw/plugins/module_utils/netapp_module.py -> build/lib/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:43,560 root INFO creating build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,560 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_access_group.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,561 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_access_group_volumes.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,561 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_account.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,561 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_admin_users.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,561 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_backup.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,561 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_check_connections.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,562 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,562 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_config.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,562 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_pair.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,562 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_snmp.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,563 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_drive.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,563 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_info.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,563 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_initiators.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,563 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_ldap.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,564 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_network_interfaces.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,564 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_node.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,564 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_qos_policy.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,564 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,564 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot_restore.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,565 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot_schedule.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,565 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_vlan.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,565 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,565 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume_clone.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,566 root INFO copying ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume_pair.py -> build/lib/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:43,566 root INFO creating build/lib/ansible_collections/netapp/ontap 2023-04-28 05:57:43,566 root INFO copying ansible_collections/netapp/ontap/CHANGELOG.rst -> build/lib/ansible_collections/netapp/ontap 2023-04-28 05:57:43,566 root INFO copying ansible_collections/netapp/ontap/COPYING -> build/lib/ansible_collections/netapp/ontap 2023-04-28 05:57:43,567 root INFO copying ansible_collections/netapp/ontap/FILES.json -> build/lib/ansible_collections/netapp/ontap 2023-04-28 05:57:43,567 root INFO copying ansible_collections/netapp/ontap/MANIFEST.json -> build/lib/ansible_collections/netapp/ontap 2023-04-28 05:57:43,567 root INFO copying ansible_collections/netapp/ontap/README.md -> build/lib/ansible_collections/netapp/ontap 2023-04-28 05:57:43,568 root INFO copying ansible_collections/netapp/ontap/requirements.txt -> build/lib/ansible_collections/netapp/ontap 2023-04-28 05:57:43,568 root INFO creating build/lib/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:43,568 root INFO copying ansible_collections/netapp/ontap/changelogs/.DS_Store -> build/lib/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:43,568 root INFO copying ansible_collections/netapp/ontap/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:43,569 root INFO copying ansible_collections/netapp/ontap/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:43,569 root INFO copying ansible_collections/netapp/ontap/changelogs/config.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:43,569 root INFO creating build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,569 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/0-copy_ignore_txt.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,570 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/19.10.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,570 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/19.11.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,570 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.1.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,570 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.2.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,571 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.3.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,571 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.4.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,571 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.4.1.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,571 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.5.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,571 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.6.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,572 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.6.1.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,572 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.7.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,572 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.8.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,572 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/20.9.0.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,572 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1661.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,573 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1665.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,573 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1926.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,573 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2353.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,573 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2422.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,574 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2426.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,574 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2459.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,574 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2459b.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,574 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2491.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,574 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2668.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,575 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2928.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,575 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2964.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,575 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2965.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,575 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2972.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,575 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3113.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,576 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3137.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,576 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3139.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,576 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3148.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,576 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3149.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,577 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3167.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,577 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3175.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,577 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3178.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,577 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3181.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,577 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3194.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,578 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3230.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,578 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3241.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,578 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3242.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,578 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3251.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,579 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3262.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,579 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3304.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,579 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3310.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,579 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3312.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,579 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3329.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,580 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3346.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,580 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3354.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,580 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3358.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,580 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3366.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,581 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3367.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,581 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3368.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,581 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3369.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,581 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3370.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,581 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3371.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,582 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3385.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,582 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3386.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,582 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3390.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,582 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3392.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,582 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3399.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,583 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3400.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,583 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3401.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,583 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3439.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,583 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3442.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,584 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3443.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,584 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3454.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,584 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3479.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,584 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3480.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,584 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3483.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,585 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3490.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,585 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3494.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,585 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3497.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,585 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3501.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,586 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3510.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,586 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3515.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,586 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3534.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,586 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3535.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,586 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3536.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,587 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3540.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,587 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3542.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,587 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3543.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,587 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3571.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,588 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3579.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,588 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3580.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,588 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3595.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,588 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3615.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,588 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3623.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,589 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3625.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,589 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3626.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,589 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3628.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,589 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3632.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,590 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3633.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,590 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3649.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,590 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3654.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,590 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3655.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,590 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3662.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,591 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3667.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,591 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3668.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,591 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3671.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,591 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3677.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,592 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3685.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,592 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3716.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,592 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3718.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,592 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3754.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,592 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3757.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,593 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3767.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,593 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3772.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,593 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3801.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,593 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3807.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,594 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3811.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,594 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3812.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,594 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3830.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,594 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3850.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,594 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3870.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,595 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3883.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,595 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3900.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,595 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3926.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,595 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3939.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,595 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3950.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,596 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3952.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,596 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3969.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,596 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3971.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,596 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3973.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,597 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3983.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,597 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3994.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,597 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4005.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,597 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4010.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,598 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4022.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,598 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4026.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,598 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4031.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,598 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4039.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,598 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4048.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,599 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4049.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,599 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4060.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,599 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4079.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,599 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4113.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,600 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4114.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,600 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4116.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,600 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4119.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,600 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4121.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,600 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4122.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,601 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4123.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,601 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4140.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,601 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4150.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,601 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4157.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,602 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4159.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,602 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4161.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,602 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4175.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,602 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4177.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,602 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4179.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,603 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4190.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,603 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4191.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,603 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4196.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,603 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4197.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,604 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4206.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,604 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4218.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,604 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4227.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,604 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4228.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,604 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4231.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,605 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4235.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,605 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4243.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,605 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4255.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,605 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4256.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,606 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4270.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,606 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4288.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,606 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4289.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,606 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4300.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,606 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4312.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,607 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4319.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,607 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4320.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,607 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4325.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,607 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4329.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,608 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4331.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,608 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4332.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,608 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4333.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,608 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4334.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,609 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4335.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,609 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4336.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,609 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4337.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,609 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4338.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,609 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4339.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,610 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4340.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,610 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4341.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,610 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4342.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,610 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4343.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,611 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4344.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,611 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4345.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,611 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4347.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,611 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4348.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,611 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4349.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,612 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4350.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,612 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4367.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,612 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4391.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,612 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4392.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,613 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4393.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,613 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4394.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,613 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4399.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,613 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4401.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,613 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4404.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,614 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4415.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,614 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4417.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,614 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4435.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,614 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4439.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,615 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4449.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,615 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4457.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,615 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4459.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,615 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4460.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,615 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4465.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,616 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4479.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,616 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4487.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,616 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4501.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,616 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4508.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,617 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4526.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,617 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4527.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,617 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4540.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,617 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4554.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,617 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4565.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,618 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4566.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,618 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4568.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,618 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4573.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,618 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4577.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,619 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4588.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,619 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4604.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,619 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4605.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,619 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4606.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,619 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4609.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,620 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4612.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,620 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4621.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,620 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4623.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,620 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4644.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,621 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4645.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,621 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4648.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,621 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4676.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,621 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4679.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,621 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4691.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,622 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4711.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,622 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4716.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,622 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4719.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,622 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4729.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,623 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4731.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,623 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4735.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,623 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4736.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,623 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4737.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,624 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4743.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,624 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4745.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,624 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4747.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,624 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4762.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,624 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4763.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,625 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4764.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,625 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4767.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,625 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4769.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,625 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4770.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,626 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4771.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,626 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4773.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,626 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4774.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,626 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4775.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,626 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4776.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,627 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4779.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,627 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4780.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,627 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4781.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,627 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4784.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,628 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4785.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,628 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4786.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,628 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4788.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,628 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4789.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,628 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4790.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,629 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4794.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,629 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4798.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,630 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4799.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,630 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4800.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,630 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4801.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,630 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4802.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,630 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4803.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,631 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4804.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,631 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4807.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,631 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4808.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,631 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4809.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,632 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4813.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,632 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4818.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,632 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4830.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,632 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4832.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,632 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4834.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,633 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4857.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,633 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4862.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,633 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4863.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,633 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4864.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,634 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4872.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,634 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4879.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,634 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4882.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,634 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4898.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,635 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4975.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,635 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4981.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,635 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4984.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,635 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4985.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,635 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4998.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,636 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5015.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,636 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5016.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,636 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5017.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,636 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5019.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,637 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5026.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,637 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5034.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,637 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5047.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,637 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5062.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,637 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5063.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,638 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5065.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,638 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5068.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,638 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5079.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,638 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5082.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,639 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5084.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,639 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5085.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,639 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5090.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,639 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5092.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,640 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5109.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,640 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5121.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,640 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5127.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,640 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5136.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,640 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5137.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,641 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5138.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,641 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5152.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,641 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5161.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,641 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5168.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,642 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5174.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,642 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5179.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,642 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5188.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,642 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5189.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,642 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5190.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,643 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5195.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,643 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5215.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,643 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5216.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,643 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5220.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,644 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5223.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,644 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5228.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,644 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5229.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,644 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5241.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,645 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5243.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,645 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5246.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,645 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5251.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,645 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5263.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,645 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5268.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,646 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5270.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,646 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5271.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,646 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5275.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,646 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5285.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,647 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5287.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,647 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5297.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,647 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5299.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,647 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5304.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,648 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5310.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,648 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5312.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,648 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5338.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,648 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5344.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,648 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5354.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,649 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5367.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,649 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5380.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,649 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5409.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,649 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5412.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,650 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5413.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,650 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5414.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,650 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5415.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,650 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5426.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,650 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5427.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,651 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5430.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,651 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5431.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,651 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5453.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,651 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5457.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,652 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5479.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,652 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5481.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,652 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5484.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,652 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5485.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,652 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5487.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,653 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5503.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,653 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5504.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,653 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5505.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,653 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5506.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,654 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5507.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,654 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5531.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,654 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5532.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,654 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5536.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,654 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5537.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,655 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5540.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,655 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5548.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,655 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5589.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,655 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5591.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,656 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5592.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,656 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5594.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,656 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5595.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,656 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5596.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,656 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5604.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,657 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5606.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,657 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5611.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,657 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5626.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,657 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5628.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,658 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5629.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,658 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5659.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,658 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5662.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,658 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5665.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,658 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5666.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,659 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5671.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,659 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5677.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,659 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5678.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,659 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5696.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,660 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5711.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,660 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5713.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,660 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5725.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,660 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5733.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,660 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5734.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,661 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5735.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,661 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5737.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,661 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5738.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,661 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5757.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,662 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5760.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,662 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5761.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,662 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5774.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,662 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5784.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,662 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5788.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,663 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5790.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,663 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5807.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,663 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5808.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,663 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5809.yml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,664 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5812.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,664 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5816.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,664 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5819.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,664 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5820.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,665 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5844.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,665 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5845.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,665 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5859.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,665 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5892.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,665 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5894.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,666 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5899.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,666 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5910.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,666 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5913.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,666 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5917.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,667 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5919.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,667 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5926.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,667 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5938.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,667 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5948.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,667 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5952.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,668 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5960.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,668 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5972.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,668 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5983.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,668 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5986.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,669 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-6005.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,669 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/github-110.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,669 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/github-56.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,669 root INFO copying ansible_collections/netapp/ontap/changelogs/fragments/no-story-1.yaml -> build/lib/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:43,669 root INFO creating build/lib/ansible_collections/netapp/ontap/execution_environments 2023-04-28 05:57:43,670 root INFO copying ansible_collections/netapp/ontap/execution_environments/README.md -> build/lib/ansible_collections/netapp/ontap/execution_environments 2023-04-28 05:57:43,670 root INFO copying ansible_collections/netapp/ontap/execution_environments/requirements.txt -> build/lib/ansible_collections/netapp/ontap/execution_environments 2023-04-28 05:57:43,670 root INFO creating build/lib/ansible_collections/netapp/ontap/execution_environments/from_galaxy 2023-04-28 05:57:43,670 root INFO copying ansible_collections/netapp/ontap/execution_environments/from_galaxy/execution-environment.yml -> build/lib/ansible_collections/netapp/ontap/execution_environments/from_galaxy 2023-04-28 05:57:43,670 root INFO copying ansible_collections/netapp/ontap/execution_environments/from_galaxy/requirements.yml -> build/lib/ansible_collections/netapp/ontap/execution_environments/from_galaxy 2023-04-28 05:57:43,671 root INFO creating build/lib/ansible_collections/netapp/ontap/execution_environments/from_github 2023-04-28 05:57:43,671 root INFO copying ansible_collections/netapp/ontap/execution_environments/from_github/execution-environment.yml -> build/lib/ansible_collections/netapp/ontap/execution_environments/from_github 2023-04-28 05:57:43,671 root INFO copying ansible_collections/netapp/ontap/execution_environments/from_github/requirements.yml -> build/lib/ansible_collections/netapp/ontap/execution_environments/from_github 2023-04-28 05:57:43,671 root INFO creating build/lib/ansible_collections/netapp/ontap/meta 2023-04-28 05:57:43,671 root INFO copying ansible_collections/netapp/ontap/meta/execution-environment.yml -> build/lib/ansible_collections/netapp/ontap/meta 2023-04-28 05:57:43,671 root INFO copying ansible_collections/netapp/ontap/meta/runtime.yml -> build/lib/ansible_collections/netapp/ontap/meta 2023-04-28 05:57:43,672 root INFO creating build/lib/ansible_collections/netapp/ontap/playbooks 2023-04-28 05:57:43,672 root INFO creating build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,672 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/README.md -> build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,672 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_install_SSL_certificate.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,672 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_install_SSL_certificate_REST.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,673 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,673 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware_with_extra_vars.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,673 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware_with_vars_file.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,673 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/ontap_vars_file.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:43,674 root INFO creating build/lib/ansible_collections/netapp/ontap/playbooks/examples/filter 2023-04-28 05:57:43,674 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/filter/test_na_filter_iso8601.yaml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/filter 2023-04-28 05:57:43,674 root INFO creating build/lib/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:43,674 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/json_query/README.md -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:43,674 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/json_query/na_ontap_pb_get_online_volumes.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:43,674 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/json_query/na_ontap_pb_get_online_volumes_loop.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:43,675 root INFO creating build/lib/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:43,675 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/rest_apis/clusters.yaml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:43,675 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/rest_apis/list_aggregates.yaml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:43,675 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/rest_apis/volumes.yml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:43,675 root INFO creating build/lib/ansible_collections/netapp/ontap/playbooks/examples/support 2023-04-28 05:57:43,676 root INFO copying ansible_collections/netapp/ontap/playbooks/examples/support/debug_connectivity.yaml -> build/lib/ansible_collections/netapp/ontap/playbooks/examples/support 2023-04-28 05:57:43,676 root INFO creating build/lib/ansible_collections/netapp/ontap/plugins 2023-04-28 05:57:43,676 root INFO creating build/lib/ansible_collections/netapp/ontap/plugins/doc_fragments 2023-04-28 05:57:43,676 root INFO copying ansible_collections/netapp/ontap/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp/ontap/plugins/doc_fragments 2023-04-28 05:57:43,676 root INFO creating build/lib/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:43,676 root INFO copying ansible_collections/netapp/ontap/plugins/filter/iso8601_duration_from_seconds.yml -> build/lib/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:43,677 root INFO copying ansible_collections/netapp/ontap/plugins/filter/iso8601_duration_to_seconds.yml -> build/lib/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:43,677 root INFO copying ansible_collections/netapp/ontap/plugins/filter/na_filter_iso8601.py -> build/lib/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:43,677 root INFO creating build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,677 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/netapp.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,678 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/netapp_elementsw_module.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,678 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/netapp_ipaddress.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,678 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/netapp_module.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,678 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/rest_application.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,678 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/rest_generic.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,679 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/rest_owning_resource.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,679 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/rest_response_helpers.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,679 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/rest_user.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,679 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/rest_volume.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,680 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/rest_vserver.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,680 root INFO copying ansible_collections/netapp/ontap/plugins/module_utils/zapis_svm.py -> build/lib/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:43,680 root INFO creating build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,680 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_active_directory.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,680 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_aggregate.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,681 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_autosupport.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,681 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_autosupport_invoke.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,681 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_bgp_peer_group.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,681 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_broadcast_domain.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,682 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_broadcast_domain_ports.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,682 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cg_snapshot.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,682 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,682 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_acl.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,683 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_group.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,683 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_group_member.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,683 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,683 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user_modify.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,683 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user_set_password.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,684 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_server.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,684 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,684 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster_ha.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,684 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster_peer.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,685 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_command.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,685 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_debug.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,685 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_disk_options.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,685 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_disks.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,686 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_dns.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,686 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_domain_tunnel.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,686 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_efficiency_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,686 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ems_destination.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,687 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ems_filter.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,687 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_export_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,687 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_export_policy_rule.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,687 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fcp.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,688 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdsd.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,688 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdsp.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,688 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdspt.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,688 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdss.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,689 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_directory_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,689 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_security_permissions.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,689 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_security_permissions_acl.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,689 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_firewall_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,690 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_firmware_upgrade.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,690 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_flexcache.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,690 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_event.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,690 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_ext_engine.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,691 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,691 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_scope.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,691 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_status.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,691 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_igroup.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,692 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_igroup_initiator.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,692 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_info.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,692 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_interface.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,692 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ipspace.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,693 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_iscsi.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,693 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_iscsi_security.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,693 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_job_schedule.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,693 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_kerberos_realm.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,694 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ldap.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,694 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ldap_client.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,694 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_license.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,694 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_local_hosts.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,695 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_log_forward.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,695 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_login_messages.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,695 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,695 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_copy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,696 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_map.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,696 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_map_reporting_nodes.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,696 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_mcc_mediator.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,696 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_metrocluster.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,697 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_metrocluster_dr_group.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,697 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_motd.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,697 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_name_mappings.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,697 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_name_service_switch.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,698 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ndmp.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,698 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_ifgrp.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,698 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_port.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,698 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_routes.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,698 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_subnet.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,699 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_vlan.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,699 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_nfs.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,699 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_node.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,699 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntfs_dacl.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,700 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntfs_sd.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,700 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntp.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,700 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntp_key.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,700 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,701 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme_namespace.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,701 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme_subsystem.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,701 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_object_store.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,701 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_partitions.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,702 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ports.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,702 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_portset.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,702 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_publickey.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,702 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_qos_adaptive_policy_group.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,703 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_qos_policy_group.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,703 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_qtree.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,703 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_quota_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,703 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_quotas.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,704 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_rest_cli.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,704 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_rest_info.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,704 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_restit.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,704 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_buckets.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,705 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_groups.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,705 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_policies.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,705 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_services.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,705 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_users.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,706 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_certificates.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,706 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_config.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,706 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_ca_certificate.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,706 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_config.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,707 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,707 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_key_manager.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,707 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ssh.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,707 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_service_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,708 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_service_processor_network.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,708 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_snaplock_clock.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,708 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapmirror.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,708 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapmirror_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,709 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapshot.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,709 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapshot_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,709 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_snmp.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,709 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_snmp_traphosts.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,710 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_software_update.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,710 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ssh_command.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,710 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_storage_auto_giveback.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,710 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_storage_failover.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,711 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_svm.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,711 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_svm_options.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,711 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_ucadapter.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,711 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_unix_group.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,712 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_unix_user.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,712 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_user.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,712 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_user_role.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,713 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,713 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_autosize.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,713 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_clone.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,713 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_efficiency.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,714 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_snaplock.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,714 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,714 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_on_access_policy.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,714 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_on_demand_task.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,715 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_scanner_pool.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,715 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_audit.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,715 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_cifs_security.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,715 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_peer.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,716 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_peer_permissions.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,716 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_wait_for_condition.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,716 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_wwpn_alias.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,716 root INFO copying ansible_collections/netapp/ontap/plugins/modules/na_ontap_zapit.py -> build/lib/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:43,717 root INFO creating build/lib/ansible_collections/netapp/ontap/roles 2023-04-28 05:57:43,717 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config 2023-04-28 05:57:43,717 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/LICENSE -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config 2023-04-28 05:57:43,717 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/README.md -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config 2023-04-28 05:57:43,717 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/defaults 2023-04-28 05:57:43,717 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/defaults/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/defaults 2023-04-28 05:57:43,718 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/handlers 2023-04-28 05:57:43,718 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/handlers/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/handlers 2023-04-28 05:57:43,718 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/meta 2023-04-28 05:57:43,718 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/meta/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/meta 2023-04-28 05:57:43,718 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tasks 2023-04-28 05:57:43,719 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tasks/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tasks 2023-04-28 05:57:43,719 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests 2023-04-28 05:57:43,719 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests/inventory -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests 2023-04-28 05:57:43,719 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests/test.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests 2023-04-28 05:57:43,719 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/vars 2023-04-28 05:57:43,719 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/vars/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/vars 2023-04-28 05:57:43,720 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create 2023-04-28 05:57:43,720 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/LICENSE -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create 2023-04-28 05:57:43,720 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/README.md -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create 2023-04-28 05:57:43,720 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/defaults 2023-04-28 05:57:43,720 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/defaults/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/defaults 2023-04-28 05:57:43,721 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/handlers 2023-04-28 05:57:43,721 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/handlers/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/handlers 2023-04-28 05:57:43,721 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/meta 2023-04-28 05:57:43,721 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/meta/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/meta 2023-04-28 05:57:43,721 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tasks 2023-04-28 05:57:43,722 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tasks/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tasks 2023-04-28 05:57:43,722 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests 2023-04-28 05:57:43,722 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests/inventory -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests 2023-04-28 05:57:43,722 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests/test.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests 2023-04-28 05:57:43,722 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/vars 2023-04-28 05:57:43,722 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_nas_create/vars/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/vars 2023-04-28 05:57:43,723 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create 2023-04-28 05:57:43,723 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/LICENSE -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create 2023-04-28 05:57:43,723 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/README.md -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create 2023-04-28 05:57:43,723 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/defaults 2023-04-28 05:57:43,723 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/defaults/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/defaults 2023-04-28 05:57:43,724 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/handlers 2023-04-28 05:57:43,724 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/handlers/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/handlers 2023-04-28 05:57:43,724 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/meta 2023-04-28 05:57:43,724 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/meta/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/meta 2023-04-28 05:57:43,724 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tasks 2023-04-28 05:57:43,725 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/tasks/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tasks 2023-04-28 05:57:43,725 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests 2023-04-28 05:57:43,725 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests/inventory -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests 2023-04-28 05:57:43,725 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests/test.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests 2023-04-28 05:57:43,725 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/vars 2023-04-28 05:57:43,725 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_san_create/vars/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/vars 2023-04-28 05:57:43,726 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create 2023-04-28 05:57:43,726 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/README.md -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create 2023-04-28 05:57:43,726 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/defaults 2023-04-28 05:57:43,726 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/defaults/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/defaults 2023-04-28 05:57:43,726 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/handlers 2023-04-28 05:57:43,726 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/handlers/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/handlers 2023-04-28 05:57:43,727 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/meta 2023-04-28 05:57:43,727 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/meta/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/meta 2023-04-28 05:57:43,727 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tasks 2023-04-28 05:57:43,727 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tasks/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tasks 2023-04-28 05:57:43,727 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests 2023-04-28 05:57:43,728 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests/inventory -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests 2023-04-28 05:57:43,728 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests/test.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests 2023-04-28 05:57:43,728 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/vars 2023-04-28 05:57:43,728 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/vars/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/vars 2023-04-28 05:57:43,728 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create 2023-04-28 05:57:43,728 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/LICENSE -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create 2023-04-28 05:57:43,729 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/README.md -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create 2023-04-28 05:57:43,729 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/defaults 2023-04-28 05:57:43,729 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/defaults/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/defaults 2023-04-28 05:57:43,729 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/handlers 2023-04-28 05:57:43,729 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/handlers/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/handlers 2023-04-28 05:57:43,730 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/meta 2023-04-28 05:57:43,730 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/meta/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/meta 2023-04-28 05:57:43,730 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tasks 2023-04-28 05:57:43,730 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tasks/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tasks 2023-04-28 05:57:43,730 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests 2023-04-28 05:57:43,730 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests/inventory -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests 2023-04-28 05:57:43,731 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests/test.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests 2023-04-28 05:57:43,731 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/vars 2023-04-28 05:57:43,731 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/vars/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/vars 2023-04-28 05:57:43,731 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete 2023-04-28 05:57:43,731 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/.travis.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete 2023-04-28 05:57:43,732 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/README.md -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete 2023-04-28 05:57:43,732 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/defaults 2023-04-28 05:57:43,732 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/defaults/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/defaults 2023-04-28 05:57:43,732 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/handlers 2023-04-28 05:57:43,732 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/handlers/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/handlers 2023-04-28 05:57:43,732 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/meta 2023-04-28 05:57:43,733 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/meta/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/meta 2023-04-28 05:57:43,733 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,733 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/assert_prereqs_and_vserver_exists.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,733 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/delete_volumes.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,733 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/find_and_delete_volumes.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,734 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/find_and_delete_volumes_retries.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,734 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_cifs_server.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,734 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_igroups.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,734 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_interfaces.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,735 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_volumes.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,735 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:43,735 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests 2023-04-28 05:57:43,735 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests/inventory -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests 2023-04-28 05:57:43,735 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests/test.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests 2023-04-28 05:57:43,736 root INFO creating build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/vars 2023-04-28 05:57:43,736 root INFO copying ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/vars/main.yml -> build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/vars 2023-04-28 05:57:43,736 root INFO creating build/lib/ansible_collections/netapp/storagegrid 2023-04-28 05:57:43,736 root INFO copying ansible_collections/netapp/storagegrid/CHANGELOG.rst -> build/lib/ansible_collections/netapp/storagegrid 2023-04-28 05:57:43,736 root INFO copying ansible_collections/netapp/storagegrid/COPYING -> build/lib/ansible_collections/netapp/storagegrid 2023-04-28 05:57:43,737 root INFO copying ansible_collections/netapp/storagegrid/FILES.json -> build/lib/ansible_collections/netapp/storagegrid 2023-04-28 05:57:43,737 root INFO copying ansible_collections/netapp/storagegrid/MANIFEST.json -> build/lib/ansible_collections/netapp/storagegrid 2023-04-28 05:57:43,737 root INFO copying ansible_collections/netapp/storagegrid/README.md -> build/lib/ansible_collections/netapp/storagegrid 2023-04-28 05:57:43,737 root INFO copying ansible_collections/netapp/storagegrid/requirements.txt -> build/lib/ansible_collections/netapp/storagegrid 2023-04-28 05:57:43,737 root INFO creating build/lib/ansible_collections/netapp/storagegrid/changelogs 2023-04-28 05:57:43,738 root INFO copying ansible_collections/netapp/storagegrid/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs 2023-04-28 05:57:43,738 root INFO copying ansible_collections/netapp/storagegrid/changelogs/config.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs 2023-04-28 05:57:43,738 root INFO creating build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,738 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/20.10.0.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,738 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/20.6.1.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,739 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/20.7.0.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,739 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/21.11.0.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,739 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/21.11.1.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,739 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/21.6.0.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,739 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/21.9.0.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,740 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/DEVOPS-4416.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,740 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/github-10.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,740 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/github-66.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,740 root INFO copying ansible_collections/netapp/storagegrid/changelogs/fragments/github-8.yaml -> build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:43,740 root INFO creating build/lib/ansible_collections/netapp/storagegrid/meta 2023-04-28 05:57:43,741 root INFO copying ansible_collections/netapp/storagegrid/meta/runtime.yml -> build/lib/ansible_collections/netapp/storagegrid/meta 2023-04-28 05:57:43,741 root INFO creating build/lib/ansible_collections/netapp/storagegrid/plugins 2023-04-28 05:57:43,741 root INFO creating build/lib/ansible_collections/netapp/storagegrid/plugins/doc_fragments 2023-04-28 05:57:43,741 root INFO copying ansible_collections/netapp/storagegrid/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/doc_fragments 2023-04-28 05:57:43,741 root INFO creating build/lib/ansible_collections/netapp/storagegrid/plugins/module_utils 2023-04-28 05:57:43,741 root INFO copying ansible_collections/netapp/storagegrid/plugins/module_utils/netapp.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/module_utils 2023-04-28 05:57:43,742 root INFO copying ansible_collections/netapp/storagegrid/plugins/module_utils/netapp_module.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/module_utils 2023-04-28 05:57:43,742 root INFO creating build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,742 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_account.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,742 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_certificate.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,743 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_client_certificate.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,743 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_dns.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,743 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_gateway.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,743 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_group.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,743 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_ha_group.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,744 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_identity_federation.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,744 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_info.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,744 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_ntp.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,744 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_regions.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,745 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_traffic_classes.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,745 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_user.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,745 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_container.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,745 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_group.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,746 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_identity_federation.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,746 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_info.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,746 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_user.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,746 root INFO copying ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_user_s3_key.py -> build/lib/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:43,746 root INFO creating build/lib/ansible_collections/netapp/um_info 2023-04-28 05:57:43,747 root INFO copying ansible_collections/netapp/um_info/CHANGELOG.rst -> build/lib/ansible_collections/netapp/um_info 2023-04-28 05:57:43,747 root INFO copying ansible_collections/netapp/um_info/COPYING -> build/lib/ansible_collections/netapp/um_info 2023-04-28 05:57:43,747 root INFO copying ansible_collections/netapp/um_info/FILES.json -> build/lib/ansible_collections/netapp/um_info 2023-04-28 05:57:43,747 root INFO copying ansible_collections/netapp/um_info/MANIFEST.json -> build/lib/ansible_collections/netapp/um_info 2023-04-28 05:57:43,748 root INFO copying ansible_collections/netapp/um_info/README.md -> build/lib/ansible_collections/netapp/um_info 2023-04-28 05:57:43,748 root INFO copying ansible_collections/netapp/um_info/requirements.txt -> build/lib/ansible_collections/netapp/um_info 2023-04-28 05:57:43,748 root INFO creating build/lib/ansible_collections/netapp/um_info/changelogs 2023-04-28 05:57:43,748 root INFO copying ansible_collections/netapp/um_info/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs 2023-04-28 05:57:43,748 root INFO copying ansible_collections/netapp/um_info/changelogs/config.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs 2023-04-28 05:57:43,748 root INFO creating build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,749 root INFO copying ansible_collections/netapp/um_info/changelogs/fragments/20.7.0.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,749 root INFO copying ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-2952.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,749 root INFO copying ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-3920.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,749 root INFO copying ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-3962.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,749 root INFO copying ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4059.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,750 root INFO copying ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4087.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,750 root INFO copying ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4416.yaml -> build/lib/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:43,750 root INFO creating build/lib/ansible_collections/netapp/um_info/meta 2023-04-28 05:57:43,750 root INFO copying ansible_collections/netapp/um_info/meta/runtime.yml -> build/lib/ansible_collections/netapp/um_info/meta 2023-04-28 05:57:43,750 root INFO creating build/lib/ansible_collections/netapp/um_info/plugins 2023-04-28 05:57:43,751 root INFO creating build/lib/ansible_collections/netapp/um_info/plugins/doc_fragments 2023-04-28 05:57:43,751 root INFO copying ansible_collections/netapp/um_info/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp/um_info/plugins/doc_fragments 2023-04-28 05:57:43,751 root INFO creating build/lib/ansible_collections/netapp/um_info/plugins/module_utils 2023-04-28 05:57:43,751 root INFO copying ansible_collections/netapp/um_info/plugins/module_utils/netapp.py -> build/lib/ansible_collections/netapp/um_info/plugins/module_utils 2023-04-28 05:57:43,751 root INFO copying ansible_collections/netapp/um_info/plugins/module_utils/netapp_module.py -> build/lib/ansible_collections/netapp/um_info/plugins/module_utils 2023-04-28 05:57:43,752 root INFO creating build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,752 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_aggregates_info.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,752 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_clusters_info.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,752 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_list_aggregates.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,752 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_list_clusters.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,753 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_list_nodes.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,753 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_list_svms.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,753 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_list_volumes.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,753 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_nodes_info.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,753 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_svms_info.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,754 root INFO copying ansible_collections/netapp/um_info/plugins/modules/na_um_volumes_info.py -> build/lib/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:43,754 root INFO creating build/lib/ansible_collections/netapp_eseries 2023-04-28 05:57:43,754 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,755 root INFO copying ansible_collections/netapp_eseries/santricity/CHANGELOG.rst -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,755 root INFO copying ansible_collections/netapp_eseries/santricity/CONTRIBUTING.md -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,755 root INFO copying ansible_collections/netapp_eseries/santricity/COPYING -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,755 root INFO copying ansible_collections/netapp_eseries/santricity/FILES.json -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,756 root INFO copying ansible_collections/netapp_eseries/santricity/Jenkinsfile.blackduck -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,756 root INFO copying ansible_collections/netapp_eseries/santricity/MANIFEST.json -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,756 root INFO copying ansible_collections/netapp_eseries/santricity/README.md -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,756 root INFO copying ansible_collections/netapp_eseries/santricity/ansible.cfg -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,757 root INFO copying ansible_collections/netapp_eseries/santricity/eseries-ansible-collections-diagram.png -> build/lib/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:43,757 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:43,757 root INFO copying ansible_collections/netapp_eseries/santricity/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:43,757 root INFO copying ansible_collections/netapp_eseries/santricity/changelogs/changelog.yaml -> build/lib/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:43,757 root INFO copying ansible_collections/netapp_eseries/santricity/changelogs/config.yaml -> build/lib/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:43,758 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/meta 2023-04-28 05:57:43,758 root INFO copying ansible_collections/netapp_eseries/santricity/meta/runtime.yml -> build/lib/ansible_collections/netapp_eseries/santricity/meta 2023-04-28 05:57:43,758 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/plugins 2023-04-28 05:57:43,758 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments 2023-04-28 05:57:43,758 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/netapp.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments 2023-04-28 05:57:43,758 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/santricity.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments 2023-04-28 05:57:43,759 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:43,759 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_host.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:43,759 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_host_detail.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:43,759 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_lun_mapping.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:43,760 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_storage_pool.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:43,760 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_volume.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:43,760 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/plugins/module_utils 2023-04-28 05:57:43,760 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/module_utils/netapp.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/module_utils 2023-04-28 05:57:43,760 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/module_utils/santricity.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/module_utils 2023-04-28 05:57:43,761 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,761 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_alerts.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,761 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_alerts_syslog.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,761 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_asup.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,761 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_auditlog.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,762 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_auth.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,762 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_client_certificate.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,762 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_discover.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,762 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_drive_firmware.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,763 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_facts.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,763 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_firmware.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,763 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_global.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,764 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_host.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,764 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_hostgroup.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,764 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_ib_iser_interface.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,764 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_iscsi_interface.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,764 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_iscsi_target.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,765 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_ldap.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,765 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_lun_mapping.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,765 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_mgmt_interface.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,765 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_nvme_interface.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,766 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_drive_firmware_upload.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,766 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_firmware_upload.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,766 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_systems.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,766 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_server_certificate.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,767 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_snapshot.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,767 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_storagepool.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,767 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_syslog.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,767 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_volume.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,768 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_alerts.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,768 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,768 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg_role.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,768 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg_sync.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,769 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_asup.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,769 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_auditlog.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,769 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_auth.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,769 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_drive_firmware.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,770 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_facts.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,770 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_firmware.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,770 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_flashcache.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,770 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_global.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,771 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_host.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,771 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_hostgroup.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,771 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_iscsi_interface.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,771 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_iscsi_target.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,772 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_ldap.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,772 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_lun_mapping.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,772 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_mgmt_interface.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,772 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_group.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,773 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_images.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,773 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_volume.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,773 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_storage_system.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,773 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_storagepool.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,774 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_syslog.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,774 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_volume.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,774 root INFO copying ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_volume_copy.py -> build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:43,774 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles 2023-04-28 05:57:43,774 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common 2023-04-28 05:57:43,775 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/.travis.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common 2023-04-28 05:57:43,775 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/README.md -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common 2023-04-28 05:57:43,775 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/defaults 2023-04-28 05:57:43,775 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/defaults/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/defaults 2023-04-28 05:57:43,775 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/meta 2023-04-28 05:57:43,775 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/meta/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/meta 2023-04-28 05:57:43,776 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:43,776 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/build_info.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:43,776 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:43,776 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/proxy.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:43,776 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/proxy_security.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:43,777 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:43,777 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/discovery.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:43,777 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/prefer_embedded.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:43,777 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/prefer_proxy.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:43,777 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/validate_system_api_url.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:43,778 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host 2023-04-28 05:57:43,778 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/README.md -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host 2023-04-28 05:57:43,778 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/defaults 2023-04-28 05:57:43,778 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/defaults/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/defaults 2023-04-28 05:57:43,778 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/meta 2023-04-28 05:57:43,779 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/meta/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/meta 2023-04-28 05:57:43,779 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,779 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/initiator.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,779 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,779 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/lun_mapping.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,780 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,780 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,780 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/storage_pool_absent.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,780 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/storage_pool_present.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,781 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/volume.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:43,781 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:43,781 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/ib_iser.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:43,781 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/iscsi.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:43,781 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/nvme_ib.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:43,782 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/nvme_roce.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:43,782 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:43,782 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/group.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:43,782 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/rollback.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:43,782 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/view.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:43,783 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates 2023-04-28 05:57:43,783 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates/hostnqn.j2 -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates 2023-04-28 05:57:43,783 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates/initiatorname_iscsi.j2 -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates 2023-04-28 05:57:43,783 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management 2023-04-28 05:57:43,783 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/.travis.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management 2023-04-28 05:57:43,784 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/README.md -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management 2023-04-28 05:57:43,784 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/defaults 2023-04-28 05:57:43,784 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/defaults/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/defaults 2023-04-28 05:57:43,784 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/meta 2023-04-28 05:57:43,784 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/meta/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/meta 2023-04-28 05:57:43,785 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:43,785 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/firmware.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:43,785 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/interface.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:43,785 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/logging.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:43,785 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/main.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:43,786 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/security.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:43,786 root INFO copying ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/system.yml -> build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:43,786 root INFO creating build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,786 root INFO copying ansible_collections/netapp_eseries/santricity/vars/hubPreCheck.groovy -> build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,786 root INFO copying ansible_collections/netapp_eseries/santricity/vars/hubScan.groovy -> build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,787 root INFO copying ansible_collections/netapp_eseries/santricity/vars/hubScanDocker.groovy -> build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,787 root INFO copying ansible_collections/netapp_eseries/santricity/vars/hubScanProject.groovy -> build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,787 root INFO copying ansible_collections/netapp_eseries/santricity/vars/setupBlackduckBuildParameters.groovy -> build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,787 root INFO copying ansible_collections/netapp_eseries/santricity/vars/setupBuildParameters.groovy -> build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,787 root INFO copying ansible_collections/netapp_eseries/santricity/vars/setupSynopsysDetect.groovy -> build/lib/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:43,788 root INFO creating build/lib/ansible_collections/netbox 2023-04-28 05:57:43,788 root INFO creating build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,788 root INFO copying ansible_collections/netbox/netbox/CHANGELOG.rst -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,788 root INFO copying ansible_collections/netbox/netbox/CONTRIBUTING.md -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,788 root INFO copying ansible_collections/netbox/netbox/FILES.json -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,789 root INFO copying ansible_collections/netbox/netbox/LICENSE -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,789 root INFO copying ansible_collections/netbox/netbox/MANIFEST.json -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,789 root INFO copying ansible_collections/netbox/netbox/README.md -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,790 root INFO copying ansible_collections/netbox/netbox/ansible.cfg -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,790 root INFO copying ansible_collections/netbox/netbox/poetry.lock -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,790 root INFO copying ansible_collections/netbox/netbox/pyproject.toml -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,790 root INFO copying ansible_collections/netbox/netbox/requirements.txt -> build/lib/ansible_collections/netbox/netbox 2023-04-28 05:57:43,791 root INFO creating build/lib/ansible_collections/netbox/netbox/changelogs 2023-04-28 05:57:43,791 root INFO copying ansible_collections/netbox/netbox/changelogs/changelog.yaml -> build/lib/ansible_collections/netbox/netbox/changelogs 2023-04-28 05:57:43,791 root INFO copying ansible_collections/netbox/netbox/changelogs/config.yaml -> build/lib/ansible_collections/netbox/netbox/changelogs 2023-04-28 05:57:43,791 root INFO creating build/lib/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:43,791 root INFO copying ansible_collections/netbox/netbox/changelogs/fragments/.gitkeep -> build/lib/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:43,792 root INFO copying ansible_collections/netbox/netbox/changelogs/fragments/619-v3.0-ci-fixes.yml -> build/lib/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:43,792 root INFO copying ansible_collections/netbox/netbox/changelogs/fragments/allow-jinja2.yml -> build/lib/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:43,792 root INFO copying ansible_collections/netbox/netbox/changelogs/fragments/issue-558.yml -> build/lib/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:43,792 root INFO copying ansible_collections/netbox/netbox/changelogs/fragments/issue-951.yml -> build/lib/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:43,793 root INFO copying ansible_collections/netbox/netbox/changelogs/fragments/serial_and_asset.yml -> build/lib/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:43,793 root INFO creating build/lib/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:43,793 root INFO copying ansible_collections/netbox/netbox/hacking/black.sh -> build/lib/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:43,793 root INFO copying ansible_collections/netbox/netbox/hacking/build.sh -> build/lib/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:43,793 root INFO copying ansible_collections/netbox/netbox/hacking/local-test.sh -> build/lib/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:43,794 root INFO copying ansible_collections/netbox/netbox/hacking/make-docs.sh -> build/lib/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:43,794 root INFO copying ansible_collections/netbox/netbox/hacking/update_test_inventories.sh -> build/lib/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:43,794 root INFO creating build/lib/ansible_collections/netbox/netbox/meta 2023-04-28 05:57:43,794 root INFO copying ansible_collections/netbox/netbox/meta/execution-environment.yml -> build/lib/ansible_collections/netbox/netbox/meta 2023-04-28 05:57:43,794 root INFO copying ansible_collections/netbox/netbox/meta/runtime.yml -> build/lib/ansible_collections/netbox/netbox/meta 2023-04-28 05:57:43,795 root INFO creating build/lib/ansible_collections/netbox/netbox/plugins 2023-04-28 05:57:43,795 root INFO creating build/lib/ansible_collections/netbox/netbox/plugins/doc_fragments 2023-04-28 05:57:43,795 root INFO copying ansible_collections/netbox/netbox/plugins/doc_fragments/common.py -> build/lib/ansible_collections/netbox/netbox/plugins/doc_fragments 2023-04-28 05:57:43,795 root INFO creating build/lib/ansible_collections/netbox/netbox/plugins/inventory 2023-04-28 05:57:43,795 root INFO copying ansible_collections/netbox/netbox/plugins/inventory/nb_inventory.py -> build/lib/ansible_collections/netbox/netbox/plugins/inventory 2023-04-28 05:57:43,795 root INFO creating build/lib/ansible_collections/netbox/netbox/plugins/lookup 2023-04-28 05:57:43,796 root INFO copying ansible_collections/netbox/netbox/plugins/lookup/nb_lookup.py -> build/lib/ansible_collections/netbox/netbox/plugins/lookup 2023-04-28 05:57:43,796 root INFO creating build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,796 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/__init__.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,796 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_circuits.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,796 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_dcim.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,797 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_extras.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,797 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_ipam.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,797 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_secrets.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,797 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_tenancy.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,798 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_utils.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,798 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_virtualization.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,798 root INFO copying ansible_collections/netbox/netbox/plugins/module_utils/netbox_wireless.py -> build/lib/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:43,798 root INFO creating build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,798 root INFO copying ansible_collections/netbox/netbox/plugins/modules/__init__.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,799 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_aggregate.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,799 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_asn.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,799 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_cable.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,799 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_circuit.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,799 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_circuit_termination.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,800 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_circuit_type.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,800 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_cluster.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,800 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_cluster_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,800 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_cluster_type.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,801 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_config_context.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,801 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_console_port.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,801 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_console_port_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,801 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_console_server_port.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,801 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_console_server_port_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,802 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_contact.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,802 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_contact_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,802 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_contact_role.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,802 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_custom_field.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,803 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_custom_link.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,803 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_device.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,803 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_device_bay.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,803 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_device_bay_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,803 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_device_interface.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,804 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_device_interface_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,804 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_device_role.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,804 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_device_type.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,804 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_export_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,805 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_fhrp_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,805 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_front_port.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,805 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_front_port_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,805 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_inventory_item.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,805 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_inventory_item_role.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,806 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_ip_address.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,806 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_ipam_role.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,806 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_journal_entry.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,806 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_l2vpn.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,807 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_location.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,807 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_manufacturer.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,807 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_module_type.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,807 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_platform.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,807 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_power_feed.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,808 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_power_outlet.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,808 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_power_outlet_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,808 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_power_panel.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,808 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_power_port.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,809 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_power_port_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,809 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_prefix.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,809 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_provider.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,809 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_provider_network.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,810 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_rack.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,810 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_rack_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,810 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_rack_role.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,810 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_rear_port.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,810 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_rear_port_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,811 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_region.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,811 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_rir.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,811 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_route_target.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,811 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_service.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,812 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_service_template.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,812 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_site.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,812 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_site_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,812 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_tag.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,812 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_tenant.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,813 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_tenant_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,813 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_virtual_chassis.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,813 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_virtual_machine.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,813 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_vlan.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,814 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_vlan_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,814 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_vm_interface.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,814 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_vrf.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,814 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_webhook.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,814 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_lan.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,815 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_lan_group.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,815 root INFO copying ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_link.py -> build/lib/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:43,815 root INFO creating build/lib/ansible_collections/ngine_io 2023-04-28 05:57:43,815 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,815 root INFO copying ansible_collections/ngine_io/cloudstack/CHANGELOG.rst -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,816 root INFO copying ansible_collections/ngine_io/cloudstack/CONTRIBUTING.md -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,816 root INFO copying ansible_collections/ngine_io/cloudstack/COPYING -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,816 root INFO copying ansible_collections/ngine_io/cloudstack/FILES.json -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,816 root INFO copying ansible_collections/ngine_io/cloudstack/MANIFEST.json -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,817 root INFO copying ansible_collections/ngine_io/cloudstack/README.md -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,817 root INFO copying ansible_collections/ngine_io/cloudstack/codecov.yml -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,817 root INFO copying ansible_collections/ngine_io/cloudstack/requirements.txt -> build/lib/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:43,817 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:43,817 root INFO copying ansible_collections/ngine_io/cloudstack/changelogs/.gitignore -> build/lib/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:43,818 root INFO copying ansible_collections/ngine_io/cloudstack/changelogs/changelog.yaml -> build/lib/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:43,818 root INFO copying ansible_collections/ngine_io/cloudstack/changelogs/config.yaml -> build/lib/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:43,818 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/changelogs/fragments 2023-04-28 05:57:43,818 root INFO copying ansible_collections/ngine_io/cloudstack/changelogs/fragments/.keep -> build/lib/ansible_collections/ngine_io/cloudstack/changelogs/fragments 2023-04-28 05:57:43,818 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/meta 2023-04-28 05:57:43,819 root INFO copying ansible_collections/ngine_io/cloudstack/meta/runtime.yml -> build/lib/ansible_collections/ngine_io/cloudstack/meta 2023-04-28 05:57:43,819 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/plugins 2023-04-28 05:57:43,819 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:43,819 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:43,819 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/cloudstack.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:43,819 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/cloudstack_environment.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:43,820 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/plugins/inventory 2023-04-28 05:57:43,820 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/inventory/__init__.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/inventory 2023-04-28 05:57:43,820 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/inventory/instance.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/inventory 2023-04-28 05:57:43,820 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/plugins/module_utils 2023-04-28 05:57:43,820 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/module_utils/cloudstack.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/module_utils 2023-04-28 05:57:43,821 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,821 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/__init__.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,821 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_account.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,821 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_affinitygroup.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,821 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_cluster.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,822 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_configuration.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,822 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_disk_offering.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,822 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_domain.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,822 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_facts.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,823 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_firewall.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,823 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_host.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,823 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_image_store.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,823 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,824 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_info.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,824 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_nic.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,824 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_nic_secondaryip.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,824 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_password_reset.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,824 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instancegroup.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,825 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_ip_address.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,825 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_iso.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,825 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_loadbalancer_rule.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,825 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_loadbalancer_rule_member.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,826 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,826 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_acl.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,826 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_acl_rule.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,826 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_offering.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,827 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_physical_network.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,827 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_pod.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,827 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_portforward.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,827 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_project.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,827 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_region.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,828 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_resourcelimit.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,828 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_role.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,828 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_role_permission.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,828 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_router.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,829 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_securitygroup.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,829 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_securitygroup_rule.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,829 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_service_offering.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,829 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_snapshot_policy.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,830 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_sshkeypair.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,830 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_staticnat.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,830 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_storage_pool.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,830 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_template.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,830 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_traffic_type.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,831 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_user.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,831 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vlan_ip_range.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,831 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vmsnapshot.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,831 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_volume.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,832 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpc.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,832 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpc_offering.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,832 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_connection.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,832 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_customer_gateway.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,833 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_gateway.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,833 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_zone.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,833 root INFO copying ansible_collections/ngine_io/cloudstack/plugins/modules/cs_zone_info.py -> build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:43,833 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/scripts 2023-04-28 05:57:43,833 root INFO creating build/lib/ansible_collections/ngine_io/cloudstack/scripts/inventory 2023-04-28 05:57:43,834 root INFO copying ansible_collections/ngine_io/cloudstack/scripts/inventory/cloudstack.ini -> build/lib/ansible_collections/ngine_io/cloudstack/scripts/inventory 2023-04-28 05:57:43,834 root INFO copying ansible_collections/ngine_io/cloudstack/scripts/inventory/cloudstack.py -> build/lib/ansible_collections/ngine_io/cloudstack/scripts/inventory 2023-04-28 05:57:43,834 root INFO creating build/lib/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:43,834 root INFO copying ansible_collections/ngine_io/exoscale/CHANGELOG.rst -> build/lib/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:43,834 root INFO copying ansible_collections/ngine_io/exoscale/CONTRIBUTING.md -> build/lib/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:43,835 root INFO copying ansible_collections/ngine_io/exoscale/FILES.json -> build/lib/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:43,835 root INFO copying ansible_collections/ngine_io/exoscale/MANIFEST.json -> build/lib/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:43,835 root INFO copying ansible_collections/ngine_io/exoscale/README.md -> build/lib/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:43,835 root INFO creating build/lib/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:43,835 root INFO copying ansible_collections/ngine_io/exoscale/changelogs/.gitignore -> build/lib/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:43,836 root INFO copying ansible_collections/ngine_io/exoscale/changelogs/changelog.yaml -> build/lib/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:43,836 root INFO copying ansible_collections/ngine_io/exoscale/changelogs/config.yaml -> build/lib/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:43,836 root INFO creating build/lib/ansible_collections/ngine_io/exoscale/changelogs/fragments 2023-04-28 05:57:43,836 root INFO copying ansible_collections/ngine_io/exoscale/changelogs/fragments/.keep -> build/lib/ansible_collections/ngine_io/exoscale/changelogs/fragments 2023-04-28 05:57:43,836 root INFO creating build/lib/ansible_collections/ngine_io/exoscale/meta 2023-04-28 05:57:43,836 root INFO copying ansible_collections/ngine_io/exoscale/meta/runtime.yml -> build/lib/ansible_collections/ngine_io/exoscale/meta 2023-04-28 05:57:43,837 root INFO creating build/lib/ansible_collections/ngine_io/exoscale/plugins 2023-04-28 05:57:43,837 root INFO creating build/lib/ansible_collections/ngine_io/exoscale/plugins/doc_fragments 2023-04-28 05:57:43,837 root INFO copying ansible_collections/ngine_io/exoscale/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/ngine_io/exoscale/plugins/doc_fragments 2023-04-28 05:57:43,837 root INFO copying ansible_collections/ngine_io/exoscale/plugins/doc_fragments/exoscale.py -> build/lib/ansible_collections/ngine_io/exoscale/plugins/doc_fragments 2023-04-28 05:57:43,837 root INFO creating build/lib/ansible_collections/ngine_io/exoscale/plugins/module_utils 2023-04-28 05:57:43,837 root INFO copying ansible_collections/ngine_io/exoscale/plugins/module_utils/exoscale.py -> build/lib/ansible_collections/ngine_io/exoscale/plugins/module_utils 2023-04-28 05:57:43,838 root INFO creating build/lib/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:43,838 root INFO copying ansible_collections/ngine_io/exoscale/plugins/modules/__init__.py -> build/lib/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:43,838 root INFO copying ansible_collections/ngine_io/exoscale/plugins/modules/exo_dns_domain.py -> build/lib/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:43,838 root INFO copying ansible_collections/ngine_io/exoscale/plugins/modules/exo_dns_record.py -> build/lib/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:43,838 root INFO creating build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,839 root INFO copying ansible_collections/ngine_io/vultr/CHANGELOG.rst -> build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,839 root INFO copying ansible_collections/ngine_io/vultr/CONTRIBUTING.md -> build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,839 root INFO copying ansible_collections/ngine_io/vultr/COPYING -> build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,839 root INFO copying ansible_collections/ngine_io/vultr/FILES.json -> build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,840 root INFO copying ansible_collections/ngine_io/vultr/MANIFEST.json -> build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,840 root INFO copying ansible_collections/ngine_io/vultr/README.md -> build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,840 root INFO copying ansible_collections/ngine_io/vultr/codecov.yml -> build/lib/ansible_collections/ngine_io/vultr 2023-04-28 05:57:43,840 root INFO creating build/lib/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:43,840 root INFO copying ansible_collections/ngine_io/vultr/changelogs/.gitignore -> build/lib/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:43,841 root INFO copying ansible_collections/ngine_io/vultr/changelogs/changelog.yaml -> build/lib/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:43,841 root INFO copying ansible_collections/ngine_io/vultr/changelogs/config.yaml -> build/lib/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:43,841 root INFO creating build/lib/ansible_collections/ngine_io/vultr/changelogs/fragments 2023-04-28 05:57:43,841 root INFO copying ansible_collections/ngine_io/vultr/changelogs/fragments/.keep -> build/lib/ansible_collections/ngine_io/vultr/changelogs/fragments 2023-04-28 05:57:43,841 root INFO creating build/lib/ansible_collections/ngine_io/vultr/meta 2023-04-28 05:57:43,841 root INFO copying ansible_collections/ngine_io/vultr/meta/runtime.yml -> build/lib/ansible_collections/ngine_io/vultr/meta 2023-04-28 05:57:43,842 root INFO creating build/lib/ansible_collections/ngine_io/vultr/plugins 2023-04-28 05:57:43,842 root INFO creating build/lib/ansible_collections/ngine_io/vultr/plugins/doc_fragments 2023-04-28 05:57:43,842 root INFO copying ansible_collections/ngine_io/vultr/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/doc_fragments 2023-04-28 05:57:43,842 root INFO copying ansible_collections/ngine_io/vultr/plugins/doc_fragments/vultr.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/doc_fragments 2023-04-28 05:57:43,842 root INFO creating build/lib/ansible_collections/ngine_io/vultr/plugins/inventory 2023-04-28 05:57:43,842 root INFO copying ansible_collections/ngine_io/vultr/plugins/inventory/__init__.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/inventory 2023-04-28 05:57:43,843 root INFO copying ansible_collections/ngine_io/vultr/plugins/inventory/vultr.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/inventory 2023-04-28 05:57:43,843 root INFO creating build/lib/ansible_collections/ngine_io/vultr/plugins/module_utils 2023-04-28 05:57:43,843 root INFO copying ansible_collections/ngine_io/vultr/plugins/module_utils/vultr.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/module_utils 2023-04-28 05:57:43,843 root INFO creating build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,843 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/__init__.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,844 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_account_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,844 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_block_storage.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,844 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_block_storage_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,844 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_domain.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,845 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_domain_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,845 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_record.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,845 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_group.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,845 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_group_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,845 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_rule.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,846 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_network.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,846 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_network_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,846 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_os_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,846 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_plan_baremetal_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,847 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_plan_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,847 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_region_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,847 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_server.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,847 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_server_baremetal.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,847 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_server_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,848 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_ssh_key.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,848 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_ssh_key_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,848 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_startup_script.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,848 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_startup_script_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,849 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_user.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,849 root INFO copying ansible_collections/ngine_io/vultr/plugins/modules/vultr_user_info.py -> build/lib/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:43,849 root INFO creating build/lib/ansible_collections/openstack 2023-04-28 05:57:43,849 root INFO creating build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,849 root INFO copying ansible_collections/openstack/cloud/CHANGELOG.rst -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,850 root INFO copying ansible_collections/openstack/cloud/CONTRIBUTING.rst -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,850 root INFO copying ansible_collections/openstack/cloud/COPYING -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,850 root INFO copying ansible_collections/openstack/cloud/FILES.json -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,850 root INFO copying ansible_collections/openstack/cloud/MANIFEST.json -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,850 root INFO copying ansible_collections/openstack/cloud/README.md -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,851 root INFO copying ansible_collections/openstack/cloud/bindep.txt -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,851 root INFO copying ansible_collections/openstack/cloud/requirements.txt -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,851 root INFO copying ansible_collections/openstack/cloud/setup.py -> build/lib/ansible_collections/openstack/cloud 2023-04-28 05:57:43,851 root INFO creating build/lib/ansible_collections/openstack/cloud/meta 2023-04-28 05:57:43,851 root INFO copying ansible_collections/openstack/cloud/meta/runtime.yml -> build/lib/ansible_collections/openstack/cloud/meta 2023-04-28 05:57:43,852 root INFO creating build/lib/ansible_collections/openstack/cloud/plugins 2023-04-28 05:57:43,852 root INFO creating build/lib/ansible_collections/openstack/cloud/plugins/doc_fragments 2023-04-28 05:57:43,852 root INFO copying ansible_collections/openstack/cloud/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/openstack/cloud/plugins/doc_fragments 2023-04-28 05:57:43,852 root INFO copying ansible_collections/openstack/cloud/plugins/doc_fragments/openstack.py -> build/lib/ansible_collections/openstack/cloud/plugins/doc_fragments 2023-04-28 05:57:43,852 root INFO creating build/lib/ansible_collections/openstack/cloud/plugins/inventory 2023-04-28 05:57:43,853 root INFO copying ansible_collections/openstack/cloud/plugins/inventory/__init__.py -> build/lib/ansible_collections/openstack/cloud/plugins/inventory 2023-04-28 05:57:43,853 root INFO copying ansible_collections/openstack/cloud/plugins/inventory/openstack.py -> build/lib/ansible_collections/openstack/cloud/plugins/inventory 2023-04-28 05:57:43,853 root INFO creating build/lib/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:43,853 root INFO copying ansible_collections/openstack/cloud/plugins/module_utils/__init__.py -> build/lib/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:43,853 root INFO copying ansible_collections/openstack/cloud/plugins/module_utils/ironic.py -> build/lib/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:43,854 root INFO copying ansible_collections/openstack/cloud/plugins/module_utils/openstack.py -> build/lib/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:43,854 root INFO creating build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,854 root INFO copying ansible_collections/openstack/cloud/plugins/modules/__init__.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,854 root INFO copying ansible_collections/openstack/cloud/plugins/modules/address_scope.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,854 root INFO copying ansible_collections/openstack/cloud/plugins/modules/auth.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,855 root INFO copying ansible_collections/openstack/cloud/plugins/modules/baremetal_inspect.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,855 root INFO copying ansible_collections/openstack/cloud/plugins/modules/baremetal_node.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,855 root INFO copying ansible_collections/openstack/cloud/plugins/modules/baremetal_node_action.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,855 root INFO copying ansible_collections/openstack/cloud/plugins/modules/baremetal_node_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,855 root INFO copying ansible_collections/openstack/cloud/plugins/modules/baremetal_port.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,856 root INFO copying ansible_collections/openstack/cloud/plugins/modules/baremetal_port_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,856 root INFO copying ansible_collections/openstack/cloud/plugins/modules/catalog_service.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,856 root INFO copying ansible_collections/openstack/cloud/plugins/modules/coe_cluster.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,856 root INFO copying ansible_collections/openstack/cloud/plugins/modules/coe_cluster_template.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,857 root INFO copying ansible_collections/openstack/cloud/plugins/modules/compute_flavor.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,857 root INFO copying ansible_collections/openstack/cloud/plugins/modules/compute_flavor_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,857 root INFO copying ansible_collections/openstack/cloud/plugins/modules/compute_service_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,857 root INFO copying ansible_collections/openstack/cloud/plugins/modules/config.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,857 root INFO copying ansible_collections/openstack/cloud/plugins/modules/container.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,858 root INFO copying ansible_collections/openstack/cloud/plugins/modules/dns_zone.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,858 root INFO copying ansible_collections/openstack/cloud/plugins/modules/dns_zone_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,858 root INFO copying ansible_collections/openstack/cloud/plugins/modules/endpoint.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,858 root INFO copying ansible_collections/openstack/cloud/plugins/modules/federation_idp.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,859 root INFO copying ansible_collections/openstack/cloud/plugins/modules/federation_idp_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,859 root INFO copying ansible_collections/openstack/cloud/plugins/modules/federation_mapping.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,859 root INFO copying ansible_collections/openstack/cloud/plugins/modules/federation_mapping_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,859 root INFO copying ansible_collections/openstack/cloud/plugins/modules/floating_ip.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,860 root INFO copying ansible_collections/openstack/cloud/plugins/modules/floating_ip_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,860 root INFO copying ansible_collections/openstack/cloud/plugins/modules/group_assignment.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,860 root INFO copying ansible_collections/openstack/cloud/plugins/modules/host_aggregate.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,860 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_domain.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,860 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_domain_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,861 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_group.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,861 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_group_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,861 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_role.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,861 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_role_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,862 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_user.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,862 root INFO copying ansible_collections/openstack/cloud/plugins/modules/identity_user_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,862 root INFO copying ansible_collections/openstack/cloud/plugins/modules/image.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,862 root INFO copying ansible_collections/openstack/cloud/plugins/modules/image_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,862 root INFO copying ansible_collections/openstack/cloud/plugins/modules/keypair.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,863 root INFO copying ansible_collections/openstack/cloud/plugins/modules/keypair_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,863 root INFO copying ansible_collections/openstack/cloud/plugins/modules/keystone_federation_protocol.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,863 root INFO copying ansible_collections/openstack/cloud/plugins/modules/keystone_federation_protocol_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,863 root INFO copying ansible_collections/openstack/cloud/plugins/modules/lb_health_monitor.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,864 root INFO copying ansible_collections/openstack/cloud/plugins/modules/lb_listener.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,864 root INFO copying ansible_collections/openstack/cloud/plugins/modules/lb_member.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,864 root INFO copying ansible_collections/openstack/cloud/plugins/modules/lb_pool.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,864 root INFO copying ansible_collections/openstack/cloud/plugins/modules/loadbalancer.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,865 root INFO copying ansible_collections/openstack/cloud/plugins/modules/network.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,865 root INFO copying ansible_collections/openstack/cloud/plugins/modules/networks_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,865 root INFO copying ansible_collections/openstack/cloud/plugins/modules/neutron_rbac_policies_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,865 root INFO copying ansible_collections/openstack/cloud/plugins/modules/neutron_rbac_policy.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,865 root INFO copying ansible_collections/openstack/cloud/plugins/modules/object.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,866 root INFO copying ansible_collections/openstack/cloud/plugins/modules/object_container.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,866 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_auth.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,866 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_client_config.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,866 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_coe_cluster.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,867 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_coe_cluster_template.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,867 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_flavor_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,867 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_floating_ip.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,867 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_group.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,867 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_group_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,868 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_image.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,868 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_image_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,868 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_ironic.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,868 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_ironic_inspect.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,869 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_ironic_node.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,869 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keypair.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,869 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_domain.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,869 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_domain_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,870 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_endpoint.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,870 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_federation_protocol.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,870 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_federation_protocol_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,870 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_identity_provider.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,870 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_identity_provider_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,871 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_mapping.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,871 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_mapping_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,871 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_role.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,871 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_keystone_service.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,872 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_listener.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,872 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_loadbalancer.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,872 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_member.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,872 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_network.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,873 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_networks_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,873 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_nova_flavor.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,873 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_nova_host_aggregate.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,873 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_object.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,873 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_pool.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,874 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_port.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,874 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_port_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,874 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_project.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,874 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_project_access.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,875 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_project_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,875 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_quota.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,875 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_recordset.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,875 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_router.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,876 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_routers_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,876 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_security_group.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,876 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_security_group_rule.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,876 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_server.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,877 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_server_action.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,877 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_server_group.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,877 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_server_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,877 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_server_metadata.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,877 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_server_volume.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,878 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_stack.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,878 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_subnet.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,878 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_subnets_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,878 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_user.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,879 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_user_group.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,879 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_user_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,879 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_user_role.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,880 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_volume.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,880 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_volume_snapshot.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,880 root INFO copying ansible_collections/openstack/cloud/plugins/modules/os_zone.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,880 root INFO copying ansible_collections/openstack/cloud/plugins/modules/port.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,881 root INFO copying ansible_collections/openstack/cloud/plugins/modules/port_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,881 root INFO copying ansible_collections/openstack/cloud/plugins/modules/project.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,881 root INFO copying ansible_collections/openstack/cloud/plugins/modules/project_access.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,881 root INFO copying ansible_collections/openstack/cloud/plugins/modules/project_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,881 root INFO copying ansible_collections/openstack/cloud/plugins/modules/quota.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,882 root INFO copying ansible_collections/openstack/cloud/plugins/modules/recordset.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,882 root INFO copying ansible_collections/openstack/cloud/plugins/modules/role_assignment.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,882 root INFO copying ansible_collections/openstack/cloud/plugins/modules/router.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,882 root INFO copying ansible_collections/openstack/cloud/plugins/modules/routers_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,883 root INFO copying ansible_collections/openstack/cloud/plugins/modules/security_group.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,883 root INFO copying ansible_collections/openstack/cloud/plugins/modules/security_group_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,883 root INFO copying ansible_collections/openstack/cloud/plugins/modules/security_group_rule.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,883 root INFO copying ansible_collections/openstack/cloud/plugins/modules/security_group_rule_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,884 root INFO copying ansible_collections/openstack/cloud/plugins/modules/server.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,884 root INFO copying ansible_collections/openstack/cloud/plugins/modules/server_action.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,884 root INFO copying ansible_collections/openstack/cloud/plugins/modules/server_group.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,884 root INFO copying ansible_collections/openstack/cloud/plugins/modules/server_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,885 root INFO copying ansible_collections/openstack/cloud/plugins/modules/server_metadata.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,885 root INFO copying ansible_collections/openstack/cloud/plugins/modules/server_volume.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,885 root INFO copying ansible_collections/openstack/cloud/plugins/modules/stack.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,885 root INFO copying ansible_collections/openstack/cloud/plugins/modules/stack_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,886 root INFO copying ansible_collections/openstack/cloud/plugins/modules/subnet.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,886 root INFO copying ansible_collections/openstack/cloud/plugins/modules/subnet_pool.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,886 root INFO copying ansible_collections/openstack/cloud/plugins/modules/subnets_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,886 root INFO copying ansible_collections/openstack/cloud/plugins/modules/volume.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,886 root INFO copying ansible_collections/openstack/cloud/plugins/modules/volume_backup.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,887 root INFO copying ansible_collections/openstack/cloud/plugins/modules/volume_backup_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,887 root INFO copying ansible_collections/openstack/cloud/plugins/modules/volume_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,887 root INFO copying ansible_collections/openstack/cloud/plugins/modules/volume_snapshot.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,887 root INFO copying ansible_collections/openstack/cloud/plugins/modules/volume_snapshot_info.py -> build/lib/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:43,888 root INFO creating build/lib/ansible_collections/openstack/cloud/scripts 2023-04-28 05:57:43,888 root INFO creating build/lib/ansible_collections/openstack/cloud/scripts/inventory 2023-04-28 05:57:43,888 root INFO copying ansible_collections/openstack/cloud/scripts/inventory/openstack.yml -> build/lib/ansible_collections/openstack/cloud/scripts/inventory 2023-04-28 05:57:43,888 root INFO copying ansible_collections/openstack/cloud/scripts/inventory/openstack_inventory.py -> build/lib/ansible_collections/openstack/cloud/scripts/inventory 2023-04-28 05:57:43,888 root INFO creating build/lib/ansible_collections/openvswitch 2023-04-28 05:57:43,888 root INFO creating build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,889 root INFO copying ansible_collections/openvswitch/openvswitch/CHANGELOG.rst -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,889 root INFO copying ansible_collections/openvswitch/openvswitch/FILES.json -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,889 root INFO copying ansible_collections/openvswitch/openvswitch/LICENSE -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,889 root INFO copying ansible_collections/openvswitch/openvswitch/MANIFEST.json -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,889 root INFO copying ansible_collections/openvswitch/openvswitch/README.md -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,890 root INFO copying ansible_collections/openvswitch/openvswitch/bindep.txt -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,890 root INFO copying ansible_collections/openvswitch/openvswitch/requirements.txt -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,890 root INFO copying ansible_collections/openvswitch/openvswitch/test-requirements.txt -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,890 root INFO copying ansible_collections/openvswitch/openvswitch/tox.ini -> build/lib/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:43,891 root INFO creating build/lib/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:43,891 root INFO copying ansible_collections/openvswitch/openvswitch/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:43,891 root INFO copying ansible_collections/openvswitch/openvswitch/changelogs/changelog.yaml -> build/lib/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:43,891 root INFO copying ansible_collections/openvswitch/openvswitch/changelogs/config.yaml -> build/lib/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:43,891 root INFO creating build/lib/ansible_collections/openvswitch/openvswitch/meta 2023-04-28 05:57:43,891 root INFO copying ansible_collections/openvswitch/openvswitch/meta/runtime.yml -> build/lib/ansible_collections/openvswitch/openvswitch/meta 2023-04-28 05:57:43,892 root INFO creating build/lib/ansible_collections/openvswitch/openvswitch/plugins 2023-04-28 05:57:43,892 root INFO creating build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:43,892 root INFO copying ansible_collections/openvswitch/openvswitch/plugins/modules/__init__.py -> build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:43,892 root INFO copying ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_bond.py -> build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:43,892 root INFO copying ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_bridge.py -> build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:43,893 root INFO copying ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_db.py -> build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:43,893 root INFO copying ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_port.py -> build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:43,893 root INFO creating build/lib/ansible_collections/ovirt 2023-04-28 05:57:43,893 root INFO creating build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,893 root INFO copying ansible_collections/ovirt/ovirt/CHANGELOG.rst -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,894 root INFO copying ansible_collections/ovirt/ovirt/FILES.json -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,894 root INFO copying ansible_collections/ovirt/ovirt/MANIFEST.json -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,894 root INFO copying ansible_collections/ovirt/ovirt/README-developers.md -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,894 root INFO copying ansible_collections/ovirt/ovirt/README.md -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,895 root INFO copying ansible_collections/ovirt/ovirt/README.md.in -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,895 root INFO copying ansible_collections/ovirt/ovirt/bindep.txt -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,895 root INFO copying ansible_collections/ovirt/ovirt/build.sh -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,895 root INFO copying ansible_collections/ovirt/ovirt/ovirt-ansible-collection-2.4.1.tar.gz -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,896 root INFO copying ansible_collections/ovirt/ovirt/ovirt-ansible-collection.spec -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,896 root INFO copying ansible_collections/ovirt/ovirt/ovirt-ansible-collection.spec.in -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,896 root INFO copying ansible_collections/ovirt/ovirt/requirements.txt -> build/lib/ansible_collections/ovirt/ovirt 2023-04-28 05:57:43,897 root INFO creating build/lib/ansible_collections/ovirt/ovirt/automation 2023-04-28 05:57:43,897 root INFO copying ansible_collections/ovirt/ovirt/automation/README.md -> build/lib/ansible_collections/ovirt/ovirt/automation 2023-04-28 05:57:43,897 root INFO copying ansible_collections/ovirt/ovirt/automation/build.sh -> build/lib/ansible_collections/ovirt/ovirt/automation 2023-04-28 05:57:43,897 root INFO creating build/lib/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:43,897 root INFO copying ansible_collections/ovirt/ovirt/changelogs/README.md -> build/lib/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:43,898 root INFO copying ansible_collections/ovirt/ovirt/changelogs/changelog.yaml -> build/lib/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:43,898 root INFO copying ansible_collections/ovirt/ovirt/changelogs/config.yaml -> build/lib/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:43,898 root INFO creating build/lib/ansible_collections/ovirt/ovirt/changelogs/fragments 2023-04-28 05:57:43,898 root INFO copying ansible_collections/ovirt/ovirt/changelogs/fragments/.placeholder -> build/lib/ansible_collections/ovirt/ovirt/changelogs/fragments 2023-04-28 05:57:43,898 root INFO creating build/lib/ansible_collections/ovirt/ovirt/examples 2023-04-28 05:57:43,899 root INFO copying ansible_collections/ovirt/ovirt/examples/ovirt_ansible_collections.yml -> build/lib/ansible_collections/ovirt/ovirt/examples 2023-04-28 05:57:43,899 root INFO creating build/lib/ansible_collections/ovirt/ovirt/examples/filters 2023-04-28 05:57:43,899 root INFO copying ansible_collections/ovirt/ovirt/examples/filters/ovirtdiff.yml -> build/lib/ansible_collections/ovirt/ovirt/examples/filters 2023-04-28 05:57:43,899 root INFO copying ansible_collections/ovirt/ovirt/examples/filters/vmips.yml -> build/lib/ansible_collections/ovirt/ovirt/examples/filters 2023-04-28 05:57:43,899 root INFO creating build/lib/ansible_collections/ovirt/ovirt/licenses 2023-04-28 05:57:43,899 root INFO copying ansible_collections/ovirt/ovirt/licenses/Apache-license.txt -> build/lib/ansible_collections/ovirt/ovirt/licenses 2023-04-28 05:57:43,900 root INFO copying ansible_collections/ovirt/ovirt/licenses/GPL-license.txt -> build/lib/ansible_collections/ovirt/ovirt/licenses 2023-04-28 05:57:43,900 root INFO creating build/lib/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:43,900 root INFO copying ansible_collections/ovirt/ovirt/meta/execution-environment.yml -> build/lib/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:43,900 root INFO copying ansible_collections/ovirt/ovirt/meta/requirements.yml -> build/lib/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:43,901 root INFO copying ansible_collections/ovirt/ovirt/meta/runtime.yml -> build/lib/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:43,901 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins 2023-04-28 05:57:43,901 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins/callback 2023-04-28 05:57:43,901 root INFO copying ansible_collections/ovirt/ovirt/plugins/callback/stdout.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/callback 2023-04-28 05:57:43,901 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins/doc_fragments 2023-04-28 05:57:43,901 root INFO copying ansible_collections/ovirt/ovirt/plugins/doc_fragments/ovirt.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/doc_fragments 2023-04-28 05:57:43,902 root INFO copying ansible_collections/ovirt/ovirt/plugins/doc_fragments/ovirt_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/doc_fragments 2023-04-28 05:57:43,902 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,902 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/convert_to_bytes.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,902 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/convert_to_bytes.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,902 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/filtervalue.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,903 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/get_network_xml_to_dict.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,903 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/get_ovf_disk_size.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,903 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/get_ovf_disk_size.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,903 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/json_query.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,903 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/json_query.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,904 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtdiff.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,904 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmip.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,904 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmip.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,904 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmips.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,905 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipsv4.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,905 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipsv6.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,905 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipv4.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,905 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipv6.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,905 root INFO copying ansible_collections/ovirt/ovirt/plugins/filter/removesensitivevmdata.yml -> build/lib/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:43,906 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins/inventory 2023-04-28 05:57:43,906 root INFO copying ansible_collections/ovirt/ovirt/plugins/inventory/ovirt.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/inventory 2023-04-28 05:57:43,906 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:43,906 root INFO copying ansible_collections/ovirt/ovirt/plugins/module_utils/__init__.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:43,906 root INFO copying ansible_collections/ovirt/ovirt/plugins/module_utils/cloud.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:43,907 root INFO copying ansible_collections/ovirt/ovirt/plugins/module_utils/ovirt.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:43,907 root INFO copying ansible_collections/ovirt/ovirt/plugins/module_utils/version.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:43,907 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,907 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/__init__.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,907 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_group.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,908 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_label.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,908 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_label_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,908 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_api_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,908 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,909 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_cluster.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,909 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_cluster_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,909 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_datacenter.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,909 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_datacenter_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,909 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,910 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,910 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk_profile.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,910 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_event.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,910 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_event_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,911 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_external_provider.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,911 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_external_provider_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,911 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_group.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,911 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_group_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,912 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,912 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,912 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_network.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,912 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_pm.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,913 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_storage_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,913 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_instance_type.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,913 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_job.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,913 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_mac_pool.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,913 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_network.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,914 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_network_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,914 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_nic.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,914 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_nic_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,914 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_permission.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,915 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_permission_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,915 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_qos.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,915 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_quota.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,915 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_quota_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,915 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_role.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,916 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_scheduling_policy_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,916 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_snapshot.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,916 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_snapshot_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,916 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_connection.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,917 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,917 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,917 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_template_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,917 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_vm_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,918 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_system_option_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,918 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_tag.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,918 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_tag_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,918 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_template.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,919 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_template_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,919 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_user.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,919 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_user_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,919 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,920 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,920 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm_os_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,920 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vmpool.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,920 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vmpool_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,921 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vnic_profile.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,921 root INFO copying ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vnic_profile_info.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:43,921 root INFO creating build/lib/ansible_collections/ovirt/ovirt/plugins/test 2023-04-28 05:57:43,921 root INFO copying ansible_collections/ovirt/ovirt/plugins/test/ovirt_proxied_check.py -> build/lib/ansible_collections/ovirt/ovirt/plugins/test 2023-04-28 05:57:43,921 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles 2023-04-28 05:57:43,921 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade 2023-04-28 05:57:43,922 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade 2023-04-28 05:57:43,922 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/defaults 2023-04-28 05:57:43,922 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/defaults 2023-04-28 05:57:43,922 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples 2023-04-28 05:57:43,922 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples/cluster_upgrade.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples 2023-04-28 05:57:43,923 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples 2023-04-28 05:57:43,923 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:43,923 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/cluster_policy.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:43,923 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/log_progress.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:43,923 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:43,924 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/pinned_vms.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:43,924 root INFO copying ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/upgrade.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:43,924 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery 2023-04-28 05:57:43,924 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery 2023-04-28 05:57:43,924 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/defaults 2023-04-28 05:57:43,924 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/defaults 2023-04-28 05:57:43,925 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:43,925 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/disaster_recovery_vars.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:43,925 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/dr_ovirt_setup.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:43,925 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/dr_play.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:43,925 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/ovirt_passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:43,926 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,926 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/bcolors.py -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,926 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/dr.conf -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,926 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/fail_back.py -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,926 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/fail_over.py -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,927 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_mapping.py -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,927 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_vars.py -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,927 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_vars_test.py -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,927 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/ovirt-dr -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,928 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/validator.py -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,928 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/vault_secret.sh -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:43,928 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:43,928 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean_engine.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:43,929 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/generate_mapping.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:43,929 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:43,929 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover_engine.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:43,929 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/run_unregistered_entities.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:43,929 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/unregister_entities.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:43,930 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,930 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_disks.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,930 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,930 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_domain_process.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,930 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_invalid_filtered_master_domains.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,931 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_valid_filtered_master_domains.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,931 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_vms.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,931 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/shutdown_vm.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,931 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/shutdown_vms.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,932 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/update_ovf_store.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:43,932 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,932 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,932 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_fcp_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,932 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_glusterfs_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,933 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_iscsi_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,933 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_nfs_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,933 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_posixfs_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,933 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/print_info.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,933 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_template.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,934 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_templates.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,934 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_vm.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,934 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_vms.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,934 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/report_log_template.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,935 root INFO copying ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/run_vms.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:43,935 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup 2023-04-28 05:57:43,935 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup 2023-04-28 05:57:43,935 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/defaults 2023-04-28 05:57:43,935 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/defaults 2023-04-28 05:57:43,935 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:43,936 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/examples/engine-deploy.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:43,936 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/examples/engine-upgrade.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:43,936 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:43,936 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:43,936 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/engine_setup.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:43,937 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:43,937 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:43,937 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/pre_install_checks.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:43,937 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/restore_engine_from_file.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:43,937 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,938 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.1_basic.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,938 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.1_upgrade.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,938 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.2_basic.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,938 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.2_upgrade.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,938 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.3_basic.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,939 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.3_upgrade.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,939 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.4_basic.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,939 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.4_upgrade.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,939 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.5_basic.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,940 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.5_upgrade.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,940 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/templates/basic_answerfile.txt.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:43,940 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,940 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/containers-deploy.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,940 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/engine-deploy.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,941 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/engine-upgrade.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,941 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/inventory -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,941 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,941 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/requirements.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,941 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-4.2.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,942 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-master.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,942 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-upgrade-4.2-to-master.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:43,942 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/vars 2023-04-28 05:57:43,942 root INFO copying ansible_collections/ovirt/ovirt/roles/engine_setup/vars/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/vars 2023-04-28 05:57:43,942 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup 2023-04-28 05:57:43,943 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup 2023-04-28 05:57:43,943 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults 2023-04-28 05:57:43,943 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults 2023-04-28 05:57:43,943 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:43,943 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/hosted_engine_deploy_localhost.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:43,944 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/hosted_engine_deploy_remotehost.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:43,944 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/iscsi_deployment_remote.json -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:43,944 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/nfs_deployment.json -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:43,944 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:43,944 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/required_networks_fix.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:43,945 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/files 2023-04-28 05:57:43,945 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/files/35-allow-ansible-for-vdsm.rules -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/files 2023-04-28 05:57:43,945 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks 2023-04-28 05:57:43,945 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_add_host 2023-04-28 05:57:43,945 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_add_host/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_add_host 2023-04-28 05:57:43,945 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup 2023-04-28 05:57:43,946 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup 2023-04-28 05:57:43,946 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup/add_host_storage_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup 2023-04-28 05:57:43,946 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_after_engine_setup 2023-04-28 05:57:43,946 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_after_engine_setup/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_after_engine_setup 2023-04-28 05:57:43,946 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_before_engine_setup 2023-04-28 05:57:43,947 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_before_engine_setup/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_before_engine_setup 2023-04-28 05:57:43,947 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,947 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/add_engine_as_ansible_host.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,947 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/alter_libvirt_default_net_configuration.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,947 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/apply_openscap_profile.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,948 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_revoke.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,948 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_sso.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,948 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_cloud_init_config.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,948 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_local_storage_pools.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,948 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_localvm_dir.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,949 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_storage_domain.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,949 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fc_getdevices.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,949 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_engine_logs.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,949 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_host_ip.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,950 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/filter_team_devices.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,950 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/filter_unsupported_vlan_devices.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,950 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/final_clean.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,950 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/full_execution.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,950 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/get_appliance_dist.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,951 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/get_local_vm_disk_path.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,951 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/initial_clean.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,951 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/install_appliance.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,951 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/install_packages.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,951 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/ipv_switch.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,952 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/iscsi_discover.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,952 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/iscsi_getdevices.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,952 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,952 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/partial_execution.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,953 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pause_execution.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,953 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/restore_backup.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,953 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/restore_host_redeploy.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,953 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/search_available_network_subnet.yaml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,953 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_machine.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,954 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_ip_prefix.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,954 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_vlan_bond_mode.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,954 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_vlan_name.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:43,954 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:43,954 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:43,955 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/02_create_local_vm.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:43,955 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/03_engine_initial_tasks.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:43,955 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/04_engine_final_tasks.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:43,955 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:43,956 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:43,956 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:43,956 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/02_engine_vm_configuration.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:43,956 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/03_hosted_engine_final_tasks.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:43,957 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,957 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,957 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/002_validate_hostname_tasks.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,957 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/define_variables.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,957 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_data_center_name.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,958 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_firewalld.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,958 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_gateway.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,958 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_mac_address.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,958 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_memory_size.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,958 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_network_test.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,959 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_services_status.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,959 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_vcpus_count.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:43,959 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,959 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/broker.conf.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,959 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/fhanswers.conf.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,960 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/hosted-engine.conf.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,960 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-dhcp.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,960 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-static-ipv6.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,960 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-static.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,961 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/meta-data.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,961 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/network-config-dhcp.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,961 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/network-config.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,961 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/user-data.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,961 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/version.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,962 root INFO copying ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/vm.conf.j2 -> build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:43,962 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/image_template 2023-04-28 05:57:43,962 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template 2023-04-28 05:57:43,962 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/image_template/defaults 2023-04-28 05:57:43,962 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/defaults 2023-04-28 05:57:43,963 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/image_template/examples 2023-04-28 05:57:43,963 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/examples/ovirt_image_template.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/examples 2023-04-28 05:57:43,963 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/examples 2023-04-28 05:57:43,963 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:43,963 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/tasks/empty.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:43,964 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/tasks/glance_image.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:43,964 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:43,964 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/tasks/qcow2_image.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:43,964 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/image_template/vars 2023-04-28 05:57:43,964 root INFO copying ansible_collections/ovirt/ovirt/roles/image_template/vars/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/image_template/vars 2023-04-28 05:57:43,965 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra 2023-04-28 05:57:43,965 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra 2023-04-28 05:57:43,965 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/defaults 2023-04-28 05:57:43,965 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/defaults 2023-04-28 05:57:43,965 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples 2023-04-28 05:57:43,965 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/examples/ovirt_infra.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples 2023-04-28 05:57:43,966 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/examples/ovirt_infra_destroy.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples 2023-04-28 05:57:43,966 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples/vars 2023-04-28 05:57:43,966 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/examples/vars/ovirt_infra_vars.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples/vars 2023-04-28 05:57:43,966 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/examples/vars/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples/vars 2023-04-28 05:57:43,966 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles 2023-04-28 05:57:43,967 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc 2023-04-28 05:57:43,967 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc 2023-04-28 05:57:43,967 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/defaults 2023-04-28 05:57:43,967 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/defaults 2023-04-28 05:57:43,967 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/tasks 2023-04-28 05:57:43,967 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/tasks 2023-04-28 05:57:43,968 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters 2023-04-28 05:57:43,968 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters 2023-04-28 05:57:43,968 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/tasks 2023-04-28 05:57:43,968 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/tasks 2023-04-28 05:57:43,968 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/vars 2023-04-28 05:57:43,968 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/vars/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/vars 2023-04-28 05:57:43,969 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup 2023-04-28 05:57:43,969 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup 2023-04-28 05:57:43,969 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/defaults 2023-04-28 05:57:43,969 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/defaults 2023-04-28 05:57:43,969 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,970 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/cluster_and_hosts.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,970 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/datacenter.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,970 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/disks.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,970 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,970 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/storages_last.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,971 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/storages_pre.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,971 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/templates.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,971 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/vm_pools.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,971 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/vms.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:43,971 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters 2023-04-28 05:57:43,972 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters 2023-04-28 05:57:43,972 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/defaults 2023-04-28 05:57:43,972 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/defaults 2023-04-28 05:57:43,972 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/tasks 2023-04-28 05:57:43,972 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/tasks 2023-04-28 05:57:43,973 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers 2023-04-28 05:57:43,973 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers 2023-04-28 05:57:43,973 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/tasks 2023-04-28 05:57:43,973 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/tasks 2023-04-28 05:57:43,973 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts 2023-04-28 05:57:43,973 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts 2023-04-28 05:57:43,974 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/defaults 2023-04-28 05:57:43,974 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/defaults 2023-04-28 05:57:43,974 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/tasks 2023-04-28 05:57:43,974 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/tasks 2023-04-28 05:57:43,974 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools 2023-04-28 05:57:43,975 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools 2023-04-28 05:57:43,975 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/tasks 2023-04-28 05:57:43,975 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/tasks 2023-04-28 05:57:43,975 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/networks 2023-04-28 05:57:43,975 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/networks/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/networks 2023-04-28 05:57:43,975 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/networks/tasks 2023-04-28 05:57:43,976 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/networks/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/networks/tasks 2023-04-28 05:57:43,976 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions 2023-04-28 05:57:43,976 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions 2023-04-28 05:57:43,976 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/tasks 2023-04-28 05:57:43,976 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/tasks 2023-04-28 05:57:43,976 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/storages 2023-04-28 05:57:43,977 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/storages/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/storages 2023-04-28 05:57:43,977 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/storages/tasks 2023-04-28 05:57:43,977 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/roles/storages/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/storages/tasks 2023-04-28 05:57:43,977 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:43,977 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/tasks/create_infra.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:43,978 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:43,978 root INFO copying ansible_collections/ovirt/ovirt/roles/infra/tasks/remove_infra.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:43,978 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun 2023-04-28 05:57:43,978 root INFO copying ansible_collections/ovirt/ovirt/roles/remove_stale_lun/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun 2023-04-28 05:57:43,978 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/defaults 2023-04-28 05:57:43,978 root INFO copying ansible_collections/ovirt/ovirt/roles/remove_stale_lun/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/defaults 2023-04-28 05:57:43,979 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples 2023-04-28 05:57:43,979 root INFO copying ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples 2023-04-28 05:57:43,979 root INFO copying ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples/remove_stale_lun.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples 2023-04-28 05:57:43,979 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:43,979 root INFO copying ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/fetch_hosts.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:43,980 root INFO copying ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:43,980 root INFO copying ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/remove_mpath_device.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:43,980 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/repositories 2023-04-28 05:57:43,980 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories 2023-04-28 05:57:43,980 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/repositories/defaults 2023-04-28 05:57:43,981 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/defaults 2023-04-28 05:57:43,981 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:43,981 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/examples/ovirt_repositories_release_rpm.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:43,981 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/examples/ovirt_repositories_subscription_manager.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:43,981 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:43,982 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,982 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/tasks/backup-repos.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,982 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/tasks/install-satellite-ca.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,982 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,982 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/tasks/rh-subscription.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,983 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/tasks/rpm.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,983 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/tasks/satellite-subscription.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,983 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/tasks/search-pool-id.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:43,983 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,983 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/default.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,984 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.1.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,984 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.2.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,984 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.3.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,984 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.4.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,984 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_eus_4.4.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,985 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.1.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,985 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.2.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,985 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.3.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,985 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.4.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,986 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/host_eus_4.4.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,986 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/host_ppc_4.4.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,986 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/host_ppc_eus_4.4.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,986 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.1.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,986 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.2.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,987 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.3.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,987 root INFO copying ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.4.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:43,987 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env 2023-04-28 05:57:43,987 root INFO copying ansible_collections/ovirt/ovirt/roles/shutdown_env/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env 2023-04-28 05:57:43,988 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/defaults 2023-04-28 05:57:43,988 root INFO copying ansible_collections/ovirt/ovirt/roles/shutdown_env/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/defaults 2023-04-28 05:57:43,988 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples 2023-04-28 05:57:43,988 root INFO copying ansible_collections/ovirt/ovirt/roles/shutdown_env/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples 2023-04-28 05:57:43,988 root INFO copying ansible_collections/ovirt/ovirt/roles/shutdown_env/examples/shutdown_env.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples 2023-04-28 05:57:43,988 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/tasks 2023-04-28 05:57:43,989 root INFO copying ansible_collections/ovirt/ovirt/roles/shutdown_env/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/tasks 2023-04-28 05:57:43,989 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra 2023-04-28 05:57:43,989 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/README.md -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra 2023-04-28 05:57:43,989 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/defaults 2023-04-28 05:57:43,989 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/defaults/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/defaults 2023-04-28 05:57:43,990 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:43,990 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/examples/ovirt_vm_infra.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:43,990 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/examples/ovirt_vm_infra_inv.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:43,990 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/examples/passwords.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:43,990 root INFO creating build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,991 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/affinity_groups.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,991 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/affinity_labels.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,991 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/create_inventory.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,991 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/create_vms.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,991 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/main.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,992 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/manage_state.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,992 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/vm_state_absent.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,992 root INFO copying ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/vm_state_present.yml -> build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:43,992 root INFO creating build/lib/ansible_collections/purestorage 2023-04-28 05:57:43,992 root INFO creating build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,993 root INFO copying ansible_collections/purestorage/flasharray/CHANGELOG.rst -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,993 root INFO copying ansible_collections/purestorage/flasharray/COPYING.GPLv3 -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,993 root INFO copying ansible_collections/purestorage/flasharray/FILES.json -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,993 root INFO copying ansible_collections/purestorage/flasharray/LICENSE -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,994 root INFO copying ansible_collections/purestorage/flasharray/MANIFEST.json -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,994 root INFO copying ansible_collections/purestorage/flasharray/README.md -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,994 root INFO copying ansible_collections/purestorage/flasharray/README.rst -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,994 root INFO copying ansible_collections/purestorage/flasharray/requirements.txt -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,995 root INFO copying ansible_collections/purestorage/flasharray/settings.json -> build/lib/ansible_collections/purestorage/flasharray 2023-04-28 05:57:43,995 root INFO creating build/lib/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:43,995 root INFO copying ansible_collections/purestorage/flasharray/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:43,995 root INFO copying ansible_collections/purestorage/flasharray/changelogs/210_add_rename_hgroup.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:43,995 root INFO copying ansible_collections/purestorage/flasharray/changelogs/211_fix_clearing_host_inititators.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:43,996 root INFO copying ansible_collections/purestorage/flasharray/changelogs/changelog.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:43,996 root INFO copying ansible_collections/purestorage/flasharray/changelogs/config.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:43,996 root INFO creating build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,996 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/107_host_case_clarity.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,996 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/108_fix_eradicate_idempotency.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,997 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/109_fa_files_support_purefa_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,997 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/110_add_apiclient_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,997 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/111_add_filesystem_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,997 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/112_add_directory_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,997 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/113_add_exports_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,998 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/115_add_gcp_offload.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,998 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/116_add_policies.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,998 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/118_rename_host.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,998 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/121_add_multi_volume_creation.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,999 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/122_add_multi_host_creation.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,999 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/123_add_multi_vgroup_creation.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,999 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/124_sdk_handshake.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,999 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/125_dns_idempotency.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:43,999 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/126_fix_volume_move.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,000 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/130_info_ds_update.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,000 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/131_add_v6_ds_update.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,000 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/132_fc_replication.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,000 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/133_purefa_info_v6_replication.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,000 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/134_ac_pg_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,001 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/135_no_cbs_ntp.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,001 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/136_add_vol_get_send_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,001 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/137_pgsnap_regex.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,001 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/139_pgsnap_ac_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,002 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/140_pod_case.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,002 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/141_add_remote_snapshot.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,002 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/145_fix_missing_move_variable.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,002 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/149_volumes_demoted_pods_fix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,002 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/152_fix_user.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,003 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/153_syslog_update.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,003 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/156_snap_suffix_fix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,003 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/160_rename_pg.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,003 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/161_offline_offload_fix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,004 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/162_pgsnap_info_fix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,004 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/163_add_maintenance_windows.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,004 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/168_dsrole_fix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,005 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/169_add_certs.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,005 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/170_pgsnap_stretch_pod_fail.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,005 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/174_null_gateway.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,005 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/175_check_pgname.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,005 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/176_fix_promote_api_issue.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,006 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/182_allow_pgroup_with_create.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,006 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/187_add_ad.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,006 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/188_add_dirsnap.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,006 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/193_duplicate_initiators.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,007 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/194_vg_qos.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,007 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/196_fix_activedr_api_version.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,007 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/199_add_fc_port_enable.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,007 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/200_add_DAR_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,007 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/201_increase_krb_count.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,008 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/202_add_sso.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,008 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/203_add_eradication_timer.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,008 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/205_policy_protocl.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,008 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/206_add_naa_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,009 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/207_fix_disable_for_remote_assist.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,009 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/208_add_directory_quota_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,009 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/213_add_kmip.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,009 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/214_join_ou.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,009 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/220_capacity_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,010 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/224_add_nguid_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,010 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/226_deprecate_protocol.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,010 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/227_missing_regex.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,010 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/228_nguid_to_volfact.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,010 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/229_snapsuffix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,011 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/230_add_pg_deleted_vols.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,011 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/231_syslog_settings.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,011 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/234_add_vol_info_on_nochange.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,011 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/235_eula.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,012 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/237_fix_network.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,012 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/238_add_dirsnap_rename.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,012 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/239_safe_mode.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,012 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/242_multi_offload.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,012 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/243_sso_to_admin.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,013 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/246_python_precedence.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,013 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/247_fix_smb_policy_rules.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,013 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/249_allow_cert_reimport.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,013 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/252_add_saml2.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,014 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/254_sam2_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,014 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/257_fqcn.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,014 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/259_fix_gateway_check.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,014 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/261_fix_bad_arrays.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,014 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/265_fix_multiple_nfs_rules.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,015 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/268_fix_quotas_issues.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,015 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/270_add_priority_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,015 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/271_vgroup_prio.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,015 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/272_volume_prio.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,016 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/277_add_fs_repl.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,016 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/278_pgsnap_info.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,016 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/279_pg_safemode.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,016 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/280_multihost_no_suffix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,016 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/284_volfact_for_recover.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,017 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/288_zero_params.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,017 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/292_fix_ds_password.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,017 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/293_add_chassis_inventory.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,017 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/294_dns_ntp_idempotency_absent.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,017 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/294_user_map_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,018 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/296_ad_tls.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,018 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/299_fix_pgsched_zero_support.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,018 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/302_fix_pg_recover_and_target_update.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,018 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/304_host_vlan.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,019 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/305_fix_target_dempo.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,019 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/307_multiple_dns.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,019 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/308_add_vm.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,019 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/310_hg_vol_idempotency.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,019 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/312_pg_alias.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,020 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/315_spf_details.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,020 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/317_add_all_squash.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,020 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/318_vol_defaults.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,020 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/319_lockout.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,021 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/320_completed_snaps.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,021 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/328_policy_fix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,021 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/330_extend_vlan.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,021 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/334_fix_vg_qos.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,021 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/336_add_servicelist.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,022 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/337_fix_non-prod_versions.yml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,022 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/341_pg_400s.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,022 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/342_add_vol_promotion.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,022 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/343_fix_ds.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,023 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/344_fix_smtp.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,023 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/345_user_map.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,023 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/347_dns_fix.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,023 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/348_add_default_prot.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,024 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/349_add_alerts.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,024 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/351_fix_rest_check.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,024 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/354_fix_promotion.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,024 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/360_fix_volume.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,024 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/363_overwrite_combo.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,025 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/364_fc_targets.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,025 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/365_pod_pgsched.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,025 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/366_add_nvme_types.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,025 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/367_fix_vg.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,026 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/369_fix_host.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,026 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/370_add_user_role.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,026 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/374_offload_pgsnap.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,026 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/375_fix_remote_hosts.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,026 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/379_cap_compat.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,027 root INFO copying ansible_collections/purestorage/flasharray/changelogs/fragments/v1.4.0_summary.yaml -> build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:44,027 root INFO creating build/lib/ansible_collections/purestorage/flasharray/meta 2023-04-28 05:57:44,027 root INFO copying ansible_collections/purestorage/flasharray/meta/execution-environment.yml -> build/lib/ansible_collections/purestorage/flasharray/meta 2023-04-28 05:57:44,027 root INFO copying ansible_collections/purestorage/flasharray/meta/runtime.yml -> build/lib/ansible_collections/purestorage/flasharray/meta 2023-04-28 05:57:44,027 root INFO creating build/lib/ansible_collections/purestorage/flasharray/playbooks 2023-04-28 05:57:44,028 root INFO copying ansible_collections/purestorage/flasharray/playbooks/.keep -> build/lib/ansible_collections/purestorage/flasharray/playbooks 2023-04-28 05:57:44,028 root INFO creating build/lib/ansible_collections/purestorage/flasharray/playbooks/files 2023-04-28 05:57:44,028 root INFO copying ansible_collections/purestorage/flasharray/playbooks/files/.keep -> build/lib/ansible_collections/purestorage/flasharray/playbooks/files 2023-04-28 05:57:44,028 root INFO creating build/lib/ansible_collections/purestorage/flasharray/playbooks/roles 2023-04-28 05:57:44,028 root INFO copying ansible_collections/purestorage/flasharray/playbooks/roles/.keep -> build/lib/ansible_collections/purestorage/flasharray/playbooks/roles 2023-04-28 05:57:44,028 root INFO creating build/lib/ansible_collections/purestorage/flasharray/playbooks/tasks 2023-04-28 05:57:44,029 root INFO copying ansible_collections/purestorage/flasharray/playbooks/tasks/.keep -> build/lib/ansible_collections/purestorage/flasharray/playbooks/tasks 2023-04-28 05:57:44,029 root INFO creating build/lib/ansible_collections/purestorage/flasharray/playbooks/templates 2023-04-28 05:57:44,029 root INFO copying ansible_collections/purestorage/flasharray/playbooks/templates/.keep -> build/lib/ansible_collections/purestorage/flasharray/playbooks/templates 2023-04-28 05:57:44,029 root INFO creating build/lib/ansible_collections/purestorage/flasharray/playbooks/vars 2023-04-28 05:57:44,029 root INFO copying ansible_collections/purestorage/flasharray/playbooks/vars/.keep -> build/lib/ansible_collections/purestorage/flasharray/playbooks/vars 2023-04-28 05:57:44,029 root INFO creating build/lib/ansible_collections/purestorage/flasharray/plugins 2023-04-28 05:57:44,030 root INFO creating build/lib/ansible_collections/purestorage/flasharray/plugins/doc_fragments 2023-04-28 05:57:44,030 root INFO copying ansible_collections/purestorage/flasharray/plugins/doc_fragments/purestorage.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/doc_fragments 2023-04-28 05:57:44,030 root INFO creating build/lib/ansible_collections/purestorage/flasharray/plugins/module_utils 2023-04-28 05:57:44,030 root INFO copying ansible_collections/purestorage/flasharray/plugins/module_utils/purefa.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/module_utils 2023-04-28 05:57:44,030 root INFO creating build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,030 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_ad.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,031 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_admin.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,031 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_alert.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,031 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_apiclient.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,031 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_arrayname.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,032 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_banner.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,032 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_certs.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,032 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_connect.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,032 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_console.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,032 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_default_protection.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,033 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_directory.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,033 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_dirsnap.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,033 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_dns.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,033 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_ds.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,034 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_dsrole.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,034 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_endpoint.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,034 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_eradication.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,034 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_eula.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,035 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_export.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,035 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_fs.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,035 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_hg.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,035 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_host.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,035 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_info.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,036 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_inventory.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,036 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_kmip.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,036 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_maintenance.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,037 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_messages.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,037 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_network.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,037 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_ntp.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,037 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_offload.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,037 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_pg.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,038 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_pgsched.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,038 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_pgsnap.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,038 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_phonehome.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,038 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_pod.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,039 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_pod_replica.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,039 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_policy.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,039 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_proxy.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,039 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_ra.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,040 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_saml.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,040 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_smis.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,040 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_smtp.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,040 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_snap.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,041 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_snmp.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,041 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_snmp_agent.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,041 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_sso.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,041 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_subnet.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,042 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_syslog.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,042 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_syslog_settings.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,042 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_timeout.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,042 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_user.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,042 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_vg.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,043 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_vlan.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,043 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_vnc.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,043 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_volume.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,043 root INFO copying ansible_collections/purestorage/flasharray/plugins/modules/purefa_volume_tags.py -> build/lib/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:44,044 root INFO creating build/lib/ansible_collections/purestorage/flasharray/roles 2023-04-28 05:57:44,044 root INFO copying ansible_collections/purestorage/flasharray/roles/.keep -> build/lib/ansible_collections/purestorage/flasharray/roles 2023-04-28 05:57:44,044 root INFO creating build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,044 root INFO copying ansible_collections/purestorage/flashblade/CHANGELOG.rst -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,044 root INFO copying ansible_collections/purestorage/flashblade/COPYING.GPLv3 -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,045 root INFO copying ansible_collections/purestorage/flashblade/FILES.json -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,045 root INFO copying ansible_collections/purestorage/flashblade/LICENSE -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,045 root INFO copying ansible_collections/purestorage/flashblade/MANIFEST.json -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,045 root INFO copying ansible_collections/purestorage/flashblade/README.md -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,046 root INFO copying ansible_collections/purestorage/flashblade/README.rst -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,046 root INFO copying ansible_collections/purestorage/flashblade/requirements.txt -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,046 root INFO copying ansible_collections/purestorage/flashblade/settings.json -> build/lib/ansible_collections/purestorage/flashblade 2023-04-28 05:57:44,046 root INFO creating build/lib/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:44,046 root INFO copying ansible_collections/purestorage/flashblade/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:44,047 root INFO copying ansible_collections/purestorage/flashblade/changelogs/changelog.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:44,047 root INFO copying ansible_collections/purestorage/flashblade/changelogs/config.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:44,047 root INFO creating build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,047 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/101_fix_policy_and_timezone_error.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,047 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/105_max_access_key.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,048 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/107_add_remove_s3user_key.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,048 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/108_dns_search_fix.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,048 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/109_update_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,048 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/111_dsrole_update_idempotency.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,048 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/112_fix_check_mode.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,049 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/113_policy_cleanup.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,049 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/114_certificate_update.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,049 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/115_multiprotocol.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,049 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/121_replication_perf.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,050 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/123_lifecycle_rule_fix.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,050 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/127_add_eula.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,050 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/128_add_32_to_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,050 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/129-virtualhost.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,050 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/131-apiclient.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,051 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/132_add_timeout.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,051 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/135_add_user_policies.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,051 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/136_add_s3user_policy.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,051 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/138_add_ad_module.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,051 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/139_add_keytabs.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,052 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/140_more_32_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,052 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/147_no_gateway.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,052 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/150_fix_joint_nfs_version_change.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,052 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/152_s3acc_lowercase.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,053 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/153_add_quota.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,053 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/154_add_snap_now.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,053 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/158_support_lags.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,053 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/159_add_lag.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,053 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/161_add_lifecycle_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,054 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/162_new_lifecycle.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,054 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/163_admin_key.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,054 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/164_add_admin.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,054 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/166_lag_mac_note.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,055 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/167_fix_logins.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,055 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/169_pypureclient_fix.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,055 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/174_access_policies.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,055 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/175_throttle_support.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,055 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/176_nfs_export_policies.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,056 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/179_fqcn.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,056 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/183_v2_connections.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,056 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/184_certificate_typos.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,056 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/185_nfs_export_rule.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,057 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/186_add_tz.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,057 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/187_rename_nfs_policy.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,057 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/188_bucket_type.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,057 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/191_add_quota_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,057 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/194_lists_for_service.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,058 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/200_proxy.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,058 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/202_multiple_snap_rules.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,058 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/205_fix_multi_lifecycle.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,058 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/211_change_booleans.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,058 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/212_object_account_quota.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,059 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/213_sec_update.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,059 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/215_encrypt_sec_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,059 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/216_extra_bucket_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,059 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/217_inventory.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,060 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/218_object_account_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,060 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/220_s3user_key_fix.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,060 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/76_default_fs_size.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,060 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/77_filesystem_policies_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,060 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/78_update_filesystem_replica_link.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,061 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/79_hide_connect_api.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,061 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/80_support_reverse_replica_link.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,061 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/81_purefb_fs_new_options.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,061 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/83_add_certgrp.yml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,062 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/84_add_cert.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,062 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/85_add_banner.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,062 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/86_add_syslog.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,062 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/88_add_lifecycle.yml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,062 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/90_delete_conn_fix.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,063 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/90_imported_keys.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,063 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/92_fix_ds_update.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,063 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/96_fix_update_connection.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,063 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/97_fix_encrpyted_array_connection_info.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,064 root INFO copying ansible_collections/purestorage/flashblade/changelogs/fragments/v1.3.0_summary.yaml -> build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:44,064 root INFO creating build/lib/ansible_collections/purestorage/flashblade/meta 2023-04-28 05:57:44,064 root INFO copying ansible_collections/purestorage/flashblade/meta/runtime.yml -> build/lib/ansible_collections/purestorage/flashblade/meta 2023-04-28 05:57:44,064 root INFO creating build/lib/ansible_collections/purestorage/flashblade/playbooks 2023-04-28 05:57:44,064 root INFO copying ansible_collections/purestorage/flashblade/playbooks/.keep -> build/lib/ansible_collections/purestorage/flashblade/playbooks 2023-04-28 05:57:44,064 root INFO creating build/lib/ansible_collections/purestorage/flashblade/playbooks/files 2023-04-28 05:57:44,065 root INFO copying ansible_collections/purestorage/flashblade/playbooks/files/.keep -> build/lib/ansible_collections/purestorage/flashblade/playbooks/files 2023-04-28 05:57:44,065 root INFO creating build/lib/ansible_collections/purestorage/flashblade/playbooks/roles 2023-04-28 05:57:44,065 root INFO copying ansible_collections/purestorage/flashblade/playbooks/roles/.keep -> build/lib/ansible_collections/purestorage/flashblade/playbooks/roles 2023-04-28 05:57:44,065 root INFO creating build/lib/ansible_collections/purestorage/flashblade/playbooks/tasks 2023-04-28 05:57:44,065 root INFO copying ansible_collections/purestorage/flashblade/playbooks/tasks/.keep -> build/lib/ansible_collections/purestorage/flashblade/playbooks/tasks 2023-04-28 05:57:44,065 root INFO creating build/lib/ansible_collections/purestorage/flashblade/playbooks/templates 2023-04-28 05:57:44,066 root INFO copying ansible_collections/purestorage/flashblade/playbooks/templates/.keep -> build/lib/ansible_collections/purestorage/flashblade/playbooks/templates 2023-04-28 05:57:44,066 root INFO creating build/lib/ansible_collections/purestorage/flashblade/playbooks/vars 2023-04-28 05:57:44,066 root INFO copying ansible_collections/purestorage/flashblade/playbooks/vars/.keep -> build/lib/ansible_collections/purestorage/flashblade/playbooks/vars 2023-04-28 05:57:44,066 root INFO creating build/lib/ansible_collections/purestorage/flashblade/plugins 2023-04-28 05:57:44,066 root INFO creating build/lib/ansible_collections/purestorage/flashblade/plugins/doc_fragments 2023-04-28 05:57:44,066 root INFO copying ansible_collections/purestorage/flashblade/plugins/doc_fragments/purestorage.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/doc_fragments 2023-04-28 05:57:44,067 root INFO creating build/lib/ansible_collections/purestorage/flashblade/plugins/module_utils 2023-04-28 05:57:44,067 root INFO copying ansible_collections/purestorage/flashblade/plugins/module_utils/purefb.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/module_utils 2023-04-28 05:57:44,067 root INFO creating build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,067 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_ad.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,067 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_admin.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,068 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_alert.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,068 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_apiclient.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,068 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_banner.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,068 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_bladename.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,068 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_bucket.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,069 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_bucket_replica.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,069 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_certgrp.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,069 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_certs.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,069 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_connect.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,070 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_dns.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,070 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_ds.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,070 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_dsrole.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,070 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_eula.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,071 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_fs.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,071 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_fs_replica.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,071 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_groupquota.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,071 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_info.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,072 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_inventory.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,072 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_keytabs.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,072 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_lag.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,072 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_lifecycle.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,072 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_messages.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,073 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_network.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,073 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_ntp.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,073 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_phonehome.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,073 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_pingtrace.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,074 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,074 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_proxy.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,074 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_ra.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,074 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_remote_cred.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,075 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_s3acc.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,075 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_s3user.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,075 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_smtp.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,075 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_snap.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,076 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_snmp_agent.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,076 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_snmp_mgr.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,076 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_subnet.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,076 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_syslog.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,077 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_target.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,077 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_timeout.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,077 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_tz.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,077 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_user.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,077 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_userpolicy.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,078 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_userquota.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,078 root INFO copying ansible_collections/purestorage/flashblade/plugins/modules/purefb_virtualhost.py -> build/lib/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:44,078 root INFO creating build/lib/ansible_collections/purestorage/flashblade/roles 2023-04-28 05:57:44,078 root INFO copying ansible_collections/purestorage/flashblade/roles/.keep -> build/lib/ansible_collections/purestorage/flashblade/roles 2023-04-28 05:57:44,078 root INFO creating build/lib/ansible_collections/purestorage/fusion 2023-04-28 05:57:44,079 root INFO copying ansible_collections/purestorage/fusion/CHANGELOG.rst -> build/lib/ansible_collections/purestorage/fusion 2023-04-28 05:57:44,079 root INFO copying ansible_collections/purestorage/fusion/COPYING.GPLv3 -> build/lib/ansible_collections/purestorage/fusion 2023-04-28 05:57:44,079 root INFO copying ansible_collections/purestorage/fusion/FILES.json -> build/lib/ansible_collections/purestorage/fusion 2023-04-28 05:57:44,079 root INFO copying ansible_collections/purestorage/fusion/MANIFEST.json -> build/lib/ansible_collections/purestorage/fusion 2023-04-28 05:57:44,080 root INFO copying ansible_collections/purestorage/fusion/README.md -> build/lib/ansible_collections/purestorage/fusion 2023-04-28 05:57:44,080 root INFO creating build/lib/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:44,080 root INFO copying ansible_collections/purestorage/fusion/changelogs/101_improve_duration_parsing.yml -> build/lib/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:44,080 root INFO copying ansible_collections/purestorage/fusion/changelogs/109_unify_storage_classes_key_in_fusion_info.yml -> build/lib/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:44,080 root INFO copying ansible_collections/purestorage/fusion/changelogs/112_unify_hardware_types_key_in_fusion_info.yml -> build/lib/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:44,081 root INFO copying ansible_collections/purestorage/fusion/changelogs/99_update_protection_policy_retention_description.yaml -> build/lib/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:44,081 root INFO copying ansible_collections/purestorage/fusion/changelogs/changelog.yaml -> build/lib/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:44,081 root INFO copying ansible_collections/purestorage/fusion/changelogs/config.yaml -> build/lib/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:44,081 root INFO creating build/lib/ansible_collections/purestorage/fusion/meta 2023-04-28 05:57:44,081 root INFO copying ansible_collections/purestorage/fusion/meta/runtime.yml -> build/lib/ansible_collections/purestorage/fusion/meta 2023-04-28 05:57:44,082 root INFO creating build/lib/ansible_collections/purestorage/fusion/playbooks 2023-04-28 05:57:44,082 root INFO creating build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,082 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/create_array.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,082 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/create_availability_zone.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,082 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/create_tenant_space.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,082 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_all.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,083 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_api_clients.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,083 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_arrays.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,083 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_availability_zones.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,083 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_hardware_types.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,084 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_hosts.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,084 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_interfaces.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,084 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_network_interface_groups.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,084 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_placement_groups.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,084 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_protection_policies.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,085 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_roles.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,085 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_snapshots.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,085 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_storage_classes.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,085 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_storage_endpoints.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,086 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_storage_services.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,086 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_tenant_spaces.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,086 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_tenants.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,086 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_users.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,086 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/list_volumes.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,087 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/make_tenant_admin.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,087 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/remove_array.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,087 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/setup_infrastructure.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,087 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/setup_protection_policies.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,087 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/setup_storage_service_class.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,088 root INFO copying ansible_collections/purestorage/fusion/playbooks/simple/setup_workloads.yml -> build/lib/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:44,088 root INFO creating build/lib/ansible_collections/purestorage/fusion/playbooks/tasks 2023-04-28 05:57:44,088 root INFO copying ansible_collections/purestorage/fusion/playbooks/tasks/.keep -> build/lib/ansible_collections/purestorage/fusion/playbooks/tasks 2023-04-28 05:57:44,088 root INFO creating build/lib/ansible_collections/purestorage/fusion/playbooks/templates 2023-04-28 05:57:44,088 root INFO copying ansible_collections/purestorage/fusion/playbooks/templates/.keep -> build/lib/ansible_collections/purestorage/fusion/playbooks/templates 2023-04-28 05:57:44,089 root INFO creating build/lib/ansible_collections/purestorage/fusion/playbooks/vars 2023-04-28 05:57:44,089 root INFO copying ansible_collections/purestorage/fusion/playbooks/vars/.keep -> build/lib/ansible_collections/purestorage/fusion/playbooks/vars 2023-04-28 05:57:44,089 root INFO creating build/lib/ansible_collections/purestorage/fusion/plugins 2023-04-28 05:57:44,089 root INFO creating build/lib/ansible_collections/purestorage/fusion/plugins/doc_fragments 2023-04-28 05:57:44,089 root INFO copying ansible_collections/purestorage/fusion/plugins/doc_fragments/purestorage.py -> build/lib/ansible_collections/purestorage/fusion/plugins/doc_fragments 2023-04-28 05:57:44,089 root INFO creating build/lib/ansible_collections/purestorage/fusion/plugins/inventory 2023-04-28 05:57:44,089 root INFO copying ansible_collections/purestorage/fusion/plugins/inventory/__init__.py -> build/lib/ansible_collections/purestorage/fusion/plugins/inventory 2023-04-28 05:57:44,090 root INFO creating build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,090 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/errors.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,090 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/fusion.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,090 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/getters.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,091 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/networking.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,091 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/operations.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,091 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/parsing.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,091 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/prerequisites.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,091 root INFO copying ansible_collections/purestorage/fusion/plugins/module_utils/startup.py -> build/lib/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:44,092 root INFO creating build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,092 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_api_client.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,092 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_array.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,092 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_az.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,092 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_hap.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,093 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_hw.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,093 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_info.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,093 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_ni.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,093 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_nig.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,094 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_pg.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,094 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_pp.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,094 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_ra.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,094 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_region.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,095 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_sc.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,095 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_se.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,095 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_ss.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,095 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_tenant.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,095 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_tn.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,096 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_ts.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,096 root INFO copying ansible_collections/purestorage/fusion/plugins/modules/fusion_volume.py -> build/lib/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:44,096 root INFO creating build/lib/ansible_collections/sensu 2023-04-28 05:57:44,096 root INFO creating build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,096 root INFO copying ansible_collections/sensu/sensu_go/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,097 root INFO copying ansible_collections/sensu/sensu_go/COPYING -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,097 root INFO copying ansible_collections/sensu/sensu_go/FILES.json -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,097 root INFO copying ansible_collections/sensu/sensu_go/MANIFEST.json -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,097 root INFO copying ansible_collections/sensu/sensu_go/Makefile -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,098 root INFO copying ansible_collections/sensu/sensu_go/README.md -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,098 root INFO copying ansible_collections/sensu/sensu_go/collection.requirements -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,098 root INFO copying ansible_collections/sensu/sensu_go/docs.requirements -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,098 root INFO copying ansible_collections/sensu/sensu_go/integration.requirements -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,098 root INFO copying ansible_collections/sensu/sensu_go/pytest.ini -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,099 root INFO copying ansible_collections/sensu/sensu_go/sanity.requirements -> build/lib/ansible_collections/sensu/sensu_go 2023-04-28 05:57:44,099 root INFO creating build/lib/ansible_collections/sensu/sensu_go/changelogs 2023-04-28 05:57:44,099 root INFO copying ansible_collections/sensu/sensu_go/changelogs/changelog.yaml -> build/lib/ansible_collections/sensu/sensu_go/changelogs 2023-04-28 05:57:44,099 root INFO creating build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,099 root INFO copying ansible_collections/sensu/sensu_go/docker/alma-8.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,100 root INFO copying ansible_collections/sensu/sensu_go/docker/amazon-1.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,100 root INFO copying ansible_collections/sensu/sensu_go/docker/amazon-2.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,100 root INFO copying ansible_collections/sensu/sensu_go/docker/build-all.sh -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,100 root INFO copying ansible_collections/sensu/sensu_go/docker/build.sh -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,101 root INFO copying ansible_collections/sensu/sensu_go/docker/centos-6.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,101 root INFO copying ansible_collections/sensu/sensu_go/docker/centos-7.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,101 root INFO copying ansible_collections/sensu/sensu_go/docker/centos-8.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,101 root INFO copying ansible_collections/sensu/sensu_go/docker/debian-10.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,101 root INFO copying ansible_collections/sensu/sensu_go/docker/debian-9.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,102 root INFO copying ansible_collections/sensu/sensu_go/docker/oracle-8.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,102 root INFO copying ansible_collections/sensu/sensu_go/docker/redhat-7.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,102 root INFO copying ansible_collections/sensu/sensu_go/docker/rocky-8.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,102 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-5.14.2.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,102 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-5.21.3.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,103 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.2.5.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,103 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.3.0.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,103 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.4.3.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,103 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.5.5.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,104 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.6.2.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,104 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.7.5.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,104 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.8.2.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,104 root INFO copying ansible_collections/sensu/sensu_go/docker/sensu-6.9.0.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,104 root INFO copying ansible_collections/sensu/sensu_go/docker/ubuntu-14.04.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,105 root INFO copying ansible_collections/sensu/sensu_go/docker/ubuntu-16.04.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,105 root INFO copying ansible_collections/sensu/sensu_go/docker/ubuntu-18.04.docker -> build/lib/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:44,105 root INFO creating build/lib/ansible_collections/sensu/sensu_go/meta 2023-04-28 05:57:44,105 root INFO copying ansible_collections/sensu/sensu_go/meta/execution-environment.yml -> build/lib/ansible_collections/sensu/sensu_go/meta 2023-04-28 05:57:44,105 root INFO copying ansible_collections/sensu/sensu_go/meta/runtime.yml -> build/lib/ansible_collections/sensu/sensu_go/meta 2023-04-28 05:57:44,106 root INFO creating build/lib/ansible_collections/sensu/sensu_go/plugins 2023-04-28 05:57:44,106 root INFO creating build/lib/ansible_collections/sensu/sensu_go/plugins/action 2023-04-28 05:57:44,106 root INFO copying ansible_collections/sensu/sensu_go/plugins/action/bonsai_asset.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/action 2023-04-28 05:57:44,106 root INFO creating build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,106 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/annotations.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,106 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/auth.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,107 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,107 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/labels.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,107 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/name.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,107 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/namespace.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,108 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/requirements.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,108 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/secrets.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,108 root INFO copying ansible_collections/sensu/sensu_go/plugins/doc_fragments/state.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:44,108 root INFO creating build/lib/ansible_collections/sensu/sensu_go/plugins/filter 2023-04-28 05:57:44,108 root INFO copying ansible_collections/sensu/sensu_go/plugins/filter/backends.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/filter 2023-04-28 05:57:44,109 root INFO copying ansible_collections/sensu/sensu_go/plugins/filter/package_name.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/filter 2023-04-28 05:57:44,109 root INFO creating build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,109 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/arguments.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,109 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/bonsai.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,109 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/client.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,110 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/debug.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,110 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/errors.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,110 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/http.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,110 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/role_utils.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,110 root INFO copying ansible_collections/sensu/sensu_go/plugins/module_utils/utils.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:44,111 root INFO creating build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,111 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/ad_auth_provider.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,111 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/asset.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,111 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/asset_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,111 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/auth_provider_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,112 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/bonsai_asset.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,112 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/check.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,112 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/check_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,112 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/cluster.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,113 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/cluster_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,113 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/cluster_role.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,113 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_binding.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,113 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_binding_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,113 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,114 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/datastore.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,114 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/datastore_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,114 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/entity.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,114 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/entity_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,115 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/etcd_replicator.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,115 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/etcd_replicator_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,115 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/event.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,115 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/event_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,115 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/filter.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,116 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/filter_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,116 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/handler_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,116 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/handler_set.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,116 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/hook.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,117 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/hook_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,117 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/ldap_auth_provider.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,117 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/mutator.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,117 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/mutator_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,117 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/namespace.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,118 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/namespace_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,118 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/oidc_auth_provider.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,118 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/pipe_handler.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,118 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/role.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,119 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/role_binding.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,119 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/role_binding_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,119 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/role_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,119 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/secret.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,119 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/secret_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,120 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_env.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,120 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,120 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_vault.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,120 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/silence.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,121 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/silence_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,121 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/socket_handler.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,121 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/tessen.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,121 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/user.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,121 root INFO copying ansible_collections/sensu/sensu_go/plugins/modules/user_info.py -> build/lib/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:44,122 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles 2023-04-28 05:57:44,122 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent 2023-04-28 05:57:44,122 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/README.md -> build/lib/ansible_collections/sensu/sensu_go/roles/agent 2023-04-28 05:57:44,122 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/defaults 2023-04-28 05:57:44,122 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/defaults/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/defaults 2023-04-28 05:57:44,122 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/handlers 2023-04-28 05:57:44,123 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/handlers/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/handlers 2023-04-28 05:57:44,123 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/meta 2023-04-28 05:57:44,123 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/meta/argument_specs.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/meta 2023-04-28 05:57:44,123 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/meta/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/meta 2023-04-28 05:57:44,123 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:44,124 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/tasks/configure.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:44,124 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/tasks/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:44,124 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/tasks/start.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:44,124 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/linux 2023-04-28 05:57:44,124 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/tasks/linux/configure.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/linux 2023-04-28 05:57:44,125 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/windows 2023-04-28 05:57:44,125 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/tasks/windows/configure.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/windows 2023-04-28 05:57:44,125 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/templates 2023-04-28 05:57:44,125 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/templates/agent.yml.j2 -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/templates 2023-04-28 05:57:44,125 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:44,125 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/vars/linux.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:44,126 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/vars/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:44,126 root INFO copying ansible_collections/sensu/sensu_go/roles/agent/vars/windows.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:44,126 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/backend 2023-04-28 05:57:44,126 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/README.md -> build/lib/ansible_collections/sensu/sensu_go/roles/backend 2023-04-28 05:57:44,126 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/backend/defaults 2023-04-28 05:57:44,126 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/defaults/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/defaults 2023-04-28 05:57:44,127 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/backend/handlers 2023-04-28 05:57:44,127 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/handlers/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/handlers 2023-04-28 05:57:44,127 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/backend/meta 2023-04-28 05:57:44,127 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/meta/argument_specs.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/meta 2023-04-28 05:57:44,127 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/meta/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/meta 2023-04-28 05:57:44,128 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:44,128 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/tasks/configure.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:44,128 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/tasks/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:44,128 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/tasks/start.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:44,128 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/backend/templates 2023-04-28 05:57:44,129 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/templates/backend.yml.j2 -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/templates 2023-04-28 05:57:44,129 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/backend/vars 2023-04-28 05:57:44,129 root INFO copying ansible_collections/sensu/sensu_go/roles/backend/vars/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/backend/vars 2023-04-28 05:57:44,129 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install 2023-04-28 05:57:44,130 root INFO copying ansible_collections/sensu/sensu_go/roles/install/README.md -> build/lib/ansible_collections/sensu/sensu_go/roles/install 2023-04-28 05:57:44,130 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/defaults 2023-04-28 05:57:44,130 root INFO copying ansible_collections/sensu/sensu_go/roles/install/defaults/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/defaults 2023-04-28 05:57:44,130 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/meta 2023-04-28 05:57:44,130 root INFO copying ansible_collections/sensu/sensu_go/roles/install/meta/argument_specs.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/meta 2023-04-28 05:57:44,131 root INFO copying ansible_collections/sensu/sensu_go/roles/install/meta/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/meta 2023-04-28 05:57:44,131 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:44,131 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/main.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:44,131 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/packages.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:44,131 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/repositories.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:44,132 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/apt 2023-04-28 05:57:44,132 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/apt/install.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/apt 2023-04-28 05:57:44,132 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/apt/prepare.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/apt 2023-04-28 05:57:44,132 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf 2023-04-28 05:57:44,132 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/dnf/install.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf 2023-04-28 05:57:44,132 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/dnf/prepare.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf 2023-04-28 05:57:44,133 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/msi 2023-04-28 05:57:44,133 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/msi/install.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/msi 2023-04-28 05:57:44,133 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/yum 2023-04-28 05:57:44,133 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/yum/install.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/yum 2023-04-28 05:57:44,133 root INFO copying ansible_collections/sensu/sensu_go/roles/install/tasks/yum/prepare.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/yum 2023-04-28 05:57:44,134 root INFO creating build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,134 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/Alma.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,134 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/Amazon.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,134 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/CentOS.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,134 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/Debian.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,135 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/OracleLinux.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,135 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/RedHat.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,135 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/Rocky.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,135 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/Ubuntu.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,135 root INFO copying ansible_collections/sensu/sensu_go/roles/install/vars/Windows.yml -> build/lib/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:44,136 root INFO creating build/lib/ansible_collections/sensu/sensu_go/tools 2023-04-28 05:57:44,136 root INFO copying ansible_collections/sensu/sensu_go/tools/windows-versions.py -> build/lib/ansible_collections/sensu/sensu_go/tools 2023-04-28 05:57:44,136 root INFO creating build/lib/ansible_collections/sensu/sensu_go/vagrant 2023-04-28 05:57:44,136 root INFO creating build/lib/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:44,136 root INFO copying ansible_collections/sensu/sensu_go/vagrant/windows/Vagrantfile -> build/lib/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:44,137 root INFO copying ansible_collections/sensu/sensu_go/vagrant/windows/back.yaml -> build/lib/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:44,137 root INFO copying ansible_collections/sensu/sensu_go/vagrant/windows/inventory.yaml -> build/lib/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:44,137 root INFO copying ansible_collections/sensu/sensu_go/vagrant/windows/play.yaml -> build/lib/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:44,137 root INFO creating build/lib/ansible_collections/splunk 2023-04-28 05:57:44,137 root INFO creating build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,137 root INFO copying ansible_collections/splunk/es/CHANGELOG.rst -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,138 root INFO copying ansible_collections/splunk/es/FILES.json -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,138 root INFO copying ansible_collections/splunk/es/LICENSE -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,138 root INFO copying ansible_collections/splunk/es/MANIFEST.json -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,138 root INFO copying ansible_collections/splunk/es/README.md -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,139 root INFO copying ansible_collections/splunk/es/bindep.txt -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,139 root INFO copying ansible_collections/splunk/es/pyproject.toml -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,139 root INFO copying ansible_collections/splunk/es/requirements.txt -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,139 root INFO copying ansible_collections/splunk/es/test-requirements.txt -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,140 root INFO copying ansible_collections/splunk/es/tox.ini -> build/lib/ansible_collections/splunk/es 2023-04-28 05:57:44,140 root INFO creating build/lib/ansible_collections/splunk/es/changelogs 2023-04-28 05:57:44,140 root INFO copying ansible_collections/splunk/es/changelogs/changelog.yaml -> build/lib/ansible_collections/splunk/es/changelogs 2023-04-28 05:57:44,140 root INFO copying ansible_collections/splunk/es/changelogs/config.yaml -> build/lib/ansible_collections/splunk/es/changelogs 2023-04-28 05:57:44,140 root INFO creating build/lib/ansible_collections/splunk/es/changelogs/fragments 2023-04-28 05:57:44,140 root INFO copying ansible_collections/splunk/es/changelogs/fragments/.keep -> build/lib/ansible_collections/splunk/es/changelogs/fragments 2023-04-28 05:57:44,141 root INFO creating build/lib/ansible_collections/splunk/es/meta 2023-04-28 05:57:44,141 root INFO copying ansible_collections/splunk/es/meta/runtime.yml -> build/lib/ansible_collections/splunk/es/meta 2023-04-28 05:57:44,141 root INFO creating build/lib/ansible_collections/splunk/es/plugins 2023-04-28 05:57:44,141 root INFO creating build/lib/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:44,141 root INFO copying ansible_collections/splunk/es/plugins/action/splunk_adaptive_response_notable_events.py -> build/lib/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:44,141 root INFO copying ansible_collections/splunk/es/plugins/action/splunk_correlation_searches.py -> build/lib/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:44,142 root INFO copying ansible_collections/splunk/es/plugins/action/splunk_data_inputs_monitor.py -> build/lib/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:44,142 root INFO copying ansible_collections/splunk/es/plugins/action/splunk_data_inputs_network.py -> build/lib/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:44,142 root INFO creating build/lib/ansible_collections/splunk/es/plugins/httpapi 2023-04-28 05:57:44,142 root INFO copying ansible_collections/splunk/es/plugins/httpapi/splunk.py -> build/lib/ansible_collections/splunk/es/plugins/httpapi 2023-04-28 05:57:44,143 root INFO creating build/lib/ansible_collections/splunk/es/plugins/module_utils 2023-04-28 05:57:44,143 root INFO copying ansible_collections/splunk/es/plugins/module_utils/splunk.py -> build/lib/ansible_collections/splunk/es/plugins/module_utils 2023-04-28 05:57:44,143 root INFO creating build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,143 root INFO copying ansible_collections/splunk/es/plugins/modules/adaptive_response_notable_event.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,143 root INFO copying ansible_collections/splunk/es/plugins/modules/correlation_search.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,143 root INFO copying ansible_collections/splunk/es/plugins/modules/correlation_search_info.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,144 root INFO copying ansible_collections/splunk/es/plugins/modules/data_input_monitor.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,144 root INFO copying ansible_collections/splunk/es/plugins/modules/data_input_network.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,144 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_adaptive_response_notable_event.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,144 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_adaptive_response_notable_events.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,145 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_correlation_search.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,145 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_correlation_search_info.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,145 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_correlation_searches.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,145 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_data_input_monitor.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,146 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_data_input_network.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,146 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_data_inputs_monitor.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,146 root INFO copying ansible_collections/splunk/es/plugins/modules/splunk_data_inputs_network.py -> build/lib/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:44,146 root INFO creating build/lib/ansible_collections/t_systems_mms 2023-04-28 05:57:44,146 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,147 root INFO copying ansible_collections/t_systems_mms/icinga_director/CHANGELOG.md -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,147 root INFO copying ansible_collections/t_systems_mms/icinga_director/CHANGELOG.rst -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,147 root INFO copying ansible_collections/t_systems_mms/icinga_director/CODE_OF_CONDUCT.md -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,147 root INFO copying ansible_collections/t_systems_mms/icinga_director/CONTRIBUTING.md -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,147 root INFO copying ansible_collections/t_systems_mms/icinga_director/FILES.json -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,148 root INFO copying ansible_collections/t_systems_mms/icinga_director/LICENSE -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,148 root INFO copying ansible_collections/t_systems_mms/icinga_director/MANIFEST.json -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,148 root INFO copying ansible_collections/t_systems_mms/icinga_director/README.md -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,148 root INFO copying ansible_collections/t_systems_mms/icinga_director/renovate.json -> build/lib/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:44,149 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:44,149 root INFO copying ansible_collections/t_systems_mms/icinga_director/changelogs/.plugin-cache.yaml -> build/lib/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:44,149 root INFO copying ansible_collections/t_systems_mms/icinga_director/changelogs/changelog.yaml -> build/lib/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:44,149 root INFO copying ansible_collections/t_systems_mms/icinga_director/changelogs/config.yaml -> build/lib/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:44,149 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,150 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_command.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,150 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,150 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,150 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_template_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,150 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_endpoint.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,151 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_endpoint_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,151 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_host.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,151 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,151 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,152 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_template_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,152 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_hostgroup.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,152 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_hostgroup_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,152 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,152 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,153 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,153 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_template_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,153 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_scheduled_downtime.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,153 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_service.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,153 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_apply.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,154 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_apply_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,154 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,154 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,154 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_template_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,155 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_servicegroup.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,155 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_servicegroup_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,155 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_serviceset.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,155 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,155 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,156 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,156 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_template_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,156 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_user.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,156 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_group.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,156 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_group_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,157 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,157 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,157 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_template_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,157 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_zone.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,158 root INFO copying ansible_collections/t_systems_mms/icinga_director/examples/icinga_zone_info.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:44,158 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/meta 2023-04-28 05:57:44,158 root INFO copying ansible_collections/t_systems_mms/icinga_director/meta/runtime.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/meta 2023-04-28 05:57:44,158 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/plugins 2023-04-28 05:57:44,158 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments 2023-04-28 05:57:44,158 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments/common_options.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments 2023-04-28 05:57:44,159 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/inventory 2023-04-28 05:57:44,159 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/inventory/icinga_director_inventory.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/inventory 2023-04-28 05:57:44,159 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/module_utils 2023-04-28 05:57:44,159 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/module_utils/icinga.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/module_utils 2023-04-28 05:57:44,159 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,159 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,160 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,160 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_template.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,160 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_template_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,160 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_endpoint.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,161 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_endpoint_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,161 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,161 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,161 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_template.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,162 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_template_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,162 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_hostgroup.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,162 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_hostgroup_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,162 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,162 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,163 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_template.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,163 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_template_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,163 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_scheduled_downtime.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,163 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,164 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_apply.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,164 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_apply_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,164 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,164 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_template.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,164 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_template_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,165 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_servicegroup.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,165 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_servicegroup_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,165 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_serviceset.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,165 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,166 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,166 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_template.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,166 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_template_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,166 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,166 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_group.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,167 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_group_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,167 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,167 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_template.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,167 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_template_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,167 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_zone.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,168 root INFO copying ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_zone_info.py -> build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:44,168 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/roles 2023-04-28 05:57:44,168 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga 2023-04-28 05:57:44,168 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/README.md -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga 2023-04-28 05:57:44,168 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/defaults 2023-04-28 05:57:44,169 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/defaults/main.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/defaults 2023-04-28 05:57:44,169 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/meta 2023-04-28 05:57:44,169 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/meta/main.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/meta 2023-04-28 05:57:44,169 root INFO creating build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,169 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_command.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,169 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_command_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,170 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_endpoint.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,170 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_host.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,170 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_host_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,170 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_hostgroup.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,171 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_notification.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,171 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_notification_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,171 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_scheduled_downtime.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,171 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,171 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service_apply.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,172 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,172 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_servicegroup.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,172 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_serviceset.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,172 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_timeperiod.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,173 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_user.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,173 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_user_template.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,173 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_zone.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,173 root INFO copying ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/main.yml -> build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:44,173 root INFO creating build/lib/ansible_collections/theforeman 2023-04-28 05:57:44,173 root INFO creating build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,174 root INFO copying ansible_collections/theforeman/foreman/CHANGELOG.rst -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,174 root INFO copying ansible_collections/theforeman/foreman/FILES.json -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,174 root INFO copying ansible_collections/theforeman/foreman/LICENSE -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,174 root INFO copying ansible_collections/theforeman/foreman/MANIFEST.json -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,175 root INFO copying ansible_collections/theforeman/foreman/PSF-license.txt -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,175 root INFO copying ansible_collections/theforeman/foreman/README.md -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,175 root INFO copying ansible_collections/theforeman/foreman/bindep.txt -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,175 root INFO copying ansible_collections/theforeman/foreman/requirements.txt -> build/lib/ansible_collections/theforeman/foreman 2023-04-28 05:57:44,176 root INFO creating build/lib/ansible_collections/theforeman/foreman/changelogs 2023-04-28 05:57:44,176 root INFO copying ansible_collections/theforeman/foreman/changelogs/changelog.yaml -> build/lib/ansible_collections/theforeman/foreman/changelogs 2023-04-28 05:57:44,176 root INFO creating build/lib/ansible_collections/theforeman/foreman/meta 2023-04-28 05:57:44,176 root INFO copying ansible_collections/theforeman/foreman/meta/execution-environment.yml -> build/lib/ansible_collections/theforeman/foreman/meta 2023-04-28 05:57:44,176 root INFO copying ansible_collections/theforeman/foreman/meta/runtime.yml -> build/lib/ansible_collections/theforeman/foreman/meta 2023-04-28 05:57:44,177 root INFO creating build/lib/ansible_collections/theforeman/foreman/plugins 2023-04-28 05:57:44,177 root INFO creating build/lib/ansible_collections/theforeman/foreman/plugins/callback 2023-04-28 05:57:44,177 root INFO copying ansible_collections/theforeman/foreman/plugins/callback/foreman.py -> build/lib/ansible_collections/theforeman/foreman/plugins/callback 2023-04-28 05:57:44,177 root INFO creating build/lib/ansible_collections/theforeman/foreman/plugins/doc_fragments 2023-04-28 05:57:44,177 root INFO copying ansible_collections/theforeman/foreman/plugins/doc_fragments/foreman.py -> build/lib/ansible_collections/theforeman/foreman/plugins/doc_fragments 2023-04-28 05:57:44,177 root INFO creating build/lib/ansible_collections/theforeman/foreman/plugins/filter 2023-04-28 05:57:44,177 root INFO copying ansible_collections/theforeman/foreman/plugins/filter/cp_label.yml -> build/lib/ansible_collections/theforeman/foreman/plugins/filter 2023-04-28 05:57:44,178 root INFO copying ansible_collections/theforeman/foreman/plugins/filter/foreman.py -> build/lib/ansible_collections/theforeman/foreman/plugins/filter 2023-04-28 05:57:44,178 root INFO creating build/lib/ansible_collections/theforeman/foreman/plugins/inventory 2023-04-28 05:57:44,178 root INFO copying ansible_collections/theforeman/foreman/plugins/inventory/foreman.py -> build/lib/ansible_collections/theforeman/foreman/plugins/inventory 2023-04-28 05:57:44,178 root INFO creating build/lib/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:44,178 root INFO copying ansible_collections/theforeman/foreman/plugins/module_utils/_apypie.py -> build/lib/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:44,179 root INFO copying ansible_collections/theforeman/foreman/plugins/module_utils/_version.py -> build/lib/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:44,179 root INFO copying ansible_collections/theforeman/foreman/plugins/module_utils/foreman_helper.py -> build/lib/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:44,179 root INFO creating build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,179 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/activation_key.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,180 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/architecture.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,180 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/auth_source_ldap.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,180 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/bookmark.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,180 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/compute_attribute.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,181 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/compute_profile.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,181 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/compute_resource.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,181 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/config_group.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,181 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_credential.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,181 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_export_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,182 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_export_library.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,182 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_export_repository.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,182 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_export_version.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,182 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_upload.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,182 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,183 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view_filter.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,183 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,183 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_rule.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,183 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_rule_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,184 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,184 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view_version.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,184 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/content_view_version_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,184 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/discovery_rule.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,185 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/domain.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,185 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/domain_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,185 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/external_usergroup.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,185 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/global_parameter.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,185 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/hardware_model.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,186 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/host.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,186 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/host_collection.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,186 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/host_errata_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,186 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/host_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,187 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/host_power.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,187 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/hostgroup.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,187 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/hostgroup_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,187 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/http_proxy.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,187 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/image.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,188 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/installation_medium.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,188 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/job_invocation.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,188 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/job_template.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,188 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/lifecycle_environment.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,189 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/location.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,189 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/operatingsystem.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,189 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/organization.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,189 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/organization_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,189 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/os_default_template.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,190 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/partition_table.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,190 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/product.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,190 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/provisioning_template.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,190 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/puppet_environment.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,191 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/puppetclasses_import.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,191 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/realm.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,191 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/redhat_manifest.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,191 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/repository.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,191 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/repository_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,192 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/repository_set.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,192 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/repository_set_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,192 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/repository_sync.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,192 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/resource_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,193 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/role.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,193 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/scap_content.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,193 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/scap_tailoring_file.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,193 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/scc_account.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,193 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/scc_product.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,194 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/setting.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,194 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/setting_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,194 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/smart_class_parameter.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,194 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/smart_proxy.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,195 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/snapshot.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,195 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/snapshot_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,195 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/status_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,195 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/subnet.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,196 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/subnet_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,196 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/subscription_info.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,196 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/subscription_manifest.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,196 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/sync_plan.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,196 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/templates_import.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,197 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/user.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,197 root INFO copying ansible_collections/theforeman/foreman/plugins/modules/usergroup.py -> build/lib/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:44,197 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles 2023-04-28 05:57:44,197 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/activation_keys 2023-04-28 05:57:44,197 root INFO copying ansible_collections/theforeman/foreman/roles/activation_keys/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/activation_keys 2023-04-28 05:57:44,198 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/activation_keys/tasks 2023-04-28 05:57:44,198 root INFO copying ansible_collections/theforeman/foreman/roles/activation_keys/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/activation_keys/tasks 2023-04-28 05:57:44,198 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/auth_sources_ldap 2023-04-28 05:57:44,198 root INFO copying ansible_collections/theforeman/foreman/roles/auth_sources_ldap/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/auth_sources_ldap 2023-04-28 05:57:44,198 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/auth_sources_ldap/tasks 2023-04-28 05:57:44,198 root INFO copying ansible_collections/theforeman/foreman/roles/auth_sources_ldap/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/auth_sources_ldap/tasks 2023-04-28 05:57:44,199 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/compute_profiles 2023-04-28 05:57:44,199 root INFO copying ansible_collections/theforeman/foreman/roles/compute_profiles/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/compute_profiles 2023-04-28 05:57:44,199 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/compute_profiles/tasks 2023-04-28 05:57:44,199 root INFO copying ansible_collections/theforeman/foreman/roles/compute_profiles/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/compute_profiles/tasks 2023-04-28 05:57:44,199 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/compute_resources 2023-04-28 05:57:44,199 root INFO copying ansible_collections/theforeman/foreman/roles/compute_resources/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/compute_resources 2023-04-28 05:57:44,200 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/compute_resources/tasks 2023-04-28 05:57:44,200 root INFO copying ansible_collections/theforeman/foreman/roles/compute_resources/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/compute_resources/tasks 2023-04-28 05:57:44,200 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_credentials 2023-04-28 05:57:44,200 root INFO copying ansible_collections/theforeman/foreman/roles/content_credentials/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/content_credentials 2023-04-28 05:57:44,200 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_credentials/tasks 2023-04-28 05:57:44,200 root INFO copying ansible_collections/theforeman/foreman/roles/content_credentials/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_credentials/tasks 2023-04-28 05:57:44,201 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_rhel 2023-04-28 05:57:44,201 root INFO copying ansible_collections/theforeman/foreman/roles/content_rhel/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/content_rhel 2023-04-28 05:57:44,201 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_rhel/defaults 2023-04-28 05:57:44,201 root INFO copying ansible_collections/theforeman/foreman/roles/content_rhel/defaults/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_rhel/defaults 2023-04-28 05:57:44,201 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_rhel/tasks 2023-04-28 05:57:44,202 root INFO copying ansible_collections/theforeman/foreman/roles/content_rhel/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_rhel/tasks 2023-04-28 05:57:44,202 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_view_publish 2023-04-28 05:57:44,202 root INFO copying ansible_collections/theforeman/foreman/roles/content_view_publish/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/content_view_publish 2023-04-28 05:57:44,202 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_view_publish/tasks 2023-04-28 05:57:44,202 root INFO copying ansible_collections/theforeman/foreman/roles/content_view_publish/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_view_publish/tasks 2023-04-28 05:57:44,202 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup 2023-04-28 05:57:44,203 root INFO copying ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup 2023-04-28 05:57:44,203 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:44,203 root INFO copying ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/delete_cv_versions.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:44,203 root INFO copying ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/find_and_delete_unused_cv_versions.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:44,203 root INFO copying ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:44,204 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_views 2023-04-28 05:57:44,204 root INFO copying ansible_collections/theforeman/foreman/roles/content_views/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/content_views 2023-04-28 05:57:44,204 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/content_views/tasks 2023-04-28 05:57:44,204 root INFO copying ansible_collections/theforeman/foreman/roles/content_views/tasks/_create_content_view.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_views/tasks 2023-04-28 05:57:44,204 root INFO copying ansible_collections/theforeman/foreman/roles/content_views/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/content_views/tasks 2023-04-28 05:57:44,205 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel 2023-04-28 05:57:44,205 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel 2023-04-28 05:57:44,205 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/defaults 2023-04-28 05:57:44,205 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/defaults/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/defaults 2023-04-28 05:57:44,205 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:44,205 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/activation_keys.yml -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:44,206 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/content_views.yml -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:44,206 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/host_groups.yml -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:44,206 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:44,206 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/products_and_repos.yml -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:44,206 root INFO copying ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/sync.yml -> build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:44,207 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/domains 2023-04-28 05:57:44,207 root INFO copying ansible_collections/theforeman/foreman/roles/domains/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/domains 2023-04-28 05:57:44,207 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/domains/tasks 2023-04-28 05:57:44,207 root INFO copying ansible_collections/theforeman/foreman/roles/domains/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/domains/tasks 2023-04-28 05:57:44,207 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/hostgroups 2023-04-28 05:57:44,208 root INFO copying ansible_collections/theforeman/foreman/roles/hostgroups/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/hostgroups 2023-04-28 05:57:44,208 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/hostgroups/tasks 2023-04-28 05:57:44,208 root INFO copying ansible_collections/theforeman/foreman/roles/hostgroups/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/hostgroups/tasks 2023-04-28 05:57:44,208 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/lifecycle_environments 2023-04-28 05:57:44,208 root INFO copying ansible_collections/theforeman/foreman/roles/lifecycle_environments/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/lifecycle_environments 2023-04-28 05:57:44,208 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/lifecycle_environments/tasks 2023-04-28 05:57:44,209 root INFO copying ansible_collections/theforeman/foreman/roles/lifecycle_environments/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/lifecycle_environments/tasks 2023-04-28 05:57:44,209 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/manifest 2023-04-28 05:57:44,209 root INFO copying ansible_collections/theforeman/foreman/roles/manifest/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/manifest 2023-04-28 05:57:44,209 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/manifest/defaults 2023-04-28 05:57:44,209 root INFO copying ansible_collections/theforeman/foreman/roles/manifest/defaults/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/manifest/defaults 2023-04-28 05:57:44,209 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/manifest/tasks 2023-04-28 05:57:44,210 root INFO copying ansible_collections/theforeman/foreman/roles/manifest/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/manifest/tasks 2023-04-28 05:57:44,210 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/operatingsystems 2023-04-28 05:57:44,210 root INFO copying ansible_collections/theforeman/foreman/roles/operatingsystems/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/operatingsystems 2023-04-28 05:57:44,210 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/operatingsystems/tasks 2023-04-28 05:57:44,210 root INFO copying ansible_collections/theforeman/foreman/roles/operatingsystems/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/operatingsystems/tasks 2023-04-28 05:57:44,211 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/organizations 2023-04-28 05:57:44,211 root INFO copying ansible_collections/theforeman/foreman/roles/organizations/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/organizations 2023-04-28 05:57:44,211 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/organizations/tasks 2023-04-28 05:57:44,211 root INFO copying ansible_collections/theforeman/foreman/roles/organizations/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/organizations/tasks 2023-04-28 05:57:44,211 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/provisioning_templates 2023-04-28 05:57:44,211 root INFO copying ansible_collections/theforeman/foreman/roles/provisioning_templates/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/provisioning_templates 2023-04-28 05:57:44,212 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/provisioning_templates/tasks 2023-04-28 05:57:44,212 root INFO copying ansible_collections/theforeman/foreman/roles/provisioning_templates/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/provisioning_templates/tasks 2023-04-28 05:57:44,212 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/repositories 2023-04-28 05:57:44,212 root INFO copying ansible_collections/theforeman/foreman/roles/repositories/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/repositories 2023-04-28 05:57:44,212 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/repositories/tasks 2023-04-28 05:57:44,212 root INFO copying ansible_collections/theforeman/foreman/roles/repositories/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/repositories/tasks 2023-04-28 05:57:44,213 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/settings 2023-04-28 05:57:44,213 root INFO copying ansible_collections/theforeman/foreman/roles/settings/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/settings 2023-04-28 05:57:44,213 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/settings/tasks 2023-04-28 05:57:44,213 root INFO copying ansible_collections/theforeman/foreman/roles/settings/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/settings/tasks 2023-04-28 05:57:44,213 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/subnets 2023-04-28 05:57:44,214 root INFO copying ansible_collections/theforeman/foreman/roles/subnets/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/subnets 2023-04-28 05:57:44,214 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/subnets/tasks 2023-04-28 05:57:44,214 root INFO copying ansible_collections/theforeman/foreman/roles/subnets/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/subnets/tasks 2023-04-28 05:57:44,214 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/sync_plans 2023-04-28 05:57:44,214 root INFO copying ansible_collections/theforeman/foreman/roles/sync_plans/README.md -> build/lib/ansible_collections/theforeman/foreman/roles/sync_plans 2023-04-28 05:57:44,214 root INFO creating build/lib/ansible_collections/theforeman/foreman/roles/sync_plans/tasks 2023-04-28 05:57:44,215 root INFO copying ansible_collections/theforeman/foreman/roles/sync_plans/tasks/main.yml -> build/lib/ansible_collections/theforeman/foreman/roles/sync_plans/tasks 2023-04-28 05:57:44,215 root INFO creating build/lib/ansible_collections/vmware 2023-04-28 05:57:44,215 root INFO creating build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,215 root INFO copying ansible_collections/vmware/vmware_rest/CHANGELOG.rst -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,215 root INFO copying ansible_collections/vmware/vmware_rest/FILES.json -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,216 root INFO copying ansible_collections/vmware/vmware_rest/LICENSE -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,216 root INFO copying ansible_collections/vmware/vmware_rest/MANIFEST.json -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,216 root INFO copying ansible_collections/vmware/vmware_rest/README.md -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,216 root INFO copying ansible_collections/vmware/vmware_rest/bindep.txt -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,217 root INFO copying ansible_collections/vmware/vmware_rest/dev.md -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,217 root INFO copying ansible_collections/vmware/vmware_rest/docs-requirements.txt -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,217 root INFO copying ansible_collections/vmware/vmware_rest/modules.yaml -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,217 root INFO copying ansible_collections/vmware/vmware_rest/requirements.txt -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,218 root INFO copying ansible_collections/vmware/vmware_rest/test-requirements.txt -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,218 root INFO copying ansible_collections/vmware/vmware_rest/tox.ini -> build/lib/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,218 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/changelogs 2023-04-28 05:57:44,218 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/changelog.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs 2023-04-28 05:57:44,218 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/config.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs 2023-04-28 05:57:44,219 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,219 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/2.1.3-changelog.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,219 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/2.1.3-module_utils.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,219 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/allow_space_in_search_filters.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,219 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/cloud.common-bump.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,220 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/lookup-handle-special-chars.yml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,220 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/set_default_galaxy_version.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,220 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/use-FQCN-in-create_vm.yaml.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,220 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/vcenter_network_info-dvs-example.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,220 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/version_added.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,221 root INFO copying ansible_collections/vmware/vmware_rest/changelogs/fragments/vm_template_library.yaml -> build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,221 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/manual 2023-04-28 05:57:44,221 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,221 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/.rstcheck.cfg -> build/lib/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,221 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/Makefile -> build/lib/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,222 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/conf.py -> build/lib/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,222 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/export_to_ansible_ansible.sh -> build/lib/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,222 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/guide_vmware_rest.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,222 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/index.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,222 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios 2023-04-28 05:57:44,222 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,223 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/appliance_access.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,223 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/health.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,223 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/network.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,223 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/services.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,224 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/system_managment.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,224 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,224 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/1_authentication.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,224 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/1_installation.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,224 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/2_collect_information.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,225 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/3_create_vm.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,225 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/4_vm_info.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,225 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/5_vm_hardware_tuning.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,225 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/6_run_a_vm.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,225 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/7_vm_tool_information.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,226 root INFO copying ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/8_vm_tool_configuration.rst -> build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,226 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/meta 2023-04-28 05:57:44,226 root INFO copying ansible_collections/vmware/vmware_rest/meta/runtime.yml -> build/lib/ansible_collections/vmware/vmware_rest/meta 2023-04-28 05:57:44,226 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/plugins 2023-04-28 05:57:44,226 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/plugins/doc_fragments 2023-04-28 05:57:44,226 root INFO copying ansible_collections/vmware/vmware_rest/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/doc_fragments 2023-04-28 05:57:44,227 root INFO copying ansible_collections/vmware/vmware_rest/plugins/doc_fragments/moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/doc_fragments 2023-04-28 05:57:44,227 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,227 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/cluster_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,227 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/datacenter_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,227 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/datastore_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,228 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/folder_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,228 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/host_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,228 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/network_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,228 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/resource_pool_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,228 root INFO copying ansible_collections/vmware/vmware_rest/plugins/lookup/vm_moid.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,229 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/plugins/module_utils 2023-04-28 05:57:44,229 root INFO copying ansible_collections/vmware/vmware_rest/plugins/module_utils/vmware_rest.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/module_utils 2023-04-28 05:57:44,229 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,229 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_consolecli.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,229 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_consolecli_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,230 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_dcui.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,230 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_dcui_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,230 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_shell.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,230 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_shell_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,231 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_ssh.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,231 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_ssh_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,231 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_applmgmt_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,231 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_database_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,232 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_databasestorage_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,232 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_load_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,232 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_mem_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,232 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_softwarepackages_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,232 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_storage_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,233 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_swap_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,233 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_system_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,233 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_infraprofile_configs.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,233 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_infraprofile_configs_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,234 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_globalpolicy.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,234 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_globalpolicy_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,234 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,234 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_monitoring_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,235 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_monitoring_query.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,235 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,235 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_domains.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,235 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_domains_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,235 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_hostname.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,236 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_hostname_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,236 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_servers.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,236 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_servers_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,236 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_firewall_inbound.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,237 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_firewall_inbound_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,237 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,237 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,237 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv4.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,238 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv4_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,238 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv6.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,238 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv6_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,238 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_noproxy.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,238 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_noproxy_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,239 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_proxy.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,239 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_proxy_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,239 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_ntp.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,239 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_ntp_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,240 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_services.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,240 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_services_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,240 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_shutdown.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,240 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_shutdown_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,241 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_globalfips.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,241 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_globalfips_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,241 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_storage.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,241 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_storage_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,241 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,242 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_timezone.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,242 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_timezone_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,242 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_version_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,242 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_timesync.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,243 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_timesync_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,243 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_update_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,243 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_vmon_service.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,243 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/appliance_vmon_service_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,243 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/content_configuration.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,244 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/content_configuration_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,244 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/content_library_item_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,244 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/content_locallibrary.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,244 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/content_locallibrary_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,245 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/content_subscribedlibrary.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,245 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/content_subscribedlibrary_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,245 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_cluster_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,245 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datacenter.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,246 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datacenter_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,246 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datastore_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,246 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_folder_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,246 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_host.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,247 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_host_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,247 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_network_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,247 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_ovf_libraryitem.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,247 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_resourcepool.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,248 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_resourcepool_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,248 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_storage_policies_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,248 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,248 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_customization.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,249 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_filesystem_directories.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,249 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_identity_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,249 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_localfilesystem_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,249 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,250 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_interfaces_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,250 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_routes_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,250 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_operations_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,250 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_power.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,250 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_power_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,251 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,251 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_sata.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,251 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_sata_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,251 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_scsi.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,252 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_scsi_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,252 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,252 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_device.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,252 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_device_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,253 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,253 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cdrom.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,253 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cdrom_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,253 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cpu.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,254 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cpu_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,254 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_disk.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,254 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_disk_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,255 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_ethernet.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,255 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_ethernet_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,255 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_floppy.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,255 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_floppy_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,256 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,256 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_memory.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,256 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_memory_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,256 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_parallel.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,257 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_parallel_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,257 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_serial.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,257 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_serial_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,257 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,258 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_libraryitem_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,258 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_power.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,258 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_power_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,258 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,259 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_compliance.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,259 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_compliance_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,259 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,259 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,259 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,260 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_installer.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,260 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_installer_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,260 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vmtemplate_libraryitems.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,260 root INFO copying ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vmtemplate_libraryitems_info.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,261 root INFO creating build/lib/ansible_collections/vmware/vmware_rest/plugins/plugin_utils 2023-04-28 05:57:44,261 root INFO copying ansible_collections/vmware/vmware_rest/plugins/plugin_utils/lookup.py -> build/lib/ansible_collections/vmware/vmware_rest/plugins/plugin_utils 2023-04-28 05:57:44,261 root INFO creating build/lib/ansible_collections/vultr 2023-04-28 05:57:44,261 root INFO creating build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,261 root INFO copying ansible_collections/vultr/cloud/CHANGELOG.rst -> build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,261 root INFO copying ansible_collections/vultr/cloud/CONTRIBUTING.md -> build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,262 root INFO copying ansible_collections/vultr/cloud/COPYING -> build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,262 root INFO copying ansible_collections/vultr/cloud/FILES.json -> build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,262 root INFO copying ansible_collections/vultr/cloud/MANIFEST.json -> build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,262 root INFO copying ansible_collections/vultr/cloud/README.md -> build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,263 root INFO copying ansible_collections/vultr/cloud/codecov.yml -> build/lib/ansible_collections/vultr/cloud 2023-04-28 05:57:44,263 root INFO creating build/lib/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:44,263 root INFO copying ansible_collections/vultr/cloud/changelogs/.gitignore -> build/lib/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:44,263 root INFO copying ansible_collections/vultr/cloud/changelogs/changelog.yaml -> build/lib/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:44,264 root INFO copying ansible_collections/vultr/cloud/changelogs/config.yaml -> build/lib/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:44,264 root INFO creating build/lib/ansible_collections/vultr/cloud/changelogs/fragments 2023-04-28 05:57:44,264 root INFO copying ansible_collections/vultr/cloud/changelogs/fragments/.keep -> build/lib/ansible_collections/vultr/cloud/changelogs/fragments 2023-04-28 05:57:44,264 root INFO creating build/lib/ansible_collections/vultr/cloud/meta 2023-04-28 05:57:44,264 root INFO copying ansible_collections/vultr/cloud/meta/runtime.yml -> build/lib/ansible_collections/vultr/cloud/meta 2023-04-28 05:57:44,264 root INFO creating build/lib/ansible_collections/vultr/cloud/plugins 2023-04-28 05:57:44,265 root INFO creating build/lib/ansible_collections/vultr/cloud/plugins/doc_fragments 2023-04-28 05:57:44,265 root INFO copying ansible_collections/vultr/cloud/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/vultr/cloud/plugins/doc_fragments 2023-04-28 05:57:44,265 root INFO copying ansible_collections/vultr/cloud/plugins/doc_fragments/vultr_v2.py -> build/lib/ansible_collections/vultr/cloud/plugins/doc_fragments 2023-04-28 05:57:44,265 root INFO creating build/lib/ansible_collections/vultr/cloud/plugins/inventory 2023-04-28 05:57:44,265 root INFO copying ansible_collections/vultr/cloud/plugins/inventory/vultr.py -> build/lib/ansible_collections/vultr/cloud/plugins/inventory 2023-04-28 05:57:44,265 root INFO creating build/lib/ansible_collections/vultr/cloud/plugins/module_utils 2023-04-28 05:57:44,266 root INFO copying ansible_collections/vultr/cloud/plugins/module_utils/vultr_v2.py -> build/lib/ansible_collections/vultr/cloud/plugins/module_utils 2023-04-28 05:57:44,266 root INFO creating build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,266 root INFO copying ansible_collections/vultr/cloud/plugins/modules/__init__.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,266 root INFO copying ansible_collections/vultr/cloud/plugins/modules/account_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,266 root INFO copying ansible_collections/vultr/cloud/plugins/modules/block_storage.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,267 root INFO copying ansible_collections/vultr/cloud/plugins/modules/block_storage_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,267 root INFO copying ansible_collections/vultr/cloud/plugins/modules/dns_domain.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,267 root INFO copying ansible_collections/vultr/cloud/plugins/modules/dns_domain_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,267 root INFO copying ansible_collections/vultr/cloud/plugins/modules/dns_record.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,267 root INFO copying ansible_collections/vultr/cloud/plugins/modules/firewall_group.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,268 root INFO copying ansible_collections/vultr/cloud/plugins/modules/firewall_group_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,268 root INFO copying ansible_collections/vultr/cloud/plugins/modules/firewall_rule.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,268 root INFO copying ansible_collections/vultr/cloud/plugins/modules/firewall_rule_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,268 root INFO copying ansible_collections/vultr/cloud/plugins/modules/instance.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,269 root INFO copying ansible_collections/vultr/cloud/plugins/modules/instance_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,269 root INFO copying ansible_collections/vultr/cloud/plugins/modules/os_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,269 root INFO copying ansible_collections/vultr/cloud/plugins/modules/plan_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,269 root INFO copying ansible_collections/vultr/cloud/plugins/modules/plan_metal_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,270 root INFO copying ansible_collections/vultr/cloud/plugins/modules/region_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,270 root INFO copying ansible_collections/vultr/cloud/plugins/modules/reserved_ip.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,270 root INFO copying ansible_collections/vultr/cloud/plugins/modules/snapshot.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,270 root INFO copying ansible_collections/vultr/cloud/plugins/modules/snapshot_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,270 root INFO copying ansible_collections/vultr/cloud/plugins/modules/ssh_key.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,271 root INFO copying ansible_collections/vultr/cloud/plugins/modules/ssh_key_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,271 root INFO copying ansible_collections/vultr/cloud/plugins/modules/startup_script.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,271 root INFO copying ansible_collections/vultr/cloud/plugins/modules/startup_script_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,271 root INFO copying ansible_collections/vultr/cloud/plugins/modules/user.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,271 root INFO copying ansible_collections/vultr/cloud/plugins/modules/user_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,272 root INFO copying ansible_collections/vultr/cloud/plugins/modules/vpc.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,272 root INFO copying ansible_collections/vultr/cloud/plugins/modules/vpc_info.py -> build/lib/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:44,272 root INFO creating build/lib/ansible_collections/vyos 2023-04-28 05:57:44,272 root INFO creating build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,272 root INFO copying ansible_collections/vyos/vyos/CHANGELOG.rst -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,273 root INFO copying ansible_collections/vyos/vyos/FILES.json -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,273 root INFO copying ansible_collections/vyos/vyos/LICENSE -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,273 root INFO copying ansible_collections/vyos/vyos/MANIFEST.json -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,274 root INFO copying ansible_collections/vyos/vyos/README.md -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,274 root INFO copying ansible_collections/vyos/vyos/bindep.txt -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,274 root INFO copying ansible_collections/vyos/vyos/codecov.yml -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,274 root INFO copying ansible_collections/vyos/vyos/pyproject.toml -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,275 root INFO copying ansible_collections/vyos/vyos/requirements.txt -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,275 root INFO copying ansible_collections/vyos/vyos/test-requirements.txt -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,275 root INFO copying ansible_collections/vyos/vyos/tox.ini -> build/lib/ansible_collections/vyos/vyos 2023-04-28 05:57:44,275 root INFO creating build/lib/ansible_collections/vyos/vyos/changelogs 2023-04-28 05:57:44,275 root INFO copying ansible_collections/vyos/vyos/changelogs/changelog.yaml -> build/lib/ansible_collections/vyos/vyos/changelogs 2023-04-28 05:57:44,276 root INFO copying ansible_collections/vyos/vyos/changelogs/config.yaml -> build/lib/ansible_collections/vyos/vyos/changelogs 2023-04-28 05:57:44,276 root INFO creating build/lib/ansible_collections/vyos/vyos/changelogs/fragments 2023-04-28 05:57:44,276 root INFO copying ansible_collections/vyos/vyos/changelogs/fragments/.keep -> build/lib/ansible_collections/vyos/vyos/changelogs/fragments 2023-04-28 05:57:44,276 root INFO creating build/lib/ansible_collections/vyos/vyos/meta 2023-04-28 05:57:44,276 root INFO copying ansible_collections/vyos/vyos/meta/runtime.yml -> build/lib/ansible_collections/vyos/vyos/meta 2023-04-28 05:57:44,276 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins 2023-04-28 05:57:44,277 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,277 root INFO copying ansible_collections/vyos/vyos/plugins/action/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,277 root INFO copying ansible_collections/vyos/vyos/plugins/action/banner.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,277 root INFO copying ansible_collections/vyos/vyos/plugins/action/bgp_address_family.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,277 root INFO copying ansible_collections/vyos/vyos/plugins/action/bgp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,278 root INFO copying ansible_collections/vyos/vyos/plugins/action/command.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,278 root INFO copying ansible_collections/vyos/vyos/plugins/action/config.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,278 root INFO copying ansible_collections/vyos/vyos/plugins/action/facts.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,278 root INFO copying ansible_collections/vyos/vyos/plugins/action/firewall_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,278 root INFO copying ansible_collections/vyos/vyos/plugins/action/firewall_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,279 root INFO copying ansible_collections/vyos/vyos/plugins/action/firewall_rules.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,279 root INFO copying ansible_collections/vyos/vyos/plugins/action/hostname.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,279 root INFO copying ansible_collections/vyos/vyos/plugins/action/interface.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,279 root INFO copying ansible_collections/vyos/vyos/plugins/action/interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,279 root INFO copying ansible_collections/vyos/vyos/plugins/action/l3_interface.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,280 root INFO copying ansible_collections/vyos/vyos/plugins/action/l3_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,280 root INFO copying ansible_collections/vyos/vyos/plugins/action/lag_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,280 root INFO copying ansible_collections/vyos/vyos/plugins/action/linkagg.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,280 root INFO copying ansible_collections/vyos/vyos/plugins/action/lldp.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,281 root INFO copying ansible_collections/vyos/vyos/plugins/action/lldp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,281 root INFO copying ansible_collections/vyos/vyos/plugins/action/lldp_interface.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,281 root INFO copying ansible_collections/vyos/vyos/plugins/action/lldp_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,281 root INFO copying ansible_collections/vyos/vyos/plugins/action/logging.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,281 root INFO copying ansible_collections/vyos/vyos/plugins/action/logging_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,282 root INFO copying ansible_collections/vyos/vyos/plugins/action/ntp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,282 root INFO copying ansible_collections/vyos/vyos/plugins/action/ospf_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,282 root INFO copying ansible_collections/vyos/vyos/plugins/action/ospfv2.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,282 root INFO copying ansible_collections/vyos/vyos/plugins/action/ospfv3.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,283 root INFO copying ansible_collections/vyos/vyos/plugins/action/ping.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,283 root INFO copying ansible_collections/vyos/vyos/plugins/action/prefix_lists.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,283 root INFO copying ansible_collections/vyos/vyos/plugins/action/route_maps.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,283 root INFO copying ansible_collections/vyos/vyos/plugins/action/snmp_server.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,283 root INFO copying ansible_collections/vyos/vyos/plugins/action/static_route.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,284 root INFO copying ansible_collections/vyos/vyos/plugins/action/static_routes.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,284 root INFO copying ansible_collections/vyos/vyos/plugins/action/system.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,284 root INFO copying ansible_collections/vyos/vyos/plugins/action/user.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,284 root INFO copying ansible_collections/vyos/vyos/plugins/action/vlan.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,284 root INFO copying ansible_collections/vyos/vyos/plugins/action/vyos.py -> build/lib/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:44,285 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/cliconf 2023-04-28 05:57:44,285 root INFO copying ansible_collections/vyos/vyos/plugins/cliconf/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/cliconf 2023-04-28 05:57:44,285 root INFO copying ansible_collections/vyos/vyos/plugins/cliconf/vyos.py -> build/lib/ansible_collections/vyos/vyos/plugins/cliconf 2023-04-28 05:57:44,285 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/doc_fragments 2023-04-28 05:57:44,285 root INFO copying ansible_collections/vyos/vyos/plugins/doc_fragments/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/doc_fragments 2023-04-28 05:57:44,286 root INFO copying ansible_collections/vyos/vyos/plugins/doc_fragments/vyos.py -> build/lib/ansible_collections/vyos/vyos/plugins/doc_fragments 2023-04-28 05:57:44,286 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/filter 2023-04-28 05:57:44,286 root INFO copying ansible_collections/vyos/vyos/plugins/filter/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/filter 2023-04-28 05:57:44,286 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/inventory 2023-04-28 05:57:44,286 root INFO copying ansible_collections/vyos/vyos/plugins/inventory/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/inventory 2023-04-28 05:57:44,286 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils 2023-04-28 05:57:44,287 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils 2023-04-28 05:57:44,287 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network 2023-04-28 05:57:44,287 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network 2023-04-28 05:57:44,287 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos 2023-04-28 05:57:44,287 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos 2023-04-28 05:57:44,288 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/vyos.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos 2023-04-28 05:57:44,288 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec 2023-04-28 05:57:44,288 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec 2023-04-28 05:57:44,288 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family 2023-04-28 05:57:44,288 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family 2023-04-28 05:57:44,288 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family 2023-04-28 05:57:44,289 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global 2023-04-28 05:57:44,289 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global 2023-04-28 05:57:44,289 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/bgp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global 2023-04-28 05:57:44,289 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts 2023-04-28 05:57:44,289 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts 2023-04-28 05:57:44,290 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/facts.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts 2023-04-28 05:57:44,290 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global 2023-04-28 05:57:44,290 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global 2023-04-28 05:57:44,290 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/firewall_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global 2023-04-28 05:57:44,290 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces 2023-04-28 05:57:44,291 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces 2023-04-28 05:57:44,291 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/firewall_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces 2023-04-28 05:57:44,291 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules 2023-04-28 05:57:44,291 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules 2023-04-28 05:57:44,291 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/firewall_rules.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules 2023-04-28 05:57:44,292 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname 2023-04-28 05:57:44,292 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname 2023-04-28 05:57:44,292 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/hostname.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname 2023-04-28 05:57:44,292 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces 2023-04-28 05:57:44,292 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces 2023-04-28 05:57:44,292 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces 2023-04-28 05:57:44,293 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces 2023-04-28 05:57:44,293 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces 2023-04-28 05:57:44,293 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces 2023-04-28 05:57:44,293 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces 2023-04-28 05:57:44,293 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces 2023-04-28 05:57:44,294 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces 2023-04-28 05:57:44,294 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global 2023-04-28 05:57:44,294 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global 2023-04-28 05:57:44,294 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/lldp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global 2023-04-28 05:57:44,294 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces 2023-04-28 05:57:44,294 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces 2023-04-28 05:57:44,295 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces 2023-04-28 05:57:44,295 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global 2023-04-28 05:57:44,295 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global 2023-04-28 05:57:44,295 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/logging_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global 2023-04-28 05:57:44,296 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global 2023-04-28 05:57:44,296 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global 2023-04-28 05:57:44,296 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/ntp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global 2023-04-28 05:57:44,296 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces 2023-04-28 05:57:44,296 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces 2023-04-28 05:57:44,296 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces 2023-04-28 05:57:44,297 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2 2023-04-28 05:57:44,297 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2 2023-04-28 05:57:44,297 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/ospfv2.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2 2023-04-28 05:57:44,297 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3 2023-04-28 05:57:44,297 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3 2023-04-28 05:57:44,298 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/ospfv3.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3 2023-04-28 05:57:44,298 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists 2023-04-28 05:57:44,298 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists 2023-04-28 05:57:44,298 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists 2023-04-28 05:57:44,298 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps 2023-04-28 05:57:44,298 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps 2023-04-28 05:57:44,299 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/route_maps.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps 2023-04-28 05:57:44,299 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server 2023-04-28 05:57:44,299 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server 2023-04-28 05:57:44,299 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/snmp_server.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server 2023-04-28 05:57:44,299 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes 2023-04-28 05:57:44,300 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes 2023-04-28 05:57:44,300 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/static_routes.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes 2023-04-28 05:57:44,300 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config 2023-04-28 05:57:44,300 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config 2023-04-28 05:57:44,300 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family 2023-04-28 05:57:44,301 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family 2023-04-28 05:57:44,301 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family 2023-04-28 05:57:44,301 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global 2023-04-28 05:57:44,301 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global 2023-04-28 05:57:44,301 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/bgp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global 2023-04-28 05:57:44,302 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global 2023-04-28 05:57:44,302 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global 2023-04-28 05:57:44,302 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/firewall_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global 2023-04-28 05:57:44,302 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces 2023-04-28 05:57:44,302 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces 2023-04-28 05:57:44,303 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/firewall_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces 2023-04-28 05:57:44,303 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules 2023-04-28 05:57:44,303 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules 2023-04-28 05:57:44,303 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/firewall_rules.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules 2023-04-28 05:57:44,303 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname 2023-04-28 05:57:44,304 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname 2023-04-28 05:57:44,304 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/hostname.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname 2023-04-28 05:57:44,304 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces 2023-04-28 05:57:44,304 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces 2023-04-28 05:57:44,304 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces 2023-04-28 05:57:44,305 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces 2023-04-28 05:57:44,305 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces 2023-04-28 05:57:44,305 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces 2023-04-28 05:57:44,305 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces 2023-04-28 05:57:44,305 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces 2023-04-28 05:57:44,305 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces 2023-04-28 05:57:44,306 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global 2023-04-28 05:57:44,306 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global 2023-04-28 05:57:44,306 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/lldp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global 2023-04-28 05:57:44,306 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces 2023-04-28 05:57:44,306 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces 2023-04-28 05:57:44,307 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces 2023-04-28 05:57:44,307 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global 2023-04-28 05:57:44,307 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global 2023-04-28 05:57:44,307 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/logging_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global 2023-04-28 05:57:44,307 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global 2023-04-28 05:57:44,308 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global 2023-04-28 05:57:44,308 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/ntp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global 2023-04-28 05:57:44,308 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces 2023-04-28 05:57:44,308 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces 2023-04-28 05:57:44,308 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces 2023-04-28 05:57:44,309 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2 2023-04-28 05:57:44,309 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2 2023-04-28 05:57:44,309 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/ospfv2.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2 2023-04-28 05:57:44,309 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3 2023-04-28 05:57:44,309 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3 2023-04-28 05:57:44,310 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/ospfv3.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3 2023-04-28 05:57:44,310 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists 2023-04-28 05:57:44,310 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists 2023-04-28 05:57:44,310 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists 2023-04-28 05:57:44,310 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps 2023-04-28 05:57:44,311 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps 2023-04-28 05:57:44,311 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/route_maps.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps 2023-04-28 05:57:44,311 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server 2023-04-28 05:57:44,311 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server 2023-04-28 05:57:44,311 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/snmp_server.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server 2023-04-28 05:57:44,312 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes 2023-04-28 05:57:44,312 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes 2023-04-28 05:57:44,312 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/static_routes.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes 2023-04-28 05:57:44,312 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts 2023-04-28 05:57:44,312 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts 2023-04-28 05:57:44,313 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/facts.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts 2023-04-28 05:57:44,313 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family 2023-04-28 05:57:44,313 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family 2023-04-28 05:57:44,313 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/bgp_address_family.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family 2023-04-28 05:57:44,313 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global 2023-04-28 05:57:44,313 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global 2023-04-28 05:57:44,314 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/bgp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global 2023-04-28 05:57:44,314 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global 2023-04-28 05:57:44,314 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global 2023-04-28 05:57:44,314 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/firewall_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global 2023-04-28 05:57:44,314 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces 2023-04-28 05:57:44,315 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces 2023-04-28 05:57:44,315 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/firewall_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces 2023-04-28 05:57:44,315 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules 2023-04-28 05:57:44,315 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules 2023-04-28 05:57:44,315 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/firewall_rules.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules 2023-04-28 05:57:44,316 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname 2023-04-28 05:57:44,316 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname 2023-04-28 05:57:44,316 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/hostname.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname 2023-04-28 05:57:44,316 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces 2023-04-28 05:57:44,316 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces 2023-04-28 05:57:44,317 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces 2023-04-28 05:57:44,317 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces 2023-04-28 05:57:44,317 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces 2023-04-28 05:57:44,317 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/l3_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces 2023-04-28 05:57:44,317 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces 2023-04-28 05:57:44,317 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces 2023-04-28 05:57:44,318 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/lag_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces 2023-04-28 05:57:44,318 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy 2023-04-28 05:57:44,318 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy 2023-04-28 05:57:44,318 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/base.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy 2023-04-28 05:57:44,318 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global 2023-04-28 05:57:44,319 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global 2023-04-28 05:57:44,319 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/lldp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global 2023-04-28 05:57:44,319 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces 2023-04-28 05:57:44,319 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces 2023-04-28 05:57:44,319 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/lldp_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces 2023-04-28 05:57:44,320 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global 2023-04-28 05:57:44,320 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global 2023-04-28 05:57:44,320 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/logging_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global 2023-04-28 05:57:44,320 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global 2023-04-28 05:57:44,320 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global 2023-04-28 05:57:44,321 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/ntp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global 2023-04-28 05:57:44,321 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces 2023-04-28 05:57:44,321 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces 2023-04-28 05:57:44,321 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/ospf_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces 2023-04-28 05:57:44,321 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2 2023-04-28 05:57:44,321 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2 2023-04-28 05:57:44,322 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/ospfv2.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2 2023-04-28 05:57:44,322 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3 2023-04-28 05:57:44,322 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3 2023-04-28 05:57:44,322 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/ospfv3.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3 2023-04-28 05:57:44,322 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists 2023-04-28 05:57:44,323 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists 2023-04-28 05:57:44,323 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/prefix_lists.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists 2023-04-28 05:57:44,323 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps 2023-04-28 05:57:44,323 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps 2023-04-28 05:57:44,323 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/route_maps.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps 2023-04-28 05:57:44,324 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server 2023-04-28 05:57:44,324 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server 2023-04-28 05:57:44,324 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/snmp_server.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server 2023-04-28 05:57:44,324 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes 2023-04-28 05:57:44,324 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes 2023-04-28 05:57:44,325 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/static_routes.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes 2023-04-28 05:57:44,325 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,325 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,325 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/bgp_address_family.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,325 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/bgp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,326 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/hostname.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,326 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/logging_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,326 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/ntp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,326 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/ospf_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,327 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/prefix_lists.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,327 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/route_maps.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,327 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/snmp_server.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:44,327 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils 2023-04-28 05:57:44,328 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils 2023-04-28 05:57:44,328 root INFO copying ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/utils.py -> build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils 2023-04-28 05:57:44,328 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,328 root INFO copying ansible_collections/vyos/vyos/plugins/modules/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,328 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_banner.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,329 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_bgp_address_family.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,329 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_bgp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,329 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_command.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,329 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_config.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,330 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_facts.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,330 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,330 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,330 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_rules.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,331 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_hostname.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,331 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,331 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_l3_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,331 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_lag_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,332 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_lldp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,332 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_lldp_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,332 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_logging.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,332 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_logging_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,333 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_ntp_global.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,333 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_ospf_interfaces.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,333 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_ospfv2.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,334 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_ospfv3.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,334 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_ping.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,334 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_prefix_lists.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,334 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_route_maps.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,335 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_snmp_server.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,335 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_static_routes.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,335 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_system.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,335 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_user.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,336 root INFO copying ansible_collections/vyos/vyos/plugins/modules/vyos_vlan.py -> build/lib/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:44,336 root INFO creating build/lib/ansible_collections/vyos/vyos/plugins/terminal 2023-04-28 05:57:44,336 root INFO copying ansible_collections/vyos/vyos/plugins/terminal/__init__.py -> build/lib/ansible_collections/vyos/vyos/plugins/terminal 2023-04-28 05:57:44,336 root INFO copying ansible_collections/vyos/vyos/plugins/terminal/vyos.py -> build/lib/ansible_collections/vyos/vyos/plugins/terminal 2023-04-28 05:57:44,336 root INFO creating build/lib/ansible_collections/wti 2023-04-28 05:57:44,336 root INFO creating build/lib/ansible_collections/wti/remote 2023-04-28 05:57:44,337 root INFO copying ansible_collections/wti/remote/CHANGELOG.rst -> build/lib/ansible_collections/wti/remote 2023-04-28 05:57:44,337 root INFO copying ansible_collections/wti/remote/FILES.json -> build/lib/ansible_collections/wti/remote 2023-04-28 05:57:44,337 root INFO copying ansible_collections/wti/remote/MANIFEST.json -> build/lib/ansible_collections/wti/remote 2023-04-28 05:57:44,337 root INFO copying ansible_collections/wti/remote/README.md -> build/lib/ansible_collections/wti/remote 2023-04-28 05:57:44,337 root INFO copying ansible_collections/wti/remote/requirements-wti.txt -> build/lib/ansible_collections/wti/remote 2023-04-28 05:57:44,338 root INFO creating build/lib/ansible_collections/wti/remote/meta 2023-04-28 05:57:44,338 root INFO copying ansible_collections/wti/remote/meta/execution-environment.yml -> build/lib/ansible_collections/wti/remote/meta 2023-04-28 05:57:44,338 root INFO copying ansible_collections/wti/remote/meta/runtime.yml -> build/lib/ansible_collections/wti/remote/meta 2023-04-28 05:57:44,338 root INFO creating build/lib/ansible_collections/wti/remote/playbooks 2023-04-28 05:57:44,338 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_config 2023-04-28 05:57:44,338 root INFO copying ansible_collections/wti/remote/playbooks/cpm_config/cpm_config_backup.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_config 2023-04-28 05:57:44,339 root INFO copying ansible_collections/wti/remote/playbooks/cpm_config/cpm_config_restore.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_config 2023-04-28 05:57:44,339 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_firmwareupdate 2023-04-28 05:57:44,339 root INFO copying ansible_collections/wti/remote/playbooks/cpm_firmwareupdate/firmware_upgrade.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_firmwareupdate 2023-04-28 05:57:44,339 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_hostname 2023-04-28 05:57:44,339 root INFO copying ansible_collections/wti/remote/playbooks/cpm_hostname/hostname_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_hostname 2023-04-28 05:57:44,340 root INFO copying ansible_collections/wti/remote/playbooks/cpm_hostname/hostname_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_hostname 2023-04-28 05:57:44,340 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_interface 2023-04-28 05:57:44,340 root INFO copying ansible_collections/wti/remote/playbooks/cpm_interface/interface_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_interface 2023-04-28 05:57:44,340 root INFO copying ansible_collections/wti/remote/playbooks/cpm_interface/interface_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_interface 2023-04-28 05:57:44,340 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_iptables 2023-04-28 05:57:44,341 root INFO copying ansible_collections/wti/remote/playbooks/cpm_iptables/iptables_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_iptables 2023-04-28 05:57:44,341 root INFO copying ansible_collections/wti/remote/playbooks/cpm_iptables/iptables_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_iptables 2023-04-28 05:57:44,341 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_plugconfig 2023-04-28 05:57:44,341 root INFO copying ansible_collections/wti/remote/playbooks/cpm_plugconfig/plug_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_plugconfig 2023-04-28 05:57:44,341 root INFO copying ansible_collections/wti/remote/playbooks/cpm_plugconfig/plug_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_plugconfig 2023-04-28 05:57:44,342 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_plugcontrol 2023-04-28 05:57:44,342 root INFO copying ansible_collections/wti/remote/playbooks/cpm_plugcontrol/plug_control.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_plugcontrol 2023-04-28 05:57:44,342 root INFO copying ansible_collections/wti/remote/playbooks/cpm_plugcontrol/plug_control_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_plugcontrol 2023-04-28 05:57:44,342 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,342 root INFO copying ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_action_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,342 root INFO copying ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_action_set.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,343 root INFO copying ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,343 root INFO copying ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,343 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_snmp 2023-04-28 05:57:44,343 root INFO copying ansible_collections/wti/remote/playbooks/cpm_snmp/snmp_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_snmp 2023-04-28 05:57:44,343 root INFO copying ansible_collections/wti/remote/playbooks/cpm_snmp/snmp_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_snmp 2023-04-28 05:57:44,344 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,344 root INFO copying ansible_collections/wti/remote/playbooks/cpm_status/alarm_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,344 root INFO copying ansible_collections/wti/remote/playbooks/cpm_status/current_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,344 root INFO copying ansible_collections/wti/remote/playbooks/cpm_status/firmware_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,345 root INFO copying ansible_collections/wti/remote/playbooks/cpm_status/power_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,345 root INFO copying ansible_collections/wti/remote/playbooks/cpm_status/status_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,345 root INFO copying ansible_collections/wti/remote/playbooks/cpm_status/temp_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,345 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_client 2023-04-28 05:57:44,345 root INFO copying ansible_collections/wti/remote/playbooks/cpm_syslog_client/syslog_client_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_client 2023-04-28 05:57:44,346 root INFO copying ansible_collections/wti/remote/playbooks/cpm_syslog_client/syslog_client_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_client 2023-04-28 05:57:44,346 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_server 2023-04-28 05:57:44,346 root INFO copying ansible_collections/wti/remote/playbooks/cpm_syslog_server/syslog_server_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_server 2023-04-28 05:57:44,346 root INFO copying ansible_collections/wti/remote/playbooks/cpm_syslog_server/syslog_server_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_server 2023-04-28 05:57:44,346 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_time_date 2023-04-28 05:57:44,346 root INFO copying ansible_collections/wti/remote/playbooks/cpm_time_date/time_config.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_time_date 2023-04-28 05:57:44,347 root INFO copying ansible_collections/wti/remote/playbooks/cpm_time_date/time_info.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_time_date 2023-04-28 05:57:44,347 root INFO creating build/lib/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,347 root INFO copying ansible_collections/wti/remote/playbooks/cpm_user/user_add.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,347 root INFO copying ansible_collections/wti/remote/playbooks/cpm_user/user_delete.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,347 root INFO copying ansible_collections/wti/remote/playbooks/cpm_user/user_edit.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,348 root INFO copying ansible_collections/wti/remote/playbooks/cpm_user/user_get.yml -> build/lib/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,348 root INFO creating build/lib/ansible_collections/wti/remote/plugins 2023-04-28 05:57:44,348 root INFO creating build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,348 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_alarm_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,348 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_config_backup.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,349 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_config_restore.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,349 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_current_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,349 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_firmware_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,349 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_firmware_update.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,349 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_hostname_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,350 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_hostname_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,350 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_interface_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,350 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_interface_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,350 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_iptables_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,351 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_iptables_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,351 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_metering.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,351 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_plugconfig.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,351 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_plugcontrol.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,352 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_power_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,352 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_action_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,352 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_action_set.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,352 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,352 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,353 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_snmp_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,353 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_snmp_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,353 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_status.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,353 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_status_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,354 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_syslog_client_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,354 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_syslog_client_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,354 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_syslog_server_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,354 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_syslog_server_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,355 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_temp_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,355 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_time_config.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,355 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_time_info.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,355 root INFO copying ansible_collections/wti/remote/plugins/lookup/cpm_user.py -> build/lib/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,355 root INFO creating build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,356 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_alarm_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,356 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_config_backup.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,356 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_config_restore.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,356 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_current_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,356 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_firmware_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,357 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_firmware_update.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,357 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_hostname_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,357 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_hostname_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,357 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_interface_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,358 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_interface_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,358 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_iptables_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,358 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_iptables_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,358 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_plugconfig.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,358 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_plugcontrol.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,359 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_power_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,359 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_serial_port_action_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,359 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_serial_port_action_set.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,359 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_serial_port_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,360 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_serial_port_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,360 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_snmp_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,360 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_snmp_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,360 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_status_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,361 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_syslog_client_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,361 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_syslog_client_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,361 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_syslog_server_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,361 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_syslog_server_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,362 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_temp_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,362 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_time_config.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,362 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_time_info.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,362 root INFO copying ansible_collections/wti/remote/plugins/modules/cpm_user.py -> build/lib/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,388 wheel INFO installing to build/bdist.linux-x86_64/wheel 2023-04-28 05:57:44,388 root INFO running install 2023-04-28 05:57:44,396 root INFO running install_lib 2023-04-28 05:57:44,399 root INFO creating build/bdist.linux-x86_64 2023-04-28 05:57:44,399 root INFO creating build/bdist.linux-x86_64/wheel 2023-04-28 05:57:44,399 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections 2023-04-28 05:57:44,400 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks 2023-04-28 05:57:44,400 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,400 root INFO copying build/lib/ansible_collections/junipernetworks/junos/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,400 root INFO copying build/lib/ansible_collections/junipernetworks/junos/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,400 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins 2023-04-28 05:57:44,401 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/terminal 2023-04-28 05:57:44,401 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/terminal/junos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/terminal 2023-04-28 05:57:44,401 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/terminal 2023-04-28 05:57:44,401 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/doc_fragments 2023-04-28 05:57:44,401 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/doc_fragments/junos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/doc_fragments 2023-04-28 05:57:44,401 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/doc_fragments 2023-04-28 05:57:44,402 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/netconf 2023-04-28 05:57:44,402 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/netconf/junos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/netconf 2023-04-28 05:57:44,402 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/netconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/netconf 2023-04-28 05:57:44,402 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,402 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,403 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,403 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_security_policies_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,403 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_routing_instances.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,403 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_rpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,404 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,404 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,404 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,404 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,404 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,405 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,405 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,405 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,405 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,405 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_scp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,406 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,406 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,406 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,406 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_routing_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,406 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,407 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,407 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,407 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,407 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,408 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,408 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,408 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,408 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,409 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,409 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,409 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,409 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,409 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,410 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,410 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,410 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,410 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_security_zones.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,411 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,411 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,411 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_security_policies.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,411 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/modules/junos_snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/modules 2023-04-28 05:57:44,412 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/cliconf 2023-04-28 05:57:44,412 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/cliconf/junos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/cliconf 2023-04-28 05:57:44,412 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/cliconf 2023-04-28 05:57:44,412 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/action 2023-04-28 05:57:44,412 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/action/junos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/action 2023-04-28 05:57:44,413 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/action 2023-04-28 05:57:44,413 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils 2023-04-28 05:57:44,413 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils 2023-04-28 05:57:44,413 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network 2023-04-28 05:57:44,413 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos 2023-04-28 05:57:44,414 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts 2023-04-28 05:57:44,414 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans 2023-04-28 05:57:44,414 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans 2023-04-28 05:57:44,414 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans 2023-04-28 05:57:44,414 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes 2023-04-28 05:57:44,414 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes 2023-04-28 05:57:44,415 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes 2023-04-28 05:57:44,415 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies 2023-04-28 05:57:44,415 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies 2023-04-28 05:57:44,415 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/security_policies.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies 2023-04-28 05:57:44,415 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options 2023-04-28 05:57:44,416 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options 2023-04-28 05:57:44,416 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/routing_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options 2023-04-28 05:57:44,416 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2 2023-04-28 05:57:44,416 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2 2023-04-28 05:57:44,416 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2 2023-04-28 05:57:44,417 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts 2023-04-28 05:57:44,417 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces 2023-04-28 05:57:44,417 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces 2023-04-28 05:57:44,417 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces 2023-04-28 05:57:44,417 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family 2023-04-28 05:57:44,418 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family 2023-04-28 05:57:44,418 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family 2023-04-28 05:57:44,418 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global 2023-04-28 05:57:44,418 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global 2023-04-28 05:57:44,418 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/security_policies_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global 2023-04-28 05:57:44,419 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global 2023-04-28 05:57:44,419 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global 2023-04-28 05:57:44,419 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global 2023-04-28 05:57:44,419 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances 2023-04-28 05:57:44,419 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances 2023-04-28 05:57:44,420 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/routing_instances.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances 2023-04-28 05:57:44,420 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces 2023-04-28 05:57:44,420 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces 2023-04-28 05:57:44,420 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces 2023-04-28 05:57:44,420 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts 2023-04-28 05:57:44,421 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces 2023-04-28 05:57:44,421 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces 2023-04-28 05:57:44,421 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces 2023-04-28 05:57:44,421 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists 2023-04-28 05:57:44,421 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists 2023-04-28 05:57:44,421 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists 2023-04-28 05:57:44,422 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname 2023-04-28 05:57:44,422 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname 2023-04-28 05:57:44,422 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname 2023-04-28 05:57:44,422 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server 2023-04-28 05:57:44,422 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server 2023-04-28 05:57:44,423 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server 2023-04-28 05:57:44,423 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces 2023-04-28 05:57:44,423 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces 2023-04-28 05:57:44,423 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces 2023-04-28 05:57:44,423 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces 2023-04-28 05:57:44,424 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces 2023-04-28 05:57:44,424 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces 2023-04-28 05:57:44,424 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global 2023-04-28 05:57:44,424 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global 2023-04-28 05:57:44,424 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global 2023-04-28 05:57:44,425 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces 2023-04-28 05:57:44,425 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces 2023-04-28 05:57:44,425 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces 2023-04-28 05:57:44,425 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones 2023-04-28 05:57:44,425 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones 2023-04-28 05:57:44,426 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/security_zones.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones 2023-04-28 05:57:44,426 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy 2023-04-28 05:57:44,426 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy 2023-04-28 05:57:44,426 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy 2023-04-28 05:57:44,426 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces 2023-04-28 05:57:44,426 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces 2023-04-28 05:57:44,427 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces 2023-04-28 05:57:44,427 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global 2023-04-28 05:57:44,427 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global 2023-04-28 05:57:44,427 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global 2023-04-28 05:57:44,428 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global 2023-04-28 05:57:44,428 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global 2023-04-28 05:57:44,428 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global 2023-04-28 05:57:44,428 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces 2023-04-28 05:57:44,428 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces 2023-04-28 05:57:44,428 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces 2023-04-28 05:57:44,429 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp 2023-04-28 05:57:44,429 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp 2023-04-28 05:57:44,429 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp 2023-04-28 05:57:44,429 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3 2023-04-28 05:57:44,429 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3 2023-04-28 05:57:44,430 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3 2023-04-28 05:57:44,430 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls 2023-04-28 05:57:44,430 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls 2023-04-28 05:57:44,430 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls 2023-04-28 05:57:44,430 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/junos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos 2023-04-28 05:57:44,431 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils 2023-04-28 05:57:44,431 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils 2023-04-28 05:57:44,431 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils 2023-04-28 05:57:44,431 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos 2023-04-28 05:57:44,431 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config 2023-04-28 05:57:44,432 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans 2023-04-28 05:57:44,432 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans 2023-04-28 05:57:44,432 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans 2023-04-28 05:57:44,432 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes 2023-04-28 05:57:44,432 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes 2023-04-28 05:57:44,433 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes 2023-04-28 05:57:44,433 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies 2023-04-28 05:57:44,433 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies 2023-04-28 05:57:44,433 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/security_policies.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies 2023-04-28 05:57:44,433 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options 2023-04-28 05:57:44,434 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options 2023-04-28 05:57:44,434 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/routing_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options 2023-04-28 05:57:44,434 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2 2023-04-28 05:57:44,434 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2 2023-04-28 05:57:44,434 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2 2023-04-28 05:57:44,435 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces 2023-04-28 05:57:44,435 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces 2023-04-28 05:57:44,435 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces 2023-04-28 05:57:44,435 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family 2023-04-28 05:57:44,435 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family 2023-04-28 05:57:44,436 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family 2023-04-28 05:57:44,436 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global 2023-04-28 05:57:44,436 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global 2023-04-28 05:57:44,436 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/security_policies_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global 2023-04-28 05:57:44,436 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global 2023-04-28 05:57:44,436 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global 2023-04-28 05:57:44,437 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global 2023-04-28 05:57:44,437 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances 2023-04-28 05:57:44,437 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances 2023-04-28 05:57:44,437 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/routing_instances.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances 2023-04-28 05:57:44,437 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces 2023-04-28 05:57:44,438 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces 2023-04-28 05:57:44,438 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces 2023-04-28 05:57:44,438 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config 2023-04-28 05:57:44,438 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces 2023-04-28 05:57:44,438 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces 2023-04-28 05:57:44,439 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces 2023-04-28 05:57:44,439 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists 2023-04-28 05:57:44,439 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists 2023-04-28 05:57:44,439 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists 2023-04-28 05:57:44,439 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname 2023-04-28 05:57:44,440 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname 2023-04-28 05:57:44,440 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname 2023-04-28 05:57:44,440 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server 2023-04-28 05:57:44,440 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server 2023-04-28 05:57:44,440 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server 2023-04-28 05:57:44,441 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces 2023-04-28 05:57:44,441 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces 2023-04-28 05:57:44,441 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces 2023-04-28 05:57:44,441 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces 2023-04-28 05:57:44,441 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces 2023-04-28 05:57:44,441 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces 2023-04-28 05:57:44,442 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global 2023-04-28 05:57:44,442 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global 2023-04-28 05:57:44,442 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global 2023-04-28 05:57:44,442 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces 2023-04-28 05:57:44,442 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces 2023-04-28 05:57:44,443 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces 2023-04-28 05:57:44,443 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones 2023-04-28 05:57:44,443 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones 2023-04-28 05:57:44,443 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/security_zones.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones 2023-04-28 05:57:44,443 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces 2023-04-28 05:57:44,444 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces 2023-04-28 05:57:44,444 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces 2023-04-28 05:57:44,444 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global 2023-04-28 05:57:44,444 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global 2023-04-28 05:57:44,444 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global 2023-04-28 05:57:44,445 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global 2023-04-28 05:57:44,445 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global 2023-04-28 05:57:44,445 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global 2023-04-28 05:57:44,445 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces 2023-04-28 05:57:44,445 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces 2023-04-28 05:57:44,446 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces 2023-04-28 05:57:44,446 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp 2023-04-28 05:57:44,446 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp 2023-04-28 05:57:44,446 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp 2023-04-28 05:57:44,446 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3 2023-04-28 05:57:44,447 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3 2023-04-28 05:57:44,447 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3 2023-04-28 05:57:44,447 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls 2023-04-28 05:57:44,447 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls 2023-04-28 05:57:44,447 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls 2023-04-28 05:57:44,448 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec 2023-04-28 05:57:44,448 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans 2023-04-28 05:57:44,448 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans 2023-04-28 05:57:44,448 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans 2023-04-28 05:57:44,448 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes 2023-04-28 05:57:44,449 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes 2023-04-28 05:57:44,449 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes 2023-04-28 05:57:44,449 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies 2023-04-28 05:57:44,449 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies 2023-04-28 05:57:44,449 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/security_policies.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies 2023-04-28 05:57:44,450 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts 2023-04-28 05:57:44,450 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts 2023-04-28 05:57:44,450 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts 2023-04-28 05:57:44,450 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options 2023-04-28 05:57:44,450 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options 2023-04-28 05:57:44,451 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/routing_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options 2023-04-28 05:57:44,451 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2 2023-04-28 05:57:44,451 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2 2023-04-28 05:57:44,451 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2 2023-04-28 05:57:44,451 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces 2023-04-28 05:57:44,451 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces 2023-04-28 05:57:44,452 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces 2023-04-28 05:57:44,452 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family 2023-04-28 05:57:44,452 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family 2023-04-28 05:57:44,452 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family 2023-04-28 05:57:44,453 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global 2023-04-28 05:57:44,453 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global 2023-04-28 05:57:44,453 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/security_policies_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global 2023-04-28 05:57:44,453 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global 2023-04-28 05:57:44,453 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global 2023-04-28 05:57:44,453 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global 2023-04-28 05:57:44,454 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances 2023-04-28 05:57:44,454 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances 2023-04-28 05:57:44,454 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/routing_instances.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances 2023-04-28 05:57:44,454 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces 2023-04-28 05:57:44,454 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces 2023-04-28 05:57:44,455 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces 2023-04-28 05:57:44,455 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec 2023-04-28 05:57:44,455 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces 2023-04-28 05:57:44,455 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces 2023-04-28 05:57:44,455 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces 2023-04-28 05:57:44,456 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists 2023-04-28 05:57:44,456 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists 2023-04-28 05:57:44,456 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists 2023-04-28 05:57:44,456 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname 2023-04-28 05:57:44,456 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname 2023-04-28 05:57:44,456 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname 2023-04-28 05:57:44,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server 2023-04-28 05:57:44,457 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server 2023-04-28 05:57:44,457 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server 2023-04-28 05:57:44,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces 2023-04-28 05:57:44,457 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces 2023-04-28 05:57:44,458 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces 2023-04-28 05:57:44,458 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces 2023-04-28 05:57:44,458 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces 2023-04-28 05:57:44,458 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces 2023-04-28 05:57:44,458 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global 2023-04-28 05:57:44,459 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global 2023-04-28 05:57:44,459 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global 2023-04-28 05:57:44,459 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces 2023-04-28 05:57:44,459 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces 2023-04-28 05:57:44,459 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces 2023-04-28 05:57:44,460 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones 2023-04-28 05:57:44,460 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones 2023-04-28 05:57:44,460 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/security_zones.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones 2023-04-28 05:57:44,460 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces 2023-04-28 05:57:44,460 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces 2023-04-28 05:57:44,460 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces 2023-04-28 05:57:44,461 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global 2023-04-28 05:57:44,461 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global 2023-04-28 05:57:44,461 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global 2023-04-28 05:57:44,461 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global 2023-04-28 05:57:44,462 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global 2023-04-28 05:57:44,462 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global 2023-04-28 05:57:44,462 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces 2023-04-28 05:57:44,462 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces 2023-04-28 05:57:44,462 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces 2023-04-28 05:57:44,463 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp 2023-04-28 05:57:44,463 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp 2023-04-28 05:57:44,463 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp 2023-04-28 05:57:44,463 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3 2023-04-28 05:57:44,463 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3 2023-04-28 05:57:44,464 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3 2023-04-28 05:57:44,464 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls 2023-04-28 05:57:44,464 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls 2023-04-28 05:57:44,464 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls 2023-04-28 05:57:44,464 root INFO copying build/lib/ansible_collections/junipernetworks/junos/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/plugins/module_utils/network 2023-04-28 05:57:44,465 root INFO copying build/lib/ansible_collections/junipernetworks/junos/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,465 root INFO copying build/lib/ansible_collections/junipernetworks/junos/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,465 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/meta 2023-04-28 05:57:44,465 root INFO copying build/lib/ansible_collections/junipernetworks/junos/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/meta 2023-04-28 05:57:44,466 root INFO copying build/lib/ansible_collections/junipernetworks/junos/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,466 root INFO copying build/lib/ansible_collections/junipernetworks/junos/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,466 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/changelogs 2023-04-28 05:57:44,466 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/changelogs/fragments 2023-04-28 05:57:44,466 root INFO copying build/lib/ansible_collections/junipernetworks/junos/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/changelogs/fragments 2023-04-28 05:57:44,467 root INFO copying build/lib/ansible_collections/junipernetworks/junos/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/changelogs 2023-04-28 05:57:44,467 root INFO copying build/lib/ansible_collections/junipernetworks/junos/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos/changelogs 2023-04-28 05:57:44,467 root INFO copying build/lib/ansible_collections/junipernetworks/junos/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,467 root INFO copying build/lib/ansible_collections/junipernetworks/junos/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,467 root INFO copying build/lib/ansible_collections/junipernetworks/junos/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,468 root INFO copying build/lib/ansible_collections/junipernetworks/junos/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/junipernetworks/junos 2023-04-28 05:57:44,468 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure 2023-04-28 05:57:44,468 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,468 root INFO copying build/lib/ansible_collections/azure/azcollection/pr-pipelines.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,468 root INFO copying build/lib/ansible_collections/azure/azcollection/sanity-requirements-azure.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,469 root INFO copying build/lib/ansible_collections/azure/azcollection/requirements-azure.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,469 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins 2023-04-28 05:57:44,469 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:44,469 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/doc_fragments/azure.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:44,469 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/doc_fragments/azure_tags.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:44,470 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/doc_fragments/azure_rm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/doc_fragments 2023-04-28 05:57:44,470 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/inventory 2023-04-28 05:57:44,470 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/inventory/azure_rm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/inventory 2023-04-28 05:57:44,470 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,471 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_expressroute_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,471 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinesize_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,471 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationrunbook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,471 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatelinkservice.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,471 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlfirewallrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,472 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevicemodule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,472 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,472 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_networkinterface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,472 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_gallery_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,473 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointconnection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,473 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,473 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlfirewallrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,473 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultsecret_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,473 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_hostgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,474 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_diskencryptionset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,474 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqldatabase.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,474 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqldatabase_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,474 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,474 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlserver_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,475 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aduser_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,475 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothub_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,475 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistry_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,475 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_roleassignment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,475 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_autoscale.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,476 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cognitivesearch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,476 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,476 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_routetable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,476 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationaccount_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,477 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_notificationhub_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,477 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_azurefirewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,477 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_manageddisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,477 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_publicipaddress_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,477 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhubconnection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,478 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_recoveryservicesvault_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,478 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebustopicsubscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,478 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,478 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagementservice_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,478 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_openshiftmanagedcluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,479 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerinstance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,479 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebus.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,479 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_ipgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,479 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_applicationsecuritygroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,480 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_loganalyticsworkspace_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,480 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlfirewallrule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,480 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_bastionhost.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,480 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cognitivesearch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,480 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetextension_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,481 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualmachine_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,481 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksversion_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,481 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_backuppolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,481 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifact_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,481 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_lock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,482 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualmachine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,482 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineextension.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,482 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,482 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_securitygroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,483 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitorlogprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,483 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrywebhook_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,483 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlelasticpool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,483 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescaleset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,483 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_publicipaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,484 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aduser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,484 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerendpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,484 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,484 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscache_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,485 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,485 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_roleassignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,485 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,485 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_autoscale_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,485 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,486 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetextension.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,486 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adserviceprincipal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,486 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqldatabase_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,486 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabschedule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,486 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetinstance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,487 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,487 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbconfiguration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,487 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adpassword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,487 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cosmosdbaccount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,488 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,488 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnprofile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,488 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,488 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,488 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitordiagnosticsetting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,489 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_hdinsightcluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,489 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageaccount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,489 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationrunbook_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,489 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrytag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,490 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimageversion_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,490 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhub_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,490 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_webapp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,490 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_securitygroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,491 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistryreplication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,491 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifactsource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,491 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_ipgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,491 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,491 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_backuppolicy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,492 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvault.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,492 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_loadbalancer_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,492 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_vmbackuppolicy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,492 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitordiagnosticsetting_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,492 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlelasticpool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,493 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_subnet_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,493 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkpeering.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,493 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_datalakestore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,493 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevice_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,494 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_manageddisk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,494 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationassignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,494 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsitelink_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,494 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualnetwork.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,494 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_firewallpolicy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,495 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbfirewallrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,495 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,495 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatelinkservice_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,495 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothub.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,496 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_ddosprotectionplan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,496 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlconfiguration_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,496 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_applicationsecuritygroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,496 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachine_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,496 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_eventhub_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,497 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_roledefinition_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,497 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_recoveryservicesvault.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,497 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednsrecordset_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,497 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultkey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,498 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevice.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,498 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbfirewallrule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,498 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsite_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,498 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabenvironment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,498 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_resource_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,499 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_diskencryptionset_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,499 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlfirewallrule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,499 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_hdinsightcluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,499 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_openshiftmanagedcluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,499 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnszone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,500 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsite.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,500 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,500 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothubconsumergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,500 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_functionapp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,501 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabcustomimage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,501 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkgateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,501 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqldatabase.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,501 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbdatabase_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,501 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationaccount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,502 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_routetable_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,502 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_loganalyticsworkspace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,502 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageaccount_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,502 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_vmbackuppolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,502 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_resourcegroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,503 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbdatabase.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,503 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlfirewallrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,503 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,503 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagement_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,504 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationassignment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,504 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerprofile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,504 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebussaspolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,505 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultsecret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,505 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkpeering_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,505 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrytag_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,505 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlconfiguration_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,505 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_subscription_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,506 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlfirewallrule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,506 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabarmtemplate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,506 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagementservice.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,506 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappaccessrestriction.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,506 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlmanagedinstance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,507 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_natgateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,507 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbserver_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,507 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adserviceprincipal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,507 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscachefirewallrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,508 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageblob.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,508 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_appserviceplan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,508 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnendpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,508 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageshare_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,508 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_webapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,509 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetinstance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,509 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappvnetconnection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,509 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_proximityplacementgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,509 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_ddosprotectionplan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,510 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerinstance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,510 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_deployment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,510 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbconfiguration_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,510 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabenvironment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,510 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebusqueue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,511 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrywebhook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,511 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnendpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,511 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlserver_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,511 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_appgateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,511 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_natgateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,512 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednsrecordset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,512 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_roledefinition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,512 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_firewallpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,512 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabcustomimage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,513 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszonelink.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,513 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabpolicy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,513 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualwan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,513 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappaccessrestriction_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,513 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualnetwork_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,514 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappvnetconnection_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,514 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_appserviceplan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,514 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_multiplemanageddisks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,514 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_lock_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,514 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlconfiguration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,515 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,515 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_appgateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,515 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_availabilityset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,516 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,516 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_availabilityset_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,516 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvault_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,516 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_backupazurevm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,516 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimageversion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,517 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,517 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhubconnection_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,517 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,517 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistryreplication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,518 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_batchaccount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,518 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_resourcegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,518 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescaleset_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,518 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnsrecordset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,518 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualwan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,519 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlmanagedinstance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,519 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlab_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,519 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,519 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_gallery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,520 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adapplication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,520 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_managementgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,520 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_eventhub.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,520 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_networkinterface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,520 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszonelink_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,521 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagement.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,521 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointdnszonegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,521 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cosmosdbaccount_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,521 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageshare.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,522 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifactsource_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,522 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnsrecordset_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,522 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,522 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_hostgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,522 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationdefinition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,523 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_functionapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,523 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_notificationhub.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,523 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_datalakestore_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,523 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerendpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,524 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_azurefirewall_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,524 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpoolversion_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,524 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,524 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqldatabase.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,524 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabschedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,525 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aks_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,525 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,525 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhub.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,525 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_proximityplacementgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,526 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_datafactory_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,526 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_route_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,526 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,526 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_datafactory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,527 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,527 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineextension_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,527 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_bastionhost_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,527 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlconfiguration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,527 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,528 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,528 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineimage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,528 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebustopic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,528 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksupgrade_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,529 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_backupazurevm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,529 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_managementgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,529 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlserver_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,529 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationdefinition_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,529 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_loadbalancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,530 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappslot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,530 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,530 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointdnszonegroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,530 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_account_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,531 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointconnection_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,531 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adapplication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,531 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqldatabase_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,531 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnszone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,531 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adpassword_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,532 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_expressroute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,532 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebus_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,532 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_adgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,532 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/modules/azure_rm_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/modules 2023-04-28 05:57:44,533 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:44,533 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:44,533 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common_rest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:44,533 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common_ext.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/module_utils 2023-04-28 05:57:44,533 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/lookup 2023-04-28 05:57:44,534 root INFO copying build/lib/ansible_collections/azure/azcollection/plugins/lookup/azure_keyvault_secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/plugins/lookup 2023-04-28 05:57:44,534 root INFO copying build/lib/ansible_collections/azure/azcollection/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,534 root INFO copying build/lib/ansible_collections/azure/azcollection/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,535 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/meta 2023-04-28 05:57:44,535 root INFO copying build/lib/ansible_collections/azure/azcollection/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/meta 2023-04-28 05:57:44,535 root INFO copying build/lib/ansible_collections/azure/azcollection/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection/meta 2023-04-28 05:57:44,535 root INFO copying build/lib/ansible_collections/azure/azcollection/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,535 root INFO copying build/lib/ansible_collections/azure/azcollection/CHANGELOG.md -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,536 root INFO copying build/lib/ansible_collections/azure/azcollection/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,536 root INFO copying build/lib/ansible_collections/azure/azcollection/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,536 root INFO copying build/lib/ansible_collections/azure/azcollection/release-pipelines.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,536 root INFO copying build/lib/ansible_collections/azure/azcollection/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,537 root INFO copying build/lib/ansible_collections/azure/azcollection/CredScanSuppressions.json -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,537 root INFO copying build/lib/ansible_collections/azure/azcollection/shippable.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,537 root INFO copying build/lib/ansible_collections/azure/azcollection/azure-pipelines.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/azure/azcollection 2023-04-28 05:57:44,537 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr 2023-04-28 05:57:44,537 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,538 root INFO copying build/lib/ansible_collections/frr/frr/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,538 root INFO copying build/lib/ansible_collections/frr/frr/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,538 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins 2023-04-28 05:57:44,538 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/terminal 2023-04-28 05:57:44,538 root INFO copying build/lib/ansible_collections/frr/frr/plugins/terminal/frr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/terminal 2023-04-28 05:57:44,538 root INFO copying build/lib/ansible_collections/frr/frr/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/terminal 2023-04-28 05:57:44,539 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:44,539 root INFO copying build/lib/ansible_collections/frr/frr/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:44,539 root INFO copying build/lib/ansible_collections/frr/frr/plugins/modules/frr_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:44,539 root INFO copying build/lib/ansible_collections/frr/frr/plugins/modules/frr_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/modules 2023-04-28 05:57:44,539 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/cliconf 2023-04-28 05:57:44,540 root INFO copying build/lib/ansible_collections/frr/frr/plugins/cliconf/frr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/cliconf 2023-04-28 05:57:44,540 root INFO copying build/lib/ansible_collections/frr/frr/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/cliconf 2023-04-28 05:57:44,540 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils 2023-04-28 05:57:44,540 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils 2023-04-28 05:57:44,540 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network 2023-04-28 05:57:44,541 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr 2023-04-28 05:57:44,541 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:44,541 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:44,541 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/providers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:44,541 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli 2023-04-28 05:57:44,541 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli 2023-04-28 05:57:44,542 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config 2023-04-28 05:57:44,542 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:44,542 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:44,542 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:44,542 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:44,543 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/process.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp 2023-04-28 05:57:44,543 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config 2023-04-28 05:57:44,543 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config 2023-04-28 05:57:44,543 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers 2023-04-28 05:57:44,543 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/frr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr 2023-04-28 05:57:44,544 root INFO copying build/lib/ansible_collections/frr/frr/plugins/module_utils/network/frr/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/plugins/module_utils/network/frr 2023-04-28 05:57:44,544 root INFO copying build/lib/ansible_collections/frr/frr/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,544 root INFO copying build/lib/ansible_collections/frr/frr/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,544 root INFO copying build/lib/ansible_collections/frr/frr/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,544 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/meta 2023-04-28 05:57:44,544 root INFO copying build/lib/ansible_collections/frr/frr/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/meta 2023-04-28 05:57:44,545 root INFO copying build/lib/ansible_collections/frr/frr/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,545 root INFO copying build/lib/ansible_collections/frr/frr/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,545 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/changelogs 2023-04-28 05:57:44,545 root INFO copying build/lib/ansible_collections/frr/frr/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/changelogs 2023-04-28 05:57:44,545 root INFO copying build/lib/ansible_collections/frr/frr/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr/changelogs 2023-04-28 05:57:44,546 root INFO copying build/lib/ansible_collections/frr/frr/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,546 root INFO copying build/lib/ansible_collections/frr/frr/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,546 root INFO copying build/lib/ansible_collections/frr/frr/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,546 root INFO copying build/lib/ansible_collections/frr/frr/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/frr/frr 2023-04-28 05:57:44,546 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/gluster 2023-04-28 05:57:44,547 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster 2023-04-28 05:57:44,547 root INFO copying build/lib/ansible_collections/gluster/gluster/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster 2023-04-28 05:57:44,547 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/plugins 2023-04-28 05:57:44,547 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:44,547 root INFO copying build/lib/ansible_collections/gluster/gluster/plugins/modules/gluster_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:44,548 root INFO copying build/lib/ansible_collections/gluster/gluster/plugins/modules/geo_rep.py -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:44,548 root INFO copying build/lib/ansible_collections/gluster/gluster/plugins/modules/gluster_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:44,548 root INFO copying build/lib/ansible_collections/gluster/gluster/plugins/modules/gluster_heal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/plugins/modules 2023-04-28 05:57:44,548 root INFO copying build/lib/ansible_collections/gluster/gluster/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster 2023-04-28 05:57:44,548 root INFO copying build/lib/ansible_collections/gluster/gluster/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster 2023-04-28 05:57:44,549 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/meta 2023-04-28 05:57:44,549 root INFO copying build/lib/ansible_collections/gluster/gluster/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/meta 2023-04-28 05:57:44,549 root INFO copying build/lib/ansible_collections/gluster/gluster/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster 2023-04-28 05:57:44,549 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/changelogs 2023-04-28 05:57:44,549 root INFO copying build/lib/ansible_collections/gluster/gluster/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/changelogs 2023-04-28 05:57:44,549 root INFO copying build/lib/ansible_collections/gluster/gluster/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster/changelogs 2023-04-28 05:57:44,550 root INFO copying build/lib/ansible_collections/gluster/gluster/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/gluster/gluster 2023-04-28 05:57:44,550 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible 2023-04-28 05:57:44,550 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,550 root INFO copying build/lib/ansible_collections/ansible/utils/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,550 root INFO copying build/lib/ansible_collections/ansible/utils/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,551 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins 2023-04-28 05:57:44,551 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins 2023-04-28 05:57:44,551 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/validate 2023-04-28 05:57:44,551 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/validate/jsonschema.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/validate 2023-04-28 05:57:44,551 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/validate/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/validate 2023-04-28 05:57:44,552 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff 2023-04-28 05:57:44,552 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff/native.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff 2023-04-28 05:57:44,552 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,552 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/xml_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,552 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/textfsm_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,552 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/ttp_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,553 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/json_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,553 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,553 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv6_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,553 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/subnet_of.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,553 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,554 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv4_hostmask.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,554 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv4_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,554 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/loopback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,554 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,554 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/public.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,555 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/in_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,555 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/private.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,555 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv6_sixtofour.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,555 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv4_netmask.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,555 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ip_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,556 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv6_teredo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,556 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/mac.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,556 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/reserved.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,556 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,556 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/in_any_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,557 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/unspecified.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,557 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/in_one_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,557 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/resolvable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,557 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ipv6_ipv4_mapped.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,557 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,558 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/multicast.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,558 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/test/supernet_of.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/test 2023-04-28 05:57:44,558 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,558 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/ipmath.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,558 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/keep_keys.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,559 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,559 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/ipsubnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,559 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/index_of.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,559 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/ip4_hex.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,559 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/get_path.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,560 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,560 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/cidr_merge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,560 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/usable_range.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,560 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/ipaddr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,560 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/param_list_compare.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,561 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/nthhost.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,561 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/from_xml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,561 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/ipwrap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,561 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/previous_nth_usable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,561 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/ipv4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,562 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/to_xml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,562 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/macaddr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,562 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/network_in_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,562 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/hwaddr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,562 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/reduce_on_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,563 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/consolidate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,563 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/replace_keys.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,563 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/slaac.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,563 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/next_nth_usable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,563 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/network_in_usable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,564 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/to_paths.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,564 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/filter/remove_keys.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/filter 2023-04-28 05:57:44,564 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:44,564 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/modules/validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:44,564 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/modules/fact_diff.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:44,565 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/modules/cli_parse.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:44,565 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/modules/update_fact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/modules 2023-04-28 05:57:44,565 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,565 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/keep_keys.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,565 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/index_of.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,566 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:44,566 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base/ipaddr_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:44,566 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base/validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:44,566 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:44,566 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base/fact_diff.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:44,567 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base/cli_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:44,567 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/base/ipaddress_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils/base 2023-04-28 05:57:44,567 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/from_xml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,567 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/to_xml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,567 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/connection_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,568 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/consolidate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,568 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/replace_keys.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,568 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/plugin_utils/remove_keys.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/plugin_utils 2023-04-28 05:57:44,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:44,568 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/action/validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:44,569 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/action/fact_diff.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:44,569 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/action/cli_parse.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:44,569 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/action/update_fact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/action 2023-04-28 05:57:44,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/module_utils 2023-04-28 05:57:44,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:44,570 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/module_utils/common/get_path.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:44,570 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/module_utils/common/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:44,570 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/module_utils/common/argspec_validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:44,570 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/module_utils/common/to_paths.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/module_utils/common 2023-04-28 05:57:44,570 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:44,571 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/lookup/index_of.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:44,571 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/lookup/get_path.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:44,571 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/lookup/validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:44,571 root INFO copying build/lib/ansible_collections/ansible/utils/plugins/lookup/to_paths.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/plugins/lookup 2023-04-28 05:57:44,571 root INFO copying build/lib/ansible_collections/ansible/utils/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,572 root INFO copying build/lib/ansible_collections/ansible/utils/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,572 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/meta 2023-04-28 05:57:44,572 root INFO copying build/lib/ansible_collections/ansible/utils/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/meta 2023-04-28 05:57:44,572 root INFO copying build/lib/ansible_collections/ansible/utils/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,573 root INFO copying build/lib/ansible_collections/ansible/utils/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,573 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:44,573 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/changelogs/fragments 2023-04-28 05:57:44,573 root INFO copying build/lib/ansible_collections/ansible/utils/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/changelogs/fragments 2023-04-28 05:57:44,573 root INFO copying build/lib/ansible_collections/ansible/utils/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:44,573 root INFO copying build/lib/ansible_collections/ansible/utils/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:44,574 root INFO copying build/lib/ansible_collections/ansible/utils/changelogs/cli_parse_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils/changelogs 2023-04-28 05:57:44,574 root INFO copying build/lib/ansible_collections/ansible/utils/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,574 root INFO copying build/lib/ansible_collections/ansible/utils/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,574 root INFO copying build/lib/ansible_collections/ansible/utils/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,574 root INFO copying build/lib/ansible_collections/ansible/utils/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/utils 2023-04-28 05:57:44,575 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,575 root INFO copying build/lib/ansible_collections/ansible/posix/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,575 root INFO copying build/lib/ansible_collections/ansible/posix/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,575 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins 2023-04-28 05:57:44,575 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,576 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/json.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,576 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/profile_roles.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,576 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/profile_tasks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,576 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/jsonl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,576 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,577 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/skippy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,577 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/timer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,577 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/cgroup_perf_recap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,577 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/callback/debug.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/callback 2023-04-28 05:57:44,578 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,578 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/synchronize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,578 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/firewalld.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,578 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/sysctl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,578 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/rhel_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,579 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/patch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,579 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,579 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/selinux.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,579 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/mount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,579 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,580 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/firewalld_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,580 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/authorized_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,580 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/rhel_rpm_ostree.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,580 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/at.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,580 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/rpm_ostree_upgrade.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,581 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/modules/seboolean.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/modules 2023-04-28 05:57:44,581 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:44,581 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/action/synchronize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:44,581 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/action/patch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:44,581 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/action 2023-04-28 05:57:44,582 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:44,582 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/shell/fish.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:44,582 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/shell/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:44,582 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/shell/csh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/shell 2023-04-28 05:57:44,582 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:44,583 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/module_utils/firewalld.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:44,583 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:44,583 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/module_utils/mount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:44,583 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:44,583 root INFO copying build/lib/ansible_collections/ansible/posix/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/plugins/module_utils 2023-04-28 05:57:44,584 root INFO copying build/lib/ansible_collections/ansible/posix/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,584 root INFO copying build/lib/ansible_collections/ansible/posix/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,584 root INFO copying build/lib/ansible_collections/ansible/posix/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,584 root INFO copying build/lib/ansible_collections/ansible/posix/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,584 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/meta 2023-04-28 05:57:44,585 root INFO copying build/lib/ansible_collections/ansible/posix/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/meta 2023-04-28 05:57:44,585 root INFO copying build/lib/ansible_collections/ansible/posix/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,585 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/hacking 2023-04-28 05:57:44,585 root INFO copying build/lib/ansible_collections/ansible/posix/hacking/cgroup_perf_recap_graph.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/hacking 2023-04-28 05:57:44,585 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/changelogs 2023-04-28 05:57:44,586 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/changelogs/fragments 2023-04-28 05:57:44,586 root INFO copying build/lib/ansible_collections/ansible/posix/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/changelogs/fragments 2023-04-28 05:57:44,586 root INFO copying build/lib/ansible_collections/ansible/posix/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/changelogs 2023-04-28 05:57:44,586 root INFO copying build/lib/ansible_collections/ansible/posix/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix/changelogs 2023-04-28 05:57:44,586 root INFO copying build/lib/ansible_collections/ansible/posix/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,587 root INFO copying build/lib/ansible_collections/ansible/posix/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,587 root INFO copying build/lib/ansible_collections/ansible/posix/shippable.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,587 root INFO copying build/lib/ansible_collections/ansible/posix/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/posix 2023-04-28 05:57:44,587 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,587 root INFO copying build/lib/ansible_collections/ansible/netcommon/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,588 root INFO copying build/lib/ansible_collections/ansible/netcommon/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,588 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins 2023-04-28 05:57:44,588 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins 2023-04-28 05:57:44,588 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc 2023-04-28 05:57:44,588 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc 2023-04-28 05:57:44,588 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,589 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/content_templates_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,589 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/native_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,589 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/ntc_templates_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,589 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/pyats_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser 2023-04-28 05:57:44,589 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/filter 2023-04-28 05:57:44,590 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/filter/network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/filter 2023-04-28 05:57:44,590 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/doc_fragments 2023-04-28 05:57:44,590 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/doc_fragments/connection_persistent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/doc_fragments 2023-04-28 05:57:44,590 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/doc_fragments/network_agnostic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/doc_fragments 2023-04-28 05:57:44,590 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/netconf 2023-04-28 05:57:44,591 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/netconf/default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/netconf 2023-04-28 05:57:44,591 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:44,591 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/connection/network_cli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:44,591 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/connection/libssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:44,591 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/connection/netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:44,592 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/connection/grpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:44,592 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/connection/persistent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:44,592 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/connection/httpapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/connection 2023-04-28 05:57:44,592 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,592 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/netconf_rpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,593 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/restconf_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,593 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/cli_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,593 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/netconf_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,593 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/restconf_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,593 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/netconf_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,594 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/telnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,594 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/net_put.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,594 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/net_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,594 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/net_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,594 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/network_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,595 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/grpc_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,595 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/cli_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,595 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/modules/grpc_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/modules 2023-04-28 05:57:44,595 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:44,595 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils/httpapi_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:44,596 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils/cliconf_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:44,596 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils/netconf_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:44,596 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils/connection_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:44,596 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:44,596 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/plugin_utils/terminal_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/plugin_utils 2023-04-28 05:57:44,597 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,597 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,597 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/cli_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,597 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,598 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/telnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,598 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/net_put.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,598 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/net_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,598 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/net_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,598 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/grpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,598 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/network_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,599 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/action/cli_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/action 2023-04-28 05:57:44,599 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/httpapi 2023-04-28 05:57:44,599 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/httpapi/restconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/httpapi 2023-04-28 05:57:44,599 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils 2023-04-28 05:57:44,599 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/utils 2023-04-28 05:57:44,600 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/utils/data.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/utils 2023-04-28 05:57:44,600 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser 2023-04-28 05:57:44,600 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/cli_parsertemplate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser 2023-04-28 05:57:44,600 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/cli_parserbase.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser 2023-04-28 05:57:44,600 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network 2023-04-28 05:57:44,601 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc 2023-04-28 05:57:44,601 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc/grpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc 2023-04-28 05:57:44,601 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf 2023-04-28 05:57:44,601 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf/restconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf 2023-04-28 05:57:44,601 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf 2023-04-28 05:57:44,601 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf/netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf 2023-04-28 05:57:44,602 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,602 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,602 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts 2023-04-28 05:57:44,602 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts 2023-04-28 05:57:44,602 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,603 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,603 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,603 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/parsing.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,603 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/resource_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,603 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common 2023-04-28 05:57:44,604 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:44,604 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/network_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:44,604 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/resource_module_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:44,604 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/resource_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base 2023-04-28 05:57:44,605 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg 2023-04-28 05:57:44,605 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg 2023-04-28 05:57:44,605 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/become 2023-04-28 05:57:44,605 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/become/enable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/become 2023-04-28 05:57:44,605 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/cache 2023-04-28 05:57:44,605 root INFO copying build/lib/ansible_collections/ansible/netcommon/plugins/cache/memory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/plugins/cache 2023-04-28 05:57:44,606 root INFO copying build/lib/ansible_collections/ansible/netcommon/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,606 root INFO copying build/lib/ansible_collections/ansible/netcommon/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,606 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/meta 2023-04-28 05:57:44,606 root INFO copying build/lib/ansible_collections/ansible/netcommon/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/meta 2023-04-28 05:57:44,607 root INFO copying build/lib/ansible_collections/ansible/netcommon/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,607 root INFO copying build/lib/ansible_collections/ansible/netcommon/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,607 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/LICENSES 2023-04-28 05:57:44,607 root INFO copying build/lib/ansible_collections/ansible/netcommon/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/LICENSES 2023-04-28 05:57:44,607 root INFO copying build/lib/ansible_collections/ansible/netcommon/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/LICENSES 2023-04-28 05:57:44,608 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:44,608 root INFO copying build/lib/ansible_collections/ansible/netcommon/changelogs/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:44,608 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/changelogs/fragments 2023-04-28 05:57:44,608 root INFO copying build/lib/ansible_collections/ansible/netcommon/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/changelogs/fragments 2023-04-28 05:57:44,608 root INFO copying build/lib/ansible_collections/ansible/netcommon/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:44,609 root INFO copying build/lib/ansible_collections/ansible/netcommon/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon/changelogs 2023-04-28 05:57:44,609 root INFO copying build/lib/ansible_collections/ansible/netcommon/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,609 root INFO copying build/lib/ansible_collections/ansible/netcommon/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,609 root INFO copying build/lib/ansible_collections/ansible/netcommon/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,609 root INFO copying build/lib/ansible_collections/ansible/netcommon/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/netcommon 2023-04-28 05:57:44,610 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows 2023-04-28 05:57:44,610 root INFO copying build/lib/ansible_collections/ansible/windows/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows 2023-04-28 05:57:44,610 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins 2023-04-28 05:57:44,610 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:44,610 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:44,610 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/filter/quote.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:44,611 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/filter/quote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/filter 2023-04-28 05:57:44,611 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/doc_fragments 2023-04-28 05:57:44,611 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/doc_fragments 2023-04-28 05:57:44,611 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/doc_fragments/web_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/doc_fragments 2023-04-28 05:57:44,611 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,612 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_domain_membership.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,612 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_updates.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,612 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_acl_inheritance.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,612 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_group_membership.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,613 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_user_right.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,613 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_package.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,613 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_share.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,613 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_service.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,613 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_reg_stat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,614 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_wait_for.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,614 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_environment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,614 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_whoami.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,614 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_shell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,614 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,615 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/setup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,615 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_tempfile.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,615 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_find.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,615 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_certificate_store.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,615 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_share.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,616 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,616 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_owner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,616 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_regedit.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,616 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_group.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,617 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,617 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_feature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,617 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_domain_membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,617 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/slurp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,617 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_path.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,618 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_certificate_store.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,618 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_dsc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,618 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_shell.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,618 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/setup.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,618 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_powershell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,619 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_stat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,619 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_owner.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,619 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,619 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,619 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,620 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_domain.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,620 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,620 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,620 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_get_url.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,620 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,621 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_command.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,621 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_hostname.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,621 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/async_status.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,621 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_regedit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,621 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_acl.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,622 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_reg_stat.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,622 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_dns_client.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,622 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_feature.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,622 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/slurp.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,622 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_user_right.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,623 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_service_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,623 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_optional_feature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,623 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/async_status.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,623 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,623 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_tempfile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,624 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_user.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,624 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,624 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_stat.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,624 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,625 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_dsc.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,625 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_ping.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,625 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,625 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_uri.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,625 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_optional_feature.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,626 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_dns_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,626 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,626 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_get_url.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,626 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_updates.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,626 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_whoami.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,627 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_group_membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,627 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_uri.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,627 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_acl_inheritance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,627 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_domain_controller.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,627 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_wait_for.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,628 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_copy.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,628 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_environment.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,628 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_powershell.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,628 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,629 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_domain_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,629 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_file.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,629 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_path.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,630 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/modules/win_find.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/modules 2023-04-28 05:57:44,630 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:44,630 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/plugin_utils/_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:44,630 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/plugin_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:44,630 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/plugin_utils/_quote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/plugin_utils 2023-04-28 05:57:44,631 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:44,631 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/action/win_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:44,631 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:44,631 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/action/win_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:44,631 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/action/win_updates.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:44,632 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/action/win_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/action 2023-04-28 05:57:44,632 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:44,632 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/module_utils/SCManager.cs -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:44,632 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/module_utils/Process.cs -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:44,633 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:44,633 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/module_utils/Process.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:44,633 root INFO copying build/lib/ansible_collections/ansible/windows/plugins/module_utils/WebRequest.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/plugins/module_utils 2023-04-28 05:57:44,633 root INFO copying build/lib/ansible_collections/ansible/windows/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows 2023-04-28 05:57:44,633 root INFO copying build/lib/ansible_collections/ansible/windows/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows 2023-04-28 05:57:44,634 root INFO copying build/lib/ansible_collections/ansible/windows/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows 2023-04-28 05:57:44,634 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/meta 2023-04-28 05:57:44,634 root INFO copying build/lib/ansible_collections/ansible/windows/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/meta 2023-04-28 05:57:44,634 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/changelogs 2023-04-28 05:57:44,635 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/changelogs/fragments 2023-04-28 05:57:44,635 root INFO copying build/lib/ansible_collections/ansible/windows/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/changelogs/fragments 2023-04-28 05:57:44,635 root INFO copying build/lib/ansible_collections/ansible/windows/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/changelogs 2023-04-28 05:57:44,635 root INFO copying build/lib/ansible_collections/ansible/windows/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows/changelogs 2023-04-28 05:57:44,635 root INFO copying build/lib/ansible_collections/ansible/windows/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ansible/windows 2023-04-28 05:57:44,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana 2023-04-28 05:57:44,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana 2023-04-28 05:57:44,636 root INFO copying build/lib/ansible_collections/grafana/grafana/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana 2023-04-28 05:57:44,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins 2023-04-28 05:57:44,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,636 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/cloud_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,637 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/dashboard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,637 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/cloud_stack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,637 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/alert_contact_point.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,637 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/alert_notification_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,637 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/datasource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,638 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/cloud_api_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,638 root INFO copying build/lib/ansible_collections/grafana/grafana/plugins/modules/folder.py -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/plugins/modules 2023-04-28 05:57:44,638 root INFO copying build/lib/ansible_collections/grafana/grafana/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana 2023-04-28 05:57:44,638 root INFO copying build/lib/ansible_collections/grafana/grafana/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana 2023-04-28 05:57:44,639 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/meta 2023-04-28 05:57:44,639 root INFO copying build/lib/ansible_collections/grafana/grafana/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/meta 2023-04-28 05:57:44,639 root INFO copying build/lib/ansible_collections/grafana/grafana/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana 2023-04-28 05:57:44,639 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:44,639 root INFO copying build/lib/ansible_collections/grafana/grafana/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:44,639 root INFO copying build/lib/ansible_collections/grafana/grafana/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:44,640 root INFO copying build/lib/ansible_collections/grafana/grafana/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/changelogs 2023-04-28 05:57:44,640 root INFO copying build/lib/ansible_collections/grafana/grafana/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana 2023-04-28 05:57:44,640 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles 2023-04-28 05:57:44,640 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent 2023-04-28 05:57:44,640 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent/tasks 2023-04-28 05:57:44,641 root INFO copying build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent/tasks 2023-04-28 05:57:44,641 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent/defaults 2023-04-28 05:57:44,641 root INFO copying build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent/defaults 2023-04-28 05:57:44,641 root INFO copying build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent 2023-04-28 05:57:44,641 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent/meta 2023-04-28 05:57:44,641 root INFO copying build/lib/ansible_collections/grafana/grafana/roles/grafana_agent/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/grafana/grafana/roles/grafana_agent/meta 2023-04-28 05:57:44,642 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes 2023-04-28 05:57:44,642 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,642 root INFO copying build/lib/ansible_collections/kubernetes/core/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,642 root INFO copying build/lib/ansible_collections/kubernetes/core/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,642 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins 2023-04-28 05:57:44,643 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/filter 2023-04-28 05:57:44,643 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/filter/k8s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/filter 2023-04-28 05:57:44,643 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/filter/k8s_config_resource_name.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/filter 2023-04-28 05:57:44,643 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,643 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_delete_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,644 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_scale_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,644 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_auth_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,644 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_resource_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,644 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,644 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/helm_common_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,645 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_wait_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,645 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_name_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,645 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_state_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/doc_fragments 2023-04-28 05:57:44,645 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/inventory 2023-04-28 05:57:44,645 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/inventory/k8s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/inventory 2023-04-28 05:57:44,646 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/connection 2023-04-28 05:57:44,646 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/connection/kubectl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/connection 2023-04-28 05:57:44,646 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,646 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_taint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,646 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/helm_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,647 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/helm_pull.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,647 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/helm_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,647 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/helm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,647 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_scale.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,647 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_exec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,648 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,648 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/helm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,648 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/helm_plugin_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,648 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,648 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,649 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_drain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,649 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,649 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,649 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/helm_repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,650 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_json_patch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,650 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,650 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,650 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/modules/k8s_cp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/modules 2023-04-28 05:57:44,650 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,651 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/helm_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,651 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/ks8_json_patch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,651 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/helm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,651 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_scale.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,651 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_exec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,652 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,652 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/helm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,652 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/helm_plugin_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,652 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,652 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_drain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,653 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,653 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,653 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/helm_repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,653 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,653 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,654 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/action/k8s_cp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/action 2023-04-28 05:57:44,654 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,654 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,654 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,654 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,655 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/helm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,655 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/args_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,655 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,655 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/client 2023-04-28 05:57:44,655 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/client/discovery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/client 2023-04-28 05:57:44,656 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/client/resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/client 2023-04-28 05:57:44,656 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,656 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/apply.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,656 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/hashes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,656 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/helm_args_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,657 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,657 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s/core.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,657 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s/exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,657 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s/waiter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,657 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s/resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,658 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s/client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,658 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s/runner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,658 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8s/service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils/k8s 2023-04-28 05:57:44,658 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,659 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/ansiblemodule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,659 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/k8sdynamicclient.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,659 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/module_utils 2023-04-28 05:57:44,659 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/lookup 2023-04-28 05:57:44,659 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/lookup/kustomize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/lookup 2023-04-28 05:57:44,659 root INFO copying build/lib/ansible_collections/kubernetes/core/plugins/lookup/k8s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/plugins/lookup 2023-04-28 05:57:44,660 root INFO copying build/lib/ansible_collections/kubernetes/core/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,660 root INFO copying build/lib/ansible_collections/kubernetes/core/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,660 root INFO copying build/lib/ansible_collections/kubernetes/core/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,660 root INFO copying build/lib/ansible_collections/kubernetes/core/setup.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,661 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/meta 2023-04-28 05:57:44,661 root INFO copying build/lib/ansible_collections/kubernetes/core/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/meta 2023-04-28 05:57:44,661 root INFO copying build/lib/ansible_collections/kubernetes/core/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,661 root INFO copying build/lib/ansible_collections/kubernetes/core/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,661 root INFO copying build/lib/ansible_collections/kubernetes/core/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,662 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/changelogs 2023-04-28 05:57:44,662 root INFO copying build/lib/ansible_collections/kubernetes/core/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/changelogs 2023-04-28 05:57:44,662 root INFO copying build/lib/ansible_collections/kubernetes/core/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core/changelogs 2023-04-28 05:57:44,662 root INFO copying build/lib/ansible_collections/kubernetes/core/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,662 root INFO copying build/lib/ansible_collections/kubernetes/core/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,663 root INFO copying build/lib/ansible_collections/kubernetes/core/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,663 root INFO copying build/lib/ansible_collections/kubernetes/core/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,663 root INFO copying build/lib/ansible_collections/kubernetes/core/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/kubernetes/core 2023-04-28 05:57:44,663 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch 2023-04-28 05:57:44,663 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,664 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,664 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins 2023-04-28 05:57:44,664 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments 2023-04-28 05:57:44,664 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments 2023-04-28 05:57:44,664 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/api_parameters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments 2023-04-28 05:57:44,665 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/inventory 2023-04-28 05:57:44,665 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/inventory/inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/inventory 2023-04-28 05:57:44,665 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/inventory 2023-04-28 05:57:44,665 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,665 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,665 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,666 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,666 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,666 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,666 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/server_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,667 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/custom_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,667 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/objects_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,667 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/modules/floating_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/modules 2023-04-28 05:57:44,667 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/module_utils 2023-04-28 05:57:44,667 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/plugins/module_utils/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/plugins/module_utils 2023-04-28 05:57:44,668 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,668 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,668 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,668 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,668 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/meta 2023-04-28 05:57:44,669 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/meta 2023-04-28 05:57:44,669 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,669 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:44,669 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:44,669 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/changelogs/fragments 2023-04-28 05:57:44,670 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/changelogs/fragments 2023-04-28 05:57:44,670 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:44,670 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud/changelogs 2023-04-28 05:57:44,670 root INFO copying build/lib/ansible_collections/cloudscale_ch/cloud/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cloudscale_ch/cloud 2023-04-28 05:57:44,670 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware 2023-04-28 05:57:44,670 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,671 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/modules.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,671 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,671 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,671 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins 2023-04-28 05:57:44,671 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/doc_fragments 2023-04-28 05:57:44,672 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/doc_fragments 2023-04-28 05:57:44,672 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/doc_fragments/moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/doc_fragments 2023-04-28 05:57:44,672 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,672 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,672 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,673 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_localfilesystem_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,673 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_host_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,673 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datacenter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,673 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_domains.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,674 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_resourcepool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,674 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_identity_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,674 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_globalfips_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,674 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_parallel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,674 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,675 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_power.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,675 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datastore_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,675 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,675 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_noproxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,675 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_folder_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,676 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_timesync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,676 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv4_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,676 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_system_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,676 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_ethernet_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,676 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_databasestorage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,677 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_memory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,677 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,677 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,677 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_consolecli_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,677 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_sata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,678 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_floppy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,678 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_hostname_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,678 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_dcui_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,678 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/content_subscribedlibrary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,679 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,679 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_globalfips.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,679 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_operations_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,679 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_ntp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,679 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_filesystem_directories.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,680 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_firewall_inbound_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,680 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_floppy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,680 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_storage_policies_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,680 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,680 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cdrom_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,681 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_domains_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,681 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_power.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,681 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,681 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cpu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,681 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_consolecli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,682 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_ethernet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,682 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,682 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vmtemplate_libraryitems.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,682 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_database_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,683 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_noproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,683 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_applmgmt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,683 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_monitoring_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,683 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_compliance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,683 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,684 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/content_subscribedlibrary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,684 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,684 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_routes_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,684 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_scsi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,684 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,685 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_monitoring_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,685 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_parallel_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,685 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,685 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_shutdown_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,685 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,686 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_power_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,686 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_globalpolicy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,686 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_libraryitem_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,686 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_infraprofile_configs_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,687 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_swap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,687 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,687 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,687 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datacenter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,687 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_softwarepackages_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,688 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,688 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cdrom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,688 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,688 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_services_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,688 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,689 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,689 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,689 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_timezone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,689 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_interfaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,689 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_shutdown.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,690 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/content_locallibrary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,690 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv6_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,690 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_sata_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,690 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_shell_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,691 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_dcui.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,691 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_globalpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,691 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_vmon_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,691 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_serial_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,691 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,692 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_serial.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,692 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_ssh_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,692 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_scsi_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,692 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_mem_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,692 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_load_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,693 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,693 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_installer_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,693 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_shell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,693 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/content_locallibrary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,694 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_infraprofile_configs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,694 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cpu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,694 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,694 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_vmon_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,694 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,695 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_resourcepool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,695 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_customization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,695 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/content_configuration_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,695 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_timesync_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,695 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,696 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_storage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,696 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_storage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,696 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_firewall_inbound.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,696 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_servers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,697 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_installer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,697 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_ovf_libraryitem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,697 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_servers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,697 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,697 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_timezone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,698 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,698 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,698 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,698 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/content_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,699 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vmtemplate_libraryitems_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,699 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,699 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,699 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_power_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,699 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_compliance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,700 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/appliance_update_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,700 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/content_library_item_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,700 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_memory_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/modules 2023-04-28 05:57:44,700 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/plugin_utils 2023-04-28 05:57:44,700 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/plugin_utils/lookup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/plugin_utils 2023-04-28 05:57:44,701 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/module_utils 2023-04-28 05:57:44,701 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/module_utils/vmware_rest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/module_utils 2023-04-28 05:57:44,701 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,701 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/vm_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,701 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/host_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,702 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/datastore_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,702 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/network_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,702 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/datacenter_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,702 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/cluster_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,702 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/folder_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,703 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/plugins/lookup/resource_pool_moid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/plugins/lookup 2023-04-28 05:57:44,703 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/docs-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,703 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,703 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,704 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/meta 2023-04-28 05:57:44,704 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/meta 2023-04-28 05:57:44,704 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,704 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/dev.md -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,704 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual 2023-04-28 05:57:44,705 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,705 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/conf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,705 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios 2023-04-28 05:57:44,705 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,705 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/system_managment.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,705 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/network.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,706 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/appliance_access.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,706 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/services.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,706 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/health.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance 2023-04-28 05:57:44,706 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,706 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/6_run_a_vm.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,707 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/4_vm_info.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,707 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/2_collect_information.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,707 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/3_create_vm.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,707 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/5_vm_hardware_tuning.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,707 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/7_vm_tool_information.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,708 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/8_vm_tool_configuration.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,708 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/1_authentication.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,708 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/1_installation.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter 2023-04-28 05:57:44,708 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/guide_vmware_rest.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,708 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/export_to_ansible_ansible.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,709 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/index.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,709 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/.rstcheck.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,709 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/manual/source/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/manual/source 2023-04-28 05:57:44,709 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs 2023-04-28 05:57:44,709 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,710 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/cloud.common-bump.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,710 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/allow_space_in_search_filters.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,710 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/use-FQCN-in-create_vm.yaml.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,710 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/vcenter_network_info-dvs-example.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,710 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/2.1.3-module_utils.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,711 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/lookup-handle-special-chars.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,711 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/2.1.3-changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,711 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/version_added.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,711 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/set_default_galaxy_version.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,711 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/fragments/vm_template_library.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs/fragments 2023-04-28 05:57:44,712 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs 2023-04-28 05:57:44,712 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest/changelogs 2023-04-28 05:57:44,712 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,712 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,712 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,713 root INFO copying build/lib/ansible_collections/vmware/vmware_rest/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/vmware/vmware_rest 2023-04-28 05:57:44,713 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries 2023-04-28 05:57:44,713 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,713 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,713 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/Jenkinsfile.blackduck -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,714 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins 2023-04-28 05:57:44,714 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments 2023-04-28 05:57:44,714 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/santricity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments 2023-04-28 05:57:44,714 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments 2023-04-28 05:57:44,714 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,714 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,715 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_firmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,715 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_mgmt_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,715 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,715 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,716 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,716 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_nvme_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,716 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_drive_firmware_upload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,716 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,717 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,717 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_alerts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,717 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_volume_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,717 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,717 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_client_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,718 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_firmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,718 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_iscsi_target.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,718 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_asup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,718 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_flashcache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,718 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,719 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_storagepool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,719 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_drive_firmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,719 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,719 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,720 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_hostgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,720 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_drive_firmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,720 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_alerts_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,720 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_lun_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,721 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_storagepool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,721 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_discover.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,721 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,721 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_asup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,721 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,722 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_ib_iser_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,722 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,722 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_firmware_upload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,722 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_iscsi_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,722 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,723 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_server_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,723 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,723 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_mgmt_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,723 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_alerts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,724 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_auditlog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,724 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,724 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,724 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_auditlog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,725 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_hostgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,725 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_iscsi_target.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,725 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_images.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,725 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_storage_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,725 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,726 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_systems.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,726 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,726 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,726 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_iscsi_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,727 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_lun_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/modules 2023-04-28 05:57:44,727 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/module_utils 2023-04-28 05:57:44,727 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/module_utils/santricity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/module_utils 2023-04-28 05:57:44,727 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/module_utils/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/module_utils 2023-04-28 05:57:44,727 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:44,728 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:44,728 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:44,728 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_host_detail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:44,728 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_storage_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:44,728 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_lun_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/plugins/lookup 2023-04-28 05:57:44,729 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,729 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,729 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,729 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/vars/setupBlackduckBuildParameters.groovy -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,730 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/vars/setupBuildParameters.groovy -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,730 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/vars/hubScan.groovy -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,730 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/vars/hubPreCheck.groovy -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,730 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/vars/hubScanProject.groovy -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,730 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/vars/hubScanDocker.groovy -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,730 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/vars/setupSynopsysDetect.groovy -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/vars 2023-04-28 05:57:44,731 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,731 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/meta 2023-04-28 05:57:44,731 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/meta 2023-04-28 05:57:44,731 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/eseries-ansible-collections-diagram.png -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,732 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,732 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,732 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:44,732 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:44,732 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:44,733 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/changelogs 2023-04-28 05:57:44,733 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity 2023-04-28 05:57:44,733 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles 2023-04-28 05:57:44,733 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management 2023-04-28 05:57:44,733 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:44,733 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/logging.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:44,734 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/security.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:44,734 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/firmware.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:44,734 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/interface.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:44,734 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:44,734 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/system.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks 2023-04-28 05:57:44,735 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/defaults 2023-04-28 05:57:44,735 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/defaults 2023-04-28 05:57:44,735 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management 2023-04-28 05:57:44,735 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/meta 2023-04-28 05:57:44,736 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/meta 2023-04-28 05:57:44,736 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/.travis.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management 2023-04-28 05:57:44,736 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common 2023-04-28 05:57:44,736 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:44,736 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:44,736 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/validate_system_api_url.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:44,737 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/prefer_proxy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:44,737 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/discovery.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:44,737 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/prefer_embedded.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts 2023-04-28 05:57:44,737 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/proxy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:44,737 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/proxy_security.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:44,738 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:44,738 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/build_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks 2023-04-28 05:57:44,738 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/defaults 2023-04-28 05:57:44,738 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/defaults 2023-04-28 05:57:44,738 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common 2023-04-28 05:57:44,739 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/meta 2023-04-28 05:57:44,739 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/meta 2023-04-28 05:57:44,739 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/.travis.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common 2023-04-28 05:57:44,739 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host 2023-04-28 05:57:44,739 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,740 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:44,740 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:44,740 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/rollback.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:44,740 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/view.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot 2023-04-28 05:57:44,740 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,741 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/volume.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,741 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/storage_pool_present.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,741 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:44,741 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/iscsi.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:44,741 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/ib_iser.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:44,742 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/nvme_ib.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:44,742 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/nvme_roce.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface 2023-04-28 05:57:44,742 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,742 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,742 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/initiator.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,743 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/lun_mapping.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,743 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/storage_pool_absent.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks 2023-04-28 05:57:44,743 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/defaults 2023-04-28 05:57:44,743 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/defaults 2023-04-28 05:57:44,743 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host 2023-04-28 05:57:44,744 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates 2023-04-28 05:57:44,744 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates/initiatorname_iscsi.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates 2023-04-28 05:57:44,744 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates/hostnqn.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates 2023-04-28 05:57:44,744 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/meta 2023-04-28 05:57:44,744 root INFO copying build/lib/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/meta 2023-04-28 05:57:44,745 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox 2023-04-28 05:57:44,745 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,745 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,745 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins 2023-04-28 05:57:44,745 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins 2023-04-28 05:57:44,746 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/doc_fragments 2023-04-28 05:57:44,746 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/doc_fragments/nios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/doc_fragments 2023-04-28 05:57:44,746 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/inventory 2023-04-28 05:57:44,746 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/inventory/nios_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/inventory 2023-04-28 05:57:44,746 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,746 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_fixed_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,747 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,747 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_nsgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,747 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_srv_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,747 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,748 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_network_view.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,748 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,748 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_dns_view.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,748 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,748 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_mx_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,749 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_ptr_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,749 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_naptr_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,749 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_cname_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,749 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_txt_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,749 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_aaaa_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,750 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_a_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,750 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_host_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,750 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_lbdn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,750 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,750 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/modules/nios_restartservices.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/modules 2023-04-28 05:57:44,751 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/module_utils 2023-04-28 05:57:44,751 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/module_utils/network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/module_utils 2023-04-28 05:57:44,751 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/module_utils/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/module_utils 2023-04-28 05:57:44,751 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:44,751 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/lookup/nios_lookup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:44,752 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/lookup/nios_next_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:44,752 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/plugins/lookup/nios_next_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/plugins/lookup 2023-04-28 05:57:44,752 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,752 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,752 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,753 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/meta 2023-04-28 05:57:44,753 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/meta 2023-04-28 05:57:44,753 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,753 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,753 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_cname_record.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,754 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/delete_mx_record.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,754 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_dtc_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,754 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_dtc_server.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,755 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/restart_services.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,755 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/delete_dnsview.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,755 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_a_record.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,755 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/update_a_record.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,755 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/delete_network_view.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,756 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_dtc_lbdn.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,756 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_mx_record.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,756 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_network_view.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,756 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/delete_txt_record.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,756 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_txt_record.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,757 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_zone.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,757 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/delete_zone.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,757 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/delete_cname_record.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,757 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/delete_network.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,757 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_dns_view.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,758 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/playbooks/create_network.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/playbooks 2023-04-28 05:57:44,758 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:44,758 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:44,758 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:44,758 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules/changelogs 2023-04-28 05:57:44,759 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,759 root INFO copying build/lib/ansible_collections/infoblox/nios_modules/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/infoblox/nios_modules 2023-04-28 05:57:44,759 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey 2023-04-28 05:57:44,759 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:44,759 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins 2023-04-28 05:57:44,759 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins 2023-04-28 05:57:44,760 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,760 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_feature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,760 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,760 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,760 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,761 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,761 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_config.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,761 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,761 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_feature.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,761 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_source.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,762 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_facts.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/modules 2023-04-28 05:57:44,762 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:44,762 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils/Common.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:44,762 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils/Sources.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:44,762 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils/Features.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:44,763 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils/Packages.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:44,763 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/plugins/module_utils/Config.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/plugins/module_utils 2023-04-28 05:57:44,763 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:44,763 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:44,764 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/meta 2023-04-28 05:57:44,764 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/meta 2023-04-28 05:57:44,764 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:44,764 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:44,764 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:44,764 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:44,765 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey/changelogs 2023-04-28 05:57:44,765 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:44,765 root INFO copying build/lib/ansible_collections/chocolatey/chocolatey/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/chocolatey/chocolatey 2023-04-28 05:57:44,765 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft 2023-04-28 05:57:44,765 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,766 root INFO copying build/lib/ansible_collections/microsoft/ad/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins 2023-04-28 05:57:44,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/doc_fragments 2023-04-28 05:57:44,766 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/doc_fragments/ad_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/doc_fragments 2023-04-28 05:57:44,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,767 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,767 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/domain_controller.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,767 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/membership.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,767 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,767 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/ou.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,768 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,768 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,768 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/offline_join.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,768 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/object_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,768 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/object.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,769 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/group.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,769 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/object_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,769 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,769 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/ou.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,769 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/offline_join.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,770 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/user.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,770 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/computer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,770 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/domain_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,770 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/domain.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,770 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/modules/computer.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/modules 2023-04-28 05:57:44,771 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:44,771 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/plugin_utils/_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:44,771 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/plugin_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:44,771 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/plugin_utils/_module_with_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/plugin_utils 2023-04-28 05:57:44,771 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:44,772 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/action/domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:44,772 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:44,772 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/action/membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:44,772 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/action/domain_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/action 2023-04-28 05:57:44,772 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/module_utils 2023-04-28 05:57:44,773 root INFO copying build/lib/ansible_collections/microsoft/ad/plugins/module_utils/_ADObject.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/plugins/module_utils 2023-04-28 05:57:44,773 root INFO copying build/lib/ansible_collections/microsoft/ad/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,773 root INFO copying build/lib/ansible_collections/microsoft/ad/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,773 root INFO copying build/lib/ansible_collections/microsoft/ad/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,773 root INFO copying build/lib/ansible_collections/microsoft/ad/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,774 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/meta 2023-04-28 05:57:44,774 root INFO copying build/lib/ansible_collections/microsoft/ad/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/meta 2023-04-28 05:57:44,774 root INFO copying build/lib/ansible_collections/microsoft/ad/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,774 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/changelogs 2023-04-28 05:57:44,774 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/changelogs/fragments 2023-04-28 05:57:44,775 root INFO copying build/lib/ansible_collections/microsoft/ad/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/changelogs/fragments 2023-04-28 05:57:44,775 root INFO copying build/lib/ansible_collections/microsoft/ad/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/changelogs 2023-04-28 05:57:44,775 root INFO copying build/lib/ansible_collections/microsoft/ad/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad/changelogs 2023-04-28 05:57:44,775 root INFO copying build/lib/ansible_collections/microsoft/ad/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/microsoft/ad 2023-04-28 05:57:44,775 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon 2023-04-28 05:57:44,775 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,776 root INFO copying build/lib/ansible_collections/amazon/aws/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,776 root INFO copying build/lib/ansible_collections/amazon/aws/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins 2023-04-28 05:57:44,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:44,777 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/doc_fragments/aws.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:44,777 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/doc_fragments/aws_credentials.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:44,777 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/doc_fragments/aws_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:44,777 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/doc_fragments/ec2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:44,777 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/doc_fragments/tags.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:44,778 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/doc_fragments/boto3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/doc_fragments 2023-04-28 05:57:44,778 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/inventory 2023-04-28 05:57:44,778 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/inventory/aws_rds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/inventory 2023-04-28 05:57:44,778 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/inventory/aws_ec2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/inventory 2023-04-28 05:57:44,778 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/callback 2023-04-28 05:57:44,779 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/callback/aws_resource_actions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/callback 2023-04-28 05:57:44,779 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,779 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_route_table_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,779 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_tag_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,779 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_net_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,780 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_spot_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,780 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/lambda_execute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,780 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_nat_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,780 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,781 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/autoscaling_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,781 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/aws_az_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,781 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,781 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_net.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,781 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_igw_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,782 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/lambda_event.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,782 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,782 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_security_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,782 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,783 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/autoscaling_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,783 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_instance_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,783 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_route_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,783 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/iam_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,784 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,784 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_cluster_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,784 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,784 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,784 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudwatchevent_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,785 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/lambda.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,785 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,785 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,785 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/kms_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,786 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/elb_application_lb_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,786 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_dhcp_option_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,786 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/elb_classic_lb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,786 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudformation_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,787 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_eni_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,787 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/iam_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,787 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_eip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,787 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/s3_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,788 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudtrail_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,788 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_nat_gateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,788 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_param_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,788 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/s3_object_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,788 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/route53.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,789 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,789 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_subnet_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,789 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/route53_health_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,789 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_option_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,790 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/lambda_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,790 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_security_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,790 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,790 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/iam_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,790 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/aws_caller_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,791 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_spot_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,791 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vol_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,791 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,791 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group_metric_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,791 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_eni.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,792 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/route53_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,792 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_dhcp_option.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,792 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_igw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,792 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,793 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,793 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudwatch_metric_alarm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,793 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_metadata_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,793 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/lambda_alias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,793 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudwatch_metric_alarm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,794 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/iam_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,794 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_subnet_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,794 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/route53_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,794 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/elb_application_lb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,795 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,795 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/rds_option_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,795 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudformation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,795 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_ami.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,796 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_ami_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,796 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/s3_bucket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,796 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/cloudtrail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,796 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,796 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/lambda_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,797 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/kms_key_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,797 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,797 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_eip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,797 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/modules/ec2_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/modules 2023-04-28 05:57:44,798 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/action 2023-04-28 05:57:44,798 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/action/s3_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/action 2023-04-28 05:57:44,798 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,798 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/cloudfront_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,798 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/transformation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,799 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/cloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,799 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/urls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,799 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/core.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,799 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/botocore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,799 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/batch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,800 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/s3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,800 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/rds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,800 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/ec2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,800 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/elb_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,800 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/waiters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,801 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/route53.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,801 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/waf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,801 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/tower.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,801 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,801 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,802 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/acm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,802 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/modules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,802 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/direct_connect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,802 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,803 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,803 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/arn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,803 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/retries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,803 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/iam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,803 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/module_utils/elbv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/module_utils 2023-04-28 05:57:44,804 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:44,804 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/lookup/aws_ssm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:44,804 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/lookup/aws_secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:44,804 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/lookup/aws_service_ip_ranges.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:44,804 root INFO copying build/lib/ansible_collections/amazon/aws/plugins/lookup/aws_account_attribute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/plugins/lookup 2023-04-28 05:57:44,805 root INFO copying build/lib/ansible_collections/amazon/aws/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,805 root INFO copying build/lib/ansible_collections/amazon/aws/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,805 root INFO copying build/lib/ansible_collections/amazon/aws/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/meta 2023-04-28 05:57:44,806 root INFO copying build/lib/ansible_collections/amazon/aws/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/meta 2023-04-28 05:57:44,806 root INFO copying build/lib/ansible_collections/amazon/aws/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,806 root INFO copying build/lib/ansible_collections/amazon/aws/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/changelogs 2023-04-28 05:57:44,807 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/changelogs/fragments 2023-04-28 05:57:44,807 root INFO copying build/lib/ansible_collections/amazon/aws/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/changelogs/fragments 2023-04-28 05:57:44,807 root INFO copying build/lib/ansible_collections/amazon/aws/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/changelogs 2023-04-28 05:57:44,807 root INFO copying build/lib/ansible_collections/amazon/aws/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws/changelogs 2023-04-28 05:57:44,807 root INFO copying build/lib/ansible_collections/amazon/aws/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,808 root INFO copying build/lib/ansible_collections/amazon/aws/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,808 root INFO copying build/lib/ansible_collections/amazon/aws/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,808 root INFO copying build/lib/ansible_collections/amazon/aws/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/amazon/aws 2023-04-28 05:57:44,808 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx 2023-04-28 05:57:44,808 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test 2023-04-28 05:57:44,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,809 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,809 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_token.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,809 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,809 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_job_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,810 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_credential_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,810 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,810 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,810 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,810 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,811 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_workflow_job_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,811 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_label.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,811 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_workflow_job_template_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,811 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_module_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,812 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_bulk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,812 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_completeness.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,812 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_application.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,812 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_instance_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,812 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_team.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,813 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,813 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_job.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,813 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,813 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/conftest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,813 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_notification_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,814 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_ad_hoc_wait.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,814 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_credential_input_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,814 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_inventory_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,814 root INFO copying build/lib/ansible_collections/awx/awx/test/awx/test_organization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/test/awx 2023-04-28 05:57:44,814 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins 2023-04-28 05:57:44,815 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:44,815 root INFO copying build/lib/ansible_collections/awx/awx/plugins/doc_fragments/auth_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:44,815 root INFO copying build/lib/ansible_collections/awx/awx/plugins/doc_fragments/auth_legacy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:44,815 root INFO copying build/lib/ansible_collections/awx/awx/plugins/doc_fragments/auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/doc_fragments 2023-04-28 05:57:44,815 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/inventory 2023-04-28 05:57:44,816 root INFO copying build/lib/ansible_collections/awx/awx/plugins/inventory/controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/inventory 2023-04-28 05:57:44,816 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,816 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/credential_input_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,816 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/application.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,816 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/bulk_job_launch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,817 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,817 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/inventory_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,817 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/project_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,817 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/token.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,817 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,818 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/credential_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,818 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,818 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,818 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/subscriptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,818 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/bulk_host_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,819 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,819 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/label.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,819 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/ad_hoc_command_wait.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,819 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,819 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,820 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/ad_hoc_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,820 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/ad_hoc_command_cancel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,820 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/job_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,820 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,820 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/workflow_job_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,821 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/job_launch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,821 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/workflow_job_template_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,821 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/inventory_source_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,821 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/job_wait.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,821 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/organization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,822 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,822 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,822 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/workflow_approval.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,822 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/workflow_node_wait.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,822 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/notification_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,823 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/controller_meta.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,823 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/license.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,823 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/workflow_launch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,823 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/execution_environment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,823 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/team.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,824 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/job_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,824 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/job_cancel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,824 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/instance_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,824 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,824 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,825 root INFO copying build/lib/ansible_collections/awx/awx/plugins/modules/host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/modules 2023-04-28 05:57:44,825 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:44,825 root INFO copying build/lib/ansible_collections/awx/awx/plugins/module_utils/controller_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:44,825 root INFO copying build/lib/ansible_collections/awx/awx/plugins/module_utils/tower_legacy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:44,826 root INFO copying build/lib/ansible_collections/awx/awx/plugins/module_utils/awxkit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/module_utils 2023-04-28 05:57:44,826 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:44,826 root INFO copying build/lib/ansible_collections/awx/awx/plugins/lookup/controller_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:44,826 root INFO copying build/lib/ansible_collections/awx/awx/plugins/lookup/schedule_rrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:44,826 root INFO copying build/lib/ansible_collections/awx/awx/plugins/lookup/schedule_rruleset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/plugins/lookup 2023-04-28 05:57:44,827 root INFO copying build/lib/ansible_collections/awx/awx/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,827 root INFO copying build/lib/ansible_collections/awx/awx/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,827 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/images 2023-04-28 05:57:44,827 root INFO copying build/lib/ansible_collections/awx/awx/images/completeness_test_output.png -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/images 2023-04-28 05:57:44,828 root INFO copying build/lib/ansible_collections/awx/awx/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,828 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/meta 2023-04-28 05:57:44,828 root INFO copying build/lib/ansible_collections/awx/awx/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx/meta 2023-04-28 05:57:44,829 root INFO copying build/lib/ansible_collections/awx/awx/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,829 root INFO copying build/lib/ansible_collections/awx/awx/TESTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,829 root INFO copying build/lib/ansible_collections/awx/awx/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,829 root INFO copying build/lib/ansible_collections/awx/awx/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/awx/awx 2023-04-28 05:57:44,829 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks 2023-04-28 05:57:44,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:44,830 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:44,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins 2023-04-28 05:57:44,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/terminal 2023-04-28 05:57:44,830 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/terminal/bigip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/terminal 2023-04-28 05:57:44,831 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:44,831 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:44,831 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/filter/abspath.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:44,831 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/filter/markdev.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/filter 2023-04-28 05:57:44,831 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:44,831 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:44,832 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:44,832 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5_rest_cli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/doc_fragments 2023-04-28 05:57:44,832 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,832 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_https_waf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,833 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,833 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_ocsp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,833 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,833 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_fetch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,834 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_connectivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,834 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,834 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_tcp_half_open.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,834 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_oracle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,835 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snat_translation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,835 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,835 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_snmp_dca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,835 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http_compression.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,835 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_policy_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,836 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_https.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,836 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_key_cert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,836 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,836 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,837 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,837 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_imish_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,837 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_service_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,837 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,838 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_tcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,838 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,838 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cli_alias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,838 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,838 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,839 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_lx_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,839 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_traffic_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,839 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_license.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,839 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_advanced_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,840 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_dos_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,840 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_icmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,840 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_httpd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,840 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_routedomain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,840 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_group_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,841 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_traffic_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,841 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_firepass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,841 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,841 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,842 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,842 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,842 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ucs_fetch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,842 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_virtual_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,842 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,844 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,844 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_wide_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,844 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cgnat_lsn_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,844 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_gateway_icmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,845 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_udp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,845 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_datacenter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,845 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp_echo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,845 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_device_discovery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,845 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_port_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,846 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,846 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,846 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_router.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,846 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,847 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_transport_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,847 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_mysql.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,847 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ike_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,847 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,848 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ltm_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,848 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_universal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,848 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_virtual_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,848 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp_trap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,848 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_password_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,849 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_qkview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,849 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,849 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_sshd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,849 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_utility_license_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,850 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_trust.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,850 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_log_profile_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,850 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_resolver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,850 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,851 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_sip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,851 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_policy_fetch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,851 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_wait.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,851 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_data_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,851 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ucs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,852 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_pool_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,852 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_provision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,852 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_cookie.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,852 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_global_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,853 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,853 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,853 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,853 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_log_destination.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,854 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,854 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_analytics.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,854 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,854 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,854 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_signature_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,855 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fastl4_tcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,855 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_protocol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,855 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,855 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_network_globals.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,856 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_oneconnect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,856 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_ha_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,856 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,856 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_management_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,857 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,857 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_server_ssl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,857 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_vcmp_guest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,857 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_dos_vector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,858 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ipsec_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,858 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_license_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,858 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_external.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,858 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_configsync_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,858 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_https.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,859 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_rule_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,859 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_iapp_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,859 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_network_access.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,859 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_topology_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,860 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_src_addr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,860 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_trunk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,860 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_radius.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,860 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_client_ssl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,861 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,861 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,861 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,861 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,862 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,862 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_timer_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,862 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_log_publisher.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,862 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_selfip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,863 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_cache_resolver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,863 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_log_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,863 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_manage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,863 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fastl4_udp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,864 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_partition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,864 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp_half_open.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,864 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,864 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_external.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,864 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_daemon_log_tmm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,865 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_license.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,865 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,865 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_irule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,865 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,866 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_file_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,866 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cli_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,866 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,866 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,866 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,867 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_bigip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,867 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_db.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,867 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,867 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,868 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,868 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,868 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_dos_application.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,868 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,869 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,869 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_tcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,869 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fasthttp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,869 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_dns_listener.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,870 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,870 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snat_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,870 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_server_technology.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,870 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,870 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,871 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_utility_license.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,871 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,871 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_virtual_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,871 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_address_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,872 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_policy_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,872 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_csr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,872 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_iapp_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,873 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,873 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,873 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_pool_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,873 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_topology_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,873 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,874 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,874 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_udp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,874 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,874 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_nameserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,875 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_https_offload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,875 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_fastl4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/modules 2023-04-28 05:57:44,875 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:44,875 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/action/bigip_imish_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:44,876 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/action/bigip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:44,876 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:44,876 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/action/bigiq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/action 2023-04-28 05:57:44,876 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,876 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,877 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/urls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,877 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/bigip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,877 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/teem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,877 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,877 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/ipaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,878 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/bigiq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,878 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/compare.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,878 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/icontrol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,878 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,878 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/module_utils/constants.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/module_utils 2023-04-28 05:57:44,879 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:44,879 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/lookup/license_hopper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:44,879 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/lookup/bigiq_license.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:44,879 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/plugins/lookup/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/plugins/lookup 2023-04-28 05:57:44,880 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:44,880 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:44,880 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/meta 2023-04-28 05:57:44,880 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/meta 2023-04-28 05:57:44,881 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:44,881 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/changelogs/fragments 2023-04-28 05:57:44,881 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/changelogs/fragments/.gitkeep -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/changelogs/fragments 2023-04-28 05:57:44,881 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:44,881 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:44,882 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules/changelogs 2023-04-28 05:57:44,882 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:44,882 root INFO copying build/lib/ansible_collections/f5networks/f5_modules/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/f5networks/f5_modules 2023-04-28 05:57:44,882 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti 2023-04-28 05:57:44,882 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote 2023-04-28 05:57:44,883 root INFO copying build/lib/ansible_collections/wti/remote/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote 2023-04-28 05:57:44,883 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins 2023-04-28 05:57:44,883 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,883 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_syslog_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,883 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_time_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,884 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_firmware_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,884 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_syslog_client_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,884 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,884 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_serial_port_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,884 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_config_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,885 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_plugconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,885 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_interface_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,885 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_iptables_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,885 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_power_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,885 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_time_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,886 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,886 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_alarm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,886 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_firmware_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,886 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_hostname_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,887 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_current_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,887 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_syslog_client_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,887 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,887 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_config_restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,887 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_hostname_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,888 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_serial_port_action_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,888 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_plugcontrol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,888 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_syslog_server_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,888 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_temp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,888 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_snmp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,889 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_snmp_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,889 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_serial_port_action_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,889 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_serial_port_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,889 root INFO copying build/lib/ansible_collections/wti/remote/plugins/modules/cpm_iptables_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/modules 2023-04-28 05:57:44,889 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,890 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_syslog_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,890 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_time_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,890 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,890 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_firmware_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,890 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_syslog_client_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,891 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,891 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_metering.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,891 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,891 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_config_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,891 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_plugconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,892 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_interface_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,892 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_iptables_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,892 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_power_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,892 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_time_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,892 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,893 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_alarm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,893 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_firmware_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,893 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_hostname_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,893 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_current_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,893 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_syslog_client_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,894 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,894 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_config_restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,894 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_hostname_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,894 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_action_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,895 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_plugcontrol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,895 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_syslog_server_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,895 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_temp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,895 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_snmp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,895 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_snmp_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,896 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_action_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,896 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,896 root INFO copying build/lib/ansible_collections/wti/remote/plugins/lookup/cpm_iptables_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/plugins/lookup 2023-04-28 05:57:44,896 root INFO copying build/lib/ansible_collections/wti/remote/requirements-wti.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote 2023-04-28 05:57:44,896 root INFO copying build/lib/ansible_collections/wti/remote/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote 2023-04-28 05:57:44,897 root INFO copying build/lib/ansible_collections/wti/remote/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote 2023-04-28 05:57:44,897 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/meta 2023-04-28 05:57:44,897 root INFO copying build/lib/ansible_collections/wti/remote/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/meta 2023-04-28 05:57:44,897 root INFO copying build/lib/ansible_collections/wti/remote/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/meta 2023-04-28 05:57:44,897 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks 2023-04-28 05:57:44,898 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_iptables 2023-04-28 05:57:44,898 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_iptables/iptables_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_iptables 2023-04-28 05:57:44,898 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_iptables/iptables_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_iptables 2023-04-28 05:57:44,898 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_firmwareupdate 2023-04-28 05:57:44,898 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_firmwareupdate/firmware_upgrade.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_firmwareupdate 2023-04-28 05:57:44,899 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,899 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_user/user_delete.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,899 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_user/user_get.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,899 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_user/user_edit.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,899 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_user/user_add.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_user 2023-04-28 05:57:44,899 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_hostname 2023-04-28 05:57:44,900 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_hostname/hostname_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_hostname 2023-04-28 05:57:44,900 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_hostname/hostname_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_hostname 2023-04-28 05:57:44,900 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,900 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_status/firmware_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,900 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_status/power_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,901 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_status/alarm_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,901 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_status/status_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,901 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_status/temp_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,901 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_status/current_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_status 2023-04-28 05:57:44,901 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_interface 2023-04-28 05:57:44,902 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_interface/interface_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_interface 2023-04-28 05:57:44,902 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_interface/interface_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_interface 2023-04-28 05:57:44,902 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_time_date 2023-04-28 05:57:44,902 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_time_date/time_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_time_date 2023-04-28 05:57:44,902 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_time_date/time_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_time_date 2023-04-28 05:57:44,903 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_syslog_client 2023-04-28 05:57:44,903 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_client/syslog_client_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_syslog_client 2023-04-28 05:57:44,903 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_client/syslog_client_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_syslog_client 2023-04-28 05:57:44,903 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_syslog_server 2023-04-28 05:57:44,903 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_server/syslog_server_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_syslog_server 2023-04-28 05:57:44,903 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_syslog_server/syslog_server_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_syslog_server 2023-04-28 05:57:44,904 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,904 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_action_set.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,904 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,904 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_action_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,904 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_serial_ports 2023-04-28 05:57:44,905 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_plugcontrol 2023-04-28 05:57:44,905 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_plugcontrol/plug_control.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_plugcontrol 2023-04-28 05:57:44,905 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_plugcontrol/plug_control_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_plugcontrol 2023-04-28 05:57:44,905 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_snmp 2023-04-28 05:57:44,905 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_snmp/snmp_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_snmp 2023-04-28 05:57:44,905 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_snmp/snmp_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_snmp 2023-04-28 05:57:44,906 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_plugconfig 2023-04-28 05:57:44,906 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_plugconfig/plug_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_plugconfig 2023-04-28 05:57:44,906 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_plugconfig/plug_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_plugconfig 2023-04-28 05:57:44,906 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_config 2023-04-28 05:57:44,906 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_config/cpm_config_backup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_config 2023-04-28 05:57:44,907 root INFO copying build/lib/ansible_collections/wti/remote/playbooks/cpm_config/cpm_config_restore.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote/playbooks/cpm_config 2023-04-28 05:57:44,907 root INFO copying build/lib/ansible_collections/wti/remote/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/wti/remote 2023-04-28 05:57:44,907 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp 2023-04-28 05:57:44,907 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,907 root INFO copying build/lib/ansible_collections/netapp/azure/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins 2023-04-28 05:57:44,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:44,908 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/doc_fragments/azure.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:44,908 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:44,908 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/doc_fragments/azure_tags.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/doc_fragments 2023-04-28 05:57:44,909 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:44,909 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:44,909 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:44,909 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:44,909 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_capacity_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/modules 2023-04-28 05:57:44,910 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/module_utils 2023-04-28 05:57:44,910 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/module_utils/netapp_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/module_utils 2023-04-28 05:57:44,910 root INFO copying build/lib/ansible_collections/netapp/azure/plugins/module_utils/azure_rm_netapp_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/plugins/module_utils 2023-04-28 05:57:44,910 root INFO copying build/lib/ansible_collections/netapp/azure/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,910 root INFO copying build/lib/ansible_collections/netapp/azure/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,911 root INFO copying build/lib/ansible_collections/netapp/azure/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,911 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/meta 2023-04-28 05:57:44,911 root INFO copying build/lib/ansible_collections/netapp/azure/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/meta 2023-04-28 05:57:44,911 root INFO copying build/lib/ansible_collections/netapp/azure/HACK.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,911 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:44,912 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,912 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4416.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,912 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3663.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,912 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3949.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,912 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3505.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,913 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3526.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,913 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/20.6.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,913 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3704.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,913 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/20.7.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,913 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4001.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,914 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4070.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,914 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3849.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,914 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/20.4.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,914 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4246.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,914 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/20.5.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,914 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/20.2.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,915 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4135.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,915 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3935.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,915 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/fragments/20.8.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs/fragments 2023-04-28 05:57:44,915 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:44,915 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:44,916 root INFO copying build/lib/ansible_collections/netapp/azure/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure/changelogs 2023-04-28 05:57:44,916 root INFO copying build/lib/ansible_collections/netapp/azure/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,916 root INFO copying build/lib/ansible_collections/netapp/azure/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/azure 2023-04-28 05:57:44,916 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw 2023-04-28 05:57:44,916 root INFO copying build/lib/ansible_collections/netapp/elementsw/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw 2023-04-28 05:57:44,917 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins 2023-04-28 05:57:44,917 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/doc_fragments 2023-04-28 05:57:44,917 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/doc_fragments 2023-04-28 05:57:44,917 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,917 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,918 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,918 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,918 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,918 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,918 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_drive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,919 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,919 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume_pair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,919 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,919 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_qos_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,919 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_admin_users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,920 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,920 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,920 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,920 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,921 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_access_group_volumes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,921 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_check_connections.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,921 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_initiators.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,921 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,921 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,922 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_pair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,922 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_network_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,922 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_access_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,922 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot_restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/modules 2023-04-28 05:57:44,922 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:44,923 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/module_utils/netapp_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:44,923 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/module_utils/netapp_elementsw_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:44,923 root INFO copying build/lib/ansible_collections/netapp/elementsw/plugins/module_utils/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/plugins/module_utils 2023-04-28 05:57:44,923 root INFO copying build/lib/ansible_collections/netapp/elementsw/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw 2023-04-28 05:57:44,923 root INFO copying build/lib/ansible_collections/netapp/elementsw/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw 2023-04-28 05:57:44,924 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/meta 2023-04-28 05:57:44,924 root INFO copying build/lib/ansible_collections/netapp/elementsw/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/meta 2023-04-28 05:57:44,924 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs 2023-04-28 05:57:44,924 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,924 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-4416.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,924 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3174.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,925 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3188.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,925 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3731.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,925 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3117.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,925 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/20.6.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,925 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3235.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,926 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3324.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,926 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3196.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,926 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3734.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,926 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3800.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,926 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3310.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,927 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/20.2.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,927 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/2019.10.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,927 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/20.9.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,927 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3733.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,927 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/fragments/20.8.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs/fragments 2023-04-28 05:57:44,928 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs 2023-04-28 05:57:44,928 root INFO copying build/lib/ansible_collections/netapp/elementsw/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw/changelogs 2023-04-28 05:57:44,928 root INFO copying build/lib/ansible_collections/netapp/elementsw/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw 2023-04-28 05:57:44,928 root INFO copying build/lib/ansible_collections/netapp/elementsw/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/elementsw 2023-04-28 05:57:44,928 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,929 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,929 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins 2023-04-28 05:57:44,929 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins 2023-04-28 05:57:44,929 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/doc_fragments 2023-04-28 05:57:44,929 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/doc_fragments 2023-04-28 05:57:44,930 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,930 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_nss_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,930 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cifs_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,930 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_aws.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,930 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,931 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_aggregate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,931 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_aws.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,931 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_aws_fsx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,931 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_azure.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,932 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_gcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,932 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_azure.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,932 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_snapmirror.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,932 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,932 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_gcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/modules 2023-04-28 05:57:44,933 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/module_utils 2023-04-28 05:57:44,933 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/module_utils/netapp_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/module_utils 2023-04-28 05:57:44,933 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/plugins/module_utils/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/plugins/module_utils 2023-04-28 05:57:44,933 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,934 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,934 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments 2023-04-28 05:57:44,934 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy 2023-04-28 05:57:44,934 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy 2023-04-28 05:57:44,934 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy 2023-04-28 05:57:44,935 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/execution_environments/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments 2023-04-28 05:57:44,935 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments/from_github 2023-04-28 05:57:44,935 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_github/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments/from_github 2023-04-28 05:57:44,935 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/execution_environments/from_github/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments/from_github 2023-04-28 05:57:44,935 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/execution_environments/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/execution_environments 2023-04-28 05:57:44,936 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,936 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/meta 2023-04-28 05:57:44,936 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/meta 2023-04-28 05:57:44,936 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/meta 2023-04-28 05:57:44,936 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/kubectl.sha256 -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,937 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:44,937 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,937 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5151.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,937 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3922.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,937 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4416.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,938 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3912.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,938 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5562.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,938 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3946.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,938 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4327.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,938 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4542.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,938 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4264.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,939 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4321.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,939 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4358.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,939 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4386.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,939 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4271.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,939 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4065.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,940 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4200.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,940 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5002.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,940 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3947.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,940 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3948.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,940 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3909.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,941 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5472.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,941 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4703.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,941 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3844.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,941 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3984.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,941 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5452.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,942 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5366.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,942 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4328.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,942 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3910.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,942 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4513.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,942 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5252.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,943 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4458.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,943 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3995.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,943 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4105.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,943 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4567.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,943 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4021.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,944 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3965.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,944 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3911.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,944 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4303.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,944 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5437.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,944 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4500.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,945 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4820.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,945 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4164.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,945 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4136.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,945 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4647.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,945 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5342.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,945 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3913.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,946 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4201.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,946 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3985.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,946 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4281.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,946 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4292.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,946 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4758.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,947 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3803.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,947 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4492.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,947 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4205.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,947 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4118.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,947 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3975.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,948 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4223.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,948 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4298.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,948 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4563.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,948 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5527.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,948 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4516.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,949 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4267.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,949 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3967.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,949 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5307.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,949 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5540.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs/fragments 2023-04-28 05:57:44,949 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:44,950 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:44,950 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager/changelogs 2023-04-28 05:57:44,950 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,950 root INFO copying build/lib/ansible_collections/netapp/cloudmanager/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/cloudmanager 2023-04-28 05:57:44,950 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap 2023-04-28 05:57:44,951 root INFO copying build/lib/ansible_collections/netapp/ontap/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap 2023-04-28 05:57:44,951 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins 2023-04-28 05:57:44,951 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:44,951 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/filter/na_filter_iso8601.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:44,952 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/filter/iso8601_duration_to_seconds.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:44,952 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/filter/iso8601_duration_from_seconds.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/filter 2023-04-28 05:57:44,952 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/doc_fragments 2023-04-28 05:57:44,952 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/doc_fragments 2023-04-28 05:57:44,952 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,953 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_metrocluster_dr_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,953 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,953 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_service_processor_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,953 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,953 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ucadapter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,954 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_map_reporting_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,954 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_firmware_upgrade.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,954 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_mcc_mediator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,954 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,955 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_partitions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,955 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_ext_engine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,955 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cg_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,955 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_debug.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,955 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ndmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,956 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user_set_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,956 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,956 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_svm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,956 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_snaplock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,956 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,957 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,957 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme_namespace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,957 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_license.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,957 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_scanner_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,958 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_qtree.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,958 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ssh_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,958 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_job_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,958 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_ifgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,959 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdsd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,959 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_qos_adaptive_policy_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,959 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,959 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster_ha.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,959 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_audit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,960 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_log_forward.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,960 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_security_permissions_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,960 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_on_demand_task.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,960 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,960 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_autosize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,961 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_autosupport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,961 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_efficiency.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,961 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,961 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_flexcache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,962 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_nfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,962 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_kerberos_realm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,962 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ldap_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,962 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_domain_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,962 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,963 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_storage_auto_giveback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,963 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_restit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,963 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,963 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_publickey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,964 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,964 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,964 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_software_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,964 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_export_policy_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,965 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_disk_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,965 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_zapit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,965 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_policies.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,965 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_security_permissions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,965 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,966 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_scope.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,966 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,966 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_name_service_switch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,966 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,967 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,967 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_cifs_security.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,967 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_svm_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,967 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,967 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_object_store.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,968 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ipspace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,968 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_export_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,968 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_group_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,968 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,968 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdspt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,969 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,969 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_rest_cli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,969 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_qos_policy_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,969 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_aggregate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,970 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_ca_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,970 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_certificates.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,970 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,970 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,970 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,971 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,971 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_broadcast_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,971 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_key_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,972 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_iscsi_security.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,972 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_igroup_initiator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,972 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_user_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,972 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,972 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_wait_for_condition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,973 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_efficiency_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,973 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_snmp_traphosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,973 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntfs_dacl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,973 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,974 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_local_hosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,974 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_unix_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,974 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_quotas.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,974 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_bgp_peer_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,974 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_on_access_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,975 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,975 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_groups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,975 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapshot_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,975 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,976 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,976 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_igroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,976 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,976 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,976 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_rest_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,977 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,977 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_service_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,977 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,977 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_directory_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,978 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntfs_sd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,978 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user_modify.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,978 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,978 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntp_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,978 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_name_mappings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,979 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_motd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,979 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_buckets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,979 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdsp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,979 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_autosupport_invoke.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,980 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_portset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,980 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,980 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_unix_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,980 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_event.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,981 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,981 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_quota_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,981 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_metrocluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,981 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_login_messages.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,981 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ems_destination.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,982 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_peer_permissions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,982 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_snaplock_clock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,982 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_disks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,982 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,982 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapmirror.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,983 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_storage_failover.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,983 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_iscsi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,983 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_active_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,983 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,984 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_ems_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,984 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_wwpn_alias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,984 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapmirror_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,984 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_broadcast_domain_ports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,985 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,985 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,985 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme_subsystem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,985 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/modules 2023-04-28 05:57:44,985 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,986 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/netapp_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,986 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/netapp_elementsw_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,986 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/rest_owning_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,986 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/rest_generic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,986 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/zapis_svm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,987 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/netapp_ipaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,987 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,987 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/rest_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,987 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/rest_vserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,988 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/rest_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,988 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/rest_response_helpers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,988 root INFO copying build/lib/ansible_collections/netapp/ontap/plugins/module_utils/rest_application.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/plugins/module_utils 2023-04-28 05:57:44,988 root INFO copying build/lib/ansible_collections/netapp/ontap/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap 2023-04-28 05:57:44,988 root INFO copying build/lib/ansible_collections/netapp/ontap/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap 2023-04-28 05:57:44,989 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments 2023-04-28 05:57:44,989 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments/from_galaxy 2023-04-28 05:57:44,989 root INFO copying build/lib/ansible_collections/netapp/ontap/execution_environments/from_galaxy/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments/from_galaxy 2023-04-28 05:57:44,989 root INFO copying build/lib/ansible_collections/netapp/ontap/execution_environments/from_galaxy/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments/from_galaxy 2023-04-28 05:57:44,990 root INFO copying build/lib/ansible_collections/netapp/ontap/execution_environments/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments 2023-04-28 05:57:44,990 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments/from_github 2023-04-28 05:57:44,990 root INFO copying build/lib/ansible_collections/netapp/ontap/execution_environments/from_github/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments/from_github 2023-04-28 05:57:44,990 root INFO copying build/lib/ansible_collections/netapp/ontap/execution_environments/from_github/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments/from_github 2023-04-28 05:57:44,990 root INFO copying build/lib/ansible_collections/netapp/ontap/execution_environments/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/execution_environments 2023-04-28 05:57:44,991 root INFO copying build/lib/ansible_collections/netapp/ontap/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap 2023-04-28 05:57:44,991 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/meta 2023-04-28 05:57:44,991 root INFO copying build/lib/ansible_collections/netapp/ontap/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/meta 2023-04-28 05:57:44,991 root INFO copying build/lib/ansible_collections/netapp/ontap/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/meta 2023-04-28 05:57:44,991 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks 2023-04-28 05:57:44,992 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,992 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/filter 2023-04-28 05:57:44,992 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/filter/test_na_filter_iso8601.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/filter 2023-04-28 05:57:44,992 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware_with_vars_file.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,992 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,993 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:44,993 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/json_query/na_ontap_pb_get_online_volumes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:44,993 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/json_query/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:44,993 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/json_query/na_ontap_pb_get_online_volumes_loop.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/json_query 2023-04-28 05:57:44,993 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/ontap_vars_file.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,994 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:44,994 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/rest_apis/clusters.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:44,994 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/rest_apis/list_aggregates.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:44,994 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/rest_apis/volumes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/rest_apis 2023-04-28 05:57:44,994 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_install_SSL_certificate.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,995 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,995 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_install_SSL_certificate_REST.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,995 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/support 2023-04-28 05:57:44,995 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/support/debug_connectivity.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples/support 2023-04-28 05:57:44,995 root INFO copying build/lib/ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware_with_extra_vars.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/playbooks/examples 2023-04-28 05:57:44,996 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:44,996 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/.DS_Store -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:44,996 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,996 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3242.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,997 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4228.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,997 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3668.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,997 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4465.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,997 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3390.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,997 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4344.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,998 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3671.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,998 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3304.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,998 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4231.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,998 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4394.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,998 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4526.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,998 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2459b.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,999 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1661.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,999 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5666.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,999 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5034.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,999 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5243.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:44,999 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3175.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,000 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4190.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,000 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3973.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,000 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4789.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,000 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5063.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,000 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/github-56.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,001 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5427.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,001 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3543.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,001 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3479.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,001 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5629.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,001 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3632.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,002 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5960.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,002 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4864.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,002 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5606.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,002 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5626.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,002 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4235.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,003 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5082.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,003 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4114.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,003 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4338.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,003 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4460.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,003 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4049.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,004 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4150.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,004 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5665.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,004 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3483.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,005 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5092.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,005 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3628.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,005 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4339.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,005 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5713.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,005 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4762.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,006 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3662.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,006 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4774.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,006 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2491.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,006 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4818.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,006 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3497.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,007 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3571.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,007 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3181.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,007 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4026.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,007 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3454.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,007 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5892.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,008 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5136.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,008 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4769.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,008 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5671.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,008 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5241.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,008 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4140.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,009 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4415.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,009 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4554.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,009 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5917.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,009 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.4.1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,009 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4747.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,009 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4343.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,010 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5926.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,010 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3439.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,010 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4577.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,010 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5415.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,010 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5604.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,011 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3113.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,011 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3367.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,011 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3969.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,011 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4863.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,011 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5913.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,012 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1926.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,012 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5285.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,012 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4540.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,012 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5338.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,012 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3654.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,013 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4197.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,013 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4401.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,013 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3633.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,013 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5084.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,013 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4809.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,014 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4648.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,014 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4644.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,014 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5790.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,014 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5216.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,014 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5503.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,015 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4010.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,015 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2668.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,015 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4331.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,015 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4459.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,015 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5788.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,016 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5246.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,016 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3667.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,016 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3194.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,016 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4612.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,016 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5537.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,017 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5808.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,017 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3230.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,017 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3494.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,017 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4206.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,017 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5532.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,018 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3354.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,018 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3952.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,018 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5919.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,018 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4786.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,018 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5079.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,019 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3400.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,019 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5485.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,019 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5354.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,019 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3626.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,019 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4711.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,020 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5138.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,020 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4764.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,020 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5986.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,020 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5952.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,020 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4347.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,021 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5819.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,021 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4022.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,021 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5628.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,021 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5062.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,021 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5409.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,022 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4803.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,022 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3139.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,022 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5504.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,022 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5737.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,022 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3443.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,023 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4005.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,023 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4813.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,023 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/19.11.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,023 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5195.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,023 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4227.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,024 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4218.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,024 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3718.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,024 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4435.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,024 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.6.1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,024 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4832.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,025 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5734.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,025 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3399.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,025 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4645.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,025 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4800.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,026 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4737.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,026 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3542.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,026 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3615.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,026 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4679.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,026 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5757.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,027 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3883.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,027 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2972.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,027 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4872.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,027 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5015.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,027 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4300.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,028 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3649.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,028 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5215.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,028 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3754.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,028 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5310.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,028 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/no-story-1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,029 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5426.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,029 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4119.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,029 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5899.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,029 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.6.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,029 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4862.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,030 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4743.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,030 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3515.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,030 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5457.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,031 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4175.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,031 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3950.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,032 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3677.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,032 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5068.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,032 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4113.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,033 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3480.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,033 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5085.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,033 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4830.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,033 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4336.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,034 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4606.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,034 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3655.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,034 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4179.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,034 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4039.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,034 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3137.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,035 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4333.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,035 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4508.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,035 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4807.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,035 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4334.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,035 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5412.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,036 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4332.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,036 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5380.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,036 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4449.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,036 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4527.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,036 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4794.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,037 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.7.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,037 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5774.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,037 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4763.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,037 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2928.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,037 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4122.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,038 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4775.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,038 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4439.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,038 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5735.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,038 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4985.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,038 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5188.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,039 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5725.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,039 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3329.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,039 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5678.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,039 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4788.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,039 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5121.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,040 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5659.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,040 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4731.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,040 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4568.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,040 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4348.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,041 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4243.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,041 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5845.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,041 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4573.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,041 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4745.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,041 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5505.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,042 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4349.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,042 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3807.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,042 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5161.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,042 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4312.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,042 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5137.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,043 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4404.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,043 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3772.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,043 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5972.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,043 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3536.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,043 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4161.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,044 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4487.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,044 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3370.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,044 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/19.10.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,044 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5017.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,044 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5983.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,045 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4392.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,045 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4798.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,045 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4984.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,045 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3870.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,045 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4079.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,046 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5761.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,046 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3262.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,046 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5506.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,046 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4060.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,047 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5414.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,047 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5189.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,047 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4329.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,047 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5431.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,047 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5844.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,048 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4345.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,048 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5487.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,048 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5531.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,048 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4857.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,048 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3385.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,049 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3716.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,049 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4031.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,049 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3812.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,049 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4319.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,049 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3625.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,050 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5016.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,050 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4335.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,050 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5910.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,050 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5304.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,051 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5251.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,051 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5733.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,051 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4123.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,051 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3366.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,051 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4623.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,052 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3167.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,052 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5430.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,052 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4457.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,052 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5271.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,052 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4121.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,053 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5589.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,053 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4801.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,053 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4479.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,053 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4393.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,053 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3346.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,054 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5816.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,054 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3939.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,054 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4566.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,054 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.4.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,054 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4191.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,055 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4565.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,055 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4270.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,055 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3310.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,055 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4255.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,055 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5809.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,056 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4288.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,056 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4367.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,056 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5019.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,056 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5760.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,056 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4417.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,057 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4716.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,057 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5047.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,057 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5594.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,057 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4804.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,058 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4604.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,058 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.5.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,058 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.2.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,058 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4808.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,058 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5299.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,059 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5611.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,059 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3490.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,059 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5413.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,059 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3595.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,059 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3757.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,060 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5820.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,060 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5223.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,060 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4898.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,060 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5711.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,060 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/0-copy_ignore_txt.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,061 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.1.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,061 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5938.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,061 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4882.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,061 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3312.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,061 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3358.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,062 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5894.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,062 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4799.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,062 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4605.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,062 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3401.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,062 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3149.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,063 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4735.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,063 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4770.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,063 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3369.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,063 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3811.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,063 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4350.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,064 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3685.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,064 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4802.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,064 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4157.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,064 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3510.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,064 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4342.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,065 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2353.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,065 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4341.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,065 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4736.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,065 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5784.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,065 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4719.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,066 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5090.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,066 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4676.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,066 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5807.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,066 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5548.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,067 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5812.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,067 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4289.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,067 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4781.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,067 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4399.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,067 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4048.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,068 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5220.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,068 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5174.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,068 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3983.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,068 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3900.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,068 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3368.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,069 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3392.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,069 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4790.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,069 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3241.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,069 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3580.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,069 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4691.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,070 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4975.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,070 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5344.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,070 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5453.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,070 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.9.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,070 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4116.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,071 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5367.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,071 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4773.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,071 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3540.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,071 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5507.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,071 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5677.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,072 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5696.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,072 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2965.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,072 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5859.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,072 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4771.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,072 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5481.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,073 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4998.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,073 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3994.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,073 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4834.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,073 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3535.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,073 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5065.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,074 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5152.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,074 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5479.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,074 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4588.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,074 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5263.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,074 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5662.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,075 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2422.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,075 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4779.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,075 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4776.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,075 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4337.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,075 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5268.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,076 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3501.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,076 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5228.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,076 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5591.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,076 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3971.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,077 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3371.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,077 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4784.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,077 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5592.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,077 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4391.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,077 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4729.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,078 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3623.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,078 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3850.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,078 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3579.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,078 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3386.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,078 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3926.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,079 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4325.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,079 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5287.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,079 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5179.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,079 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5109.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,079 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4981.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,080 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4196.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,080 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3767.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,080 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5270.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,080 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4256.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,080 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5026.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,081 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5312.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,081 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5190.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,081 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5297.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,081 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4785.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,081 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1665.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,082 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2459.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,082 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4177.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,082 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5596.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,082 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3442.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,083 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5484.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,083 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4609.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,083 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5540.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,083 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3178.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,083 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5168.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,084 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4340.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,084 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4780.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,084 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5229.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,084 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5595.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,084 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.8.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,085 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5536.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,085 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4159.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,085 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5738.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,085 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4879.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,085 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3830.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,086 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4767.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,086 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4621.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,086 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5127.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,086 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3148.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,086 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4501.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,087 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/20.3.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,087 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-6005.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,087 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2426.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,087 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5275.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,087 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4320.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,088 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3534.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,088 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2964.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,088 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3801.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,088 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3251.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,088 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/github-110.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,089 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5948.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs/fragments 2023-04-28 05:57:45,089 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:45,089 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:45,089 root INFO copying build/lib/ansible_collections/netapp/ontap/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/changelogs 2023-04-28 05:57:45,090 root INFO copying build/lib/ansible_collections/netapp/ontap/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap 2023-04-28 05:57:45,090 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles 2023-04-28 05:57:45,090 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create 2023-04-28 05:57:45,090 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tasks 2023-04-28 05:57:45,091 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tasks 2023-04-28 05:57:45,091 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/defaults 2023-04-28 05:57:45,091 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/defaults 2023-04-28 05:57:45,091 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/handlers 2023-04-28 05:57:45,091 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/handlers 2023-04-28 05:57:45,092 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create 2023-04-28 05:57:45,092 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests 2023-04-28 05:57:45,092 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests 2023-04-28 05:57:45,092 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests 2023-04-28 05:57:45,092 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/vars 2023-04-28 05:57:45,092 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/vars 2023-04-28 05:57:45,093 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/meta 2023-04-28 05:57:45,093 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/meta 2023-04-28 05:57:45,093 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_create 2023-04-28 05:57:45,093 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create 2023-04-28 05:57:45,093 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tasks 2023-04-28 05:57:45,094 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tasks 2023-04-28 05:57:45,094 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/defaults 2023-04-28 05:57:45,094 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/defaults 2023-04-28 05:57:45,094 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/handlers 2023-04-28 05:57:45,094 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/handlers 2023-04-28 05:57:45,095 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create 2023-04-28 05:57:45,095 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests 2023-04-28 05:57:45,095 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests 2023-04-28 05:57:45,095 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests 2023-04-28 05:57:45,095 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/vars 2023-04-28 05:57:45,095 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/vars 2023-04-28 05:57:45,096 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/meta 2023-04-28 05:57:45,096 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create/meta 2023-04-28 05:57:45,096 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_san_create/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_san_create 2023-04-28 05:57:45,096 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create 2023-04-28 05:57:45,096 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tasks 2023-04-28 05:57:45,097 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tasks 2023-04-28 05:57:45,097 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/defaults 2023-04-28 05:57:45,097 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/defaults 2023-04-28 05:57:45,097 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/handlers 2023-04-28 05:57:45,097 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/handlers 2023-04-28 05:57:45,098 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create 2023-04-28 05:57:45,098 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests 2023-04-28 05:57:45,098 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests 2023-04-28 05:57:45,098 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests 2023-04-28 05:57:45,098 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/vars 2023-04-28 05:57:45,098 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/vars 2023-04-28 05:57:45,099 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/meta 2023-04-28 05:57:45,099 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/meta 2023-04-28 05:57:45,099 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_nas_create/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_nas_create 2023-04-28 05:57:45,099 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete 2023-04-28 05:57:45,099 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,100 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/assert_prereqs_and_vserver_exists.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,100 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/find_and_delete_volumes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,100 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/delete_volumes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,100 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_interfaces.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,100 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_igroups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,101 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_volumes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,101 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,101 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/find_and_delete_volumes_retries.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,101 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_cifs_server.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks 2023-04-28 05:57:45,101 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/defaults 2023-04-28 05:57:45,102 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/defaults 2023-04-28 05:57:45,102 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/handlers 2023-04-28 05:57:45,102 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/handlers 2023-04-28 05:57:45,102 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete 2023-04-28 05:57:45,102 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests 2023-04-28 05:57:45,103 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests 2023-04-28 05:57:45,103 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests 2023-04-28 05:57:45,103 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/vars 2023-04-28 05:57:45,103 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/vars 2023-04-28 05:57:45,103 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/meta 2023-04-28 05:57:45,103 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/meta 2023-04-28 05:57:45,104 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/.travis.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete 2023-04-28 05:57:45,104 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config 2023-04-28 05:57:45,104 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tasks 2023-04-28 05:57:45,104 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tasks 2023-04-28 05:57:45,104 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/defaults 2023-04-28 05:57:45,105 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/defaults 2023-04-28 05:57:45,105 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/handlers 2023-04-28 05:57:45,105 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/handlers 2023-04-28 05:57:45,105 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config 2023-04-28 05:57:45,105 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests 2023-04-28 05:57:45,105 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests 2023-04-28 05:57:45,106 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests 2023-04-28 05:57:45,106 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/vars 2023-04-28 05:57:45,106 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/vars 2023-04-28 05:57:45,106 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/meta 2023-04-28 05:57:45,106 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/meta 2023-04-28 05:57:45,107 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_cluster_config 2023-04-28 05:57:45,107 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create 2023-04-28 05:57:45,107 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tasks 2023-04-28 05:57:45,107 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tasks 2023-04-28 05:57:45,107 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/defaults 2023-04-28 05:57:45,108 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/defaults 2023-04-28 05:57:45,108 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/handlers 2023-04-28 05:57:45,108 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/handlers 2023-04-28 05:57:45,108 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create 2023-04-28 05:57:45,108 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests 2023-04-28 05:57:45,109 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests 2023-04-28 05:57:45,109 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests 2023-04-28 05:57:45,109 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/vars 2023-04-28 05:57:45,109 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/vars 2023-04-28 05:57:45,109 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/meta 2023-04-28 05:57:45,109 root INFO copying build/lib/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/meta 2023-04-28 05:57:45,110 root INFO copying build/lib/ansible_collections/netapp/ontap/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/ontap 2023-04-28 05:57:45,110 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid 2023-04-28 05:57:45,110 root INFO copying build/lib/ansible_collections/netapp/storagegrid/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid 2023-04-28 05:57:45,110 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins 2023-04-28 05:57:45,110 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/doc_fragments 2023-04-28 05:57:45,111 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/doc_fragments 2023-04-28 05:57:45,111 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,111 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_user_s3_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,111 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,111 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_identity_federation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,112 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_regions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,112 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,112 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_ha_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,112 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,112 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,113 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_traffic_classes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,113 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,113 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_client_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,113 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_identity_federation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,113 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,114 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,114 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,114 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,114 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,115 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,115 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/modules 2023-04-28 05:57:45,115 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/module_utils 2023-04-28 05:57:45,115 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/module_utils/netapp_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/module_utils 2023-04-28 05:57:45,115 root INFO copying build/lib/ansible_collections/netapp/storagegrid/plugins/module_utils/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/plugins/module_utils 2023-04-28 05:57:45,116 root INFO copying build/lib/ansible_collections/netapp/storagegrid/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid 2023-04-28 05:57:45,116 root INFO copying build/lib/ansible_collections/netapp/storagegrid/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid 2023-04-28 05:57:45,116 root INFO copying build/lib/ansible_collections/netapp/storagegrid/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid 2023-04-28 05:57:45,116 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/meta 2023-04-28 05:57:45,116 root INFO copying build/lib/ansible_collections/netapp/storagegrid/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/meta 2023-04-28 05:57:45,117 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs 2023-04-28 05:57:45,117 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,117 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/20.10.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,117 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/DEVOPS-4416.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,117 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/github-66.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,118 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/github-10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,118 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/21.11.1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,118 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/github-8.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,118 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/20.6.1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,118 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/21.6.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,118 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/20.7.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,119 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/21.9.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,119 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/fragments/21.11.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs/fragments 2023-04-28 05:57:45,119 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs 2023-04-28 05:57:45,119 root INFO copying build/lib/ansible_collections/netapp/storagegrid/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid/changelogs 2023-04-28 05:57:45,119 root INFO copying build/lib/ansible_collections/netapp/storagegrid/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid 2023-04-28 05:57:45,120 root INFO copying build/lib/ansible_collections/netapp/storagegrid/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/storagegrid 2023-04-28 05:57:45,120 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info 2023-04-28 05:57:45,120 root INFO copying build/lib/ansible_collections/netapp/um_info/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info 2023-04-28 05:57:45,120 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins 2023-04-28 05:57:45,120 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/doc_fragments 2023-04-28 05:57:45,121 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/doc_fragments 2023-04-28 05:57:45,121 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,121 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_list_volumes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,121 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_list_aggregates.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,121 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_list_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,122 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_volumes_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,122 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_svms_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,122 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_nodes_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,122 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_aggregates_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,122 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_list_svms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,123 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_list_clusters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,123 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/modules/na_um_clusters_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/modules 2023-04-28 05:57:45,123 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/module_utils 2023-04-28 05:57:45,123 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/module_utils/netapp_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/module_utils 2023-04-28 05:57:45,123 root INFO copying build/lib/ansible_collections/netapp/um_info/plugins/module_utils/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/plugins/module_utils 2023-04-28 05:57:45,124 root INFO copying build/lib/ansible_collections/netapp/um_info/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info 2023-04-28 05:57:45,124 root INFO copying build/lib/ansible_collections/netapp/um_info/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info 2023-04-28 05:57:45,124 root INFO copying build/lib/ansible_collections/netapp/um_info/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info 2023-04-28 05:57:45,124 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/meta 2023-04-28 05:57:45,124 root INFO copying build/lib/ansible_collections/netapp/um_info/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/meta 2023-04-28 05:57:45,125 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs 2023-04-28 05:57:45,125 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,125 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4416.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,125 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/fragments/20.7.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,125 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-3962.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,126 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4087.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,126 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4059.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,126 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-3920.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,126 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-2952.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs/fragments 2023-04-28 05:57:45,126 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs 2023-04-28 05:57:45,127 root INFO copying build/lib/ansible_collections/netapp/um_info/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info/changelogs 2023-04-28 05:57:45,127 root INFO copying build/lib/ansible_collections/netapp/um_info/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info 2023-04-28 05:57:45,127 root INFO copying build/lib/ansible_collections/netapp/um_info/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/um_info 2023-04-28 05:57:45,127 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws 2023-04-28 05:57:45,127 root INFO copying build/lib/ansible_collections/netapp/aws/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws 2023-04-28 05:57:45,127 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins 2023-04-28 05:57:45,128 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/doc_fragments 2023-04-28 05:57:45,128 root INFO copying build/lib/ansible_collections/netapp/aws/plugins/doc_fragments/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/doc_fragments 2023-04-28 05:57:45,128 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:45,128 root INFO copying build/lib/ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:45,128 root INFO copying build/lib/ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_active_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:45,129 root INFO copying build/lib/ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_filesystems.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:45,129 root INFO copying build/lib/ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_snapshots.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/modules 2023-04-28 05:57:45,129 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/module_utils 2023-04-28 05:57:45,130 root INFO copying build/lib/ansible_collections/netapp/aws/plugins/module_utils/netapp_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/module_utils 2023-04-28 05:57:45,130 root INFO copying build/lib/ansible_collections/netapp/aws/plugins/module_utils/netapp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/plugins/module_utils 2023-04-28 05:57:45,130 root INFO copying build/lib/ansible_collections/netapp/aws/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws 2023-04-28 05:57:45,130 root INFO copying build/lib/ansible_collections/netapp/aws/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws 2023-04-28 05:57:45,130 root INFO copying build/lib/ansible_collections/netapp/aws/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws 2023-04-28 05:57:45,131 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/meta 2023-04-28 05:57:45,131 root INFO copying build/lib/ansible_collections/netapp/aws/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/meta 2023-04-28 05:57:45,131 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs 2023-04-28 05:57:45,131 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,131 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-4416.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,132 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-3569.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,132 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/20.6.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,132 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-3644.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,132 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/20.2.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,132 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/2019.10.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,132 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/20.9.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,133 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/fragments/20.8.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs/fragments 2023-04-28 05:57:45,133 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs 2023-04-28 05:57:45,133 root INFO copying build/lib/ansible_collections/netapp/aws/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws/changelogs 2023-04-28 05:57:45,133 root INFO copying build/lib/ansible_collections/netapp/aws/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws 2023-04-28 05:57:45,133 root INFO copying build/lib/ansible_collections/netapp/aws/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netapp/aws 2023-04-28 05:57:45,134 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox 2023-04-28 05:57:45,134 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx 2023-04-28 05:57:45,134 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins 2023-04-28 05:57:45,134 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/terminal 2023-04-28 05:57:45,134 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/terminal/onyx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/terminal 2023-04-28 05:57:45,135 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/terminal 2023-04-28 05:57:45,135 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/doc_fragments 2023-04-28 05:57:45,135 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/doc_fragments/onyx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/doc_fragments 2023-04-28 05:57:45,135 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/doc_fragments 2023-04-28 05:57:45,135 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,135 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_aaa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,136 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_l2_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,136 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_syslog_files.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,136 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_bfd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,136 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,137 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,137 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_mlag_ipl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,137 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_syslog_remote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,137 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,137 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,138 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,138 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_qos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,138 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_ptp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,138 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_username.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,138 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,139 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_vxlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,139 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_ntp_servers_peers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,139 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,139 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,139 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_lldp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,140 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,140 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp_users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,140 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,140 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_ptp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,140 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_buffer_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,141 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_wjh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,141 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_traffic_class.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,141 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,141 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,141 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_pfc_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,142 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,142 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_mlag_vip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,142 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,142 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,142 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,143 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_protocol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,143 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp_hosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,143 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/modules/onyx_magp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/modules 2023-04-28 05:57:45,143 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/cliconf 2023-04-28 05:57:45,144 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/cliconf/onyx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/cliconf 2023-04-28 05:57:45,144 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/cliconf 2023-04-28 05:57:45,144 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/action 2023-04-28 05:57:45,144 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/action 2023-04-28 05:57:45,144 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/action/onyx_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/action 2023-04-28 05:57:45,144 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/module_utils 2023-04-28 05:57:45,145 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/module_utils 2023-04-28 05:57:45,145 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/module_utils/network 2023-04-28 05:57:45,145 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx 2023-04-28 05:57:45,145 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/onyx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx 2023-04-28 05:57:45,145 root INFO copying build/lib/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx 2023-04-28 05:57:45,145 root INFO copying build/lib/ansible_collections/mellanox/onyx/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx 2023-04-28 05:57:45,146 root INFO copying build/lib/ansible_collections/mellanox/onyx/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx 2023-04-28 05:57:45,146 root INFO copying build/lib/ansible_collections/mellanox/onyx/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx 2023-04-28 05:57:45,146 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:45,146 root INFO copying build/lib/ansible_collections/mellanox/onyx/changelogs/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:45,147 root INFO copying build/lib/ansible_collections/mellanox/onyx/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:45,147 root INFO copying build/lib/ansible_collections/mellanox/onyx/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx/changelogs 2023-04-28 05:57:45,147 root INFO copying build/lib/ansible_collections/mellanox/onyx/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/mellanox/onyx 2023-04-28 05:57:45,147 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community 2023-04-28 05:57:45,147 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/azure 2023-04-28 05:57:45,148 root INFO copying build/lib/ansible_collections/community/azure/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure 2023-04-28 05:57:45,148 root INFO copying build/lib/ansible_collections/community/azure/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure 2023-04-28 05:57:45,148 root INFO copying build/lib/ansible_collections/community/azure/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure 2023-04-28 05:57:45,148 root INFO copying build/lib/ansible_collections/community/azure/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure 2023-04-28 05:57:45,149 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/meta 2023-04-28 05:57:45,149 root INFO copying build/lib/ansible_collections/community/azure/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/meta 2023-04-28 05:57:45,149 root INFO copying build/lib/ansible_collections/community/azure/meta/action_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/meta 2023-04-28 05:57:45,149 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/changelogs 2023-04-28 05:57:45,149 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/changelogs/fragments 2023-04-28 05:57:45,149 root INFO copying build/lib/ansible_collections/community/azure/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/changelogs/fragments 2023-04-28 05:57:45,150 root INFO copying build/lib/ansible_collections/community/azure/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/changelogs 2023-04-28 05:57:45,150 root INFO copying build/lib/ansible_collections/community/azure/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure/changelogs 2023-04-28 05:57:45,150 root INFO copying build/lib/ansible_collections/community/azure/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure 2023-04-28 05:57:45,150 root INFO copying build/lib/ansible_collections/community/azure/shippable.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/azure 2023-04-28 05:57:45,150 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,151 root INFO copying build/lib/ansible_collections/community/rabbitmq/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,151 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins 2023-04-28 05:57:45,151 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/doc_fragments 2023-04-28 05:57:45,151 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/doc_fragments/rabbitmq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/doc_fragments 2023-04-28 05:57:45,151 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/doc_fragments 2023-04-28 05:57:45,152 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,152 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_parameter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,152 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_upgrade.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,152 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_publish.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,152 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_exchange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,153 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,153 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_vhost_limits.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,153 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,153 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,153 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_user_limits.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,154 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_global_parameter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,154 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_feature_flag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,154 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_queue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,154 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_vhost.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,154 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_binding.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/modules 2023-04-28 05:57:45,155 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:45,155 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/module_utils/rabbitmq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:45,155 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:45,155 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/module_utils 2023-04-28 05:57:45,155 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/lookup 2023-04-28 05:57:45,156 root INFO copying build/lib/ansible_collections/community/rabbitmq/plugins/lookup/rabbitmq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/plugins/lookup 2023-04-28 05:57:45,156 root INFO copying build/lib/ansible_collections/community/rabbitmq/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,156 root INFO copying build/lib/ansible_collections/community/rabbitmq/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,156 root INFO copying build/lib/ansible_collections/community/rabbitmq/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,156 root INFO copying build/lib/ansible_collections/community/rabbitmq/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,157 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/meta 2023-04-28 05:57:45,157 root INFO copying build/lib/ansible_collections/community/rabbitmq/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/meta 2023-04-28 05:57:45,157 root INFO copying build/lib/ansible_collections/community/rabbitmq/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,157 root INFO copying build/lib/ansible_collections/community/rabbitmq/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,157 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/changelogs 2023-04-28 05:57:45,158 root INFO copying build/lib/ansible_collections/community/rabbitmq/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/changelogs 2023-04-28 05:57:45,158 root INFO copying build/lib/ansible_collections/community/rabbitmq/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq/changelogs 2023-04-28 05:57:45,158 root INFO copying build/lib/ansible_collections/community/rabbitmq/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,158 root INFO copying build/lib/ansible_collections/community/rabbitmq/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/rabbitmq 2023-04-28 05:57:45,158 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean 2023-04-28 05:57:45,159 root INFO copying build/lib/ansible_collections/community/digitalocean/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean 2023-04-28 05:57:45,159 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins 2023-04-28 05:57:45,159 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/doc_fragments 2023-04-28 05:57:45,159 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/doc_fragments/digital_ocean.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/doc_fragments 2023-04-28 05:57:45,159 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/inventory 2023-04-28 05:57:45,159 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/inventory/digitalocean.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/inventory 2023-04-28 05:57:45,160 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,160 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_region_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,160 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_size_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,160 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_block_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,161 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,161 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_spaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,161 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_region_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,161 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,161 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,162 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_cdn_endpoints_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,162 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_balance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,162 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,162 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_droplet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,162 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,163 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_volume_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,163 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_image_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,163 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_project_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,163 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,163 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,164 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,164 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,164 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_account_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,164 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_size_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,164 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,165 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_monitoring_alerts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,165 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,165 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,165 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_account_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,165 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,166 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_monitoring_alerts_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,166 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_cdn_endpoints.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,166 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,166 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,166 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_droplet_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,167 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_kubernetes_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,167 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,167 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,167 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,167 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,168 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,168 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,168 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,168 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,169 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_record_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,169 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,169 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,169 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_vpc_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,169 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_volume_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,170 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_vpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,170 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,170 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,170 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,170 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_kubernetes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,171 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_database_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,171 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,171 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/modules/digital_ocean_spaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/modules 2023-04-28 05:57:45,171 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/module_utils 2023-04-28 05:57:45,171 root INFO copying build/lib/ansible_collections/community/digitalocean/plugins/module_utils/digital_ocean.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/plugins/module_utils 2023-04-28 05:57:45,172 root INFO copying build/lib/ansible_collections/community/digitalocean/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean 2023-04-28 05:57:45,172 root INFO copying build/lib/ansible_collections/community/digitalocean/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean 2023-04-28 05:57:45,172 root INFO copying build/lib/ansible_collections/community/digitalocean/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean 2023-04-28 05:57:45,172 root INFO copying build/lib/ansible_collections/community/digitalocean/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean 2023-04-28 05:57:45,173 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/meta 2023-04-28 05:57:45,173 root INFO copying build/lib/ansible_collections/community/digitalocean/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/meta 2023-04-28 05:57:45,173 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:45,173 root INFO copying build/lib/ansible_collections/community/digitalocean/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:45,173 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/changelogs/fragments 2023-04-28 05:57:45,174 root INFO copying build/lib/ansible_collections/community/digitalocean/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/changelogs/fragments 2023-04-28 05:57:45,174 root INFO copying build/lib/ansible_collections/community/digitalocean/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:45,174 root INFO copying build/lib/ansible_collections/community/digitalocean/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/changelogs 2023-04-28 05:57:45,174 root INFO copying build/lib/ansible_collections/community/digitalocean/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean 2023-04-28 05:57:45,174 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/scripts 2023-04-28 05:57:45,175 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/scripts/inventory 2023-04-28 05:57:45,175 root INFO copying build/lib/ansible_collections/community/digitalocean/scripts/inventory/digital_ocean.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/scripts/inventory 2023-04-28 05:57:45,175 root INFO copying build/lib/ansible_collections/community/digitalocean/scripts/inventory/digital_ocean.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/digitalocean/scripts/inventory 2023-04-28 05:57:45,175 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana 2023-04-28 05:57:45,175 root INFO copying build/lib/ansible_collections/community/grafana/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana 2023-04-28 05:57:45,176 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins 2023-04-28 05:57:45,176 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:45,176 root INFO copying build/lib/ansible_collections/community/grafana/plugins/doc_fragments/api_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:45,176 root INFO copying build/lib/ansible_collections/community/grafana/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:45,176 root INFO copying build/lib/ansible_collections/community/grafana/plugins/doc_fragments/basic_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/doc_fragments 2023-04-28 05:57:45,176 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/callback 2023-04-28 05:57:45,177 root INFO copying build/lib/ansible_collections/community/grafana/plugins/callback/grafana_annotations.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/callback 2023-04-28 05:57:45,177 root INFO copying build/lib/ansible_collections/community/grafana/plugins/callback/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/callback 2023-04-28 05:57:45,177 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,177 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_folder.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,177 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_datasource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,178 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_notification_channel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,178 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_dashboard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,178 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,178 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,179 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_team.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,179 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_organization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,179 root INFO copying build/lib/ansible_collections/community/grafana/plugins/modules/grafana_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/modules 2023-04-28 05:57:45,179 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/module_utils 2023-04-28 05:57:45,179 root INFO copying build/lib/ansible_collections/community/grafana/plugins/module_utils/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/module_utils 2023-04-28 05:57:45,180 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/lookup 2023-04-28 05:57:45,180 root INFO copying build/lib/ansible_collections/community/grafana/plugins/lookup/grafana_dashboard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/lookup 2023-04-28 05:57:45,180 root INFO copying build/lib/ansible_collections/community/grafana/plugins/lookup/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/plugins/lookup 2023-04-28 05:57:45,180 root INFO copying build/lib/ansible_collections/community/grafana/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana 2023-04-28 05:57:45,180 root INFO copying build/lib/ansible_collections/community/grafana/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana 2023-04-28 05:57:45,181 root INFO copying build/lib/ansible_collections/community/grafana/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana 2023-04-28 05:57:45,181 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/meta 2023-04-28 05:57:45,181 root INFO copying build/lib/ansible_collections/community/grafana/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/meta 2023-04-28 05:57:45,181 root INFO copying build/lib/ansible_collections/community/grafana/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana 2023-04-28 05:57:45,181 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/hacking 2023-04-28 05:57:45,182 root INFO copying build/lib/ansible_collections/community/grafana/hacking/find_grafana_versions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/hacking 2023-04-28 05:57:45,182 root INFO copying build/lib/ansible_collections/community/grafana/hacking/check_fragment.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/hacking 2023-04-28 05:57:45,182 root INFO copying build/lib/ansible_collections/community/grafana/hacking/NEED_FRAGMENT -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/hacking 2023-04-28 05:57:45,182 root INFO copying build/lib/ansible_collections/community/grafana/hacking/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/hacking 2023-04-28 05:57:45,182 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs 2023-04-28 05:57:45,183 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,183 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/fix_slashes_in_datasources.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,183 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/0.2.1.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,183 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/170_remove_requirement_ds_type_ds_url.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,183 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/1.0.0.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,183 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/257_pretty_printed_dashboard_export.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,184 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/230-uid-datasource.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,184 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/248_ds_update_error_grafana_9.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,184 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/136_add_grafana_action_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,184 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/ci.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,184 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/1.2.1.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,185 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/update_deprecation.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,185 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/1.2.2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,185 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/239_keyerror_grafana_url.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,185 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/fix-263.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,185 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/grafana_users_note.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,186 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/0.1.0.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,186 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/1.2.3.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,186 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/288_get_actual_org_encode.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,186 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/158-grafana_dashboard-lookup-api-key.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,186 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/0.2.2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,187 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/00_drop_eol_ansible.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,187 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/notifi_channel_refacto.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,187 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/265-url-encode-user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,187 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/0-copy_ignore_txt.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,187 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/1.5.3.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,187 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/172_support_azure_datasource.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,188 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/1.2.0.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,188 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/add-units-datasource.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,188 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/datasource-issue-204.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,188 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/threema.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,188 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/186_check_fragments.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,189 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/270-gha--ansible-test--integration.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,189 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/277-gha-ansible-test-versions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,189 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/01_grafana_bump.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,189 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/0.2.0.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,189 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/191.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,190 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/fragments/1.3.1.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs/fragments 2023-04-28 05:57:45,190 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs 2023-04-28 05:57:45,190 root INFO copying build/lib/ansible_collections/community/grafana/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana/changelogs 2023-04-28 05:57:45,190 root INFO copying build/lib/ansible_collections/community/grafana/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/grafana 2023-04-28 05:57:45,191 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,191 root INFO copying build/lib/ansible_collections/community/hrobot/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,191 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins 2023-04-28 05:57:45,191 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/doc_fragments 2023-04-28 05:57:45,191 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/doc_fragments 2023-04-28 05:57:45,191 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/doc_fragments/robot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/doc_fragments 2023-04-28 05:57:45,192 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/inventory 2023-04-28 05:57:45,192 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/inventory/robot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/inventory 2023-04-28 05:57:45,192 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,192 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/failover_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,192 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/reset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,193 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/reverse_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,193 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,193 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/boot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,193 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/ssh_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,193 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/firewall_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,194 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/failover_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,194 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,194 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/ssh_key_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,194 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,194 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/modules/v_switch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/modules 2023-04-28 05:57:45,195 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/module_utils 2023-04-28 05:57:45,195 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/module_utils/failover.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/module_utils 2023-04-28 05:57:45,195 root INFO copying build/lib/ansible_collections/community/hrobot/plugins/module_utils/robot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/plugins/module_utils 2023-04-28 05:57:45,195 root INFO copying build/lib/ansible_collections/community/hrobot/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,195 root INFO copying build/lib/ansible_collections/community/hrobot/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,196 root INFO copying build/lib/ansible_collections/community/hrobot/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,196 root INFO copying build/lib/ansible_collections/community/hrobot/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,196 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/meta 2023-04-28 05:57:45,196 root INFO copying build/lib/ansible_collections/community/hrobot/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/meta 2023-04-28 05:57:45,196 root INFO copying build/lib/ansible_collections/community/hrobot/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/meta 2023-04-28 05:57:45,197 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/LICENSES 2023-04-28 05:57:45,197 root INFO copying build/lib/ansible_collections/community/hrobot/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/LICENSES 2023-04-28 05:57:45,197 root INFO copying build/lib/ansible_collections/community/hrobot/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/LICENSES 2023-04-28 05:57:45,197 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:45,197 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/changelogs/fragments 2023-04-28 05:57:45,198 root INFO copying build/lib/ansible_collections/community/hrobot/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/changelogs/fragments 2023-04-28 05:57:45,198 root INFO copying build/lib/ansible_collections/community/hrobot/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:45,198 root INFO copying build/lib/ansible_collections/community/hrobot/changelogs/changelog.yaml.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:45,198 root INFO copying build/lib/ansible_collections/community/hrobot/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot/changelogs 2023-04-28 05:57:45,198 root INFO copying build/lib/ansible_collections/community/hrobot/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,199 root INFO copying build/lib/ansible_collections/community/hrobot/CHANGELOG.rst.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hrobot 2023-04-28 05:57:45,199 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,199 root INFO copying build/lib/ansible_collections/community/vmware/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,199 root INFO copying build/lib/ansible_collections/community/vmware/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,199 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins 2023-04-28 05:57:45,200 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:45,200 root INFO copying build/lib/ansible_collections/community/vmware/plugins/doc_fragments/vmware_rest_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:45,200 root INFO copying build/lib/ansible_collections/community/vmware/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:45,200 root INFO copying build/lib/ansible_collections/community/vmware/plugins/doc_fragments/vmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/doc_fragments 2023-04-28 05:57:45,200 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:45,201 root INFO copying build/lib/ansible_collections/community/vmware/plugins/inventory/vmware_vm_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:45,201 root INFO copying build/lib/ansible_collections/community/vmware/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:45,201 root INFO copying build/lib/ansible_collections/community/vmware/plugins/inventory/vmware_host_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/inventory 2023-04-28 05:57:45,201 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/connection 2023-04-28 05:57:45,201 root INFO copying build/lib/ansible_collections/community/vmware/plugins/connection/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/connection 2023-04-28 05:57:45,202 root INFO copying build/lib/ansible_collections/community/vmware/plugins/connection/vmware_tools.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/connection 2023-04-28 05:57:45,202 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,202 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_portgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,202 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_object_role_permission.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,202 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_datastore_cluster_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,203 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_datastore_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,203 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_datacenter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,203 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_content_library_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,203 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vsan_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,204 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_capability_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,204 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_local_user_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,204 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_vgpu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,204 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,204 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_ntp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,205 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_pvlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,205 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_logbundle_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,205 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_deploy_ovf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,205 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_storage_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,205 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,206 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vcenter_domain_user_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,206 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_local_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,206 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,206 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vspan_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,207 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vcenter_statistics.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,207 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_tag_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,207 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,207 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_content_deploy_ovf_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,207 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_storage_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,208 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vcenter_extension.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,208 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,208 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_datacenter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,208 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,209 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_serial_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,209 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_move.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,209 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,209 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_datastore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,209 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_sendkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,210 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_host_drs_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,210 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,210 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_customization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,210 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_resource_pool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,210 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_scsidisk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,211 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_vmnic_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,211 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vc_infraprofile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,211 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,211 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_custom_attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,212 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_export_ovf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,212 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_recommended_datastore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,212 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_datastore_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,212 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vcenter_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,212 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_object_role_permission_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,213 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,213 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_resource_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,213 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vmotion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,213 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,214 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_config_option.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,214 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_instant_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,214 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_maintenancemode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,214 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_drs_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,215 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,215 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_acceptance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,215 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_drs_group_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,215 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_local_role_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,215 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_vss_dvs_migrate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,216 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_drs_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,216 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vmkernel_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,216 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cluster_drs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,216 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_dns_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,216 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_lockdown.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,217 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_passthrough.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,217 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_auto_start.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,217 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_content_deploy_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,217 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_shell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,217 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_register_operation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,218 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vcenter_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,218 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_ssl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,218 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_uplink_pg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,218 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,219 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,219 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cluster_dpm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,219 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_sriov.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,219 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,220 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,220 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_scanhba.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,220 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,220 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_logbundle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,220 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_custom_attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,221 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_iscsi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,221 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_config_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,221 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,221 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,221 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,222 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_tpm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,222 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vcenter_standard_key_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,222 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_vgpu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,222 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cluster_ha.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,223 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_storage_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,223 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_boot_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,223 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cfg_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,223 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vsphere_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,223 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_boot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,224 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_category.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,224 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_kernel_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,224 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,224 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_wait.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,224 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vsan_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,225 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_folder_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,225 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_firewall_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,225 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_cross_vc_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,225 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_custom_attribute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,225 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cluster_vsan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,226 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_nioc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,226 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_iscsi_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,226 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_find.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,226 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_local_role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,227 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_custom_attribute_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,227 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_first_class_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,227 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup_find.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,227 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_powermgmt_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,227 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_active_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,228 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_hyperthreading.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,228 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_about_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,228 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_upgrade.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,228 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_drs_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,229 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_portgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,229 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_custom_attribute_defs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,229 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,229 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_lockdown_exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,230 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vswitch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,230 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_migrate_vmk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,230 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,230 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_vmhba_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,230 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vcenter_folder.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,231 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vcenter_license.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,231 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_tcpip_stacks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,231 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_evc_mode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,231 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,231 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_content_library_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,232 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_tag_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,232 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vm_vm_drs_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,232 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_cluster_vcls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,232 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_object_rename.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,233 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_datastore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,233 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_powerstate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,233 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,233 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,233 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_package_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,234 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_service_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,234 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vmkernel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,234 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_datastore_maintenancemode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,234 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vcenter_extension_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,235 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,235 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_vsan_hcl_db.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,235 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,235 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_dvs_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,235 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_video.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,236 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_feature_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,236 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_file_operation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,236 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_screenshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,236 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_guest_powerstate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,237 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,237 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_category_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,237 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_object_custom_attributes_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,237 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_user_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,237 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vsphere_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,238 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_host_firewall_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,238 root INFO copying build/lib/ansible_collections/community/vmware/plugins/modules/vmware_target_canonical_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/modules 2023-04-28 05:57:45,238 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/plugin_utils 2023-04-28 05:57:45,238 root INFO copying build/lib/ansible_collections/community/vmware/plugins/plugin_utils/inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/plugin_utils 2023-04-28 05:57:45,238 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/httpapi 2023-04-28 05:57:45,239 root INFO copying build/lib/ansible_collections/community/vmware/plugins/httpapi/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/httpapi 2023-04-28 05:57:45,239 root INFO copying build/lib/ansible_collections/community/vmware/plugins/httpapi/vmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/httpapi 2023-04-28 05:57:45,239 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:45,239 root INFO copying build/lib/ansible_collections/community/vmware/plugins/module_utils/vmware_rest_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:45,239 root INFO copying build/lib/ansible_collections/community/vmware/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:45,240 root INFO copying build/lib/ansible_collections/community/vmware/plugins/module_utils/vmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:45,240 root INFO copying build/lib/ansible_collections/community/vmware/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:45,240 root INFO copying build/lib/ansible_collections/community/vmware/plugins/module_utils/vm_device_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:45,240 root INFO copying build/lib/ansible_collections/community/vmware/plugins/module_utils/vmware_spbm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/plugins/module_utils 2023-04-28 05:57:45,241 root INFO copying build/lib/ansible_collections/community/vmware/testing.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,241 root INFO copying build/lib/ansible_collections/community/vmware/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,241 root INFO copying build/lib/ansible_collections/community/vmware/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,242 root INFO copying build/lib/ansible_collections/community/vmware/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,242 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/meta 2023-04-28 05:57:45,242 root INFO copying build/lib/ansible_collections/community/vmware/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/meta 2023-04-28 05:57:45,242 root INFO copying build/lib/ansible_collections/community/vmware/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,242 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/LICENSES 2023-04-28 05:57:45,243 root INFO copying build/lib/ansible_collections/community/vmware/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/LICENSES 2023-04-28 05:57:45,243 root INFO copying build/lib/ansible_collections/community/vmware/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/LICENSES 2023-04-28 05:57:45,243 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/tools 2023-04-28 05:57:45,243 root INFO copying build/lib/ansible_collections/community/vmware/tools/check-ignores-order -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/tools 2023-04-28 05:57:45,243 root INFO copying build/lib/ansible_collections/community/vmware/tools/create_documentation_tasks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/tools 2023-04-28 05:57:45,244 root INFO copying build/lib/ansible_collections/community/vmware/tools/unset_version.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/tools 2023-04-28 05:57:45,244 root INFO copying build/lib/ansible_collections/community/vmware/tools/update_documentation.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/tools 2023-04-28 05:57:45,244 root INFO copying build/lib/ansible_collections/community/vmware/tools/prepare_release.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/tools 2023-04-28 05:57:45,244 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/changelogs 2023-04-28 05:57:45,244 root INFO copying build/lib/ansible_collections/community/vmware/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/changelogs 2023-04-28 05:57:45,245 root INFO copying build/lib/ansible_collections/community/vmware/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/changelogs 2023-04-28 05:57:45,245 root INFO copying build/lib/ansible_collections/community/vmware/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,245 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/scripts 2023-04-28 05:57:45,245 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:45,246 root INFO copying build/lib/ansible_collections/community/vmware/scripts/inventory/vmware_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:45,246 root INFO copying build/lib/ansible_collections/community/vmware/scripts/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:45,246 root INFO copying build/lib/ansible_collections/community/vmware/scripts/inventory/vmware_inventory.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:45,246 root INFO copying build/lib/ansible_collections/community/vmware/scripts/inventory/vmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:45,246 root INFO copying build/lib/ansible_collections/community/vmware/scripts/inventory/vmware.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware/scripts/inventory 2023-04-28 05:57:45,247 root INFO copying build/lib/ansible_collections/community/vmware/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,247 root INFO copying build/lib/ansible_collections/community/vmware/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/vmware 2023-04-28 05:57:45,247 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,247 root INFO copying build/lib/ansible_collections/community/zabbix/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,247 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins 2023-04-28 05:57:45,248 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/doc_fragments 2023-04-28 05:57:45,248 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/doc_fragments/connection_persistent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/doc_fragments 2023-04-28 05:57:45,248 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/doc_fragments/zabbix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/doc_fragments 2023-04-28 05:57:45,248 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/inventory 2023-04-28 05:57:45,248 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/inventory/zabbix_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/inventory 2023-04-28 05:57:45,249 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,249 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,249 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,249 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_mediatype.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,249 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_maintenance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,250 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_usergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,250 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,250 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_discovery_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,250 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_host_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,250 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,251 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_valuemap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,251 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,251 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_hostmacro.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,251 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,252 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_housekeeping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,252 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,252 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,252 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_host_events_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,252 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,253 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,253 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_host_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,253 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_globalmacro.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,253 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_authentication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,254 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_user_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,254 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,254 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,255 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,255 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_group_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,255 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,255 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_autoregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,256 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_user_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,256 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/modules/zabbix_screen.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/modules 2023-04-28 05:57:45,256 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/httpapi 2023-04-28 05:57:45,256 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/httpapi/zabbix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/httpapi 2023-04-28 05:57:45,256 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:45,257 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/module_utils/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:45,257 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:45,257 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/module_utils/helpers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:45,257 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/module_utils/wrappers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:45,257 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:45,258 root INFO copying build/lib/ansible_collections/community/zabbix/plugins/module_utils/api_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/plugins/module_utils 2023-04-28 05:57:45,258 root INFO copying build/lib/ansible_collections/community/zabbix/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,258 root INFO copying build/lib/ansible_collections/community/zabbix/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,258 root INFO copying build/lib/ansible_collections/community/zabbix/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,259 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/meta 2023-04-28 05:57:45,259 root INFO copying build/lib/ansible_collections/community/zabbix/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/meta 2023-04-28 05:57:45,259 root INFO copying build/lib/ansible_collections/community/zabbix/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,259 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule 2023-04-28 05:57:45,259 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests 2023-04-28 05:57:45,260 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule 2023-04-28 05:57:45,260 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk 2023-04-28 05:57:45,260 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests 2023-04-28 05:57:45,260 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk 2023-04-28 05:57:45,260 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk/test_auto_psk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk 2023-04-28 05:57:45,260 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common 2023-04-28 05:57:45,261 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common/test_agent2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common 2023-04-28 05:57:45,261 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/conftest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests 2023-04-28 05:57:45,261 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common 2023-04-28 05:57:45,261 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common/test_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common 2023-04-28 05:57:45,261 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk 2023-04-28 05:57:45,262 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default 2023-04-28 05:57:45,262 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests 2023-04-28 05:57:45,262 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk 2023-04-28 05:57:45,262 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk/test_no_auto_psk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk 2023-04-28 05:57:45,262 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/conftest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests 2023-04-28 05:57:45,263 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common 2023-04-28 05:57:45,263 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common/test_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common 2023-04-28 05:57:45,263 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default 2023-04-28 05:57:45,263 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk 2023-04-28 05:57:45,263 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests 2023-04-28 05:57:45,263 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk 2023-04-28 05:57:45,264 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk/test_auto_psk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk 2023-04-28 05:57:45,264 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/conftest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests 2023-04-28 05:57:45,264 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common 2023-04-28 05:57:45,264 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common/test_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common 2023-04-28 05:57:45,264 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk 2023-04-28 05:57:45,265 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2 2023-04-28 05:57:45,265 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests 2023-04-28 05:57:45,265 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk 2023-04-28 05:57:45,265 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk/test_no_auto_psk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk 2023-04-28 05:57:45,265 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common 2023-04-28 05:57:45,265 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common/test_agent2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common 2023-04-28 05:57:45,266 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/conftest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests 2023-04-28 05:57:45,266 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common 2023-04-28 05:57:45,266 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common/test_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common 2023-04-28 05:57:45,266 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2 2023-04-28 05:57:45,266 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common 2023-04-28 05:57:45,267 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests 2023-04-28 05:57:45,267 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk 2023-04-28 05:57:45,267 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk/test_no_auto_psk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk 2023-04-28 05:57:45,267 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk 2023-04-28 05:57:45,267 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk/test_auto_psk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk 2023-04-28 05:57:45,268 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common 2023-04-28 05:57:45,268 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common/test_agent2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common 2023-04-28 05:57:45,268 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/test_docker.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests 2023-04-28 05:57:45,268 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common 2023-04-28 05:57:45,268 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common/test_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common 2023-04-28 05:57:45,269 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks 2023-04-28 05:57:45,269 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks 2023-04-28 05:57:45,269 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks 2023-04-28 05:57:45,269 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common 2023-04-28 05:57:45,269 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:45,269 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests 2023-04-28 05:57:45,270 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests 2023-04-28 05:57:45,270 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:45,270 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:45,270 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_javagateway/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_javagateway 2023-04-28 05:57:45,270 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:45,271 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_server/tests 2023-04-28 05:57:45,271 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_server/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_server/tests 2023-04-28 05:57:45,271 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_server/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:45,271 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_server/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:45,271 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_server/destroy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:45,272 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_server/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_server 2023-04-28 05:57:45,272 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:45,272 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_proxy/tests 2023-04-28 05:57:45,272 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_proxy/tests 2023-04-28 05:57:45,272 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:45,272 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:45,273 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy/destroy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:45,273 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_proxy/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_proxy 2023-04-28 05:57:45,273 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:45,273 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web/tests 2023-04-28 05:57:45,273 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web/tests 2023-04-28 05:57:45,274 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:45,274 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:45,274 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/destroy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:45,274 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:45,274 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/zabbix_web/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule/zabbix_web 2023-04-28 05:57:45,275 root INFO copying build/lib/ansible_collections/community/zabbix/molecule/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/molecule 2023-04-28 05:57:45,275 root INFO copying build/lib/ansible_collections/community/zabbix/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,275 root INFO copying build/lib/ansible_collections/community/zabbix/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,275 root INFO copying build/lib/ansible_collections/community/zabbix/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,275 root INFO copying build/lib/ansible_collections/community/zabbix/docker-compose.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,276 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:45,276 root INFO copying build/lib/ansible_collections/community/zabbix/changelogs/roles_zabbix64.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:45,276 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/changelogs/fragments 2023-04-28 05:57:45,276 root INFO copying build/lib/ansible_collections/community/zabbix/changelogs/fragments/.gitkeep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/changelogs/fragments 2023-04-28 05:57:45,276 root INFO copying build/lib/ansible_collections/community/zabbix/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:45,277 root INFO copying build/lib/ansible_collections/community/zabbix/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:45,277 root INFO copying build/lib/ansible_collections/community/zabbix/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/changelogs 2023-04-28 05:57:45,277 root INFO copying build/lib/ansible_collections/community/zabbix/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,277 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/scripts 2023-04-28 05:57:45,277 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/scripts/inventory 2023-04-28 05:57:45,278 root INFO copying build/lib/ansible_collections/community/zabbix/scripts/inventory/zabbix.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/scripts/inventory 2023-04-28 05:57:45,278 root INFO copying build/lib/ansible_collections/community/zabbix/scripts/inventory/zabbix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/scripts/inventory 2023-04-28 05:57:45,278 root INFO copying build/lib/ansible_collections/community/zabbix/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,278 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles 2023-04-28 05:57:45,278 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway 2023-04-28 05:57:45,279 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:45,279 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:45,279 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:45,279 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks 2023-04-28 05:57:45,279 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/defaults 2023-04-28 05:57:45,279 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/defaults 2023-04-28 05:57:45,280 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/handlers 2023-04-28 05:57:45,280 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/handlers 2023-04-28 05:57:45,280 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway 2023-04-28 05:57:45,280 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/templates 2023-04-28 05:57:45,280 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/templates/zabbix_java_gateway.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/templates 2023-04-28 05:57:45,281 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:45,281 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:45,281 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:45,281 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:45,281 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/zabbix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/vars 2023-04-28 05:57:45,282 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/meta 2023-04-28 05:57:45,282 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/meta 2023-04-28 05:57:45,282 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/files 2023-04-28 05:57:45,282 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_javagateway/files/systemd.service -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_javagateway/files 2023-04-28 05:57:45,282 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent 2023-04-28 05:57:45,283 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,283 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_common.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,283 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,283 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/firewall.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,283 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/remove.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,284 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Windows.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,284 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Windows_conf.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,284 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_windows.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,284 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/userparameter.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,284 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/macOS.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,285 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,285 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,285 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_windows.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,285 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,285 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_linux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,286 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_linux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,286 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/selinux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,286 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/api.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,286 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,286 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_common.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,287 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Darwin.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,287 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Suse.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,287 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Linux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,287 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Docker.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/tasks 2023-04-28 05:57:45,287 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/defaults 2023-04-28 05:57:45,288 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/defaults 2023-04-28 05:57:45,288 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/handlers 2023-04-28 05:57:45,288 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/handlers 2023-04-28 05:57:45,288 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent 2023-04-28 05:57:45,288 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/templates 2023-04-28 05:57:45,289 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates/zabbix_agent2.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/templates 2023-04-28 05:57:45,289 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters 2023-04-28 05:57:45,289 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters/win_sample.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters 2023-04-28 05:57:45,289 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters/mysql.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters 2023-04-28 05:57:45,289 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/templates/zabbix_agentd.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/templates 2023-04-28 05:57:45,290 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,290 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,290 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/Sangoma.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,290 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/Windows.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,290 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,291 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,291 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/zabbix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,291 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/Darwin.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,291 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/vars/Suse.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/vars 2023-04-28 05:57:45,291 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/meta 2023-04-28 05:57:45,291 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/meta 2023-04-28 05:57:45,292 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule 2023-04-28 05:57:45,292 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:45,292 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:45,292 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests 2023-04-28 05:57:45,292 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests 2023-04-28 05:57:45,293 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/test_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests 2023-04-28 05:57:45,293 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:45,293 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:45,293 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/INSTALL.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:45,293 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:45,294 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server 2023-04-28 05:57:45,294 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/files 2023-04-28 05:57:45,294 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/files/win_sample 2023-04-28 05:57:45,294 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/files/win_sample/doSomething.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/files/win_sample 2023-04-28 05:57:45,294 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_agent/files/sample.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_agent/files 2023-04-28 05:57:45,295 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server 2023-04-28 05:57:45,295 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,295 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,295 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks/scripts.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,295 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,296 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks/postgresql.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,296 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,296 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks/mysql.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,296 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/tasks/selinux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/tasks 2023-04-28 05:57:45,296 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/defaults 2023-04-28 05:57:45,297 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/defaults 2023-04-28 05:57:45,297 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/handlers 2023-04-28 05:57:45,297 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/handlers 2023-04-28 05:57:45,297 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server 2023-04-28 05:57:45,297 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/templates 2023-04-28 05:57:45,298 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/templates/zabbix_server.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/templates 2023-04-28 05:57:45,298 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:45,298 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:45,298 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:45,298 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:45,299 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/vars/zabbix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/vars 2023-04-28 05:57:45,299 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/meta 2023-04-28 05:57:45,299 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/meta 2023-04-28 05:57:45,299 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/files 2023-04-28 05:57:45,299 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/files/install_semodule.bsx -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server/files 2023-04-28 05:57:45,300 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_server/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_server 2023-04-28 05:57:45,300 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy 2023-04-28 05:57:45,300 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,300 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,300 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,301 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/postgresql.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,301 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,301 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/mysql.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,301 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/selinux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,301 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/sqlite3.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/tasks 2023-04-28 05:57:45,302 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/defaults 2023-04-28 05:57:45,302 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/defaults 2023-04-28 05:57:45,302 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/handlers 2023-04-28 05:57:45,302 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/handlers 2023-04-28 05:57:45,302 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy 2023-04-28 05:57:45,303 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/templates 2023-04-28 05:57:45,303 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/templates/zabbix_proxy.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/templates 2023-04-28 05:57:45,303 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:45,303 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:45,303 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:45,304 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:45,304 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars/zabbix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:45,304 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/vars/Amazon.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/vars 2023-04-28 05:57:45,304 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/meta 2023-04-28 05:57:45,304 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/meta 2023-04-28 05:57:45,305 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/files 2023-04-28 05:57:45,305 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/files/install_semodule.bsx -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy/files 2023-04-28 05:57:45,305 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_proxy/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_proxy 2023-04-28 05:57:45,305 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web 2023-04-28 05:57:45,305 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,305 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,306 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,306 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache_Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,306 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache_RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,306 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,306 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/nginx.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,307 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/php_Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,307 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,307 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/selinux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,307 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/tasks/access.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/tasks 2023-04-28 05:57:45,307 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/defaults 2023-04-28 05:57:45,308 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/defaults 2023-04-28 05:57:45,308 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/handlers 2023-04-28 05:57:45,308 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/handlers 2023-04-28 05:57:45,308 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web 2023-04-28 05:57:45,308 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:45,309 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates/apache_vhost.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:45,309 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates/php-fpm.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:45,309 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates/zabbix.conf.php.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:45,309 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/templates/nginx_vhost.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/templates 2023-04-28 05:57:45,309 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,310 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,310 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-22.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,310 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-9.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,310 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-7.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,310 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-11.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,311 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,311 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-18.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,311 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-8.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,311 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/zabbix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,311 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-9.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,312 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-8.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,312 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-10.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,312 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-20.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/vars 2023-04-28 05:57:45,312 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/meta 2023-04-28 05:57:45,312 root INFO copying build/lib/ansible_collections/community/zabbix/roles/zabbix_web/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix/roles/zabbix_web/meta 2023-04-28 05:57:45,312 root INFO copying build/lib/ansible_collections/community/zabbix/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/zabbix 2023-04-28 05:57:45,313 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,313 root INFO copying build/lib/ansible_collections/community/okd/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,313 root INFO copying build/lib/ansible_collections/community/okd/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,313 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins 2023-04-28 05:57:45,313 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/inventory 2023-04-28 05:57:45,314 root INFO copying build/lib/ansible_collections/community/okd/plugins/inventory/openshift.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/inventory 2023-04-28 05:57:45,314 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/connection 2023-04-28 05:57:45,314 root INFO copying build/lib/ansible_collections/community/okd/plugins/connection/oc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/connection 2023-04-28 05:57:45,314 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,314 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,315 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_registry_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,315 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_adm_prune_builds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,315 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_adm_prune_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,315 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/k8s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,315 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_build.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,316 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_adm_prune_deployments.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,316 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_process.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,316 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_adm_migrate_template_instances.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,316 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_adm_prune_images.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,316 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_adm_groups_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,317 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,317 root INFO copying build/lib/ansible_collections/community/okd/plugins/modules/openshift_import_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/modules 2023-04-28 05:57:45,317 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,317 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,318 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_builds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,318 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/k8s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,318 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,318 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_images_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,318 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_deployments.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,319 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_groups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,319 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_process.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,319 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_images.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,319 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,319 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_registry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,320 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_docker_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,320 root INFO copying build/lib/ansible_collections/community/okd/plugins/module_utils/openshift_import_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/plugins/module_utils 2023-04-28 05:57:45,320 root INFO copying build/lib/ansible_collections/community/okd/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,320 root INFO copying build/lib/ansible_collections/community/okd/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,320 root INFO copying build/lib/ansible_collections/community/okd/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,321 root INFO copying build/lib/ansible_collections/community/okd/setup.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,321 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/meta 2023-04-28 05:57:45,321 root INFO copying build/lib/ansible_collections/community/okd/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/meta 2023-04-28 05:57:45,321 root INFO copying build/lib/ansible_collections/community/okd/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,321 root INFO copying build/lib/ansible_collections/community/okd/OWNERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,322 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule 2023-04-28 05:57:45,322 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:45,322 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,322 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_prune_images.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,322 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_deployments.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,323 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_auth_roles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,323 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/validate_not_installed.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,323 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_process.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,323 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/validate_installed.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,323 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_auth_clusterroles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,324 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_builds.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,324 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_auth.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,324 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_route.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,324 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/tasks/openshift_import_images.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/tasks 2023-04-28 05:57:45,324 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:45,325 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/vars 2023-04-28 05:57:45,325 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/vars 2023-04-28 05:57:45,325 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/verify.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:45,325 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:45,325 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:45,326 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,326 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/simple-template.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,326 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/setup-crd.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,326 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/kuard-extra-property.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,326 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/crd-resource.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,327 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/example.env -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,327 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/nginx.env -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,327 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/kuard-invalid-type.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,327 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/files/pod-template.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/files 2023-04-28 05:57:45,327 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/destroy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:45,328 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles 2023-04-28 05:57:45,328 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups 2023-04-28 05:57:45,328 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:45,328 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/augmentedActiveDirectory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:45,328 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/python-ldap-not-installed.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:45,328 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/activeDirectory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:45,329 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:45,329 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/rfc2307.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks 2023-04-28 05:57:45,329 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/defaults 2023-04-28 05:57:45,329 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/defaults 2023-04-28 05:57:45,330 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates 2023-04-28 05:57:45,330 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad 2023-04-28 05:57:45,330 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad/definition.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad 2023-04-28 05:57:45,330 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad/sync-config.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad 2023-04-28 05:57:45,330 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307 2023-04-28 05:57:45,330 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307/definition.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307 2023-04-28 05:57:45,331 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307/sync-config.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307 2023-04-28 05:57:45,331 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad 2023-04-28 05:57:45,331 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad/definition.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad 2023-04-28 05:57:45,331 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad/sync-config.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad 2023-04-28 05:57:45,331 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/meta 2023-04-28 05:57:45,332 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/meta 2023-04-28 05:57:45,332 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library 2023-04-28 05:57:45,332 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/openshift_ldap_entry_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library 2023-04-28 05:57:45,332 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/openshift_ldap_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library 2023-04-28 05:57:45,332 root INFO copying build/lib/ansible_collections/community/okd/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/molecule/default 2023-04-28 05:57:45,333 root INFO copying build/lib/ansible_collections/community/okd/OWNERS_ALIASES -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,333 root INFO copying build/lib/ansible_collections/community/okd/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,333 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/ci 2023-04-28 05:57:45,333 root INFO copying build/lib/ansible_collections/community/okd/ci/doc_fragment_modules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/ci 2023-04-28 05:57:45,333 root INFO copying build/lib/ansible_collections/community/okd/ci/Dockerfile -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/ci 2023-04-28 05:57:45,334 root INFO copying build/lib/ansible_collections/community/okd/ci/downstream_fragments.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/ci 2023-04-28 05:57:45,334 root INFO copying build/lib/ansible_collections/community/okd/ci/downstream.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/ci 2023-04-28 05:57:45,334 root INFO copying build/lib/ansible_collections/community/okd/ci/incluster_integration.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/ci 2023-04-28 05:57:45,334 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/changelogs 2023-04-28 05:57:45,334 root INFO copying build/lib/ansible_collections/community/okd/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/changelogs 2023-04-28 05:57:45,335 root INFO copying build/lib/ansible_collections/community/okd/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/changelogs 2023-04-28 05:57:45,335 root INFO copying build/lib/ansible_collections/community/okd/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd/changelogs 2023-04-28 05:57:45,335 root INFO copying build/lib/ansible_collections/community/okd/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,335 root INFO copying build/lib/ansible_collections/community/okd/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,335 root INFO copying build/lib/ansible_collections/community/okd/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,335 root INFO copying build/lib/ansible_collections/community/okd/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/okd 2023-04-28 05:57:45,336 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,336 root INFO copying build/lib/ansible_collections/community/general/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,336 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins 2023-04-28 05:57:45,336 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/test 2023-04-28 05:57:45,337 root INFO copying build/lib/ansible_collections/community/general/plugins/test/a_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/test 2023-04-28 05:57:45,337 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,337 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/json_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,337 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/time.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,337 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/hashids_encode.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,338 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_months.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,338 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/hashids.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,338 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_years.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,338 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_minutes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,338 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/unicode_normalize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,339 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/hashids_decode.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,339 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_hours.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,339 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/random_mac.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,339 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/jc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,339 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_time_unit.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,340 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/lists_mergeby.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,340 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_seconds.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,340 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/groupby_as_dict.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,340 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/dict.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,340 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/dict_kv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,341 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/from_csv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,341 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_days.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,341 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_milliseconds.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,341 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/version_sort.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,341 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/counter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,342 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/to_weeks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,342 root INFO copying build/lib/ansible_collections/community/general/plugins/filter/crc32.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/filter 2023-04-28 05:57:45,342 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,342 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/oracle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,342 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/vexata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,343 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/gitlab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,343 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/emc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,343 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/pritunl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,343 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/dimensiondata_wait.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,343 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/xenserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,344 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/dimensiondata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,344 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/openswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,344 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/ipa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,344 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/scaleway_waitable_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,344 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/oracle_tags.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,345 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/proxmox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,345 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/opennebula.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,345 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/rackspace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,345 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/lxca_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,345 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/oracle_creatable_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,346 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/hwc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,346 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/utm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,346 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,346 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/oracle_name_option.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,346 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/oracle_wait_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,347 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/oneview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,347 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/bitbucket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,347 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/influxdb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,347 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/manageiq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,347 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/alicloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,348 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/rundeck.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,348 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/nomad.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,348 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/purestorage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,348 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/online.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,348 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/oracle_display_name_option.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,349 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/scaleway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,349 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/redis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,349 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/ibm_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,349 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/hpe3par.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,349 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/auth_basic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,350 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/keycloak.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,350 root INFO copying build/lib/ansible_collections/community/general/plugins/doc_fragments/ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/doc_fragments 2023-04-28 05:57:45,350 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,350 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/linode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,350 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/cobbler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,351 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/lxd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,351 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/proxmox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,351 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/opennebula.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,351 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/virtualbox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,352 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/online.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,352 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/stackpath_compute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,352 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/scaleway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,352 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/xen_orchestra.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,352 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/gitlab_runners.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,353 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/icinga2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,353 root INFO copying build/lib/ansible_collections/community/general/plugins/inventory/nmap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/inventory 2023-04-28 05:57:45,353 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,353 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/saltstack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,353 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/funcd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,354 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/lxd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,354 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/lxc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,354 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/qubes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,354 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/chroot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,354 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/iocage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,355 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/jail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,355 root INFO copying build/lib/ansible_collections/community/general/plugins/connection/zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/connection 2023-04-28 05:57:45,355 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,355 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/unixy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,355 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/jabber.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,356 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/log_plays.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,356 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/null.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,356 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/yaml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,356 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/dense.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,356 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/sumologic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,357 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/slack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,357 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/cgroup_memory_recap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,357 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/diy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,357 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/loganalytics.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,357 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/counter_enabled.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,358 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/logstash.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,358 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/mail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,358 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/logentries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,358 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/splunk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,359 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/elastic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,359 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/context_demo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,359 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/hipchat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,359 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/selective.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,359 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/opentelemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,360 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/syslog_json.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,360 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/say.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,360 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/nrdp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,360 root INFO copying build/lib/ansible_collections/community/general/plugins/callback/logdna.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/callback 2023-04-28 05:57:45,361 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,361 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/idrac_redfish_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,361 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pkgin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,361 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xbps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,362 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_realm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,362 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cpanm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,362 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nomad_job.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,362 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_sudocmd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,363 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pipx_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,363 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_network_interface_address_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,363 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_keypair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,363 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,363 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/github_deploy_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,364 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cronvar.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,364 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/idrac_redfish_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,364 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ilo_redfish_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,364 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,365 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/github_issue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,365 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/opendj_backendprop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,365 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,365 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cobbler_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,365 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,366 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_network_interface_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,366 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/circonus_annotation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,366 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dimensiondata_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,366 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/monit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,366 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_security_group_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,367 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hpilo_boot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,367 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_logical_interconnect_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,367 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,367 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_security_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,368 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xenserver_guest_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,368 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/wakeonlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,368 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_vault.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,368 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/influxdb_retention_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,368 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,369 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/linode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,369 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/imc_rest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,369 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jabber.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,369 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ldap_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,369 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ilo_redfish_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,370 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_clb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,370 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/selinux_permissive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,370 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,370 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/memset_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,370 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,371 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/one_vm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,371 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/memset_memstore_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,371 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pushover.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,371 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ovh_ip_loadbalancing_backend.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,372 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sapcar_extract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,372 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pamd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,372 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/aix_lvol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,372 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/github_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,373 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sensu_silence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,373 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_client_rolemapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,373 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nexmo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,373 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/btrfs_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,373 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/terraform.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,374 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,374 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rhsm_repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,374 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,374 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,375 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/taiga_issue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,375 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/make.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,375 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/filesystem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,375 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/read_csv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,376 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_publicip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,376 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dnsimple.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,376 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/kernel_blacklist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,376 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/github_webhook_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,376 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_tasks_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,377 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/zypper_repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,377 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dnsimple_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,377 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/java_cert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,377 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,377 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gconftool2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,378 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rhsm_release.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,378 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneandone_load_balancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,378 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/influxdb_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,378 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/typetalk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,378 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_group_variable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,379 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/python_requirements_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,379 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_dnszone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,380 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cloudflare_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,380 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_ca_host_key_cert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,380 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/consul_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,380 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/icinga2_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,380 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/filesize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,381 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sensu_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,381 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,381 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/office_365_connector_card.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,381 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dpkg_divert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,381 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_otptoken.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,382 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/udm_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,382 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pritunl_org_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,382 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/macports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,382 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/newrelic_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,383 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_organization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,383 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_authentication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,383 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_clb_ssl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,383 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/java_keystore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,383 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_clientscope.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,384 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/packet_volume_attachment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,384 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_container_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,384 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pulp_repo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,384 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pids.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,385 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/mattermost.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,385 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/iso_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,385 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_clienttemplate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,385 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/alternatives.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,385 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_mon_notification.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,386 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pkg5.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,386 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,386 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_database_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,386 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/capabilities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,387 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/one_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,387 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/influxdb_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,387 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bower.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,387 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lxd_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,387 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/packet_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,388 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redis_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,388 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pipx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,388 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/catapult.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,388 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/logentries_msg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,388 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/stackdriver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,389 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bitbucket_pipeline_known_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,389 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/locale_gen.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,389 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nomad_job_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,389 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sysupgrade.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,390 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_identity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,390 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/modprobe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,390 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,390 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/zfs_delegate_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,390 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_private_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,391 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/iso_customize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,391 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ocapi_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,391 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rundeck_job_run.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,391 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/supervisorctl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,392 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/webfaction_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,392 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,392 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_kvm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,392 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/archive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,393 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_mon_alarm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,393 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_snap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,393 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,393 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_alerts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,393 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_group_members.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,394 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_realm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,394 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pacman.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,394 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/online_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,394 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ssh_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,395 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vdo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,395 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_network_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,395 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipify_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,395 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redis_data_incr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,396 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/discord.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,396 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/mssql_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,396 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_clientscope_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,396 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pritunl_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,396 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/atomic_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,397 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sensu_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,397 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/flatpak.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,397 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_volume_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,397 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_function.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,397 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/consul_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,398 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sensu_subscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,398 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/packet_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,398 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_subca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,398 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/haproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,399 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oci_vcn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,399 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/flowdock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,399 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jenkins_build.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,399 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cloud_init_data_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,399 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,400 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rhn_channel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,400 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bigpanda.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,400 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pacemaker_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,400 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/homectl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,401 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xfconf_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,401 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/maven_artifact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,401 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pagerduty_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,401 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ldap_search.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,401 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_function_namespace_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,402 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_runner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,402 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/btrfs_subvolume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,402 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/open_iscsi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,402 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_project_variable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,403 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,403 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_mon_notification_plan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,403 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_ethernet_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,403 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/webfaction_mailbox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,403 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/spotinst_aws_elastigroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,404 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipwcli_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,404 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,404 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/kibana_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,404 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/profitbricks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,405 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/npm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,405 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/packet_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,405 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jboss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,405 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/smartos_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,406 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ufw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,406 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vexata_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,406 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/aix_inittab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,406 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pip_package_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,406 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/influxdb_write.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,407 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_branch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,407 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,407 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_compute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,407 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/profitbricks_volume_attachments.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,408 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/slack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,408 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_tags.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,408 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/one_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,408 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_nic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,408 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,409 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bundler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,409 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_otpconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,409 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/infinity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,409 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/github_release.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,410 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/homebrew_cask.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,410 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/datadog_event.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,410 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_hook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,410 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/git_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,410 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_eip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,411 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/snap_alias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,411 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_meta.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,411 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_datacenter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,411 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_aaa_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,411 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/emc_vnx_sg_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,412 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_tags_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,412 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/packet_sshkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,412 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/influxdb_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,412 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/facter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,413 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/elasticsearch_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,413 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hponcfg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,413 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_policies.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,413 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_security_group_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,413 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/imgadm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,414 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jira.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,414 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sorcery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,414 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/syslogger.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,414 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,415 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ip_netns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,415 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_smn_topic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,415 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_modify_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,415 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ldap_attrs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,416 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_project_badge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,416 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_queue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,416 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xcc_redfish_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,416 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/memset_zone_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,416 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/aerospike_migrations.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,417 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dnsmadeeasy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,417 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_ethernet_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,417 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xfconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,417 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/zfs_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,418 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nictagadm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,418 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ibm_sa_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,418 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_aaa_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,418 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ovh_monthly_billing.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,418 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,419 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_peering_connect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,419 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jenkins_job.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,419 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pear.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,419 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sl_vm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,419 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/udm_share.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,420 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bitbucket_pipeline_key_pair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,420 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_dnsrecord.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,420 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sysrc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,420 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/spectrum_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,421 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pacman_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,421 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_alert_profiles.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,421 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pagerduty_alert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,421 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hpilo_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,421 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_clb_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,422 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ss_3par_cpg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,422 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lxca_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,422 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/github_repo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,422 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,422 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/crypttab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,423 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,423 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/irc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,423 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/layman.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,423 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vertica_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,424 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,424 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/svc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,424 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/swdepot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,424 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/easy_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,425 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,425 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lvol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,425 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_fcoe_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,425 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_san_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,425 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/znode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,426 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/apt_rpm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,426 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/atomic_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,426 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/memset_zone_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,426 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/udm_dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,427 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/parted.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,427 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_cdb_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,427 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/puppet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,427 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/consul.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,427 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jenkins_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,428 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,428 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/profitbricks_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,428 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/memset_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,428 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_user_rolemapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,429 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneandone_monitoring_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,429 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ali_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,429 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/idrac_redfish_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,429 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/twilio.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,429 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/timezone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,430 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/selogin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,430 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/portinstall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,430 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/snap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,430 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_fc_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,431 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/webfaction_db.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,431 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,431 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/odbc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,431 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pagerduty_change.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,432 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bitbucket_pipeline_variable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,432 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_deploy_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,432 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_san_manager_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,432 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_blueprint_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,432 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_evs_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,433 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pkgutil.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,433 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rundeck_job_executions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,433 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_proxy_auth_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,433 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,434 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipinfoio_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,434 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/one_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,434 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/shutdown.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,434 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_pwpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,434 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/wdc_redfish_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,435 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lxc_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,435 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/svr4pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,435 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pam_limits.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,435 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ovh_ip_failover.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,436 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nginx_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,436 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ibm_sa_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,436 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nmcli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,436 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_aa_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,437 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vmadm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,437 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,437 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/linode_v4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,437 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneandone_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,437 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/zpool_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,438 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/logstash_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,438 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_user_data.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,438 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/memset_dns_reload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,438 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,438 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_cdb_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,439 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneandone_private_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,439 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_container_namespace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,439 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ali_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,439 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_container_registry_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,440 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/packet_ip_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,440 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/snmp_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,440 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/portage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,440 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ejabberd_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,441 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ibm_sa_vol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,441 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pritunl_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,441 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/mas.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,441 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/solaris_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,441 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rpm_ostree_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,442 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,442 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vertica_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,442 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bzr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,442 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_fc_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,442 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dimensiondata_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,443 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/aix_filesystem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,443 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nagios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,443 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/apache2_mod_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,443 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_function_namespace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,444 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/profitbricks_datacenter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,444 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/zfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,444 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/mail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,444 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/apt_repo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,444 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_loadbalancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,445 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/openbsd_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,445 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/github_webhook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,445 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ibm_sa_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,445 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lvg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,446 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xfs_quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,446 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/beadm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,446 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/campfire.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,446 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/osx_defaults.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,446 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/webfaction_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,447 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,447 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/statusio_maintenance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,447 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rundeck_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,447 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redhat_subscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,448 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/spectrum_model_attrs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,448 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ibm_sa_vol_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,448 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hana_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,448 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xattr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,449 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/profitbricks_nic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,449 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_hbacrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,449 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redfish_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,449 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rollbar_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,450 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,450 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/icinga2_feature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,450 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keyring.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,450 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jenkins_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,450 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,451 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lxd_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,451 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,451 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_lb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,451 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/installp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,452 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/iptables_state.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,452 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vertica_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,452 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_network_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,452 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/logentries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,452 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/consul_kv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,453 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/syspatch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,453 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/launchd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,453 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/interfaces_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,453 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,453 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/kdeconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,454 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/yarn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,454 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/librato_annotation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,454 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_cbs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,454 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_storage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,454 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sendgrid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,455 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_policies_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,455 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rocketchat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,455 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/aix_devices.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,455 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keyring_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,456 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/online_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,456 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/stacki_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,456 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/mqtt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,456 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/zypper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,456 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_cbs_attachments.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,457 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vertica_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,457 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rundeck_acl_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,457 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_alert_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,457 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/one_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,458 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/seport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,458 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_sudorule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,458 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_protected_branch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,458 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_ecs_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,459 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_tenant.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,459 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/matrix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,459 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/wdc_redfish_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,459 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,460 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/clc_server_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,460 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pingdom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,460 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gunicorn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,460 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,460 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/runit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,461 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/datadog_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,461 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/jenkins_job_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,461 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/manageiq_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,461 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_ca_host_key_cert_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,462 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/etcd3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,462 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_user_federation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,462 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/composer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,462 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/homebrew_tap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,462 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_cdb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,463 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/dnf_versionlock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,463 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pritunl_org.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,463 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bearychat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,463 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/proxmox_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,464 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_private_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,464 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pkgng.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,464 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pushbullet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,464 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gitlab_project_members.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,464 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cisco_webex.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,465 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_security_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,465 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_mon_entity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,465 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/onepassword_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,465 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_proxy_exception.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,466 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redis_data_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,466 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/htpasswd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,466 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_scaling_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,466 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_sudocmdgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,466 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lbu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,467 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/riak.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,467 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/alerta_customer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,467 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rhevm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,467 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_logical_interconnect_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,468 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xenserver_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,468 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_enclosure_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,468 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cargo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,468 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nsupdate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,468 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/webfaction_app.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,469 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pmem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,469 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/slackpkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,469 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_mon_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,469 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gandi_livedns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,470 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_vpc_security_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,470 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/gconftool2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,470 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/mksysb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,470 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/airbrake_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,470 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vexata_eg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,471 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_authz_authorization_scope.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,471 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ini_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,471 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/telegram.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,471 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/statsd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,472 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_proxy_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,472 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pkg5_publisher.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,472 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hipchat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,472 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/one_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,472 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_sshkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,473 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/honeybadger_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,473 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/openwrt_init.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,473 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redis_data.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,473 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/urpmi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,473 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xenserver_guest_powerstate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,474 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,474 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_function_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,474 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lxca_cmms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,474 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/xenserver_guest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,475 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/apache2_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,475 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ibm_sa_host_ports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,475 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/uptimerobot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,475 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sensu_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,475 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ocapi_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,476 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/copr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,476 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/udm_dns_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,476 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/iso_extract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,476 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/flatpak_remote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,477 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_compute_private_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,477 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_dns_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,477 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneandone_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,477 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/serverless.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,478 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/netcup_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,478 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sefcontext.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,478 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redfish_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,478 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sudoers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,478 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/bitbucket_access_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,479 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_container_namespace_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,479 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rhn_register.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,479 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/scaleway_container_registry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,479 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_files_objects.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,480 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/yum_versionlock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,480 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/cobbler_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,480 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/aix_lvg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,480 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneview_fcoe_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,480 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/udm_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,481 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/heroku_collaborator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,481 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/hwc_network_vpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,481 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/grove.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,481 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/sap_task_list_execute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,481 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/atomic_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,482 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/nosh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,482 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ansible_galaxy_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,482 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_proxy_frontend_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,482 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pagerduty.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,483 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/say.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,483 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/vertica_schema.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,483 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/omapi_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,483 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/django_manage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,483 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_files.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,484 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/pubnub_blocks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,484 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/mssql_db.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,484 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_proxy_frontend.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,484 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/datadog_downtime.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,485 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/homebrew.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,485 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/listen_ports_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,485 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipa_hostgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,485 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/apk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,485 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,486 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipmi_boot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,486 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_clientsecret_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,486 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ldap_passwd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,486 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/swupd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,487 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/utm_proxy_location_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,487 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/redfish_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,487 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/oneandone_public_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,487 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ohai.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,487 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/awall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,488 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_clientsecret_regenerate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,488 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/rax_scaling_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,488 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ilo_redfish_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,488 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/lxd_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,489 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/ipmi_power.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,489 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/deploy_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,489 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/keycloak_identity_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,489 root INFO copying build/lib/ansible_collections/community/general/plugins/modules/opkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/modules 2023-04-28 05:57:45,490 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/action 2023-04-28 05:57:45,490 root INFO copying build/lib/ansible_collections/community/general/plugins/action/shutdown.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/action 2023-04-28 05:57:45,490 root INFO copying build/lib/ansible_collections/community/general/plugins/action/iptables_state.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/action 2023-04-28 05:57:45,490 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,490 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/memset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,490 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,491 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/oracle 2023-04-28 05:57:45,491 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/oracle/oci_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/oracle 2023-04-28 05:57:45,491 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/saslprep.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,491 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/linode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,492 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/vexata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,492 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/gitlab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,492 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/cloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,492 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/gandi_livedns_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,492 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/lxd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,493 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/btrfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,493 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/oneandone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,493 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:45,493 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:45,493 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:45,494 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins/cmd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:45,494 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins/deprecate_attrs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:45,494 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins/vars.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:45,494 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins/state.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:45,494 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/mixins/deps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh/mixins 2023-04-28 05:57:45,495 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:45,495 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/deco.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:45,495 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/mh/module_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/mh 2023-04-28 05:57:45,495 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/jenkins.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,495 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/ibm_sa_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,496 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/rax.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,496 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/xenserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,496 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/dimensiondata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,496 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/pipx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,497 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/ipa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,497 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/alicloud_ecs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,497 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/_stormssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,497 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/proxmox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,497 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/opennebula.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,498 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/utm_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,498 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/remote_management 2023-04-28 05:57:45,498 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/remote_management/lxca 2023-04-28 05:57:45,498 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/remote_management/lxca/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/remote_management/lxca 2023-04-28 05:57:45,498 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/source_control 2023-04-28 05:57:45,499 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/source_control/bitbucket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/source_control 2023-04-28 05:57:45,499 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/net_tools 2023-04-28 05:57:45,499 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/net_tools/pritunl 2023-04-28 05:57:45,499 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/net_tools/pritunl/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/net_tools/pritunl 2023-04-28 05:57:45,499 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/xfconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,500 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/identity 2023-04-28 05:57:45,500 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/identity/keycloak 2023-04-28 05:57:45,500 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/identity/keycloak/keycloak.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/identity/keycloak 2023-04-28 05:57:45,500 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/identity/keycloak/keycloak_clientsecret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/identity/keycloak 2023-04-28 05:57:45,500 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/pure.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,501 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/onepassword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,501 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/puppet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,501 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/oneview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,501 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/_mount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,501 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/influxdb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,502 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/manageiq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,502 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/cmd_runner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,502 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/rundeck.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,502 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/wdc_redfish_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,503 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/hwc_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,503 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/online.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,503 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/redhat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,503 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/storage 2023-04-28 05:57:45,503 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/storage/emc 2023-04-28 05:57:45,504 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/storage/emc/emc_vnx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/storage/emc 2023-04-28 05:57:45,504 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/storage/hpe3par 2023-04-28 05:57:45,504 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/storage/hpe3par/hpe3par.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils/storage/hpe3par 2023-04-28 05:57:45,504 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,505 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/scaleway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,505 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/heroku.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,505 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/redis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,505 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/redfish_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,506 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/csv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,506 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/univention_umc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,506 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/module_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,506 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,507 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/gconftool2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,507 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/ocapi_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,507 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,507 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/deps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,507 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/ilo_redfish_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,508 root INFO copying build/lib/ansible_collections/community/general/plugins/module_utils/known_hosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/module_utils 2023-04-28 05:57:45,508 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,508 root INFO copying build/lib/ansible_collections/community/general/plugins/become/doas.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,508 root INFO copying build/lib/ansible_collections/community/general/plugins/become/sudosu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,508 root INFO copying build/lib/ansible_collections/community/general/plugins/become/pfexec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,509 root INFO copying build/lib/ansible_collections/community/general/plugins/become/ksu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,509 root INFO copying build/lib/ansible_collections/community/general/plugins/become/machinectl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,509 root INFO copying build/lib/ansible_collections/community/general/plugins/become/pmrun.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,509 root INFO copying build/lib/ansible_collections/community/general/plugins/become/sesu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,509 root INFO copying build/lib/ansible_collections/community/general/plugins/become/pbrun.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,510 root INFO copying build/lib/ansible_collections/community/general/plugins/become/dzdo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/become 2023-04-28 05:57:45,510 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,510 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/lmdb_kv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,510 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/dsv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,510 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/onepassword_raw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,511 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/cyberarkpassword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,511 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/hiera.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,511 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/credstash.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,511 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/cartesian.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,511 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/random_string.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,512 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/filetree.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,512 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/passwordstore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,512 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/tss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,512 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/merge_variables.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,512 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/shelvefile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,513 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/random_words.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,513 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/dependent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,513 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/onepassword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,513 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/etcd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,514 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/random_pet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,514 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/dnstxt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,514 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/keyring.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,514 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/redis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,514 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/consul_kv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,514 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/collection_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,515 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/flattened.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,515 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/bitwarden.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,515 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/etcd3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,515 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/lastpass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,515 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/chef_databag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,516 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/dig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,516 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/manifold.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,516 root INFO copying build/lib/ansible_collections/community/general/plugins/lookup/revbitspss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/lookup 2023-04-28 05:57:45,516 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:45,517 root INFO copying build/lib/ansible_collections/community/general/plugins/cache/yaml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:45,517 root INFO copying build/lib/ansible_collections/community/general/plugins/cache/pickle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:45,517 root INFO copying build/lib/ansible_collections/community/general/plugins/cache/memcached.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:45,517 root INFO copying build/lib/ansible_collections/community/general/plugins/cache/redis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/plugins/cache 2023-04-28 05:57:45,517 root INFO copying build/lib/ansible_collections/community/general/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,518 root INFO copying build/lib/ansible_collections/community/general/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,519 root INFO copying build/lib/ansible_collections/community/general/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,519 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/meta 2023-04-28 05:57:45,519 root INFO copying build/lib/ansible_collections/community/general/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/meta 2023-04-28 05:57:45,520 root INFO copying build/lib/ansible_collections/community/general/commit-rights.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,520 root INFO copying build/lib/ansible_collections/community/general/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,521 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/LICENSES 2023-04-28 05:57:45,521 root INFO copying build/lib/ansible_collections/community/general/LICENSES/MIT.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/LICENSES 2023-04-28 05:57:45,521 root INFO copying build/lib/ansible_collections/community/general/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/LICENSES 2023-04-28 05:57:45,521 root INFO copying build/lib/ansible_collections/community/general/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/LICENSES 2023-04-28 05:57:45,521 root INFO copying build/lib/ansible_collections/community/general/LICENSES/PSF-2.0.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/LICENSES 2023-04-28 05:57:45,522 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/changelogs 2023-04-28 05:57:45,522 root INFO copying build/lib/ansible_collections/community/general/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/changelogs 2023-04-28 05:57:45,522 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/general/changelogs/fragments 2023-04-28 05:57:45,522 root INFO copying build/lib/ansible_collections/community/general/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/changelogs/fragments 2023-04-28 05:57:45,522 root INFO copying build/lib/ansible_collections/community/general/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/changelogs 2023-04-28 05:57:45,523 root INFO copying build/lib/ansible_collections/community/general/changelogs/changelog.yaml.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/changelogs 2023-04-28 05:57:45,523 root INFO copying build/lib/ansible_collections/community/general/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general/changelogs 2023-04-28 05:57:45,523 root INFO copying build/lib/ansible_collections/community/general/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,523 root INFO copying build/lib/ansible_collections/community/general/CHANGELOG.rst.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/general 2023-04-28 05:57:45,524 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,524 root INFO copying build/lib/ansible_collections/community/proxysql/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,524 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins 2023-04-28 05:57:45,524 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins 2023-04-28 05:57:45,524 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/doc_fragments 2023-04-28 05:57:45,525 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/doc_fragments/proxysql.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/doc_fragments 2023-04-28 05:57:45,525 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,525 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_query_rules_fast_routing.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,525 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_mysql_users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,525 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_global_variables.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,526 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_manage_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,526 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_replication_hostgroups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,526 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_scheduler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,526 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,526 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_query_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,527 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/modules/proxysql_backend_servers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/modules 2023-04-28 05:57:45,527 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/module_utils 2023-04-28 05:57:45,527 root INFO copying build/lib/ansible_collections/community/proxysql/plugins/module_utils/mysql.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/plugins/module_utils 2023-04-28 05:57:45,527 root INFO copying build/lib/ansible_collections/community/proxysql/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,527 root INFO copying build/lib/ansible_collections/community/proxysql/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,528 root INFO copying build/lib/ansible_collections/community/proxysql/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,528 root INFO copying build/lib/ansible_collections/community/proxysql/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,528 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/meta 2023-04-28 05:57:45,528 root INFO copying build/lib/ansible_collections/community/proxysql/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/meta 2023-04-28 05:57:45,528 root INFO copying build/lib/ansible_collections/community/proxysql/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,529 root INFO copying build/lib/ansible_collections/community/proxysql/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,529 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/changelogs 2023-04-28 05:57:45,529 root INFO copying build/lib/ansible_collections/community/proxysql/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/changelogs 2023-04-28 05:57:45,529 root INFO copying build/lib/ansible_collections/community/proxysql/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/changelogs 2023-04-28 05:57:45,529 root INFO copying build/lib/ansible_collections/community/proxysql/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,530 root INFO copying build/lib/ansible_collections/community/proxysql/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,530 root INFO copying build/lib/ansible_collections/community/proxysql/REVIEW_CHECKLIST.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,530 root INFO copying build/lib/ansible_collections/community/proxysql/CONTRIBUTORS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql 2023-04-28 05:57:45,530 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles 2023-04-28 05:57:45,530 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql 2023-04-28 05:57:45,531 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:45,531 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks/config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:45,531 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks/setvars.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:45,531 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks/users.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:45,531 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:45,531 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/tasks/install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/tasks 2023-04-28 05:57:45,532 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/defaults 2023-04-28 05:57:45,532 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/defaults 2023-04-28 05:57:45,532 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/handlers 2023-04-28 05:57:45,532 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/handlers 2023-04-28 05:57:45,532 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql 2023-04-28 05:57:45,533 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/templates 2023-04-28 05:57:45,533 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/templates/proxysql.cnf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/templates 2023-04-28 05:57:45,533 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/templates/client.my.cnf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/templates 2023-04-28 05:57:45,533 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/vars 2023-04-28 05:57:45,533 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/vars 2023-04-28 05:57:45,534 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/meta 2023-04-28 05:57:45,534 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/meta 2023-04-28 05:57:45,534 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/molecule 2023-04-28 05:57:45,534 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:45,534 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests 2023-04-28 05:57:45,534 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests 2023-04-28 05:57:45,535 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:45,535 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:45,535 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql/molecule/default 2023-04-28 05:57:45,535 root INFO copying build/lib/ansible_collections/community/proxysql/roles/proxysql/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/proxysql/roles/proxysql 2023-04-28 05:57:45,536 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,536 root INFO copying build/lib/ansible_collections/community/dns/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,536 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins 2023-04-28 05:57:45,536 root INFO copying build/lib/ansible_collections/community/dns/plugins/public_suffix_list.dat.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins 2023-04-28 05:57:45,536 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:45,536 root INFO copying build/lib/ansible_collections/community/dns/plugins/filter/domain_suffix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:45,537 root INFO copying build/lib/ansible_collections/community/dns/plugins/filter/remove_registrable_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:45,537 root INFO copying build/lib/ansible_collections/community/dns/plugins/filter/get_public_suffix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:45,537 root INFO copying build/lib/ansible_collections/community/dns/plugins/filter/remove_public_suffix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:45,537 root INFO copying build/lib/ansible_collections/community/dns/plugins/filter/get_registrable_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/filter 2023-04-28 05:57:45,537 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,538 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/module_record_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,538 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/module_zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,538 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/module_record_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,538 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/hetzner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,538 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/inventory_records.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,539 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,539 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/module_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,539 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/hosttech.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,539 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/module_record_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,539 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/module_record_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,540 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,540 root INFO copying build/lib/ansible_collections/community/dns/plugins/doc_fragments/filters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/doc_fragments 2023-04-28 05:57:45,540 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/inventory 2023-04-28 05:57:45,540 root INFO copying build/lib/ansible_collections/community/dns/plugins/inventory/hosttech_dns_records.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/inventory 2023-04-28 05:57:45,540 root INFO copying build/lib/ansible_collections/community/dns/plugins/inventory/hetzner_dns_records.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/inventory 2023-04-28 05:57:45,541 root INFO copying build/lib/ansible_collections/community/dns/plugins/public_suffix_list.dat -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins 2023-04-28 05:57:45,541 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,541 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hetzner_dns_record_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,542 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hosttech_dns_records.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,542 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hosttech_dns_record_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,542 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hosttech_dns_record_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,542 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hetzner_dns_record_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,542 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hetzner_dns_zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,542 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hosttech_dns_record_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,543 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hosttech_dns_zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,543 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/wait_for_txt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,543 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hosttech_dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,543 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hetzner_dns_record_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,543 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hetzner_dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,544 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hosttech_dns_record_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,544 root INFO copying build/lib/ansible_collections/community/dns/plugins/modules/hetzner_dns_record_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/modules 2023-04-28 05:57:45,544 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/plugin_utils 2023-04-28 05:57:45,544 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/plugin_utils/inventory 2023-04-28 05:57:45,544 root INFO copying build/lib/ansible_collections/community/dns/plugins/plugin_utils/inventory/records.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/plugin_utils/inventory 2023-04-28 05:57:45,545 root INFO copying build/lib/ansible_collections/community/dns/plugins/plugin_utils/templated_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/plugin_utils 2023-04-28 05:57:45,545 root INFO copying build/lib/ansible_collections/community/dns/plugins/plugin_utils/public_suffix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/plugin_utils 2023-04-28 05:57:45,545 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,545 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,545 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/zone_record_helpers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,546 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,546 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/resolver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,546 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/wsdl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,546 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/json_api_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,546 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,547 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/zone_record_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,547 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:45,547 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/hosttech/json_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:45,547 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/hosttech/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:45,547 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/hosttech/wsdl_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/hosttech 2023-04-28 05:57:45,548 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,548 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/module/record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,548 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/module/record_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,548 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/module/record_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,548 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/module/record_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,549 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/module/record_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,549 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/module/_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,549 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/module/zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/module 2023-04-28 05:57:45,549 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/names.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,549 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:45,550 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/conversion/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:45,550 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/conversion/txt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:45,550 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/conversion/converter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/conversion 2023-04-28 05:57:45,550 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/argspec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,550 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,551 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils 2023-04-28 05:57:45,551 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/hetzner 2023-04-28 05:57:45,551 root INFO copying build/lib/ansible_collections/community/dns/plugins/module_utils/hetzner/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/plugins/module_utils/hetzner 2023-04-28 05:57:45,551 root INFO copying build/lib/ansible_collections/community/dns/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,551 root INFO copying build/lib/ansible_collections/community/dns/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,552 root INFO copying build/lib/ansible_collections/community/dns/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,552 root INFO copying build/lib/ansible_collections/community/dns/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,552 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/meta 2023-04-28 05:57:45,552 root INFO copying build/lib/ansible_collections/community/dns/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/meta 2023-04-28 05:57:45,553 root INFO copying build/lib/ansible_collections/community/dns/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/meta 2023-04-28 05:57:45,553 root INFO copying build/lib/ansible_collections/community/dns/meta/ee-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/meta 2023-04-28 05:57:45,553 root INFO copying build/lib/ansible_collections/community/dns/update-docs-fragments.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,553 root INFO copying build/lib/ansible_collections/community/dns/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,553 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/LICENSES 2023-04-28 05:57:45,554 root INFO copying build/lib/ansible_collections/community/dns/LICENSES/MPL-2.0.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/LICENSES 2023-04-28 05:57:45,554 root INFO copying build/lib/ansible_collections/community/dns/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/LICENSES 2023-04-28 05:57:45,554 root INFO copying build/lib/ansible_collections/community/dns/update-psl.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,554 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/changelogs 2023-04-28 05:57:45,554 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/changelogs/fragments 2023-04-28 05:57:45,555 root INFO copying build/lib/ansible_collections/community/dns/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/changelogs/fragments 2023-04-28 05:57:45,555 root INFO copying build/lib/ansible_collections/community/dns/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/changelogs 2023-04-28 05:57:45,555 root INFO copying build/lib/ansible_collections/community/dns/changelogs/changelog.yaml.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/changelogs 2023-04-28 05:57:45,555 root INFO copying build/lib/ansible_collections/community/dns/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns/changelogs 2023-04-28 05:57:45,555 root INFO copying build/lib/ansible_collections/community/dns/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,556 root INFO copying build/lib/ansible_collections/community/dns/CHANGELOG.rst.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,556 root INFO copying build/lib/ansible_collections/community/dns/TESTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/dns 2023-04-28 05:57:45,556 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,556 root INFO copying build/lib/ansible_collections/community/mysql/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,556 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins 2023-04-28 05:57:45,557 root INFO copying build/lib/ansible_collections/community/mysql/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins 2023-04-28 05:57:45,557 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/doc_fragments 2023-04-28 05:57:45,557 root INFO copying build/lib/ansible_collections/community/mysql/plugins/doc_fragments/mysql.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/doc_fragments 2023-04-28 05:57:45,557 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,557 root INFO copying build/lib/ansible_collections/community/mysql/plugins/modules/mysql_variables.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,558 root INFO copying build/lib/ansible_collections/community/mysql/plugins/modules/mysql_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,558 root INFO copying build/lib/ansible_collections/community/mysql/plugins/modules/mysql_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,558 root INFO copying build/lib/ansible_collections/community/mysql/plugins/modules/mysql_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,558 root INFO copying build/lib/ansible_collections/community/mysql/plugins/modules/mysql_replication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,558 root INFO copying build/lib/ansible_collections/community/mysql/plugins/modules/mysql_db.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,559 root INFO copying build/lib/ansible_collections/community/mysql/plugins/modules/mysql_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/modules 2023-04-28 05:57:45,559 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:45,559 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:45,559 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/mysql.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:45,560 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations 2023-04-28 05:57:45,560 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:45,560 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:45,560 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/replication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:45,560 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql 2023-04-28 05:57:45,560 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:45,561 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:45,561 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/replication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:45,561 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb 2023-04-28 05:57:45,561 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:45,561 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:45,562 root INFO copying build/lib/ansible_collections/community/mysql/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/plugins/module_utils 2023-04-28 05:57:45,562 root INFO copying build/lib/ansible_collections/community/mysql/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,562 root INFO copying build/lib/ansible_collections/community/mysql/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,562 root INFO copying build/lib/ansible_collections/community/mysql/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,562 root INFO copying build/lib/ansible_collections/community/mysql/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,563 root INFO copying build/lib/ansible_collections/community/mysql/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,563 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/meta 2023-04-28 05:57:45,563 root INFO copying build/lib/ansible_collections/community/mysql/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/meta 2023-04-28 05:57:45,563 root INFO copying build/lib/ansible_collections/community/mysql/simplified_bsd.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,563 root INFO copying build/lib/ansible_collections/community/mysql/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,564 root INFO copying build/lib/ansible_collections/community/mysql/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,564 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/changelogs 2023-04-28 05:57:45,564 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/changelogs/fragments 2023-04-28 05:57:45,564 root INFO copying build/lib/ansible_collections/community/mysql/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/changelogs/fragments 2023-04-28 05:57:45,564 root INFO copying build/lib/ansible_collections/community/mysql/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/changelogs 2023-04-28 05:57:45,565 root INFO copying build/lib/ansible_collections/community/mysql/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql/changelogs 2023-04-28 05:57:45,565 root INFO copying build/lib/ansible_collections/community/mysql/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,565 root INFO copying build/lib/ansible_collections/community/mysql/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,565 root INFO copying build/lib/ansible_collections/community/mysql/CONTRIBUTORS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mysql 2023-04-28 05:57:45,565 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,566 root INFO copying build/lib/ansible_collections/community/sops/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,566 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins 2023-04-28 05:57:45,566 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/filter 2023-04-28 05:57:45,566 root INFO copying build/lib/ansible_collections/community/sops/plugins/filter/decrypt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/filter 2023-04-28 05:57:45,566 root INFO copying build/lib/ansible_collections/community/sops/plugins/filter/_latest_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/filter 2023-04-28 05:57:45,567 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/doc_fragments 2023-04-28 05:57:45,567 root INFO copying build/lib/ansible_collections/community/sops/plugins/doc_fragments/sops.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/doc_fragments 2023-04-28 05:57:45,567 root INFO copying build/lib/ansible_collections/community/sops/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/doc_fragments 2023-04-28 05:57:45,567 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/vars 2023-04-28 05:57:45,567 root INFO copying build/lib/ansible_collections/community/sops/plugins/vars/sops.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/vars 2023-04-28 05:57:45,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/modules 2023-04-28 05:57:45,568 root INFO copying build/lib/ansible_collections/community/sops/plugins/modules/load_vars.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/modules 2023-04-28 05:57:45,568 root INFO copying build/lib/ansible_collections/community/sops/plugins/modules/sops_encrypt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/modules 2023-04-28 05:57:45,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/plugin_utils 2023-04-28 05:57:45,568 root INFO copying build/lib/ansible_collections/community/sops/plugins/plugin_utils/action_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/plugin_utils 2023-04-28 05:57:45,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/action 2023-04-28 05:57:45,569 root INFO copying build/lib/ansible_collections/community/sops/plugins/action/load_vars.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/action 2023-04-28 05:57:45,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/module_utils 2023-04-28 05:57:45,569 root INFO copying build/lib/ansible_collections/community/sops/plugins/module_utils/sops.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/module_utils 2023-04-28 05:57:45,569 root INFO copying build/lib/ansible_collections/community/sops/plugins/module_utils/io.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/module_utils 2023-04-28 05:57:45,570 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/lookup 2023-04-28 05:57:45,570 root INFO copying build/lib/ansible_collections/community/sops/plugins/lookup/sops.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/plugins/lookup 2023-04-28 05:57:45,570 root INFO copying build/lib/ansible_collections/community/sops/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,570 root INFO copying build/lib/ansible_collections/community/sops/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,570 root INFO copying build/lib/ansible_collections/community/sops/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,571 root INFO copying build/lib/ansible_collections/community/sops/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,571 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/meta 2023-04-28 05:57:45,571 root INFO copying build/lib/ansible_collections/community/sops/meta/ee-bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/meta 2023-04-28 05:57:45,571 root INFO copying build/lib/ansible_collections/community/sops/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/meta 2023-04-28 05:57:45,571 root INFO copying build/lib/ansible_collections/community/sops/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/meta 2023-04-28 05:57:45,572 root INFO copying build/lib/ansible_collections/community/sops/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,572 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/LICENSES 2023-04-28 05:57:45,572 root INFO copying build/lib/ansible_collections/community/sops/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/LICENSES 2023-04-28 05:57:45,572 root INFO copying build/lib/ansible_collections/community/sops/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/LICENSES 2023-04-28 05:57:45,572 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/playbooks 2023-04-28 05:57:45,573 root INFO copying build/lib/ansible_collections/community/sops/playbooks/install_localhost.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/playbooks 2023-04-28 05:57:45,573 root INFO copying build/lib/ansible_collections/community/sops/playbooks/install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/playbooks 2023-04-28 05:57:45,573 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/changelogs 2023-04-28 05:57:45,573 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/changelogs/fragments 2023-04-28 05:57:45,573 root INFO copying build/lib/ansible_collections/community/sops/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/changelogs/fragments 2023-04-28 05:57:45,574 root INFO copying build/lib/ansible_collections/community/sops/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/changelogs 2023-04-28 05:57:45,574 root INFO copying build/lib/ansible_collections/community/sops/changelogs/changelog.yaml.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/changelogs 2023-04-28 05:57:45,574 root INFO copying build/lib/ansible_collections/community/sops/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/changelogs 2023-04-28 05:57:45,574 root INFO copying build/lib/ansible_collections/community/sops/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,574 root INFO copying build/lib/ansible_collections/community/sops/CHANGELOG.rst.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops 2023-04-28 05:57:45,575 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles 2023-04-28 05:57:45,575 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install 2023-04-28 05:57:45,575 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:45,575 root INFO copying build/lib/ansible_collections/community/sops/roles/install/tasks/github_latest_release.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:45,575 root INFO copying build/lib/ansible_collections/community/sops/roles/install/tasks/detect_source.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:45,575 root INFO copying build/lib/ansible_collections/community/sops/roles/install/tasks/github_api.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:45,576 root INFO copying build/lib/ansible_collections/community/sops/roles/install/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:45,576 root INFO copying build/lib/ansible_collections/community/sops/roles/install/tasks/system.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:45,576 root INFO copying build/lib/ansible_collections/community/sops/roles/install/tasks/github.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/tasks 2023-04-28 05:57:45,576 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/defaults 2023-04-28 05:57:45,576 root INFO copying build/lib/ansible_collections/community/sops/roles/install/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/defaults 2023-04-28 05:57:45,577 root INFO copying build/lib/ansible_collections/community/sops/roles/install/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install 2023-04-28 05:57:45,577 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:45,577 root INFO copying build/lib/ansible_collections/community/sops/roles/install/vars/D-Archlinux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:45,577 root INFO copying build/lib/ansible_collections/community/sops/roles/install/vars/D-Alpine.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:45,577 root INFO copying build/lib/ansible_collections/community/sops/roles/install/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:45,578 root INFO copying build/lib/ansible_collections/community/sops/roles/install/vars/OS-Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:45,578 root INFO copying build/lib/ansible_collections/community/sops/roles/install/vars/OS-RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/vars 2023-04-28 05:57:45,578 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/meta 2023-04-28 05:57:45,578 root INFO copying build/lib/ansible_collections/community/sops/roles/install/meta/argument_specs.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/meta 2023-04-28 05:57:45,578 root INFO copying build/lib/ansible_collections/community/sops/roles/install/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/install/meta 2023-04-28 05:57:45,579 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age 2023-04-28 05:57:45,579 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/tasks 2023-04-28 05:57:45,579 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/tasks 2023-04-28 05:57:45,579 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/defaults 2023-04-28 05:57:45,579 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/defaults 2023-04-28 05:57:45,579 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age 2023-04-28 05:57:45,580 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,580 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/D-Debian-10.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,580 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/D-Archlinux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,580 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-16.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,580 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/D-Alpine.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,581 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,581 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/OS-Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,581 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/D-Fedora.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,581 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-18.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,581 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-20.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/vars 2023-04-28 05:57:45,582 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/meta 2023-04-28 05:57:45,582 root INFO copying build/lib/ansible_collections/community/sops/roles/_install_age/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sops/roles/_install_age/meta 2023-04-28 05:57:45,582 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios 2023-04-28 05:57:45,582 root INFO copying build/lib/ansible_collections/community/fortios/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios 2023-04-28 05:57:45,582 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins 2023-04-28 05:57:45,583 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,583 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_ssl_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,583 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,583 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_spam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,584 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/faz_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,584 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_device_provision_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,584 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,584 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_provisioning.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,584 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_waf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,585 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,585 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_vip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,585 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,585 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_device_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,586 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,586 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,586 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_wanopt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,586 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_appctrl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,587 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_voip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,587 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_fwpol_ipv4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,587 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_ippool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,587 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_ippool6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,587 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,588 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_fwpol_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,588 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_ha.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,588 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_device_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,588 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_web.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,589 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_av.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,589 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_ips.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,589 root INFO copying build/lib/ansible_collections/community/fortios/plugins/modules/fmgr_secprof_profile_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/modules 2023-04-28 05:57:45,589 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/httpapi 2023-04-28 05:57:45,590 root INFO copying build/lib/ansible_collections/community/fortios/plugins/httpapi/fortianalyzer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/httpapi 2023-04-28 05:57:45,590 root INFO copying build/lib/ansible_collections/community/fortios/plugins/httpapi/fortimanager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/httpapi 2023-04-28 05:57:45,590 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/module_utils 2023-04-28 05:57:45,590 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer 2023-04-28 05:57:45,590 root INFO copying build/lib/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer 2023-04-28 05:57:45,591 root INFO copying build/lib/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/fortianalyzer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer 2023-04-28 05:57:45,591 root INFO copying build/lib/ansible_collections/community/fortios/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios 2023-04-28 05:57:45,591 root INFO copying build/lib/ansible_collections/community/fortios/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios 2023-04-28 05:57:45,591 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/meta 2023-04-28 05:57:45,591 root INFO copying build/lib/ansible_collections/community/fortios/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/meta 2023-04-28 05:57:45,592 root INFO copying build/lib/ansible_collections/community/fortios/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios 2023-04-28 05:57:45,592 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/changelogs 2023-04-28 05:57:45,592 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/changelogs/fragments 2023-04-28 05:57:45,592 root INFO copying build/lib/ansible_collections/community/fortios/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/changelogs/fragments 2023-04-28 05:57:45,592 root INFO copying build/lib/ansible_collections/community/fortios/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/changelogs 2023-04-28 05:57:45,593 root INFO copying build/lib/ansible_collections/community/fortios/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios/changelogs 2023-04-28 05:57:45,593 root INFO copying build/lib/ansible_collections/community/fortios/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/fortios 2023-04-28 05:57:45,593 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,593 root INFO copying build/lib/ansible_collections/community/sap/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,593 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins 2023-04-28 05:57:45,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/doc_fragments 2023-04-28 05:57:45,594 root INFO copying build/lib/ansible_collections/community/sap/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/doc_fragments 2023-04-28 05:57:45,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,594 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/sapcar_extract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/database 2023-04-28 05:57:45,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/database/saphana 2023-04-28 05:57:45,595 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/database/saphana/hana_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/database/saphana 2023-04-28 05:57:45,595 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/sap_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,595 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/identity 2023-04-28 05:57:45,595 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/identity/sap_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/identity 2023-04-28 05:57:45,595 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/identity/sap_company.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/identity 2023-04-28 05:57:45,596 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/files 2023-04-28 05:57:45,596 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/files/sapcar_extract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/files 2023-04-28 05:57:45,596 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/sap_snote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,596 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/sap_system_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,596 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:45,597 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/system/sap_snote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:45,597 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/system/sap_system_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:45,597 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/system/sap_task_list_execute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules/system 2023-04-28 05:57:45,597 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/hana_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,597 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/sap_company.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,598 root INFO copying build/lib/ansible_collections/community/sap/plugins/modules/sap_task_list_execute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/modules 2023-04-28 05:57:45,598 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/module_utils 2023-04-28 05:57:45,598 root INFO copying build/lib/ansible_collections/community/sap/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/plugins/module_utils 2023-04-28 05:57:45,598 root INFO copying build/lib/ansible_collections/community/sap/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,598 root INFO copying build/lib/ansible_collections/community/sap/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,599 root INFO copying build/lib/ansible_collections/community/sap/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,599 root INFO copying build/lib/ansible_collections/community/sap/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,599 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/meta 2023-04-28 05:57:45,599 root INFO copying build/lib/ansible_collections/community/sap/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/meta 2023-04-28 05:57:45,599 root INFO copying build/lib/ansible_collections/community/sap/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,600 root INFO copying build/lib/ansible_collections/community/sap/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,600 root INFO copying build/lib/ansible_collections/community/sap/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,600 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/changelogs 2023-04-28 05:57:45,600 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/changelogs/fragments 2023-04-28 05:57:45,600 root INFO copying build/lib/ansible_collections/community/sap/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/changelogs/fragments 2023-04-28 05:57:45,600 root INFO copying build/lib/ansible_collections/community/sap/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/changelogs 2023-04-28 05:57:45,601 root INFO copying build/lib/ansible_collections/community/sap/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap/changelogs 2023-04-28 05:57:45,601 root INFO copying build/lib/ansible_collections/community/sap/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,601 root INFO copying build/lib/ansible_collections/community/sap/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,601 root INFO copying build/lib/ansible_collections/community/sap/REVIEW_CHECKLIST.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap 2023-04-28 05:57:45,601 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto 2023-04-28 05:57:45,602 root INFO copying build/lib/ansible_collections/community/crypto/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto 2023-04-28 05:57:45,602 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins 2023-04-28 05:57:45,602 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:45,602 root INFO copying build/lib/ansible_collections/community/crypto/plugins/filter/x509_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:45,602 root INFO copying build/lib/ansible_collections/community/crypto/plugins/filter/openssl_csr_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:45,603 root INFO copying build/lib/ansible_collections/community/crypto/plugins/filter/openssl_privatekey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:45,603 root INFO copying build/lib/ansible_collections/community/crypto/plugins/filter/openssl_publickey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:45,603 root INFO copying build/lib/ansible_collections/community/crypto/plugins/filter/split_pem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:45,603 root INFO copying build/lib/ansible_collections/community/crypto/plugins/filter/x509_crl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/filter 2023-04-28 05:57:45,604 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,604 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/module_privatekey_convert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,604 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/module_privatekey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,604 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/module_csr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,604 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/name_encoding.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,604 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,605 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/module_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,605 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/ecs_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,605 root INFO copying build/lib/ansible_collections/community/crypto/plugins/doc_fragments/acme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/doc_fragments 2023-04-28 05:57:45,605 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,605 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/acme_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,606 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_dhparam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,606 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_signature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,606 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_privatekey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,606 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/certificate_complete_chain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,607 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/x509_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,607 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/luks_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,607 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_csr_pipe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,607 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssh_cert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,607 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_privatekey_convert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,608 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_privatekey_pipe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,608 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_csr_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,608 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/x509_certificate_pipe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,608 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/acme_challenge_cert_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,608 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/crypto_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,609 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_privatekey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,609 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_publickey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,609 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/get_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,609 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/ecs_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,610 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/acme_certificate_revoke.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,610 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/acme_account_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,610 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/acme_inspect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,610 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssh_keypair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,610 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_csr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,611 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_signature_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,611 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/x509_crl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,611 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_publickey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,611 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/x509_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,611 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/x509_crl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,612 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/openssl_pkcs12.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,612 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/ecs_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,612 root INFO copying build/lib/ansible_collections/community/crypto/plugins/modules/acme_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/modules 2023-04-28 05:57:45,612 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/plugin_utils 2023-04-28 05:57:45,613 root INFO copying build/lib/ansible_collections/community/crypto/plugins/plugin_utils/filter_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/plugin_utils 2023-04-28 05:57:45,613 root INFO copying build/lib/ansible_collections/community/crypto/plugins/plugin_utils/action_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/plugin_utils 2023-04-28 05:57:45,613 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/action 2023-04-28 05:57:45,613 root INFO copying build/lib/ansible_collections/community/crypto/plugins/action/openssl_privatekey_pipe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/action 2023-04-28 05:57:45,613 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:45,613 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/io.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:45,614 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/ecs 2023-04-28 05:57:45,614 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/ecs/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/ecs 2023-04-28 05:57:45,614 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:45,614 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:45,614 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:45,615 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/openssh/backends 2023-04-28 05:57:45,615 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/backends/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/openssh/backends 2023-04-28 05:57:45,615 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/backends/keypair_backend.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/openssh/backends 2023-04-28 05:57:45,615 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/openssh/cryptography.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/openssh 2023-04-28 05:57:45,616 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:45,616 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,616 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/orders.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,616 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,616 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/io.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,617 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/certificates.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,617 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/errors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,617 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/backend_cryptography.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,617 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,617 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/challenges.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,618 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/backend_openssl_cli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,618 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/backends.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,618 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/acme/acme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/acme 2023-04-28 05:57:45,618 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,618 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/support.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,619 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/_asn1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,619 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/basic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,619 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/_obj2txt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,619 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/cryptography_crl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,619 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/cryptography_support.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,620 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/_objects_data.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,620 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/_objects.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,620 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,620 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/csr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,620 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,621 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey_convert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,621 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,621 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,621 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/csr_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,622 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_acme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,622 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/publickey_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,622 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,622 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,622 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_ownca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,623 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_entrust.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,623 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_selfsigned.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,623 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/crl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends 2023-04-28 05:57:45,623 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/math.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,623 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/pem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,624 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/crypto/openssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils/crypto 2023-04-28 05:57:45,624 root INFO copying build/lib/ansible_collections/community/crypto/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/plugins/module_utils 2023-04-28 05:57:45,624 root INFO copying build/lib/ansible_collections/community/crypto/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto 2023-04-28 05:57:45,624 root INFO copying build/lib/ansible_collections/community/crypto/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto 2023-04-28 05:57:45,625 root INFO copying build/lib/ansible_collections/community/crypto/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto 2023-04-28 05:57:45,625 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/meta 2023-04-28 05:57:45,625 root INFO copying build/lib/ansible_collections/community/crypto/meta/ee-bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/meta 2023-04-28 05:57:45,625 root INFO copying build/lib/ansible_collections/community/crypto/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/meta 2023-04-28 05:57:45,625 root INFO copying build/lib/ansible_collections/community/crypto/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/meta 2023-04-28 05:57:45,626 root INFO copying build/lib/ansible_collections/community/crypto/meta/ee-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/meta 2023-04-28 05:57:45,626 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:45,626 root INFO copying build/lib/ansible_collections/community/crypto/LICENSES/Apache-2.0.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:45,626 root INFO copying build/lib/ansible_collections/community/crypto/LICENSES/BSD-3-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:45,626 root INFO copying build/lib/ansible_collections/community/crypto/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:45,627 root INFO copying build/lib/ansible_collections/community/crypto/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:45,627 root INFO copying build/lib/ansible_collections/community/crypto/LICENSES/PSF-2.0.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/LICENSES 2023-04-28 05:57:45,627 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:45,627 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/changelogs/fragments 2023-04-28 05:57:45,627 root INFO copying build/lib/ansible_collections/community/crypto/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/changelogs/fragments 2023-04-28 05:57:45,628 root INFO copying build/lib/ansible_collections/community/crypto/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:45,628 root INFO copying build/lib/ansible_collections/community/crypto/changelogs/changelog.yaml.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:45,628 root INFO copying build/lib/ansible_collections/community/crypto/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto/changelogs 2023-04-28 05:57:45,628 root INFO copying build/lib/ansible_collections/community/crypto/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto 2023-04-28 05:57:45,628 root INFO copying build/lib/ansible_collections/community/crypto/CHANGELOG.rst.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/crypto 2023-04-28 05:57:45,629 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,629 root INFO copying build/lib/ansible_collections/community/postgresql/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,629 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins 2023-04-28 05:57:45,630 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/doc_fragments 2023-04-28 05:57:45,630 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/doc_fragments/postgres.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/doc_fragments 2023-04-28 05:57:45,630 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,630 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_ext.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,630 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_sequence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,631 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_pg_hba.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,631 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_subscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,631 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_privs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,631 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,631 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,632 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,632 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_lang.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,632 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,632 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_publication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,633 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_schema.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,633 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,633 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_user_obj_stat_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,633 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_tablespace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,633 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,634 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_owner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,634 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_db.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,634 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,634 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,635 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_slot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,635 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,635 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/modules/postgresql_idx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/modules 2023-04-28 05:57:45,635 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:45,635 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/module_utils/database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:45,636 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/module_utils/saslprep.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:45,636 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/module_utils/postgres.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:45,636 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:45,636 root INFO copying build/lib/ansible_collections/community/postgresql/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/plugins/module_utils 2023-04-28 05:57:45,636 root INFO copying build/lib/ansible_collections/community/postgresql/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,637 root INFO copying build/lib/ansible_collections/community/postgresql/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,637 root INFO copying build/lib/ansible_collections/community/postgresql/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,637 root INFO copying build/lib/ansible_collections/community/postgresql/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,637 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/meta 2023-04-28 05:57:45,638 root INFO copying build/lib/ansible_collections/community/postgresql/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/meta 2023-04-28 05:57:45,638 root INFO copying build/lib/ansible_collections/community/postgresql/simplified_bsd.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,638 root INFO copying build/lib/ansible_collections/community/postgresql/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,638 root INFO copying build/lib/ansible_collections/community/postgresql/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,638 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/changelogs 2023-04-28 05:57:45,638 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/changelogs/fragments 2023-04-28 05:57:45,639 root INFO copying build/lib/ansible_collections/community/postgresql/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/changelogs/fragments 2023-04-28 05:57:45,639 root INFO copying build/lib/ansible_collections/community/postgresql/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/changelogs 2023-04-28 05:57:45,639 root INFO copying build/lib/ansible_collections/community/postgresql/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql/changelogs 2023-04-28 05:57:45,639 root INFO copying build/lib/ansible_collections/community/postgresql/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,639 root INFO copying build/lib/ansible_collections/community/postgresql/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,640 root INFO copying build/lib/ansible_collections/community/postgresql/shippable.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,640 root INFO copying build/lib/ansible_collections/community/postgresql/CONTRIBUTORS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,640 root INFO copying build/lib/ansible_collections/community/postgresql/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/postgresql 2023-04-28 05:57:45,640 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,640 root INFO copying build/lib/ansible_collections/community/aws/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,641 root INFO copying build/lib/ansible_collections/community/aws/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,641 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins 2023-04-28 05:57:45,641 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/connection 2023-04-28 05:57:45,641 root INFO copying build/lib/ansible_collections/community/aws/plugins/connection/aws_ssm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/connection 2023-04-28 05:57:45,642 root INFO copying build/lib/ansible_collections/community/aws/plugins/connection/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/connection 2023-04-28 05:57:45,642 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,642 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elb_target_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,642 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/opensearch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,643 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/msk_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,643 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_resources_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,643 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_ami_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,643 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/dynamodb_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,643 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/glue_crawler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,644 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ssm_parameter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,644 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/waf_web_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,644 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_taskdefinition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,644 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/data_pipeline.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,645 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elb_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,645 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_bucket_notification.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,645 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_launch_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,645 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,645 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/cloudformation_stack_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,646 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,646 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/eks_fargate_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,646 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_scheduled_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,646 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ses_identity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,646 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/batch_job_definition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,647 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/aws_region_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,647 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/eks_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,647 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/sqs_queue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,647 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/application_autoscaling_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,648 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_instance_refresh_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,648 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/config_aggregation_authorization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,648 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_vgw_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,648 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/networkfirewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,648 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_complete_lifecycle_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,649 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_web_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,649 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/directconnect_connection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,649 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_access_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,649 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elb_classic_lb_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,649 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elb_target.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,650 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/stepfunctions_state_machine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,650 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,650 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/config_recorder.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,650 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_task.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,650 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,651 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/dms_endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,651 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_vgw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,651 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_vpn_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,651 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ses_rule_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,651 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_web_acl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,652 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/sns_topic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,652 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/cloudfront_invalidation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,652 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,652 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,653 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/codepipeline.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,653 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/config_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,653 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,653 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/accessanalyzer_validate_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,653 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/eks_nodegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,654 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,654 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/cloudformation_exports_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,654 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/networkfirewall_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,654 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,654 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/networkfirewall_rule_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,655 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_vpn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,655 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_website.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,655 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_lifecycle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,655 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_managed_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,656 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/codebuild_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,656 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/glue_connection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,656 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_ip_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,656 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_metrics_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,656 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_password_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,657 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_peering_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,657 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/batch_compute_environment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,657 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,657 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/efs_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,658 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/directconnect_link_aggregation_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,658 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/acm_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,658 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,658 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_saml_federation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,658 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/waf_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,659 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/sts_assume_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,659 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/redshift_subnet_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,659 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_vpc_attachment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,659 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elasticache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,659 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/cloudfront_distribution.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,660 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/api_gateway_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,660 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ses_identity_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,660 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/lightsail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,660 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/opensearch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,661 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_instance_refresh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,661 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/msk_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,661 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_launch_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,661 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/glue_job.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,662 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_server_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,662 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/efs_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,662 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_ip_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,662 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_snapshot_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,662 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/secretsmanager_secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,663 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/networkfirewall_rule_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,663 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elb_network_lb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,663 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/redshift.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,663 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/networkfirewall_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,663 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/batch_job_queue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,664 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/networkfirewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,664 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/sns_topic_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,664 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_egress_igw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,664 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_customer_gateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,664 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/waf_condition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,665 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elasticache_subnet_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,665 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_ecr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,665 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elb_target_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,665 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,666 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elasticache_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,666 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_resources.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,666 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_mfa_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,666 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_bucket_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,666 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/dynamodb_ttl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,667 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/efs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,667 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/sts_session_token.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,667 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elasticache_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,667 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/s3_cors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,667 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/cloudfront_distribution_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,668 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/api_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,668 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_lifecycle_hook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,668 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_rule_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,668 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/waf_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,669 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/cloudfront_response_headers_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,669 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/codecommit_repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,669 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_transit_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,669 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elb_target_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,669 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/lightsail_static_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,670 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_access_key_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,670 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_placement_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,670 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_nacl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,670 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_launch_config_find.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,670 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/config_delivery_channel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,671 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/directconnect_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,671 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/acm_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,671 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elasticache_parameter_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,671 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/stepfunctions_state_machine_execution.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,672 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/config_aggregator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,672 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_win_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,672 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/redshift_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,672 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/inspector_target.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,672 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/iam_server_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,673 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/autoscaling_launch_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,673 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_vpc_nacl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,673 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/directconnect_virtual_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,673 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_attribute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,673 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,674 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_vpc_attachment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,674 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/wafv2_rule_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,674 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/directconnect_confirm_connection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,674 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_customer_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,674 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ecs_taskdefinition_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,675 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/dms_replication_subnet_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,675 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/cloudfront_origin_access_identity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,675 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/kinesis_stream.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,675 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/elasticbeanstalk_app.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,676 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/sns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,676 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/storagegateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,676 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/ec2_placement_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,676 root INFO copying build/lib/ansible_collections/community/aws/plugins/modules/redshift_cross_region_snapshots.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/modules 2023-04-28 05:57:45,676 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,677 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/wafv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,677 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,677 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/ec2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,677 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/etag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,677 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/transitgateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,678 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/opensearch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,678 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/networkfirewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,678 root INFO copying build/lib/ansible_collections/community/aws/plugins/module_utils/sns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/plugins/module_utils 2023-04-28 05:57:45,678 root INFO copying build/lib/ansible_collections/community/aws/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,678 root INFO copying build/lib/ansible_collections/community/aws/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,679 root INFO copying build/lib/ansible_collections/community/aws/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,680 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/meta 2023-04-28 05:57:45,680 root INFO copying build/lib/ansible_collections/community/aws/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/meta 2023-04-28 05:57:45,680 root INFO copying build/lib/ansible_collections/community/aws/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,680 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/changelogs 2023-04-28 05:57:45,680 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/changelogs/fragments 2023-04-28 05:57:45,680 root INFO copying build/lib/ansible_collections/community/aws/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/changelogs/fragments 2023-04-28 05:57:45,681 root INFO copying build/lib/ansible_collections/community/aws/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/changelogs 2023-04-28 05:57:45,681 root INFO copying build/lib/ansible_collections/community/aws/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws/changelogs 2023-04-28 05:57:45,681 root INFO copying build/lib/ansible_collections/community/aws/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,682 root INFO copying build/lib/ansible_collections/community/aws/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,682 root INFO copying build/lib/ansible_collections/community/aws/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/aws 2023-04-28 05:57:45,682 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker 2023-04-28 05:57:45,682 root INFO copying build/lib/ansible_collections/community/docker/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker 2023-04-28 05:57:45,683 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins 2023-04-28 05:57:45,683 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/doc_fragments 2023-04-28 05:57:45,683 root INFO copying build/lib/ansible_collections/community/docker/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/doc_fragments 2023-04-28 05:57:45,683 root INFO copying build/lib/ansible_collections/community/docker/plugins/doc_fragments/docker.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/doc_fragments 2023-04-28 05:57:45,683 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:45,684 root INFO copying build/lib/ansible_collections/community/docker/plugins/inventory/docker_machine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:45,684 root INFO copying build/lib/ansible_collections/community/docker/plugins/inventory/docker_swarm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:45,684 root INFO copying build/lib/ansible_collections/community/docker/plugins/inventory/docker_containers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/inventory 2023-04-28 05:57:45,684 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:45,684 root INFO copying build/lib/ansible_collections/community/docker/plugins/connection/nsenter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:45,685 root INFO copying build/lib/ansible_collections/community/docker/plugins/connection/docker.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:45,685 root INFO copying build/lib/ansible_collections/community/docker/plugins/connection/docker_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/connection 2023-04-28 05:57:45,685 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,685 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_login.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,686 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,686 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,686 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_container_exec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,686 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_stack_task_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,687 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,687 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_prune.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,687 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_volume_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,687 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/current_container_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,688 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,688 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,688 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_swarm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,688 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,689 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,689 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_image_load.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,689 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,689 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_container_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,690 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_host_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,690 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,690 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,690 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_container_copy_into.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,691 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_swarm_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,691 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_stack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,691 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,692 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_stack_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,692 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_swarm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,692 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_compose.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,692 root INFO copying build/lib/ansible_collections/community/docker/plugins/modules/docker_swarm_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/modules 2023-04-28 05:57:45,693 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:45,693 root INFO copying build/lib/ansible_collections/community/docker/plugins/plugin_utils/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:45,693 root INFO copying build/lib/ansible_collections/community/docker/plugins/plugin_utils/common_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:45,693 root INFO copying build/lib/ansible_collections/community/docker/plugins/plugin_utils/socket_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/plugin_utils 2023-04-28 05:57:45,694 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/action 2023-04-28 05:57:45,694 root INFO copying build/lib/ansible_collections/community/docker/plugins/action/docker_container_copy_into.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/action 2023-04-28 05:57:45,694 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,694 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/socket_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,694 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,695 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/util.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,695 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/swarm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,695 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,695 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/image_archive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,695 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:45,696 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/types 2023-04-28 05:57:45,696 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/types/daemon.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/types 2023-04-28 05:57:45,696 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,696 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/fnmatch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,696 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,697 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,697 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/ports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,697 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/build.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,697 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/socket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,697 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,698 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/decorators.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,698 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/utils/json_stream.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/utils 2023-04-28 05:57:45,698 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/errors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:45,698 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/tls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:45,698 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/api 2023-04-28 05:57:45,699 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/api/daemon.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/api 2023-04-28 05:57:45,699 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/api/client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/api 2023-04-28 05:57:45,699 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:45,699 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/_import_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:45,699 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:45,700 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:45,700 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials/errors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:45,700 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials/store.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:45,700 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/credentials/constants.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/credentials 2023-04-28 05:57:45,700 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/constants.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api 2023-04-28 05:57:45,701 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:45,701 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport/ssladapter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:45,701 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport/unixconn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:45,701 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport/basehttpadapter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:45,701 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport/npipeconn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:45,702 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport/sshconn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:45,702 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_api/transport/npipesocket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/_api/transport 2023-04-28 05:57:45,702 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/_scramble.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,702 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,702 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/common_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,703 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:45,703 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/module_container/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:45,703 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/module_container/docker_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:45,703 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/module_container/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils/module_container 2023-04-28 05:57:45,704 root INFO copying build/lib/ansible_collections/community/docker/plugins/module_utils/socket_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/plugins/module_utils 2023-04-28 05:57:45,704 root INFO copying build/lib/ansible_collections/community/docker/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker 2023-04-28 05:57:45,704 root INFO copying build/lib/ansible_collections/community/docker/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker 2023-04-28 05:57:45,704 root INFO copying build/lib/ansible_collections/community/docker/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker 2023-04-28 05:57:45,705 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/meta 2023-04-28 05:57:45,705 root INFO copying build/lib/ansible_collections/community/docker/meta/ee-bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/meta 2023-04-28 05:57:45,705 root INFO copying build/lib/ansible_collections/community/docker/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/meta 2023-04-28 05:57:45,705 root INFO copying build/lib/ansible_collections/community/docker/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/meta 2023-04-28 05:57:45,705 root INFO copying build/lib/ansible_collections/community/docker/meta/ee-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/meta 2023-04-28 05:57:45,706 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/LICENSES 2023-04-28 05:57:45,706 root INFO copying build/lib/ansible_collections/community/docker/LICENSES/Apache-2.0.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/LICENSES 2023-04-28 05:57:45,706 root INFO copying build/lib/ansible_collections/community/docker/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/LICENSES 2023-04-28 05:57:45,706 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/changelogs 2023-04-28 05:57:45,706 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/changelogs/fragments 2023-04-28 05:57:45,707 root INFO copying build/lib/ansible_collections/community/docker/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/changelogs/fragments 2023-04-28 05:57:45,707 root INFO copying build/lib/ansible_collections/community/docker/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/changelogs 2023-04-28 05:57:45,707 root INFO copying build/lib/ansible_collections/community/docker/changelogs/changelog.yaml.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/changelogs 2023-04-28 05:57:45,707 root INFO copying build/lib/ansible_collections/community/docker/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker/changelogs 2023-04-28 05:57:45,707 root INFO copying build/lib/ansible_collections/community/docker/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker 2023-04-28 05:57:45,708 root INFO copying build/lib/ansible_collections/community/docker/CHANGELOG.rst.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/docker 2023-04-28 05:57:45,708 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,708 root INFO copying build/lib/ansible_collections/community/skydive/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,708 root INFO copying build/lib/ansible_collections/community/skydive/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,708 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins 2023-04-28 05:57:45,709 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/doc_fragments 2023-04-28 05:57:45,709 root INFO copying build/lib/ansible_collections/community/skydive/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/doc_fragments 2023-04-28 05:57:45,709 root INFO copying build/lib/ansible_collections/community/skydive/plugins/doc_fragments/skydive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/doc_fragments 2023-04-28 05:57:45,709 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:45,709 root INFO copying build/lib/ansible_collections/community/skydive/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:45,709 root INFO copying build/lib/ansible_collections/community/skydive/plugins/modules/skydive_capture.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:45,710 root INFO copying build/lib/ansible_collections/community/skydive/plugins/modules/skydive_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:45,710 root INFO copying build/lib/ansible_collections/community/skydive/plugins/modules/skydive_edge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/modules 2023-04-28 05:57:45,710 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/module_utils 2023-04-28 05:57:45,710 root INFO copying build/lib/ansible_collections/community/skydive/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/module_utils 2023-04-28 05:57:45,710 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/module_utils/network 2023-04-28 05:57:45,711 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/module_utils/network/skydive 2023-04-28 05:57:45,711 root INFO copying build/lib/ansible_collections/community/skydive/plugins/module_utils/network/skydive/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/module_utils/network/skydive 2023-04-28 05:57:45,711 root INFO copying build/lib/ansible_collections/community/skydive/plugins/module_utils/network/skydive/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/module_utils/network/skydive 2023-04-28 05:57:45,711 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/lookup 2023-04-28 05:57:45,711 root INFO copying build/lib/ansible_collections/community/skydive/plugins/lookup/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/lookup 2023-04-28 05:57:45,711 root INFO copying build/lib/ansible_collections/community/skydive/plugins/lookup/skydive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/plugins/lookup 2023-04-28 05:57:45,712 root INFO copying build/lib/ansible_collections/community/skydive/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,712 root INFO copying build/lib/ansible_collections/community/skydive/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,712 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/meta 2023-04-28 05:57:45,712 root INFO copying build/lib/ansible_collections/community/skydive/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/meta 2023-04-28 05:57:45,712 root INFO copying build/lib/ansible_collections/community/skydive/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,713 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/changelogs 2023-04-28 05:57:45,713 root INFO copying build/lib/ansible_collections/community/skydive/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/changelogs 2023-04-28 05:57:45,713 root INFO copying build/lib/ansible_collections/community/skydive/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive/changelogs 2023-04-28 05:57:45,713 root INFO copying build/lib/ansible_collections/community/skydive/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,713 root INFO copying build/lib/ansible_collections/community/skydive/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,714 root INFO copying build/lib/ansible_collections/community/skydive/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,714 root INFO copying build/lib/ansible_collections/community/skydive/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/skydive 2023-04-28 05:57:45,714 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,714 root INFO copying build/lib/ansible_collections/community/sap_libs/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,714 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins 2023-04-28 05:57:45,715 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/doc_fragments 2023-04-28 05:57:45,715 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/doc_fragments 2023-04-28 05:57:45,715 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,715 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sapcar_extract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,715 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,716 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_snote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,716 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_system_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,716 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_control_exec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,716 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_hdbsql.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,716 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_company.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,717 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_pyrfc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,717 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/modules/sap_task_list_execute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/modules 2023-04-28 05:57:45,717 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:45,717 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/module_utils/pyrfc_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:45,717 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:45,718 root INFO copying build/lib/ansible_collections/community/sap_libs/plugins/module_utils/swpm2_parameters_inifile_generate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/plugins/module_utils 2023-04-28 05:57:45,718 root INFO copying build/lib/ansible_collections/community/sap_libs/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,718 root INFO copying build/lib/ansible_collections/community/sap_libs/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,718 root INFO copying build/lib/ansible_collections/community/sap_libs/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,718 root INFO copying build/lib/ansible_collections/community/sap_libs/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,719 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/meta 2023-04-28 05:57:45,719 root INFO copying build/lib/ansible_collections/community/sap_libs/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/meta 2023-04-28 05:57:45,719 root INFO copying build/lib/ansible_collections/community/sap_libs/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,719 root INFO copying build/lib/ansible_collections/community/sap_libs/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,719 root INFO copying build/lib/ansible_collections/community/sap_libs/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,720 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/changelogs 2023-04-28 05:57:45,720 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/changelogs/fragments 2023-04-28 05:57:45,720 root INFO copying build/lib/ansible_collections/community/sap_libs/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/changelogs/fragments 2023-04-28 05:57:45,720 root INFO copying build/lib/ansible_collections/community/sap_libs/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/changelogs 2023-04-28 05:57:45,720 root INFO copying build/lib/ansible_collections/community/sap_libs/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs/changelogs 2023-04-28 05:57:45,720 root INFO copying build/lib/ansible_collections/community/sap_libs/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,721 root INFO copying build/lib/ansible_collections/community/sap_libs/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,721 root INFO copying build/lib/ansible_collections/community/sap_libs/REVIEW_CHECKLIST.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/sap_libs 2023-04-28 05:57:45,721 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,721 root INFO copying build/lib/ansible_collections/community/libvirt/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,721 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins 2023-04-28 05:57:45,722 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:45,722 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/doc_fragments/requirements.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:45,722 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:45,722 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/doc_fragments/virt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/doc_fragments 2023-04-28 05:57:45,722 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/inventory 2023-04-28 05:57:45,723 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/inventory 2023-04-28 05:57:45,723 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/inventory/libvirt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/inventory 2023-04-28 05:57:45,723 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/connection 2023-04-28 05:57:45,723 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/connection/libvirt_lxc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/connection 2023-04-28 05:57:45,723 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/connection/libvirt_qemu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/connection 2023-04-28 05:57:45,724 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:45,724 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/modules/virt_net.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:45,724 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/modules/virt_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:45,724 root INFO copying build/lib/ansible_collections/community/libvirt/plugins/modules/virt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/plugins/modules 2023-04-28 05:57:45,724 root INFO copying build/lib/ansible_collections/community/libvirt/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,725 root INFO copying build/lib/ansible_collections/community/libvirt/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,725 root INFO copying build/lib/ansible_collections/community/libvirt/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,725 root INFO copying build/lib/ansible_collections/community/libvirt/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,725 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/meta 2023-04-28 05:57:45,725 root INFO copying build/lib/ansible_collections/community/libvirt/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/meta 2023-04-28 05:57:45,726 root INFO copying build/lib/ansible_collections/community/libvirt/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,726 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/changelogs 2023-04-28 05:57:45,726 root INFO copying build/lib/ansible_collections/community/libvirt/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/changelogs 2023-04-28 05:57:45,726 root INFO copying build/lib/ansible_collections/community/libvirt/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt/changelogs 2023-04-28 05:57:45,726 root INFO copying build/lib/ansible_collections/community/libvirt/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,727 root INFO copying build/lib/ansible_collections/community/libvirt/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,727 root INFO copying build/lib/ansible_collections/community/libvirt/REVIEW_CHECKLIST.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,727 root INFO copying build/lib/ansible_collections/community/libvirt/shippable.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/libvirt 2023-04-28 05:57:45,727 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault 2023-04-28 05:57:45,727 root INFO copying build/lib/ansible_collections/community/hashi_vault/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault 2023-04-28 05:57:45,728 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins 2023-04-28 05:57:45,728 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/filter 2023-04-28 05:57:45,728 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/filter/vault_login_token.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/filter 2023-04-28 05:57:45,728 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/filter/vault_login_token.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/filter 2023-04-28 05:57:45,728 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:45,729 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:45,729 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments/wrapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:45,729 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments/auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:45,729 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments/connection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:45,729 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments/token_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:45,729 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/doc_fragments/engine_mount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/doc_fragments 2023-04-28 05:57:45,730 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,730 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_write.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,730 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_login.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,730 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_read.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,730 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,731 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_write.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,731 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,731 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_token_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,731 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_kv1_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,731 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,732 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/modules/vault_pki_generate_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/modules 2023-04-28 05:57:45,732 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/plugin_utils 2023-04-28 05:57:45,732 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/plugin_utils/_hashi_vault_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/plugin_utils 2023-04-28 05:57:45,732 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/plugin_utils/_hashi_vault_lookup_base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/plugin_utils 2023-04-28 05:57:45,732 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,733 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_jwt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,733 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,733 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_approle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,733 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_aws_iam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,733 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_authenticator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,734 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_token.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,734 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_none.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,734 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_hashi_vault_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,734 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_azure.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,734 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_connection_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,735 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_userpass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,735 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_cert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,735 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/module_utils/_hashi_vault_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/module_utils 2023-04-28 05:57:45,735 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,735 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_login.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,736 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_read.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,736 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,736 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_write.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,736 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_ansible_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,736 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_token_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,737 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/hashi_vault.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,737 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_kv1_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,737 root INFO copying build/lib/ansible_collections/community/hashi_vault/plugins/lookup/vault_kv2_get.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/plugins/lookup 2023-04-28 05:57:45,737 root INFO copying build/lib/ansible_collections/community/hashi_vault/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault 2023-04-28 05:57:45,738 root INFO copying build/lib/ansible_collections/community/hashi_vault/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault 2023-04-28 05:57:45,738 root INFO copying build/lib/ansible_collections/community/hashi_vault/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault 2023-04-28 05:57:45,738 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:45,738 root INFO copying build/lib/ansible_collections/community/hashi_vault/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:45,739 root INFO copying build/lib/ansible_collections/community/hashi_vault/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:45,739 root INFO copying build/lib/ansible_collections/community/hashi_vault/meta/ee-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/meta 2023-04-28 05:57:45,739 root INFO copying build/lib/ansible_collections/community/hashi_vault/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault 2023-04-28 05:57:45,739 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/LICENSES 2023-04-28 05:57:45,739 root INFO copying build/lib/ansible_collections/community/hashi_vault/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/LICENSES 2023-04-28 05:57:45,740 root INFO copying build/lib/ansible_collections/community/hashi_vault/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/LICENSES 2023-04-28 05:57:45,740 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/changelogs 2023-04-28 05:57:45,740 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/changelogs/fragments 2023-04-28 05:57:45,740 root INFO copying build/lib/ansible_collections/community/hashi_vault/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/changelogs/fragments 2023-04-28 05:57:45,740 root INFO copying build/lib/ansible_collections/community/hashi_vault/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/changelogs 2023-04-28 05:57:45,740 root INFO copying build/lib/ansible_collections/community/hashi_vault/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault/changelogs 2023-04-28 05:57:45,741 root INFO copying build/lib/ansible_collections/community/hashi_vault/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/hashi_vault 2023-04-28 05:57:45,741 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google 2023-04-28 05:57:45,741 root INFO copying build/lib/ansible_collections/community/google/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google 2023-04-28 05:57:45,741 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins 2023-04-28 05:57:45,741 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/doc_fragments 2023-04-28 05:57:45,742 root INFO copying build/lib/ansible_collections/community/google/plugins/doc_fragments/_gcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/doc_fragments 2023-04-28 05:57:45,742 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,742 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_labels.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,742 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,742 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,743 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_mig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,743 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gc_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,743 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_lb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,743 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_img.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,744 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gcpubsub_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,744 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_net.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,744 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gcpubsub.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,744 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_instance_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,744 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_eip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,745 root INFO copying build/lib/ansible_collections/community/google/plugins/modules/gce_pd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/modules 2023-04-28 05:57:45,745 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/module_utils 2023-04-28 05:57:45,745 root INFO copying build/lib/ansible_collections/community/google/plugins/module_utils/gcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/module_utils 2023-04-28 05:57:45,745 root INFO copying build/lib/ansible_collections/community/google/plugins/module_utils/gce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/module_utils 2023-04-28 05:57:45,745 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/lookup 2023-04-28 05:57:45,746 root INFO copying build/lib/ansible_collections/community/google/plugins/lookup/gcp_storage_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/plugins/lookup 2023-04-28 05:57:45,746 root INFO copying build/lib/ansible_collections/community/google/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google 2023-04-28 05:57:45,746 root INFO copying build/lib/ansible_collections/community/google/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google 2023-04-28 05:57:45,746 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/meta 2023-04-28 05:57:45,746 root INFO copying build/lib/ansible_collections/community/google/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/meta 2023-04-28 05:57:45,747 root INFO copying build/lib/ansible_collections/community/google/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google 2023-04-28 05:57:45,747 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/changelogs 2023-04-28 05:57:45,747 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/changelogs/fragments 2023-04-28 05:57:45,747 root INFO copying build/lib/ansible_collections/community/google/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/changelogs/fragments 2023-04-28 05:57:45,747 root INFO copying build/lib/ansible_collections/community/google/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/changelogs 2023-04-28 05:57:45,748 root INFO copying build/lib/ansible_collections/community/google/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/changelogs 2023-04-28 05:57:45,748 root INFO copying build/lib/ansible_collections/community/google/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google 2023-04-28 05:57:45,748 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/scripts 2023-04-28 05:57:45,748 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/google/scripts/inventory 2023-04-28 05:57:45,748 root INFO copying build/lib/ansible_collections/community/google/scripts/inventory/gce.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/scripts/inventory 2023-04-28 05:57:45,749 root INFO copying build/lib/ansible_collections/community/google/scripts/inventory/gce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/google/scripts/inventory 2023-04-28 05:57:45,749 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,749 root INFO copying build/lib/ansible_collections/community/mongodb/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,749 root INFO copying build/lib/ansible_collections/community/mongodb/requirements-3.6.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,749 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins 2023-04-28 05:57:45,750 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/doc_fragments 2023-04-28 05:57:45,750 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/doc_fragments/login_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/doc_fragments 2023-04-28 05:57:45,750 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/doc_fragments/ssl_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/doc_fragments 2023-04-28 05:57:45,750 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,750 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_shard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,750 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,751 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_index.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,751 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_shard_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,751 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,751 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_shell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,751 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_shard_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,752 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_schema.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,752 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_monitoring.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,752 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,752 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,752 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_parameter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,753 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_maintenance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,753 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_stepdown.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,753 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_shutdown.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,753 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,753 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_oplog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,754 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_replicaset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,754 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/modules/mongodb_balancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/modules 2023-04-28 05:57:45,755 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:45,755 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/module_utils/mongodb_shell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:45,755 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:45,755 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/module_utils/mongodb_common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/module_utils 2023-04-28 05:57:45,755 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/lookup 2023-04-28 05:57:45,755 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/lookup/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/lookup 2023-04-28 05:57:45,756 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/lookup/mongodb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/lookup 2023-04-28 05:57:45,756 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/cache 2023-04-28 05:57:45,756 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/cache/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/cache 2023-04-28 05:57:45,756 root INFO copying build/lib/ansible_collections/community/mongodb/plugins/cache/mongodb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/plugins/cache 2023-04-28 05:57:45,756 root INFO copying build/lib/ansible_collections/community/mongodb/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,757 root INFO copying build/lib/ansible_collections/community/mongodb/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,757 root INFO copying build/lib/ansible_collections/community/mongodb/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,757 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/meta 2023-04-28 05:57:45,757 root INFO copying build/lib/ansible_collections/community/mongodb/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/meta 2023-04-28 05:57:45,758 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:45,758 root INFO copying build/lib/ansible_collections/community/mongodb/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:45,758 root INFO copying build/lib/ansible_collections/community/mongodb/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:45,758 root INFO copying build/lib/ansible_collections/community/mongodb/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/changelogs 2023-04-28 05:57:45,758 root INFO copying build/lib/ansible_collections/community/mongodb/requirements-3.8.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,758 root INFO copying build/lib/ansible_collections/community/mongodb/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb 2023-04-28 05:57:45,759 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles 2023-04-28 05:57:45,759 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository 2023-04-28 05:57:45,759 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:45,759 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/tasks/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:45,759 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/tasks/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:45,760 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/tasks 2023-04-28 05:57:45,760 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/defaults 2023-04-28 05:57:45,760 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/defaults 2023-04-28 05:57:45,760 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository 2023-04-28 05:57:45,760 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/meta 2023-04-28 05:57:45,761 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/meta 2023-04-28 05:57:45,761 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule 2023-04-28 05:57:45,761 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:45,761 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:45,761 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests 2023-04-28 05:57:45,762 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests 2023-04-28 05:57:45,762 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:45,762 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default 2023-04-28 05:57:45,762 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox 2023-04-28 05:57:45,762 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests 2023-04-28 05:57:45,762 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests 2023-04-28 05:57:45,763 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox 2023-04-28 05:57:45,763 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox 2023-04-28 05:57:45,763 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_repository/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_repository 2023-04-28 05:57:45,763 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod 2023-04-28 05:57:45,763 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/tasks 2023-04-28 05:57:45,764 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/tasks 2023-04-28 05:57:45,764 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/defaults 2023-04-28 05:57:45,764 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/defaults 2023-04-28 05:57:45,764 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/handlers 2023-04-28 05:57:45,764 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/handlers 2023-04-28 05:57:45,765 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod 2023-04-28 05:57:45,765 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/templates 2023-04-28 05:57:45,765 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/templates/mongod.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/templates 2023-04-28 05:57:45,765 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:45,765 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:45,766 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:45,766 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:45,766 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/vars 2023-04-28 05:57:45,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/meta 2023-04-28 05:57:45,766 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/meta 2023-04-28 05:57:45,767 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule 2023-04-28 05:57:45,767 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:45,767 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:45,767 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests 2023-04-28 05:57:45,767 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests 2023-04-28 05:57:45,767 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:45,768 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:45,768 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default 2023-04-28 05:57:45,768 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:45,768 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:45,768 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests 2023-04-28 05:57:45,769 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests 2023-04-28 05:57:45,769 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:45,769 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:45,769 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip 2023-04-28 05:57:45,769 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:45,770 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests 2023-04-28 05:57:45,770 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests 2023-04-28 05:57:45,770 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:45,770 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:45,770 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox 2023-04-28 05:57:45,771 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:45,771 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:45,771 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests 2023-04-28 05:57:45,771 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests 2023-04-28 05:57:45,771 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:45,771 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:45,772 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path 2023-04-28 05:57:45,772 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongod/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongod 2023-04-28 05:57:45,772 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config 2023-04-28 05:57:45,772 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/tasks 2023-04-28 05:57:45,772 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/tasks 2023-04-28 05:57:45,773 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/defaults 2023-04-28 05:57:45,773 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/defaults 2023-04-28 05:57:45,773 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/handlers 2023-04-28 05:57:45,773 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/handlers 2023-04-28 05:57:45,773 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config 2023-04-28 05:57:45,774 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/templates 2023-04-28 05:57:45,774 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/templates/configsrv.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/templates 2023-04-28 05:57:45,774 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:45,774 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:45,774 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:45,775 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:45,775 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/vars 2023-04-28 05:57:45,775 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/meta 2023-04-28 05:57:45,775 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/meta 2023-04-28 05:57:45,775 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule 2023-04-28 05:57:45,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:45,776 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:45,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests 2023-04-28 05:57:45,776 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests 2023-04-28 05:57:45,776 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:45,776 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:45,777 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default 2023-04-28 05:57:45,777 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:45,777 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests 2023-04-28 05:57:45,777 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests 2023-04-28 05:57:45,777 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:45,778 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:45,778 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox 2023-04-28 05:57:45,778 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:45,778 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:45,778 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests 2023-04-28 05:57:45,779 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests 2023-04-28 05:57:45,779 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:45,779 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:45,779 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path 2023-04-28 05:57:45,779 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_config/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_config 2023-04-28 05:57:45,780 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth 2023-04-28 05:57:45,780 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/tasks 2023-04-28 05:57:45,780 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/tasks/mongodb_auth_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/tasks 2023-04-28 05:57:45,780 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/tasks 2023-04-28 05:57:45,780 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/defaults 2023-04-28 05:57:45,780 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/defaults 2023-04-28 05:57:45,781 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth 2023-04-28 05:57:45,781 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:45,781 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars/RedHat-7.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:45,781 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:45,781 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:45,782 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars/RedHat-8.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:45,782 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/vars/Amazon.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/vars 2023-04-28 05:57:45,782 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/meta 2023-04-28 05:57:45,782 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/meta 2023-04-28 05:57:45,782 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule 2023-04-28 05:57:45,783 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:45,783 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:45,783 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests 2023-04-28 05:57:45,783 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests 2023-04-28 05:57:45,783 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:45,784 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:45,784 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default 2023-04-28 05:57:45,784 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:45,784 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests 2023-04-28 05:57:45,784 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests 2023-04-28 05:57:45,785 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:45,785 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:45,785 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox 2023-04-28 05:57:45,785 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_auth/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_auth 2023-04-28 05:57:45,785 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos 2023-04-28 05:57:45,786 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/tasks 2023-04-28 05:57:45,786 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/tasks 2023-04-28 05:57:45,786 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/defaults 2023-04-28 05:57:45,786 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/defaults 2023-04-28 05:57:45,786 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/handlers 2023-04-28 05:57:45,787 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/handlers 2023-04-28 05:57:45,787 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos 2023-04-28 05:57:45,787 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:45,787 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos.service.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:45,787 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos_pre.sh.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:45,787 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/templates 2023-04-28 05:57:45,788 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:45,788 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:45,788 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:45,788 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/vars 2023-04-28 05:57:45,788 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/meta 2023-04-28 05:57:45,789 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/meta 2023-04-28 05:57:45,789 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule 2023-04-28 05:57:45,789 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:45,789 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:45,789 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests 2023-04-28 05:57:45,790 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests 2023-04-28 05:57:45,790 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:45,790 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:45,790 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default 2023-04-28 05:57:45,790 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:45,791 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests 2023-04-28 05:57:45,791 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests 2023-04-28 05:57:45,791 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:45,791 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:45,791 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox 2023-04-28 05:57:45,792 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_mongos/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_mongos 2023-04-28 05:57:45,792 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux 2023-04-28 05:57:45,792 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/tasks 2023-04-28 05:57:45,792 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/tasks 2023-04-28 05:57:45,792 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/defaults 2023-04-28 05:57:45,792 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/defaults 2023-04-28 05:57:45,793 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux 2023-04-28 05:57:45,793 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:45,793 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:45,793 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars/Fedora.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:45,793 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:45,794 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:45,794 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:45,794 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/vars/RedHat-8.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/vars 2023-04-28 05:57:45,794 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/meta 2023-04-28 05:57:45,794 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/meta 2023-04-28 05:57:45,795 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule 2023-04-28 05:57:45,795 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:45,795 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:45,795 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests 2023-04-28 05:57:45,795 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests 2023-04-28 05:57:45,795 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:45,796 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default 2023-04-28 05:57:45,796 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:45,796 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests 2023-04-28 05:57:45,796 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests 2023-04-28 05:57:45,796 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:45,797 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:45,797 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox 2023-04-28 05:57:45,797 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/files 2023-04-28 05:57:45,797 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_linux/files/thp-disable.service -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_linux/files 2023-04-28 05:57:45,797 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install 2023-04-28 05:57:45,798 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/tasks 2023-04-28 05:57:45,798 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/tasks 2023-04-28 05:57:45,798 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install 2023-04-28 05:57:45,798 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/meta 2023-04-28 05:57:45,798 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/meta 2023-04-28 05:57:45,799 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule 2023-04-28 05:57:45,799 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:45,799 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:45,799 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests 2023-04-28 05:57:45,799 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests 2023-04-28 05:57:45,800 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:45,800 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:45,800 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages 2023-04-28 05:57:45,800 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:45,800 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:45,801 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests 2023-04-28 05:57:45,801 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests 2023-04-28 05:57:45,801 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:45,801 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default 2023-04-28 05:57:45,801 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:45,801 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:45,802 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests 2023-04-28 05:57:45,802 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests 2023-04-28 05:57:45,802 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:45,802 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:45,802 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages 2023-04-28 05:57:45,803 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:45,803 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:45,803 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests 2023-04-28 05:57:45,803 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests 2023-04-28 05:57:45,803 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:45,804 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version 2023-04-28 05:57:45,804 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:45,804 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests 2023-04-28 05:57:45,804 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests 2023-04-28 05:57:45,804 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:45,805 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:45,805 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox 2023-04-28 05:57:45,805 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/files 2023-04-28 05:57:45,805 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/files/lock_mongodb_packages.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install/files 2023-04-28 05:57:45,805 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_install/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_install 2023-04-28 05:57:45,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux 2023-04-28 05:57:45,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/tasks 2023-04-28 05:57:45,806 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/tasks 2023-04-28 05:57:45,806 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux 2023-04-28 05:57:45,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,806 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Ubuntu-16.04.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,807 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,807 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars/RedHat-7.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,807 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Fedora.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,807 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,807 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars/RedHat-8.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,808 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Amazon.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/vars 2023-04-28 05:57:45,808 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/meta 2023-04-28 05:57:45,808 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/meta 2023-04-28 05:57:45,808 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule 2023-04-28 05:57:45,808 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:45,808 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:45,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests 2023-04-28 05:57:45,809 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests 2023-04-28 05:57:45,809 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:45,809 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default 2023-04-28 05:57:45,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox 2023-04-28 05:57:45,810 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests 2023-04-28 05:57:45,810 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests 2023-04-28 05:57:45,810 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox 2023-04-28 05:57:45,810 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox 2023-04-28 05:57:45,810 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/files 2023-04-28 05:57:45,811 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/files/compile_mongodb_selinux.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux/files 2023-04-28 05:57:45,811 root INFO copying build/lib/ansible_collections/community/mongodb/roles/mongodb_selinux/.yamllint -> build/bdist.linux-x86_64/wheel/ansible_collections/community/mongodb/roles/mongodb_selinux 2023-04-28 05:57:45,811 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,811 root INFO copying build/lib/ansible_collections/community/ciscosmb/requirements-dev.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,811 root INFO copying build/lib/ansible_collections/community/ciscosmb/galaxy-importer.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,812 root INFO copying build/lib/ansible_collections/community/ciscosmb/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,812 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins 2023-04-28 05:57:45,812 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/terminal 2023-04-28 05:57:45,812 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/terminal/ciscosmb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/terminal 2023-04-28 05:57:45,812 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:45,812 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/modules/command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:45,813 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/modules/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:45,813 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/modules 2023-04-28 05:57:45,813 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/cliconf 2023-04-28 05:57:45,813 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/cliconf/ciscosmb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/cliconf 2023-04-28 05:57:45,814 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:45,814 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/module_utils/ciscosmb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:45,814 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:45,814 root INFO copying build/lib/ansible_collections/community/ciscosmb/plugins/module_utils/ciscosmb_canonical_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/plugins/module_utils 2023-04-28 05:57:45,814 root INFO copying build/lib/ansible_collections/community/ciscosmb/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,814 root INFO copying build/lib/ansible_collections/community/ciscosmb/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,815 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/meta 2023-04-28 05:57:45,815 root INFO copying build/lib/ansible_collections/community/ciscosmb/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/meta 2023-04-28 05:57:45,815 root INFO copying build/lib/ansible_collections/community/ciscosmb/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,815 root INFO copying build/lib/ansible_collections/community/ciscosmb/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,816 root INFO copying build/lib/ansible_collections/community/ciscosmb/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,816 root INFO copying build/lib/ansible_collections/community/ciscosmb/RELEASE_POLICY.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,816 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/changelogs 2023-04-28 05:57:45,816 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/changelogs/fragments 2023-04-28 05:57:45,816 root INFO copying build/lib/ansible_collections/community/ciscosmb/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/changelogs/fragments 2023-04-28 05:57:45,816 root INFO copying build/lib/ansible_collections/community/ciscosmb/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/changelogs 2023-04-28 05:57:45,817 root INFO copying build/lib/ansible_collections/community/ciscosmb/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb/changelogs 2023-04-28 05:57:45,817 root INFO copying build/lib/ansible_collections/community/ciscosmb/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/ciscosmb 2023-04-28 05:57:45,817 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows 2023-04-28 05:57:45,817 root INFO copying build/lib/ansible_collections/community/windows/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows 2023-04-28 05:57:45,817 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins 2023-04-28 05:57:45,818 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,818 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_format.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,818 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_virtualdirectory.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,818 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scoop_bucket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,819 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_data_deduplication.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,819 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psmodule.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,819 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_xml.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,819 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_say.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,819 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_pssession_configuration.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,820 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_webbinding.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,820 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scheduled_task.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,820 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_computer_description.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,820 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_auto_logon.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,820 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psrepository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,821 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_regmerge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,821 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_zip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,821 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dns_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,821 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_firewall_rule.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,821 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_firewall.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,822 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_toast.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,822 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_webpicmd.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,822 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_product_facts.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,822 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dotnet_ngen.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,822 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psrepository.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,823 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_lineinfile.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,823 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psscript.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,823 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psrepository_copy.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,823 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_unzip.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,824 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rds_rap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,824 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_object_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,824 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psmodule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,824 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scheduled_task_stat.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,824 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rds_rap.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,825 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_disk_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,825 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_eventlog_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,825 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_audit_rule.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,825 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_group_membership.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,825 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_certificate_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,826 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_hosts.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,826 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,826 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_feature_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,826 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_route.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,826 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_shortcut.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,827 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,827 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_inet_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,827 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_user_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,827 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rabbitmq_plugin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,827 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psmodule_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,828 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_wakeonlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,828 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_disk_image.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,828 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_file_compression.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,828 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_webpicmd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,828 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_msg.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,829 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scoop.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,829 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rds_settings.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,829 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_file_compression.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,829 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,829 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_group.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,830 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_computer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,830 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_net_adapter_feature.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,830 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_group_membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,830 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_audit_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,830 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_wait_for_process.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,831 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dhcp_lease.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,831 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_listen_ports_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,831 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_robocopy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,831 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scoop_bucket.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,831 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_robocopy.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,832 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_firewall_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,832 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_disk_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,832 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_security_policy.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,832 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,832 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,833 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_credential.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,833 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psexec.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,833 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_audit_policy_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,833 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_netbios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,834 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_product_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,834 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_listen_ports_facts.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,834 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_hotfix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,834 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_pester.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,834 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_webbinding.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,835 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_user.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,835 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_website.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,835 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,835 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_eventlog_entry.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,835 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rabbitmq_plugin.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,836 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/psexec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,836 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_computer_description.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,836 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_partition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,836 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_netbios.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,836 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_mapped_drive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,837 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_format.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,837 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_pagefile.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,837 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psrepository_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,837 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_hotfix.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,837 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psscript_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,838 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_regmerge.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,838 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_snmp.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,838 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dns_zone.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,838 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_wakeonlan.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,838 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_initialize_disk.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,839 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_unzip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,839 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rds_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,839 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_data_deduplication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,839 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_http_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,839 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_defrag.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,840 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_object_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,840 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_initialize_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,840 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_ou.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,840 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rds_cap.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,841 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_pester.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,841 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_xml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,841 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_hosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,841 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_wait_for_process.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,841 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dns_record.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,842 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_power_plan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,842 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_computer.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,842 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psscript.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,842 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_msg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,842 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_website.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,843 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_webapppool.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,843 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_webapplication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,843 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_partition.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,843 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_rds_cap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,843 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psscript_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,844 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dotnet_ngen.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,844 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_net_adapter_feature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,844 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_zip.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,844 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_defrag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,844 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_pagefile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,845 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,845 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_ou.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,845 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_say.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,845 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_webapplication.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,845 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_domain_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,846 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scheduled_task.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,846 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_feature_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,846 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_inet_proxy.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,846 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_auto_logon.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,847 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,847 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_lineinfile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,847 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_power_plan.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,847 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scoop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,847 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_toast.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,848 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_eventlog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,848 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_webapppool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,848 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_file_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,848 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_pssession_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,848 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_security_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,849 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_scheduled_task_stat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,849 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_nssm.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,849 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_eventlog.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,849 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_region.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,850 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_timezone.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,850 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_user_profile.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,850 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_shortcut.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,850 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_disk_facts.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,850 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_http_proxy.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,851 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_audit_policy_system.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,851 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psexec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,851 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psrepository_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,851 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,851 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_dhcp_lease.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,852 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_file_version.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,852 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_nssm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,852 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_iis_virtualdirectory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,852 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psrepository_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,852 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_mapped_drive.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,853 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_psmodule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,853 root INFO copying build/lib/ansible_collections/community/windows/plugins/modules/win_timezone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/modules 2023-04-28 05:57:45,853 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/action 2023-04-28 05:57:45,853 root INFO copying build/lib/ansible_collections/community/windows/plugins/action/win_pssession_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/action 2023-04-28 05:57:45,853 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/lookup 2023-04-28 05:57:45,854 root INFO copying build/lib/ansible_collections/community/windows/plugins/lookup/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/lookup 2023-04-28 05:57:45,854 root INFO copying build/lib/ansible_collections/community/windows/plugins/lookup/laps_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/plugins/lookup 2023-04-28 05:57:45,854 root INFO copying build/lib/ansible_collections/community/windows/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows 2023-04-28 05:57:45,854 root INFO copying build/lib/ansible_collections/community/windows/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows 2023-04-28 05:57:45,855 root INFO copying build/lib/ansible_collections/community/windows/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows 2023-04-28 05:57:45,855 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/meta 2023-04-28 05:57:45,855 root INFO copying build/lib/ansible_collections/community/windows/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/meta 2023-04-28 05:57:45,855 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/changelogs 2023-04-28 05:57:45,856 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/changelogs/fragments 2023-04-28 05:57:45,856 root INFO copying build/lib/ansible_collections/community/windows/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/changelogs/fragments 2023-04-28 05:57:45,856 root INFO copying build/lib/ansible_collections/community/windows/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/changelogs 2023-04-28 05:57:45,856 root INFO copying build/lib/ansible_collections/community/windows/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows/changelogs 2023-04-28 05:57:45,856 root INFO copying build/lib/ansible_collections/community/windows/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/windows 2023-04-28 05:57:45,857 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,857 root INFO copying build/lib/ansible_collections/community/network/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,857 root INFO copying build/lib/ansible_collections/community/network/103-nclu-check-diff.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,857 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins 2023-04-28 05:57:45,857 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,858 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/ironware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,858 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/ce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,858 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/aireos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,858 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/netvisor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,858 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/icx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,859 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/aruba.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,859 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/sros.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,859 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/nos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,859 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/slxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,859 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/weos4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,860 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/enos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,860 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,860 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/eric_eccli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,860 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/edgeswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,860 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/exos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,860 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/apconos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,861 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/edgeos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,861 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/cnos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,861 root INFO copying build/lib/ansible_collections/community/network/plugins/terminal/voss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/terminal 2023-04-28 05:57:45,861 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/filter 2023-04-28 05:57:45,861 root INFO copying build/lib/ansible_collections/community/network/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/filter 2023-04-28 05:57:45,862 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,862 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/ironware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,862 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/ce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,862 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/aireos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,862 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/aruba.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,863 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/sros.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,863 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/enos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,863 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,863 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/ingate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,863 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/a10.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,864 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/netscaler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,864 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/avi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,864 root INFO copying build/lib/ansible_collections/community/network/plugins/doc_fragments/cnos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/doc_fragments 2023-04-28 05:57:45,864 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/netconf 2023-04-28 05:57:45,864 root INFO copying build/lib/ansible_collections/community/network/plugins/netconf/ce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/netconf 2023-04-28 05:57:45,865 root INFO copying build/lib/ansible_collections/community/network/plugins/netconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/netconf 2023-04-28 05:57:45,865 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/inventory 2023-04-28 05:57:45,865 root INFO copying build/lib/ansible_collections/community/network/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/inventory 2023-04-28 05:57:45,865 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/connection 2023-04-28 05:57:45,865 root INFO copying build/lib/ansible_collections/community/network/plugins/connection/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/connection 2023-04-28 05:57:45,866 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/callback 2023-04-28 05:57:45,866 root INFO copying build/lib/ansible_collections/community/network/plugins/callback/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/callback 2023-04-28 05:57:45,866 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,866 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,866 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/apconos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,867 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,867 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ipadm_addr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,867 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/bcf_switch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,867 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/sros_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,867 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,868 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/iap_start_workflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,868 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,868 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vxlan_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,868 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_alertsyslogconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,869 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,869 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,869 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,869 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,869 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,870 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/enos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,870 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/a10_virtual_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,870 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_multicast_igmp_enable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,870 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cv_server_provision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,871 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/voss_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,871 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_poolgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,871 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_alertscriptconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,871 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_backupconfiguration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,871 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,872 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_serviceenginegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,872 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_gslb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,872 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,872 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_ospf6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,872 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/nos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,873 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,873 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_reload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,873 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,873 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ftd_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,874 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/vdirect_commit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,874 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,874 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_cloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,874 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/dladm_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,874 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_multicast_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,875 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,875 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_useraccountprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,875 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_mdn_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,875 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/bigmon_chain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,875 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_cloudproperties.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,876 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_save_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,876 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ordnance_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,876 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_ssl_certkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,876 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,877 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_stringgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,877 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_nitro_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,877 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_evpn_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,877 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_snmp_vacm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,877 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_sslprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,878 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_startup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,878 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,878 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_snmp_contact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,878 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ironware_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,879 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_l2_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,879 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_bgp_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,880 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,880 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_l4policyset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,880 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_dldp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,880 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/dladm_etherstub.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,880 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,881 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,881 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_applicationprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,881 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vtep.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,881 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_sflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,881 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,882 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_switchport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,882 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_info_center_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,882 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_api_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,882 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_netstream_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,883 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,883 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_tenant.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,883 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,883 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/aruba_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,883 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_aaa_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,884 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,884 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,884 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_actiongroupconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,884 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_vrfcontext.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,885 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_servicegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,885 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vrrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,885 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,885 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ig_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,886 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/exos_lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,886 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_bfd_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,886 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_switch_setup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,886 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/exos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,886 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_serverautoscalepolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,887 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,887 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_aaa_server_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,887 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,887 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_bgp_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,888 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_admin_session_timeout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,888 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_snmp_target_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,888 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vflow_table_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,888 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_igmp_snooping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,888 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/dladm_vnic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,889 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_ip_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,889 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_ospf_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,889 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_mlag_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,890 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ipadm_ifprop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,890 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,890 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_virtualservice.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,890 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_certificatemanagementprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,890 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/enos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,891 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_dscp_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,891 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_connection_stats_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,891 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/edgeos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,891 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_lldp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,892 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_acl_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,892 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/nclu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,892 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ironware_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,892 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_controllerproperties.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,892 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_snmptrapprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,893 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,893 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/eric_eccli_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,893 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_networkprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,893 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vxlan_vap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,894 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vrf_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,894 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/a10_server_axapi3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,894 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,894 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,894 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,895 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_log_audit_exception.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,895 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,895 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,895 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_authprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,895 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_port_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,896 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_admin_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,896 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,896 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/edgeos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,896 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,897 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,897 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,897 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,897 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,897 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netact_cm_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,898 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ipadm_prop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,898 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/edgeos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,898 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_useraccount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,898 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_poolgroupdeploymentpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,899 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,899 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/opx_cps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,899 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_serviceengine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,899 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_mtu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,899 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_vlag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,900 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_sslkeyandcertificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,900 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_l2_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,900 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/exos_l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,900 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ordnance_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,901 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_autoscalelaunchconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,901 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_file_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,901 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_conditional_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,901 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,901 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_ntp_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,902 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,902 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,902 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_evpn_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,902 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,903 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/edgeswitch_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,903 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,903 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,903 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,903 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_prefix_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,904 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,904 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/aireos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,904 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_dhcp_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,904 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vrf_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,904 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_is_is_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,905 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_cpu_class.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,905 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/sros_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,905 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_mlag_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,905 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_conditional_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,906 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/sros_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,906 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,906 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_bfd_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,906 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_acl_advance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,907 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/exos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,907 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_dscp_map_pri_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,907 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/exos_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,907 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/vdirect_runnable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,907 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,908 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_interface_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,908 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,908 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_customipamdnsprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,908 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/bigmon_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,909 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_microservicegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,909 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/dladm_linkprop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,909 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_analyticsprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,909 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_fabric_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,909 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,910 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_dnspolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,910 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_admin_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,910 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_access_list_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,910 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ftd_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,910 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_port_cos_bw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,911 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,911 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,911 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,911 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,911 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_gslbservice_patch_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,912 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vxlan_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,912 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/a10_service_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,912 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_eth_trunk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,912 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_lb_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,913 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/nos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,913 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_healthmonitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,913 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_gslbservice.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,913 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/nos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,914 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_cs_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,914 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_bgp_neighbor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,914 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_cs_vserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,914 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ftd_file_download.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,915 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ipadm_if.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,915 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_port_cos_rate_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,915 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/flowadm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,915 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/exos_lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,915 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_evpn_bgp_rr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,916 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/voss_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,916 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_pim_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,916 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_cpu_mgmt_class.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,916 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_save.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,917 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/aruba_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,917 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_loopback_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,917 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_webhook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,917 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_snmp_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,917 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_api_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,918 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_vsdatascriptset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,918 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,918 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/vdirect_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,918 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_httppolicyset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,918 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/nuage_vspk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,919 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_cs_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,919 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_vrouter_packet_relay.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,919 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_bgp_neighbor_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,920 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_link_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,920 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,920 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_systemconfiguration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,920 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_prefix_list_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,920 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_errorpagebody.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,921 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_ipamdnsproviderprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,921 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,921 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_info_center_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,921 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_errorpageprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,922 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,922 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_ipaddrgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,922 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_cloudconnectoruser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,922 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_info_center_debug.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,922 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/exos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,923 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ftd_file_upload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,923 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_clusterclouddetails.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,923 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_factory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,923 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_networksecuritypolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,923 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_bfd_view.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,924 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_netstream_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,924 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,924 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_stp_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,924 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ipadm_addrprop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,925 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_snmp_trap_sink.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,925 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_stp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,925 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_vsvip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,925 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ironware_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,925 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_access_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,926 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_interface_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,926 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,926 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,926 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/slxos_linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,927 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_static_route_bfd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,927 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/a10_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,927 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/edgeswitch_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,927 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/enos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,927 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_evpn_bd_vni.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,928 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,928 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vxlan_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,928 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_gslb_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,928 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,929 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_prioritylabels.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,929 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ig_unit_information.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,929 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_scheduler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,929 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_snmp_traps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,929 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,930 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_applicationpersistenceprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,930 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,930 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_lb_vserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,930 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_is_is_view.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,931 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/aireos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,931 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,931 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_netstream_aging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,931 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,932 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_showrun.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,932 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/voss_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,932 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_stp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,932 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_dldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,933 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/dladm_iptun.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,933 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_alertconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,933 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,933 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_netstream_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,933 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_gslb_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,934 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_vxlan_arp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,934 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_hardwaresecuritymodulegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,934 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_alertemailconfig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,934 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_is_is_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,935 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/pn_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,935 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_seproperties.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,935 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,935 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/netscaler_gslb_vserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,935 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/icx_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,936 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/iap_token.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,936 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_pkiprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,936 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_gslbgeodbprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,936 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/cnos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,937 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/ce_info_center_trap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,937 root INFO copying build/lib/ansible_collections/community/network/plugins/modules/avi_trafficcloneprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/modules 2023-04-28 05:57:45,937 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,937 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/ironware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,937 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/ce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,938 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/aireos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,938 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/netvisor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,938 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/icx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,938 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/aruba.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,938 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/nos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,939 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/slxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,939 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/weos4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,939 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/enos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,939 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,939 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/eric_eccli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,940 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/edgeswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,940 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/exos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,940 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/apconos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,940 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/edgeos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,940 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/cnos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,941 root INFO copying build/lib/ansible_collections/community/network/plugins/cliconf/voss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cliconf 2023-04-28 05:57:45,941 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,941 root INFO copying build/lib/ansible_collections/community/network/plugins/action/ironware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,941 root INFO copying build/lib/ansible_collections/community/network/plugins/action/ce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,941 root INFO copying build/lib/ansible_collections/community/network/plugins/action/aireos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,942 root INFO copying build/lib/ansible_collections/community/network/plugins/action/nos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,942 root INFO copying build/lib/ansible_collections/community/network/plugins/action/aruba.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,942 root INFO copying build/lib/ansible_collections/community/network/plugins/action/sros.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,942 root INFO copying build/lib/ansible_collections/community/network/plugins/action/slxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,942 root INFO copying build/lib/ansible_collections/community/network/plugins/action/ce_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,943 root INFO copying build/lib/ansible_collections/community/network/plugins/action/edgeos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,943 root INFO copying build/lib/ansible_collections/community/network/plugins/action/enos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,943 root INFO copying build/lib/ansible_collections/community/network/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,943 root INFO copying build/lib/ansible_collections/community/network/plugins/action/exos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,943 root INFO copying build/lib/ansible_collections/community/network/plugins/action/cnos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,944 root INFO copying build/lib/ansible_collections/community/network/plugins/action/voss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/action 2023-04-28 05:57:45,944 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:45,944 root INFO copying build/lib/ansible_collections/community/network/plugins/httpapi/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:45,944 root INFO copying build/lib/ansible_collections/community/network/plugins/httpapi/exos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:45,944 root INFO copying build/lib/ansible_collections/community/network/plugins/httpapi/ftd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/httpapi 2023-04-28 05:57:45,945 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:45,945 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:45,945 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:45,945 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils 2023-04-28 05:57:45,945 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network 2023-04-28 05:57:45,946 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:45,946 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/netvisor/netvisor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:45,946 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/netvisor/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:45,946 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/netvisor/pn_nvos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/netvisor 2023-04-28 05:57:45,946 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:45,946 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:45,947 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd/device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:45,947 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd/fdm_swagger_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:45,947 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:45,947 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd/operation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:45,947 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ftd/configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ftd 2023-04-28 05:57:45,948 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aos 2023-04-28 05:57:45,948 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/aos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aos 2023-04-28 05:57:45,948 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/aos/aos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aos 2023-04-28 05:57:45,948 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ironware 2023-04-28 05:57:45,948 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ironware/ironware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ironware 2023-04-28 05:57:45,949 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ironware/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ironware 2023-04-28 05:57:45,949 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:45,949 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/avi/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:45,949 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/avi/avi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:45,949 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/avi/ansible_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:45,950 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/avi/avi_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/avi 2023-04-28 05:57:45,950 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aruba 2023-04-28 05:57:45,950 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/aruba/aruba.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aruba 2023-04-28 05:57:45,950 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/aruba/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aruba 2023-04-28 05:57:45,950 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/slxos 2023-04-28 05:57:45,951 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/slxos/slxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/slxos 2023-04-28 05:57:45,951 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/slxos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/slxos 2023-04-28 05:57:45,951 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:45,951 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeswitch/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:45,951 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeswitch/edgeswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:45,952 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeswitch/edgeswitch_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/edgeswitch 2023-04-28 05:57:45,952 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ingate 2023-04-28 05:57:45,952 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ingate/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ingate 2023-04-28 05:57:45,952 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ingate/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ingate 2023-04-28 05:57:45,952 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cloudengine 2023-04-28 05:57:45,952 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/cloudengine/ce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cloudengine 2023-04-28 05:57:45,953 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/cloudengine/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cloudengine 2023-04-28 05:57:45,953 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/nos 2023-04-28 05:57:45,953 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/nos/nos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/nos 2023-04-28 05:57:45,953 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/nos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/nos 2023-04-28 05:57:45,953 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/bigswitch 2023-04-28 05:57:45,954 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/bigswitch/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/bigswitch 2023-04-28 05:57:45,954 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/bigswitch/bigswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/bigswitch 2023-04-28 05:57:45,954 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/voss 2023-04-28 05:57:45,954 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/voss/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/voss 2023-04-28 05:57:45,954 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/voss/voss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/voss 2023-04-28 05:57:45,955 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/eric_eccli 2023-04-28 05:57:45,955 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/eric_eccli/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/eric_eccli 2023-04-28 05:57:45,955 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/eric_eccli/eric_eccli.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/eric_eccli 2023-04-28 05:57:45,955 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network 2023-04-28 05:57:45,955 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/netscaler 2023-04-28 05:57:45,955 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/netscaler/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/netscaler 2023-04-28 05:57:45,956 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/netscaler/netscaler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/netscaler 2023-04-28 05:57:45,956 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ordnance 2023-04-28 05:57:45,956 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ordnance/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ordnance 2023-04-28 05:57:45,956 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/ordnance/ordnance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/ordnance 2023-04-28 05:57:45,956 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/icx 2023-04-28 05:57:45,957 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/icx/icx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/icx 2023-04-28 05:57:45,957 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/icx/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/icx 2023-04-28 05:57:45,957 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos 2023-04-28 05:57:45,957 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts 2023-04-28 05:57:45,957 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans 2023-04-28 05:57:45,958 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans 2023-04-28 05:57:45,958 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans 2023-04-28 05:57:45,958 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts 2023-04-28 05:57:45,958 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global 2023-04-28 05:57:45,958 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global 2023-04-28 05:57:45,959 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global 2023-04-28 05:57:45,959 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces 2023-04-28 05:57:45,959 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces 2023-04-28 05:57:45,959 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces 2023-04-28 05:57:45,959 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts 2023-04-28 05:57:45,959 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces 2023-04-28 05:57:45,960 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces 2023-04-28 05:57:45,960 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces 2023-04-28 05:57:45,960 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy 2023-04-28 05:57:45,960 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy 2023-04-28 05:57:45,960 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy 2023-04-28 05:57:45,961 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/utils 2023-04-28 05:57:45,961 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/utils 2023-04-28 05:57:45,961 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/utils 2023-04-28 05:57:45,961 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos 2023-04-28 05:57:45,961 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config 2023-04-28 05:57:45,962 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans 2023-04-28 05:57:45,962 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans 2023-04-28 05:57:45,962 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans 2023-04-28 05:57:45,962 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global 2023-04-28 05:57:45,962 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global 2023-04-28 05:57:45,962 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global 2023-04-28 05:57:45,963 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces 2023-04-28 05:57:45,963 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces 2023-04-28 05:57:45,963 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces 2023-04-28 05:57:45,963 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config 2023-04-28 05:57:45,963 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces 2023-04-28 05:57:45,964 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces 2023-04-28 05:57:45,964 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces 2023-04-28 05:57:45,964 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec 2023-04-28 05:57:45,964 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans 2023-04-28 05:57:45,964 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans 2023-04-28 05:57:45,965 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans 2023-04-28 05:57:45,965 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts 2023-04-28 05:57:45,965 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts 2023-04-28 05:57:45,965 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts 2023-04-28 05:57:45,965 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global 2023-04-28 05:57:45,966 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global 2023-04-28 05:57:45,966 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global 2023-04-28 05:57:45,966 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces 2023-04-28 05:57:45,966 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces 2023-04-28 05:57:45,966 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces 2023-04-28 05:57:45,966 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec 2023-04-28 05:57:45,967 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces 2023-04-28 05:57:45,967 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces 2023-04-28 05:57:45,967 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces 2023-04-28 05:57:45,967 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/exos/exos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/exos 2023-04-28 05:57:45,968 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/a10 2023-04-28 05:57:45,968 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/a10/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/a10 2023-04-28 05:57:45,968 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/a10/a10.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/a10 2023-04-28 05:57:45,968 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/apconos 2023-04-28 05:57:45,968 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/apconos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/apconos 2023-04-28 05:57:45,968 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/apconos/apconos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/apconos 2023-04-28 05:57:45,969 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/enos 2023-04-28 05:57:45,969 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/enos/enos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/enos 2023-04-28 05:57:45,969 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/enos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/enos 2023-04-28 05:57:45,969 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aireos 2023-04-28 05:57:45,969 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/aireos/aireos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aireos 2023-04-28 05:57:45,970 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/aireos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/aireos 2023-04-28 05:57:45,970 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/sros 2023-04-28 05:57:45,970 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/sros/sros.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/sros 2023-04-28 05:57:45,970 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/sros/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/sros 2023-04-28 05:57:45,970 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:45,971 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos/cnos_devicerules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:45,971 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:45,971 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos/cnos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:45,971 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/cnos/cnos_errorcodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/cnos 2023-04-28 05:57:45,972 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/edgeos 2023-04-28 05:57:45,972 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/edgeos 2023-04-28 05:57:45,972 root INFO copying build/lib/ansible_collections/community/network/plugins/module_utils/network/edgeos/edgeos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/module_utils/network/edgeos 2023-04-28 05:57:45,972 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/become 2023-04-28 05:57:45,972 root INFO copying build/lib/ansible_collections/community/network/plugins/become/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/become 2023-04-28 05:57:45,972 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/lookup 2023-04-28 05:57:45,973 root INFO copying build/lib/ansible_collections/community/network/plugins/lookup/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/lookup 2023-04-28 05:57:45,973 root INFO copying build/lib/ansible_collections/community/network/plugins/lookup/avi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/lookup 2023-04-28 05:57:45,973 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cache 2023-04-28 05:57:45,973 root INFO copying build/lib/ansible_collections/community/network/plugins/cache/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/plugins/cache 2023-04-28 05:57:45,973 root INFO copying build/lib/ansible_collections/community/network/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,974 root INFO copying build/lib/ansible_collections/community/network/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,974 root INFO copying build/lib/ansible_collections/community/network/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,975 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/meta 2023-04-28 05:57:45,975 root INFO copying build/lib/ansible_collections/community/network/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/meta 2023-04-28 05:57:45,975 root INFO copying build/lib/ansible_collections/community/network/simplified_bsd.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,975 root INFO copying build/lib/ansible_collections/community/network/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,975 root INFO copying build/lib/ansible_collections/community/network/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,976 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/changelogs 2023-04-28 05:57:45,976 root INFO copying build/lib/ansible_collections/community/network/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/changelogs 2023-04-28 05:57:45,976 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/network/changelogs/fragments 2023-04-28 05:57:45,976 root INFO copying build/lib/ansible_collections/community/network/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/changelogs/fragments 2023-04-28 05:57:45,976 root INFO copying build/lib/ansible_collections/community/network/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/changelogs 2023-04-28 05:57:45,977 root INFO copying build/lib/ansible_collections/community/network/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network/changelogs 2023-04-28 05:57:45,977 root INFO copying build/lib/ansible_collections/community/network/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,977 root INFO copying build/lib/ansible_collections/community/network/shippable.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/network 2023-04-28 05:57:45,977 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,977 root INFO copying build/lib/ansible_collections/community/routeros/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,978 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins 2023-04-28 05:57:45,978 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/terminal 2023-04-28 05:57:45,978 root INFO copying build/lib/ansible_collections/community/routeros/plugins/terminal/routeros.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/terminal 2023-04-28 05:57:45,978 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:45,978 root INFO copying build/lib/ansible_collections/community/routeros/plugins/filter/list_to_dict.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:45,979 root INFO copying build/lib/ansible_collections/community/routeros/plugins/filter/join.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:45,979 root INFO copying build/lib/ansible_collections/community/routeros/plugins/filter/split.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:45,979 root INFO copying build/lib/ansible_collections/community/routeros/plugins/filter/quote_argument_value.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:45,979 root INFO copying build/lib/ansible_collections/community/routeros/plugins/filter/quote_argument.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:45,979 root INFO copying build/lib/ansible_collections/community/routeros/plugins/filter/quoting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/filter 2023-04-28 05:57:45,980 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/doc_fragments 2023-04-28 05:57:45,980 root INFO copying build/lib/ansible_collections/community/routeros/plugins/doc_fragments/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/doc_fragments 2023-04-28 05:57:45,980 root INFO copying build/lib/ansible_collections/community/routeros/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/doc_fragments 2023-04-28 05:57:45,980 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,980 root INFO copying build/lib/ansible_collections/community/routeros/plugins/modules/api_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,981 root INFO copying build/lib/ansible_collections/community/routeros/plugins/modules/command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,981 root INFO copying build/lib/ansible_collections/community/routeros/plugins/modules/api_modify.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,981 root INFO copying build/lib/ansible_collections/community/routeros/plugins/modules/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,981 root INFO copying build/lib/ansible_collections/community/routeros/plugins/modules/api_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,981 root INFO copying build/lib/ansible_collections/community/routeros/plugins/modules/api_find_and_modify.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,982 root INFO copying build/lib/ansible_collections/community/routeros/plugins/modules/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/modules 2023-04-28 05:57:45,982 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/cliconf 2023-04-28 05:57:45,982 root INFO copying build/lib/ansible_collections/community/routeros/plugins/cliconf/routeros.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/cliconf 2023-04-28 05:57:45,982 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:45,982 root INFO copying build/lib/ansible_collections/community/routeros/plugins/module_utils/api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:45,983 root INFO copying build/lib/ansible_collections/community/routeros/plugins/module_utils/routeros.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:45,983 root INFO copying build/lib/ansible_collections/community/routeros/plugins/module_utils/_api_data.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:45,983 root INFO copying build/lib/ansible_collections/community/routeros/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:45,983 root INFO copying build/lib/ansible_collections/community/routeros/plugins/module_utils/quoting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:45,984 root INFO copying build/lib/ansible_collections/community/routeros/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/plugins/module_utils 2023-04-28 05:57:45,984 root INFO copying build/lib/ansible_collections/community/routeros/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,984 root INFO copying build/lib/ansible_collections/community/routeros/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,984 root INFO copying build/lib/ansible_collections/community/routeros/update-docs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,984 root INFO copying build/lib/ansible_collections/community/routeros/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,985 root INFO copying build/lib/ansible_collections/community/routeros/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,985 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/meta 2023-04-28 05:57:45,985 root INFO copying build/lib/ansible_collections/community/routeros/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/meta 2023-04-28 05:57:45,985 root INFO copying build/lib/ansible_collections/community/routeros/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/meta 2023-04-28 05:57:45,985 root INFO copying build/lib/ansible_collections/community/routeros/meta/ee-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/meta 2023-04-28 05:57:45,986 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:45,986 root INFO copying build/lib/ansible_collections/community/routeros/LICENSES/GPL-3.0-or-later.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:45,986 root INFO copying build/lib/ansible_collections/community/routeros/LICENSES/BSD-2-Clause.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:45,986 root INFO copying build/lib/ansible_collections/community/routeros/LICENSES/PSF-2.0.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/LICENSES 2023-04-28 05:57:45,987 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:45,987 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/changelogs/fragments 2023-04-28 05:57:45,987 root INFO copying build/lib/ansible_collections/community/routeros/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/changelogs/fragments 2023-04-28 05:57:45,987 root INFO copying build/lib/ansible_collections/community/routeros/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:45,987 root INFO copying build/lib/ansible_collections/community/routeros/changelogs/changelog.yaml.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:45,987 root INFO copying build/lib/ansible_collections/community/routeros/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros/changelogs 2023-04-28 05:57:45,988 root INFO copying build/lib/ansible_collections/community/routeros/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,988 root INFO copying build/lib/ansible_collections/community/routeros/CHANGELOG.rst.license -> build/bdist.linux-x86_64/wheel/ansible_collections/community/routeros 2023-04-28 05:57:45,988 root INFO copying build/lib/ansible_collections/ansible_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections 2023-04-28 05:57:45,988 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud 2023-04-28 05:57:45,989 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,989 root INFO copying build/lib/ansible_collections/cloud/common/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,989 root INFO copying build/lib/ansible_collections/cloud/common/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,989 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins 2023-04-28 05:57:45,989 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:45,990 root INFO copying build/lib/ansible_collections/cloud/common/plugins/modules/turbo_demo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:45,990 root INFO copying build/lib/ansible_collections/cloud/common/plugins/modules/turbo_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:45,990 root INFO copying build/lib/ansible_collections/cloud/common/plugins/modules/turbo_fail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/modules 2023-04-28 05:57:45,990 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/plugin_utils 2023-04-28 05:57:45,990 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/plugin_utils/turbo 2023-04-28 05:57:45,990 root INFO copying build/lib/ansible_collections/cloud/common/plugins/plugin_utils/turbo/lookup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/plugin_utils/turbo 2023-04-28 05:57:45,991 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/module_utils 2023-04-28 05:57:45,991 root INFO copying build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo_demo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/module_utils 2023-04-28 05:57:45,991 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:45,991 root INFO copying build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:45,991 root INFO copying build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo/exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:45,992 root INFO copying build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo/server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:45,992 root INFO copying build/lib/ansible_collections/cloud/common/plugins/module_utils/turbo/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/module_utils/turbo 2023-04-28 05:57:45,992 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/lookup 2023-04-28 05:57:45,992 root INFO copying build/lib/ansible_collections/cloud/common/plugins/lookup/turbo_demo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/plugins/lookup 2023-04-28 05:57:45,992 root INFO copying build/lib/ansible_collections/cloud/common/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,993 root INFO copying build/lib/ansible_collections/cloud/common/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,993 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/meta 2023-04-28 05:57:45,993 root INFO copying build/lib/ansible_collections/cloud/common/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/meta 2023-04-28 05:57:45,993 root INFO copying build/lib/ansible_collections/cloud/common/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,993 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/changelogs 2023-04-28 05:57:45,994 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/changelogs/fragments 2023-04-28 05:57:45,994 root INFO copying build/lib/ansible_collections/cloud/common/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/changelogs/fragments 2023-04-28 05:57:45,994 root INFO copying build/lib/ansible_collections/cloud/common/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/changelogs 2023-04-28 05:57:45,994 root INFO copying build/lib/ansible_collections/cloud/common/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common/changelogs 2023-04-28 05:57:45,994 root INFO copying build/lib/ansible_collections/cloud/common/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,995 root INFO copying build/lib/ansible_collections/cloud/common/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,995 root INFO copying build/lib/ansible_collections/cloud/common/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cloud/common 2023-04-28 05:57:45,995 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu 2023-04-28 05:57:45,995 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:45,995 root INFO copying build/lib/ansible_collections/sensu/sensu_go/sanity.requirements -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:45,995 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins 2023-04-28 05:57:45,996 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/filter 2023-04-28 05:57:45,996 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/filter/package_name.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/filter 2023-04-28 05:57:45,996 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/filter/backends.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/filter 2023-04-28 05:57:45,996 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,996 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/namespace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,997 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/annotations.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,997 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/secrets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,997 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/requirements.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,997 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,997 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/name.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,998 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,998 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/state.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,998 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/doc_fragments/labels.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/doc_fragments 2023-04-28 05:57:45,998 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:45,998 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_binding.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:45,999 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/asset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:45,999 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/mutator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:45,999 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_binding_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:45,999 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/namespace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:45,999 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,000 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,000 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/silence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,000 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/filter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,000 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/ldap_auth_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,000 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/handler_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,001 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/check_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,001 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/handler_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,001 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/entity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,001 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_vault.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,001 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,002 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/pipe_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,002 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/silence_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,002 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/secret_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,002 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/role_binding_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,002 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/ad_auth_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,003 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,003 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/datastore_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,003 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,003 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,003 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_env.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,004 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/asset_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,004 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,004 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/entity_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,004 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/etcd_replicator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,005 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,005 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/role_binding.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,005 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,005 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/event_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,005 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/auth_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,006 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/hook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,006 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,006 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/tessen.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,006 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/hook_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,006 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/namespace_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,007 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/bonsai_asset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,007 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/etcd_replicator_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,007 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/datastore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,007 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/socket_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,007 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/oidc_auth_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,008 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,008 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/mutator_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,008 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/event.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,008 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/modules/cluster_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/modules 2023-04-28 05:57:46,008 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/action 2023-04-28 05:57:46,009 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/action/bonsai_asset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/action 2023-04-28 05:57:46,009 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,009 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/bonsai.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,009 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/arguments.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,009 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,010 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/errors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,010 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,010 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,010 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/debug.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,010 root INFO copying build/lib/ansible_collections/sensu/sensu_go/plugins/module_utils/role_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/plugins/module_utils 2023-04-28 05:57:46,011 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/vagrant 2023-04-28 05:57:46,011 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:46,011 root INFO copying build/lib/ansible_collections/sensu/sensu_go/vagrant/windows/back.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:46,011 root INFO copying build/lib/ansible_collections/sensu/sensu_go/vagrant/windows/Vagrantfile -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:46,011 root INFO copying build/lib/ansible_collections/sensu/sensu_go/vagrant/windows/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:46,012 root INFO copying build/lib/ansible_collections/sensu/sensu_go/vagrant/windows/play.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/vagrant/windows 2023-04-28 05:57:46,012 root INFO copying build/lib/ansible_collections/sensu/sensu_go/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,012 root INFO copying build/lib/ansible_collections/sensu/sensu_go/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,012 root INFO copying build/lib/ansible_collections/sensu/sensu_go/integration.requirements -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,012 root INFO copying build/lib/ansible_collections/sensu/sensu_go/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,013 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/meta 2023-04-28 05:57:46,013 root INFO copying build/lib/ansible_collections/sensu/sensu_go/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/meta 2023-04-28 05:57:46,013 root INFO copying build/lib/ansible_collections/sensu/sensu_go/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/meta 2023-04-28 05:57:46,013 root INFO copying build/lib/ansible_collections/sensu/sensu_go/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,014 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/tools 2023-04-28 05:57:46,014 root INFO copying build/lib/ansible_collections/sensu/sensu_go/tools/windows-versions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/tools 2023-04-28 05:57:46,014 root INFO copying build/lib/ansible_collections/sensu/sensu_go/collection.requirements -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,014 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/changelogs 2023-04-28 05:57:46,014 root INFO copying build/lib/ansible_collections/sensu/sensu_go/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/changelogs 2023-04-28 05:57:46,014 root INFO copying build/lib/ansible_collections/sensu/sensu_go/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,015 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,015 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/debian-9.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,015 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.3.0.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,015 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.7.5.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,015 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/redhat-7.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,016 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/oracle-8.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,016 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/rocky-8.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,016 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.8.2.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,016 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.2.5.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,016 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/ubuntu-14.04.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,017 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/centos-7.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,017 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/centos-6.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,017 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.4.3.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,017 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.5.5.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,017 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.6.2.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,018 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/build.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,018 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-5.21.3.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,018 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-5.14.2.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,018 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/sensu-6.9.0.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,018 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/amazon-1.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,018 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/centos-8.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,019 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/ubuntu-18.04.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,019 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/build-all.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,019 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/ubuntu-16.04.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,019 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/debian-10.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,019 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/alma-8.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,020 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docker/amazon-2.docker -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/docker 2023-04-28 05:57:46,020 root INFO copying build/lib/ansible_collections/sensu/sensu_go/docs.requirements -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,020 root INFO copying build/lib/ansible_collections/sensu/sensu_go/pytest.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles 2023-04-28 05:57:46,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install 2023-04-28 05:57:46,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:46,021 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/repositories.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:46,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/msi 2023-04-28 05:57:46,021 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/msi/install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/msi 2023-04-28 05:57:46,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/yum 2023-04-28 05:57:46,021 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/yum/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/yum 2023-04-28 05:57:46,022 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/yum/install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/yum 2023-04-28 05:57:46,022 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf 2023-04-28 05:57:46,022 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf 2023-04-28 05:57:46,022 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf/install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/dnf 2023-04-28 05:57:46,022 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/packages.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:46,023 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks 2023-04-28 05:57:46,023 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/apt 2023-04-28 05:57:46,023 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/apt/prepare.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/apt 2023-04-28 05:57:46,023 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/tasks/apt/install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/tasks/apt 2023-04-28 05:57:46,023 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/defaults 2023-04-28 05:57:46,024 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/defaults 2023-04-28 05:57:46,024 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install 2023-04-28 05:57:46,024 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,024 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/Alma.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,024 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/Rocky.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,025 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/Debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,025 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/CentOS.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,025 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/Windows.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,025 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/Ubuntu.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,025 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/RedHat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,026 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/OracleLinux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,026 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/vars/Amazon.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/vars 2023-04-28 05:57:46,026 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/meta 2023-04-28 05:57:46,026 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/meta/argument_specs.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/meta 2023-04-28 05:57:46,026 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/install/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/install/meta 2023-04-28 05:57:46,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend 2023-04-28 05:57:46,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:46,027 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/tasks/start.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:46,027 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:46,027 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/tasks/configure.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/tasks 2023-04-28 05:57:46,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/defaults 2023-04-28 05:57:46,028 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/defaults 2023-04-28 05:57:46,028 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/handlers 2023-04-28 05:57:46,028 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/handlers 2023-04-28 05:57:46,028 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend 2023-04-28 05:57:46,028 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/templates 2023-04-28 05:57:46,029 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/templates/backend.yml.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/templates 2023-04-28 05:57:46,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/vars 2023-04-28 05:57:46,029 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/vars 2023-04-28 05:57:46,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/meta 2023-04-28 05:57:46,029 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/meta/argument_specs.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/meta 2023-04-28 05:57:46,029 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/backend/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/backend/meta 2023-04-28 05:57:46,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent 2023-04-28 05:57:46,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:46,030 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/start.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:46,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks/linux 2023-04-28 05:57:46,030 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/linux/configure.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks/linux 2023-04-28 05:57:46,031 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:46,031 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/configure.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks 2023-04-28 05:57:46,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks/windows 2023-04-28 05:57:46,031 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/tasks/windows/configure.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/tasks/windows 2023-04-28 05:57:46,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/defaults 2023-04-28 05:57:46,032 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/defaults 2023-04-28 05:57:46,032 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/handlers 2023-04-28 05:57:46,032 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/handlers 2023-04-28 05:57:46,032 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent 2023-04-28 05:57:46,032 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/templates 2023-04-28 05:57:46,032 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/templates/agent.yml.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/templates 2023-04-28 05:57:46,033 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:46,033 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/vars/linux.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:46,033 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/vars/windows.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:46,033 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/vars 2023-04-28 05:57:46,033 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/meta 2023-04-28 05:57:46,034 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/meta/argument_specs.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/meta 2023-04-28 05:57:46,034 root INFO copying build/lib/ansible_collections/sensu/sensu_go/roles/agent/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go/roles/agent/meta 2023-04-28 05:57:46,034 root INFO copying build/lib/ansible_collections/sensu/sensu_go/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/sensu/sensu_go 2023-04-28 05:57:46,034 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat 2023-04-28 05:57:46,034 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,035 root INFO copying build/lib/ansible_collections/infinidat/infinibox/requirements-dev.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,035 root INFO copying build/lib/ansible_collections/infinidat/infinibox/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,035 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins 2023-04-28 05:57:46,035 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/filter 2023-04-28 05:57:46,035 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/filter/delta_time.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/filter 2023-04-28 05:57:46,036 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/filter/psus_filters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/filter 2023-04-28 05:57:46,036 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/doc_fragments 2023-04-28 05:57:46,036 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/doc_fragments/infinibox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/doc_fragments 2023-04-28 05:57:46,036 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,036 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,037 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_export_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,037 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_vol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,037 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,037 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,037 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,038 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,038 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,038 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,038 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_fs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,038 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,039 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/modules/infini_network_space.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/modules 2023-04-28 05:57:46,039 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/module_utils 2023-04-28 05:57:46,039 root INFO copying build/lib/ansible_collections/infinidat/infinibox/plugins/module_utils/infinibox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/plugins/module_utils 2023-04-28 05:57:46,039 root INFO copying build/lib/ansible_collections/infinidat/infinibox/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,039 root INFO copying build/lib/ansible_collections/infinidat/infinibox/Makefile-help -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,040 root INFO copying build/lib/ansible_collections/infinidat/infinibox/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,040 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/meta 2023-04-28 05:57:46,040 root INFO copying build/lib/ansible_collections/infinidat/infinibox/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/meta 2023-04-28 05:57:46,040 root INFO copying build/lib/ansible_collections/infinidat/infinibox/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/meta 2023-04-28 05:57:46,040 root INFO copying build/lib/ansible_collections/infinidat/infinibox/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,041 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/ibox_vars 2023-04-28 05:57:46,041 root INFO copying build/lib/ansible_collections/infinidat/infinibox/ibox_vars/iboxCICD.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/ibox_vars 2023-04-28 05:57:46,041 root INFO copying build/lib/ansible_collections/infinidat/infinibox/ibox_vars/iboxNNNN_example.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/ibox_vars 2023-04-28 05:57:46,041 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,041 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_setup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,042 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_remove_snapshots.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,042 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_create_snapshots.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,042 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_create_network_spaces.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,042 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,042 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_create_resources.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,043 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_remove_network_spaces.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,043 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_create_map_cluster.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,043 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_remove_map_cluster.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,043 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_runtest.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,043 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,044 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/test_remove_resources.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,044 root INFO copying build/lib/ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_teardown.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox/playbooks 2023-04-28 05:57:46,044 root INFO copying build/lib/ansible_collections/infinidat/infinibox/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,044 root INFO copying build/lib/ansible_collections/infinidat/infinibox/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,044 root INFO copying build/lib/ansible_collections/infinidat/infinibox/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/infinidat/infinibox 2023-04-28 05:57:46,045 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet 2023-04-28 05:57:46,045 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:46,045 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:46,045 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins 2023-04-28 05:57:46,045 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins 2023-04-28 05:57:46,046 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,046 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_disableentry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,047 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,047 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertevent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,047 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_securitypolicy_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,047 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,048 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,048 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiview_autocache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,048 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,048 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_ocspserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,049 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollinganalyzer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,049 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_apcfgprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,049 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6delegatedprefixlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,049 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_filepattern.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,049 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_socfabric.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,050 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_respmodforwardrules_headergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,050 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,050 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_vrrp6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,050 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_nntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,050 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_add_devlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,051 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,051 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,051 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,051 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_address_dynamicaddrmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,052 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_dlpfilesautodeletion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,052 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_webfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,052 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,052 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_automation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,053 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_icon.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,053 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_contentheader.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,053 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,053 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_templategroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,053 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_nsx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,054 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_service_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,054 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_filefilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,054 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_onetime.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,054 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpipaddresstype.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,055 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_filefilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,055 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,055 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_dnsbl_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,055 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_cliprof_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,055 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_logout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,056 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,056 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,056 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_apcfgprofile_commandlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,056 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,057 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_hascheduledcheck.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,057 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpsysinfo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,057 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_task_result.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,057 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_diskquota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,057 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,058 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,058 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_youtubechannelfilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,058 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_passwordpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,058 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider_friendlyname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,059 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,059 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_serverpubkeyauthsettings_certextension.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,059 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_metadata_admins.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,059 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_discover_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,060 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fssopolling_adgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,060 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_revert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,060 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_multicastpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,060 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,060 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_sign_certificate_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,061 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_emailserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,061 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ssl_settings_authenticationrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,061 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_policyv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,061 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_ipdscpmap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,062 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_ftgddns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,062 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,062 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,062 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,062 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_domainfilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,063 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile_fortiguardcategory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,063 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_filefilter_profile_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,063 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_authentication_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,063 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,064 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpconncapability.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,064 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_disableentry_iprange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,064 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,064 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_https.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,064 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fwmsetting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,065 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_profile_headers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,065 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_mheader.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,065 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_move.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,065 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shaper_peripshaper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,066 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,066 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_dsl_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,066 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,066 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ftps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,067 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ieremovepolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,067 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_mmschecksum_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,067 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_contentlength.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,067 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_protectedsubnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,067 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,068 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_dnstranslation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,068 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,068 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,068 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,069 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,069 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,069 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ioc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,070 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping_sslciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,070 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6_sslciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,070 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_pblock_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,070 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_priorityprotocol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,071 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,071 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,071 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenueurl_valuelist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,071 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,072 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,072 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_localinpolicy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,072 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_adgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,072 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_macaddrcheckrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,073 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_custommessage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,073 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_vrrp6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,073 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_restrictdevvdom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,073 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_credentialstore_domaincontroller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,073 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_folder.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,074 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,074 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_adom_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,074 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_summaryaddr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,074 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_filefilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,074 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_excluderange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,075 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,075 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_mail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,075 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,075 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_notifmsisdn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,076 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_disk_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,076 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_proxy_json.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,076 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface_platformmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,076 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf_filters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,077 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_nacquar.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,077 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,077 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_urlextraction.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,077 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_customurllist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,078 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_consolidated_policy_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,078 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,078 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,078 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_route6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,078 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_radius.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,079 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,079 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_excluderange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,079 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,079 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_filefilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,080 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature_mainclass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,080 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ievalidation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,080 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddrgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,080 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,081 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,081 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,081 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_mms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,081 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,082 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_customtlvs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,082 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_neighbor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,082 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_customskipidx.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,082 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_match.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,082 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_contentheader_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,083 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_remote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,083 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_service_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,083 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bword_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,083 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_centralsnatmap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,084 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fctservices.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,084 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,084 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_method_methodpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,084 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy6_anomaly.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,084 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_trafficquota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,085 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ipsourceguard_bindingentry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,085 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipcountry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,085 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,086 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_commit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,086 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_switchlog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,086 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_customindex.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,086 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_meta_sysmetafields.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,087 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,087 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_device_profile_fortianalyzer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,087 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile_logfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,087 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_localinpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,088 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_domaincontroller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,088 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_override.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,088 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_appfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,088 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_krbkeytab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,089 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,089 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,089 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_healthcheck_sla.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,089 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_variable_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,089 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,090 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_sysinfo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,090 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp46.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,090 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,090 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,091 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_fospolicystats.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,091 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer2_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,091 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_malformed.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,091 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer3_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,092 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_platform.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,092 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_outbreakprevention.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,092 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_iprange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,092 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_simprofile_autoswitchprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,092 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_medlocationservice.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,093 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_iptrust.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,093 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_respmodforwardrules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,093 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,093 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_webproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,094 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_log_customfield.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,094 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,094 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_filefilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,094 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,095 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,095 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_vlanname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,095 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,095 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup_bookmarks_formdata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,095 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fsso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,096 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group_groupby.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,096 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_utmprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,096 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_mmschecksum.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,096 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_policy_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,097 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,097 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6prefixlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,097 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_group_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,097 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_excluderange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,097 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_wanprof_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,098 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,098 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,098 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,098 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,099 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_input_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,099 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverridetoclient.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,099 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_notification.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,099 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_pop3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,099 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,100 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_securitypolicy_8021x.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,100 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_controllerreport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,100 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_msnhotmail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,100 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,101 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,101 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_obj.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,101 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_vcenter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,101 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_sip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,102 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_ippool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,102 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_workflow_approvalmatrix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,102 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_backup_allsettings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,102 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_dot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,103 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_match.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,103 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_certificate_local_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,103 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_vcenter_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,103 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6extraaddr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,103 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_workflow_approvalmatrix_approver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,104 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,104 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,104 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_pop3s.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,104 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_sslvpn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,105 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_server_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,105 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shapingprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,105 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,105 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_filefilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,106 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_dynamicmapping_subnetsegment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,106 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_execute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,106 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_simprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,106 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_dnsbl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,106 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,107 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_utm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,107 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_connector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,107 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_exchange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,107 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_addrgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,108 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_remote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,108 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_spam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,108 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicecategory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,108 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,109 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd3_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,109 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_sslserverciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,109 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqp3gppcellular_mccmnclist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,109 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_securitypolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,110 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_vrrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,110 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,110 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fssopolling.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,110 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,110 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_dnsbl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,111 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_devicedetectionportal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,111 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverridetoclient_announceip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,111 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_members.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,111 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries_parameters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,112 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_neighbor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,112 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting_serveroverride_servlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,112 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,112 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,112 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_portcpumap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,113 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_shapingpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,113 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,113 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,114 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,114 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_otherwebmails.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,114 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_lan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,115 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_ipsfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,115 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd2_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,115 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_aspathlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,115 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_carrierendpointbwl_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,116 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_messagefilterv0v1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,116 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_central_dnat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,116 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,116 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,117 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,117 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_sslciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,117 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,117 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pblock_obj.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,117 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_export_playbooks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,118 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,119 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy6_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,119 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,119 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_notification_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,119 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_meta.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,120 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_serverpubkeyauthsettings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,120 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,120 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_datatype.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,120 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,121 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_addresslist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,121 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveroverridestatus.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,121 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,121 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_hsprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,122 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_oftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,122 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device_vdom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,122 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_filefilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,122 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_devprof_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,122 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_nacquar.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,123 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_ca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,123 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_dataplan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,123 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,123 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,124 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy6_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,124 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,124 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_serverkeytab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,124 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_exception.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,124 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,125 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxrangesegment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,125 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,125 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_commit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,126 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,126 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_tsindexfield.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,126 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,126 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_dashboardtabs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,126 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_rename.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,127 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,128 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_tcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,128 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_blockallowlist_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,128 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_gmail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,128 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_fortishield.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,129 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride_iprange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,129 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,130 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_securityexemptlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,130 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,130 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_hostchecksoftware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,130 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,131 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_iptrust.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,131 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_customcommand.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,131 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_centralmanagement_serverlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,131 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile_devicefilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,132 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_multilayer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,132 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,132 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,132 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_ntp_ntpserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,132 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bwl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,133 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_subclass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,133 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_filefilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,133 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpoperatorname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,133 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,134 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,134 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_8021xsettings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,134 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride_ip6range.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,135 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_mcpolicydisabledadoms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,135 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_hostchecksoftware_checkitemlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,135 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_localinpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,135 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_dashboard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,136 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,136 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,136 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_mapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,136 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,137 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template_subnetsegment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,137 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_icon_iconlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,137 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_updateschedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,137 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bonjourprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,137 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_mapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,138 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_trafficclass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,138 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_saml_fabricidp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,138 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries_parameters_members.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,138 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_import_dev_objs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,139 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_assign_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,139 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,139 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,139 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_secondaryip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,140 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf_quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,140 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_virtualwirepair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,140 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_reload_devlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,140 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_abort.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,140 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_sslvpnoschecklist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,141 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist6_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,141 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_imaps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,141 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,141 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_defaultnetworkservices.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,142 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping_sslciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,142 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_webproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,142 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_secondaryip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,142 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,143 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_splittunnelingacl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,143 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_fpsensitivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,143 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_generic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,143 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,144 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,144 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ippolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,144 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap_dscpexcept.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,144 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_categories.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,144 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_urlaccess.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,145 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit_ratelimits.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,145 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_shellcommands.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,145 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,145 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_filepattern_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,146 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_iptrust_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,146 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,146 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_entry_portrange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,146 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,146 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge_aoclist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,147 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sniffer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,147 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_certificate_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,147 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool6_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,147 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,148 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,148 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_save.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,148 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,148 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_dot1pmap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,149 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_imap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,149 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_connector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,149 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_proxypolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,149 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_messagefilterv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,150 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_saml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,150 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,150 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_youtubechannelfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,150 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_reset_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,151 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,151 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,151 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification_alert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,151 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,152 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,152 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,152 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,153 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenuename_valuelist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,153 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ssh_localca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,153 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_members_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,154 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_authentication_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,154 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_urlfilter_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,154 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,154 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_routemap_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,154 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_content.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,155 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_mailsignature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,155 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,155 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,155 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,156 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_pop3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,156 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_apn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,156 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bwl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,156 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_localinpolicy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,156 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_dynamicmapping_accountingserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,157 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxcookie.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,157 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_crl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,157 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,157 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,157 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,158 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,158 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_utm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,158 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_imap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,159 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fortitoken.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,159 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_imap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,159 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,159 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_api_sdnconnector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,159 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,160 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,160 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_duplication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,160 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,160 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_blockallowlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,161 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiguard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,161 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bwl_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,161 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_publicnetwork.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,161 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,162 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,162 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_disk_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,162 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertemail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,162 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_authgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,162 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,163 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,163 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,163 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_eslsesdongle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,163 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_iewhitelist_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,164 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpuser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,164 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxurlparam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,164 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_changehaseq.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,164 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_wildcardfqdn_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,164 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bwl_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,165 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,165 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,165 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qptermsandconditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,165 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,165 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_scriptschedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,166 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,166 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,166 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,166 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,167 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_externalaccountlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,167 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_centralmanagement.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,167 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_lbs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,167 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,168 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenueurl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,168 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,168 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,168 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_authentication_scheme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,169 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,169 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition_entry_portrange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,169 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_ftgddns_filters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,169 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_docker.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,170 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_pxgrid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,170 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_outbreakprevention.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,170 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature_customsignature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,170 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_queuepolicy_cosqueue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,170 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_mheader.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,171 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish_inspectionentries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,171 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_customcommand.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,171 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_reservedaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,171 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_sslciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,172 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_domaincontroller_extraserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,172 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,172 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_wanprof_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,173 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_trafficquota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,173 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting_serveroverride.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,173 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_cancel_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,173 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_dictionary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,174 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,174 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_syslogd_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,174 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_securityexemptlist_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,174 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,175 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveraccesspriorities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,175 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template_subnetsegment_values.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,175 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,175 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_ec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,176 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_switchstpsettings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,176 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_reinstall_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,176 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_healthcheck_sla.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,176 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_sysinfo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,176 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,177 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpwanmetric.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,177 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_customlanguage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,177 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,177 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_method.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,178 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,178 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_objectmember.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,178 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,178 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_service_sla.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,178 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,179 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,179 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,180 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_discard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,180 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,180 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_neighbor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,180 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_lock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,181 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,181 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_devprof_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,181 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,181 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_maildomain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,181 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_devicedisable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,182 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge_aoclist_planinfo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,182 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,182 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_unlock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,182 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovidernai.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,182 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,183 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_communitylist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,183 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress_headergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,183 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_iprange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,183 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,184 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_securitypolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,184 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,184 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_upgrade.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,184 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensitivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,185 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_denymaclist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,185 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fips.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,185 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,185 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,186 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqproamingconsortium.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,186 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_guest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,186 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,186 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_ftgdlocalcat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,186 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollinglocal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,187 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_cifs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,187 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_urlaccess_accesspattern.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,187 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_neighbor_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,187 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,188 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,188 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,188 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,188 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,189 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_ipv4excluderange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,189 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,189 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_portnpumap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,189 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_fpanomaly.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,189 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_drop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,190 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_msrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,190 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_securitypolicy_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,190 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_contentdisarm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,190 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,191 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_serverkeytab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,191 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_lanextension.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,191 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_apn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,191 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_sslserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,192 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_group_objectmember.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,192 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_endpointcontrol_fctems.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,192 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_del_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,192 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_imap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,192 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_serveroverride.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,193 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,193 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_categories.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,193 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_filefilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,193 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,194 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_login_challenge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,194 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy_anomaly.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,194 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_dev.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,194 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_ftgdlocalrating.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,194 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_macfilterlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,195 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_consolidated_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,195 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_login_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,195 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_mirror.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,195 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,196 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,196 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_qospolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,196 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_preview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,196 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenuename.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,196 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group_chartalternative.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,197 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress6_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,197 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_serveroverride_servlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,197 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile_fortiguardcategory_filters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,197 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_move.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,197 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_multicast_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,198 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem1_autoswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,198 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_obj.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,198 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_urlfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,198 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservice.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,199 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_mainclass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,199 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ipsourceguard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,199 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,199 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vapgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,200 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,200 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_sslexempt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,200 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,200 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_reservedaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,200 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,201 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,201 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_tunnellimit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,201 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_saml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,201 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,202 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_routemap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,202 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_oschecklist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,202 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_yahoomail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,202 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,202 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_generate_wsdl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,203 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertevent_alertdestination.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,203 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv0.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,203 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,203 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_guiact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,204 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6delegatedprefixlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,204 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,204 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_dev.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,204 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_ldap_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,204 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_forwardingrule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,205 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,205 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bleprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,205 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,205 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_logautodeletion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,206 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,206 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_dictionary_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,206 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6extraaddr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,206 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_estbrowsetime.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,206 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_centralsnatmap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,207 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_topology.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,207 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,207 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,207 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_externalip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,208 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_preview_result.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,208 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider_servicedescription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,208 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,208 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_submit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,208 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer3_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,209 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsgimage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,209 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_repair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,209 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,209 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ipsec_fec_mappings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,209 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_linelength.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,210 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,210 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_central_dnat6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,210 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,210 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wagprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,211 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_update_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,211 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile_mpskgroup_mpskkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,211 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_externalresource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,211 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd3_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,212 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_monitoredips.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,212 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_clearpass.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,212 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,212 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,212 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,213 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqproamingconsortium_oilist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,213 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_fortianalyzercloud_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,213 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,213 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,214 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_category.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,214 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community_hosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,214 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_fortianalyzer_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,214 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_review.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,214 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_vpntable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,215 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_widsprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,215 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardservergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,215 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ssl_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,216 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_mheader_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,216 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddrgrp_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,216 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,216 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,216 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_queuepolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,217 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap_dscprange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,217 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_decryptedtrafficmirror.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,217 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,217 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_sslserverciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,217 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_nntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,218 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicename.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,218 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_multicastpolicy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,218 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_identitybasedroute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,218 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,219 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_vpndstnode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,219 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_wildcardfqdn_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,219 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,219 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverride.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,219 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_autocache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,220 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_alertmail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,220 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_certificate_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,220 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_vlanpool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,220 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_filefilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,221 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqp3gppcellular.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,221 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_nic_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,221 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,221 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpcommunity_hosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,221 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_memory_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,222 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_nntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,222 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,222 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,222 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_profile_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,223 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bword_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,223 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_icapheaders.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,223 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_routetable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,223 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device_replace_sn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,223 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup_bookmarks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,224 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_method.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,224 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_dev.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,224 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_start.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,224 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_input_interface_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,225 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,225 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,225 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy46.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,225 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_update_devlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,225 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_gmail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,226 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_reject.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,226 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_add_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,226 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_realm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,226 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pblock_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,227 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_device_blueprint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,227 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_nacprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,227 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist_eapmethod_authparam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,227 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,227 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_interfacestats.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,228 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community_hosts6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,228 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_adom_objectmember.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,228 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,229 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpcommunity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,229 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer2_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,230 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm7.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,230 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_members.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,230 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveraccesspriorities_privateserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,231 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,231 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,231 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_content_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,231 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,232 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_headerlength.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,232 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_passwordpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,232 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_quarantinefilesautodeletion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,232 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_shapingpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,233 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_lanextension_backhaul.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,233 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_mapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,233 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fsso_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,233 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_tacacs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,234 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_del_devlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,234 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,234 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmptrapthreshold.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,234 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertconsole.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,234 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_paramlength.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,235 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_swehhash.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,235 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,235 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,235 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_igmpsnooping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,235 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_apngrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,236 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,236 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,236 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_portalmessageoverrides.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,236 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_avips_advancedlog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,237 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_pop3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,237 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_ipdscpmap_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,237 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vpntunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,237 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_device_profile_fortiguard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,237 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ssl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,238 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_iptrust_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,238 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_flood.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,238 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_web.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,238 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_memory_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,239 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiview_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,239 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_adomexclude.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,239 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_import_devlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,239 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_qosprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,240 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profilegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,240 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,240 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish_custompatterns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,240 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_avips_webproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,241 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_pop3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,241 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,241 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxyvirtualhost.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,241 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_subnetsegment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,241 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_alert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,242 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,242 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_cifs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,242 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_urlparamlength.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,242 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,242 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_signature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,243 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_mail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,243 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,243 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,244 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_metafields_system_admin_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,244 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shaper_trafficshaper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,244 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_nntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,244 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,245 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,245 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_iprange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,245 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_tacacs_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,245 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_carrierendpointbwl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,245 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_mpskkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,246 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,246 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardservergroup_serverlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,246 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,246 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,247 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_pkg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,247 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_notification.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,247 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification_receiver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,247 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_routetable_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,248 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,248 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_mheader_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,248 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_recurring.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,248 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway_sslciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,249 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_serversettings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,249 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,249 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vpntunnel_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,249 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,250 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,250 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_webproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,250 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,250 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,250 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ntp_ntpserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,251 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_arrpprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,251 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_exec_fgfm_reclaimdevtunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,251 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,251 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,252 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_profile_datamaskcustomfields.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,252 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_identitybasedroute_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,252 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_isfnpqueues.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,252 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,252 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_members.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,253 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_gcpprojectlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,253 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sslciphersuites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,253 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_sccp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,253 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservice_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,254 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem2_autoswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,254 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_domainfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,254 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,255 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_noippolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,255 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,255 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_ca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,255 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_remotelog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,256 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_ldap_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,256 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_sslvpn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,256 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,256 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_metadata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,257 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,257 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,257 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_communitylist_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,257 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_service_sla.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,257 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,258 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_imsi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,258 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustomgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,258 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_webproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,258 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_smb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,258 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,259 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_obj.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,259 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_youtubechannelfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,259 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_mapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,259 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd2_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,260 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_domaincontroller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,260 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist_eapmethod.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,260 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_adom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,260 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile_mpskgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,260 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_alertmail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,261 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_nsx_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,261 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_domainfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,261 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_iprange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,261 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,262 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_healthcheck.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,262 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,262 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,262 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_variable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,263 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_securitypolicy_captiveportal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,263 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,263 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,263 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_stormcontrol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,264 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_accountingserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,264 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_fortiguardwf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,264 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_smtps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,264 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,264 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,265 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_monitoredinterfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,265 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_revision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,265 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_filefilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,265 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_healthcheck.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,266 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_fortiguardwf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,266 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,266 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,267 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,267 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_smsserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,267 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_splitdns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,268 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_msnhotmail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,268 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_guest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,268 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollingregular.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,268 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpoperatorname_valuelist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,269 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,269 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_icap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,269 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_multicast_interface_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,269 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_reservedaddress.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,269 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,270 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_proxypolicy_sectionvalue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,270 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_analyzer_virusreport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,270 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,270 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_mednetworkpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,271 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnetworkauthtype.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,271 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ipsec_fec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,271 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,271 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_vpnsrcnode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,272 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_dupe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,272 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_acl6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,272 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_objecttagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,272 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_pop3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,272 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,273 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,273 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,273 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_perapnshaper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,273 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_mapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,274 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovidernai_nailist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,274 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,274 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface_ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,274 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,274 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxheaderline.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,275 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,275 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6_realservers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,275 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shapingprofile_shapingentries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,275 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_stpsettings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,276 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_spam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,276 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_devicedetectionportal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,276 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_nic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,276 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_iewhitelist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,277 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community_hosts6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,277 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ldbmonitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,277 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_dnsbl_entries.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,277 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,278 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,278 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_policypackage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,278 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_reportautodeletion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,278 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_shapingpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,279 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6prefixlist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,279 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_nacquar.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,279 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_wisp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,279 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,279 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist6_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,280 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor_entries_exemptip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,280 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_aspathlist_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,280 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_tacacs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,280 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface_dynamicmapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,281 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community_hosts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,281 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_peergrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,281 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bonjourprofile_policylist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,281 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_syslogd_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,281 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_ec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/modules 2023-04-28 05:57:46,282 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/httpapi 2023-04-28 05:57:46,282 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/httpapi/fortimanager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/httpapi 2023-04-28 05:57:46,282 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:46,282 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:46,283 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:46,283 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils/napi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:46,283 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils/fortimanager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:46,283 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/plugins/module_utils/exported_schema.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/plugins/module_utils 2023-04-28 05:57:46,295 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:46,296 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:46,297 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/meta 2023-04-28 05:57:46,297 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/meta 2023-04-28 05:57:46,297 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:46,297 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:46,298 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:46,298 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager/changelogs 2023-04-28 05:57:46,298 root INFO copying build/lib/ansible_collections/fortinet/fortimanager/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortimanager 2023-04-28 05:57:46,299 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios 2023-04-28 05:57:46,299 root INFO copying build/lib/ansible_collections/fortinet/fortios/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios 2023-04-28 05:57:46,299 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins 2023-04-28 05:57:46,299 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/doc_fragments 2023-04-28 05:57:46,299 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/doc_fragments/fortios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/doc_fragments 2023-04-28 05:57:46,300 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,300 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,301 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_session_ttl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,301 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_saml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,301 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,302 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_dictionary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,302 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_auth_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,302 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dscp_based_priority.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,303 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dos_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,303 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_application_rule_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,303 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,303 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dpdk_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,304 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,305 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ftgd_local_rating.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,305 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_fp_sensitivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,305 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_radius.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,306 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_decoder.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,306 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_virtual_port_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,306 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_tunnel_limit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,306 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_consolidated_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,307 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,307 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_security_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,307 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_custom_language.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,308 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,308 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_carrier_endpoint_bwl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,308 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sdwan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,309 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_wildcard_fqdn_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,309 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,309 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,309 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_pppoe_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,310 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_manualkey_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,310 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy46.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,310 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting2_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,310 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,311 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mobile_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,311 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_device_detection_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,311 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_scheme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,311 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mac_address_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,312 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_nat64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,312 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_alertmail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,312 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_ec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,312 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_local_in_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,313 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_category.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,313 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_dataplan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,313 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,313 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortimanager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,314 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_forticlient_registration_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,314 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortindr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,314 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_exception.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,314 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_password_policy_guest_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,315 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_traffic_class.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,315 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipmacbinding_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,315 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_mms_checksum.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,315 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_traffic_quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,315 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,316 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_extender.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,316 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_alertemail_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,317 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_data_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,317 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,317 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_local_in_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,318 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_nd_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,318 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_ip_dscp_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,318 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,319 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,319 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_registered_forticlient.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,319 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_name.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,319 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,320 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_profile_protocol_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,320 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_email_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,321 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_spam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,321 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_iptrust.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,321 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dnstranslation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,322 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_bword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,322 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_server_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,322 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_disk_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,323 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_quarantine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,323 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ble_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,323 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_acme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,323 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_report_chart.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,324 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_reputation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,324 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,325 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,325 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,325 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,326 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_federated_upgrade.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,326 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_netflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,327 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_property.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,327 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_mms_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,327 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_domain_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,328 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_ca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,328 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,328 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,328 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_export_config_playbook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,329 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_alarm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,329 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,329 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_owner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,329 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_sensor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,330 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_debug_url.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,330 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_object_tagging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,330 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apn_shaper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,331 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_json_generic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,331 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_nic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,331 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,331 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_nac_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,332 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wids_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,332 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_local_access.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,332 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_link_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,333 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_sensitivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,333 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_ftp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,333 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_dnsbl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,333 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,333 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipv6_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,334 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,334 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,334 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_dynamic_port_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,335 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,335 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_webtrends_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,336 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_3gpp_cellular.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,336 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_address6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,336 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_rat_timeout_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,336 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dnsfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,337 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_speed_test_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,337 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaping_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,337 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_802_1x.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,338 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_access_control_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,338 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,338 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_sctp_filter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,338 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_webcache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,339 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_sse_stats.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,339 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_filepattern.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,339 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,340 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_peergrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,340 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,340 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_report_layout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,341 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,341 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_access_list6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,342 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,343 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,343 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_access_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,343 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_prefix_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,343 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaper_traffic_shaper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,344 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sit_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,344 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_lldp_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,344 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_gre_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,345 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_report_style.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,345 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,345 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_wan_link.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,345 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_sysinfo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,346 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,346 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_dataplan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,347 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_standalone_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,347 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,347 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_fortishield.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,347 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_disk_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,348 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_automation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,348 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_monitoring_npu_hpe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,348 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ttl_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,348 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_sld.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,349 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_nsxt_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,349 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,349 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_ca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,349 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,350 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,350 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_cifs_domain_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,350 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_session_stats.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,350 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,352 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,354 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting2_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,354 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_npu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,355 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geneve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,355 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_block_allow_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,355 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_onetime.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,356 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_realm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,356 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,356 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,357 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,357 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_proxy_arp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,357 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,357 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,358 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sms_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,358 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_password_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,358 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_performance_top.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,358 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_access_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,359 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_dnsbl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,359 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_syslog_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,359 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fips_cc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,359 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_interface_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,359 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,360 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_auto_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,360 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_l2tp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,360 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,360 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,361 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_mheader.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,361 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_central_management.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,361 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dhcp6_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,362 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,362 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,363 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,363 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipv6_eh_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,363 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_smc_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,363 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ftp_proxy_explicit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,364 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,364 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ippool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,364 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_rf_analysis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,364 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_tacacsplus.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,365 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bfd6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,365 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_push_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,365 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_np6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,366 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,366 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortiguard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,366 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortisandbox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,367 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy_ssh_client_cert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,367 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_network_visibility.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,367 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_affinity_packet_redistribution.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,367 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_venue_name.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,368 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,368 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_cache_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,368 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_profile_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,368 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_main_class.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,368 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vendor_mac.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,369 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_utm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,369 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,369 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,369 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_nac_quar.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,370 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_stitch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,370 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bfd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,370 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip46.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,370 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_modem_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,371 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_interface_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,371 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_forward_server_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,371 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_affinity_interrupt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,371 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_fctems.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,372 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_nac_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,372 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,372 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_nac_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,372 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_content_delivery_network_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,373 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_addrgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,373 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_search_engine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,373 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ptp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,374 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,374 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,374 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wag_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,374 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_auto_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,375 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sso_forticloud_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,375 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_forticlient_ems.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,375 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_traffic_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,375 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,376 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_voip_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,376 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,377 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_mib_view.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,377 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_bwl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,377 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_password_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,378 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_stp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,378 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_eventfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,378 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,379 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,379 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm7.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,380 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,380 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,380 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_initial_config_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,380 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,381 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_bonjour_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,381 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,381 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_conn_capability.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,381 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,382 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_cache_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,382 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,382 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,383 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,383 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_interface_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,383 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,384 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_manualkey.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,384 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,384 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_inter_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,384 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_custom_field.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,385 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_setting6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,385 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_console.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,385 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_key_chain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,385 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_fortigate_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,386 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ippool6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,386 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_ptp_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,386 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_gtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,387 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy64.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,387 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_management_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,387 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_venue_url.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,388 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_tos_based_priority.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,388 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_flow_tracking.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,388 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_fp_doc_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,388 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,389 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,389 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_terms_and_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,389 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,390 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ripng.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,390 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,390 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_gui_display.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,390 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_definition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,391 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,391 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_nac_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,391 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_host_check_software.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,392 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,392 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_null_device_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,392 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_override.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,392 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_3g_modem_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,393 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,393 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,393 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geoip_override.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,393 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_advice_of_charge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,394 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,394 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_traffic_sniffer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,394 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_destination.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,394 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_automation_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,395 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geoip_country.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,395 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_fortishield.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,395 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,395 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_dce.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,396 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_remote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,396 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_report_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,396 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_mac_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,396 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_rule_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,397 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dedicated_mgmt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,397 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_wire_pair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,397 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_sniffer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,397 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_lte_carrier_by_mcc_mnc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,398 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,398 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,398 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,399 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_operator_name.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,399 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ospf6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,399 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,400 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_port_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,400 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,400 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_webproxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,400 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_application_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,400 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_ie_white_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,401 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_netflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,401 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,401 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_isf_queue_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,401 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fsso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,402 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,402 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,402 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,403 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_tunneling.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,403 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_central_snat_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,403 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_bwl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,403 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_remote.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,404 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,404 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_prefix_list6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,404 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,404 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,405 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,406 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_lldp_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,406 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_view_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,407 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fsso_polling.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,407 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,407 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaping_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,407 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,408 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_speed_test_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,408 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vne_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,408 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,409 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,409 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_wccp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,409 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_qos_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,409 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_hs_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,410 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_local_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,410 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_timers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,410 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_nai_realm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,411 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_sflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,411 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,411 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_external_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,412 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,412 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_application_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,412 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ldb_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,413 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_credential_store_domain_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,413 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,413 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ssh_filter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,413 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,414 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,414 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_fortiguard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,414 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_addition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,414 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips_urlfilter_dns6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,415 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_urlfilter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,415 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_ocsp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,415 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,415 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_icon.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,416 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,416 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,417 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,417 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_cifs_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,417 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_community_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,417 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_content.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,418 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_vlan_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,418 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaper_per_ip_shaper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,418 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_trap_threshold.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,418 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase2_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,419 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_city.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,419 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,419 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_extender_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,419 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_youtube_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,420 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,420 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_pop3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,420 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,420 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,421 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,421 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,421 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_message_filter_v0v1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,422 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,422 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,422 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_wildcard_fqdn_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,422 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_url_match.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,423 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_forward_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,423 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,423 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_route_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,423 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_country.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,424 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_user_bookmark.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,424 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ike.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,425 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dnsfilter_domain_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,425 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address6_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,425 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_utm_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,425 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,426 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_sysinfo.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,426 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_append.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,426 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_report_dataset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,426 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,427 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_bword.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,427 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_fortilink_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,427 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_sslvpn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,427 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,428 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_addrgrp6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,428 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_monitoring_np6_ipsec_engine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,428 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,428 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_ipbl_vendor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,429 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_iptrust.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,429 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipv6_neighbor_cache.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,429 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_lte_modem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,429 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy_virtual_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,429 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_icap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,430 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,431 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_extender_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,431 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,432 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_alias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,432 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_sflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,432 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_captive_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,432 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,433 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_category.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,433 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_host_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,433 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipmacbinding_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,434 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ha.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,434 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_content_header.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,434 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,435 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,435 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apngrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,435 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,435 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vxlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,436 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,436 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,436 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_configuration_fact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,437 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,437 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_fec.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,437 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_sub_class.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,437 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast_flow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,438 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_api_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,438 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_file_filter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,438 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_youtube_channel_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,438 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,439 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,439 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_igmp_snooping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,439 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_addrgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,439 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,440 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_sys_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,440 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting3_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,440 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,440 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,440 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,441 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,441 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_stp_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,441 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_ptp_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,442 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,443 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_osu_provider_nai.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,443 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,444 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_pptp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,444 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_quarantine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,444 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,445 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_auth_path.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,445 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_decrypted_traffic_mirror.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,445 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_pfcp_message_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,445 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,446 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,446 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,446 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ip_translation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,446 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_lte_carrier_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,447 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,447 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_accprofile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,448 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_iprope_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,448 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ha_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,448 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,448 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,449 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_ie_allow_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,449 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,449 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,449 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_mac_sync_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,449 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_storm_control.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,450 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_lldp_network_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,450 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,451 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_physical_switch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,451 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,451 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_crl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,451 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_message_filter_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,452 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_adgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,452 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipip_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,452 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_arp_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,452 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_extender.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,453 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,453 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_explicit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,453 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dos_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,454 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipsec_aggregate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,454 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_queue_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,454 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,454 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_custom_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,455 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,455 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_auth_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,455 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_addrgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,455 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,456 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_dot1p_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,456 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_http.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,456 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,456 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_apcfg_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,457 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,457 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_monitor_fact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,457 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_network_auth_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,458 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_gi_gk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,458 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ftm_push.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,458 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_user_group_bookmark.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,458 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,459 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_isis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,459 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_wan_metric.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,459 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fortitoken.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,460 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,460 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ocvpn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,460 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp46.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,461 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,461 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_mheader.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,461 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_threat_weight.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,462 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ssid_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,462 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_rip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,462 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ike_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,463 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_initial_config_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,463 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_concentrator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,463 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,464 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,465 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ddns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,465 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_acl6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,465 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_override_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,466 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_roaming_consortium.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,466 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_webtrends_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,466 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_custom_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,467 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,467 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,467 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_storm_control_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,468 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_link.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,468 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_resource_limits.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,468 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,468 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_qos_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,469 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortiai.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,469 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,469 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_security_exempt_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,469 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ap_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,470 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,470 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ftgd_local_cat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,470 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_spectral_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,470 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_report_theme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,471 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_global_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,471 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_pfcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,471 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sso_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,471 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_heuristic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,472 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_session_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,472 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,472 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_fortiguard_wf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,472 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_network_monitor_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,473 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,473 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_qos_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,473 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dpdk_cpus.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,473 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_custom.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,474 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_network_service_dynamic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,474 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_probe_response.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,474 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting3_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,474 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,475 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_remote_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,475 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_krb_keytab.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,475 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_mpsk_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,475 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,476 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_signature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,476 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_modem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,476 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm1.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,476 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,477 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_exchange.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,477 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,477 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_ipbl_reason.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,478 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips_urlfilter_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,478 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,479 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_nntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,479 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,479 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_saml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,480 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_nsxt_service_chain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,480 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase1_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,481 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,481 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_forticlient.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,481 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_csf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,482 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_trigger.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,482 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_extension.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,482 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_sensor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,483 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_recurring.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,483 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_aspath_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,483 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_remote_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,484 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_arrp_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,484 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,484 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_switch_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,484 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_local_ca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,485 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,485 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sdn_connector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,485 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_override_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,486 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_client_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,486 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_osu_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,486 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_switch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,486 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,487 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_802_1x_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,487 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_wisp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,487 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_notification.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,487 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_ssh_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,488 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_crl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,488 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_application_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,489 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_botnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,489 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,489 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fsso_polling.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,490 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mem_mgr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,490 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_application_name.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,490 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_identity_based_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,490 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_log_null_device_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,491 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_policy6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,491 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,491 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_cluster_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,491 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_extender_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,492 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dhcp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,492 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_quarantine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,493 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_fortigate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,493 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_stp_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,493 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_managed_switch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,494 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_poe.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,494 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_ip_address_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/modules 2023-04-28 05:57:46,495 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/httpapi 2023-04-28 05:57:46,495 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/httpapi/fortios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/httpapi 2023-04-28 05:57:46,495 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils 2023-04-28 05:57:46,495 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:46,496 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:46,496 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:46,496 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/fortimanager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager 2023-04-28 05:57:46,496 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:46,496 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts 2023-04-28 05:57:46,497 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts 2023-04-28 05:57:46,497 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts 2023-04-28 05:57:46,497 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system 2023-04-28 05:57:46,497 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system 2023-04-28 05:57:46,497 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system 2023-04-28 05:57:46,498 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/data_post_processor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:46,498 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/secret_field.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:46,498 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:46,498 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/comparison.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:46,499 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec 2023-04-28 05:57:46,499 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts 2023-04-28 05:57:46,499 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts 2023-04-28 05:57:46,499 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts 2023-04-28 05:57:46,499 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec 2023-04-28 05:57:46,500 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system 2023-04-28 05:57:46,500 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system 2023-04-28 05:57:46,500 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system 2023-04-28 05:57:46,500 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/fortios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/fortios 2023-04-28 05:57:46,501 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/common 2023-04-28 05:57:46,501 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/common/type_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/common 2023-04-28 05:57:46,501 root INFO copying build/lib/ansible_collections/fortinet/fortios/plugins/module_utils/common/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/plugins/module_utils/common 2023-04-28 05:57:46,501 root INFO copying build/lib/ansible_collections/fortinet/fortios/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios 2023-04-28 05:57:46,501 root INFO copying build/lib/ansible_collections/fortinet/fortios/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios 2023-04-28 05:57:46,502 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/meta 2023-04-28 05:57:46,502 root INFO copying build/lib/ansible_collections/fortinet/fortios/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/meta 2023-04-28 05:57:46,502 root INFO copying build/lib/ansible_collections/fortinet/fortios/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios 2023-04-28 05:57:46,503 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:46,503 root INFO copying build/lib/ansible_collections/fortinet/fortios/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:46,503 root INFO copying build/lib/ansible_collections/fortinet/fortios/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:46,503 root INFO copying build/lib/ansible_collections/fortinet/fortios/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/changelogs 2023-04-28 05:57:46,503 root INFO copying build/lib/ansible_collections/fortinet/fortios/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios 2023-04-28 05:57:46,504 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,504 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_system_global.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,504 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_system_zone.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,504 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_system_ha_monitor.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,505 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_firewall_address_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,505 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_system_ntp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,505 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_firewall_address.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,505 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_system_alias.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,505 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples/httpapi 2023-04-28 05:57:46,506 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/httpapi/set_system_global.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples/httpapi 2023-04-28 05:57:46,506 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples/httpapi/inventory 2023-04-28 05:57:46,506 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/httpapi/inventory/hosts -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples/httpapi/inventory 2023-04-28 05:57:46,506 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/httpapi/readme -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples/httpapi 2023-04-28 05:57:46,506 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_firewall_vip.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,507 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_system_dns.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,507 root INFO copying build/lib/ansible_collections/fortinet/fortios/examples/set_system_ha.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/fortinet/fortios/examples 2023-04-28 05:57:46,507 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur 2023-04-28 05:57:46,507 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,507 root INFO copying build/lib/ansible_collections/inspur/sm/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,508 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins 2023-04-28 05:57:46,508 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/doc_fragments 2023-04-28 05:57:46,508 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/doc_fragments/ism.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/doc_fragments 2023-04-28 05:57:46,508 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,508 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/pcie_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,509 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/snmp_trap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,509 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/fru_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,509 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/user_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,509 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/add_ad_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,509 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/boot_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,510 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/power_consumption_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,510 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_snmp_trap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,510 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/bios_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,510 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/clear_audit_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,510 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/del_ldap_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,511 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_auto_capture.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,511 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/media_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,511 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_alert_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,511 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/sensor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,511 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/add_ldisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,512 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_pass_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,512 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/clear_system_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,512 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/event_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,512 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/update_cpld.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,512 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_smtp_com.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,513 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_event_log_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,513 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/fw_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,513 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,513 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/bmc_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,513 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ncsi_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,514 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,514 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/smtp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,514 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/power_restore_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,514 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/boot_option_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,514 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,515 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/psu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,515 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/del_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,515 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/event_log_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,515 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/gpu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,515 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,515 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_boot_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,516 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,516 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,516 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/snmp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,516 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_power_restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,516 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_restore_factory_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,517 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/download_manual_screenshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,517 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,517 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/del_ad_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,517 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/mem_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,517 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_pdisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,518 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_manual_capture.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,518 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_kvm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,518 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,518 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/psu_peak_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,518 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_boot_option.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,519 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/adapter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,519 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/network_link_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,519 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/reset_bmc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,519 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ldap_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,519 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/raid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,520 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_media_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,520 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,520 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_network_bond.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,520 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/session_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,520 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,521 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_uid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,521 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/psu_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,521 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ldap_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,521 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_power_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,521 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/audit_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,522 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,522 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/uid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,522 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/threshold_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,522 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ad_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,522 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/reset_kvm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,523 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,523 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ad_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,523 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/update_fw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,523 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/volt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,523 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,524 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/bios_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,524 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/network_bond_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,524 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,524 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/del_user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,524 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ldap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,525 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/add_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,525 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_network_link.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,525 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/kvm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,525 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/connect_media_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,525 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_log_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,526 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_preserve_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,526 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/bios_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,526 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ad_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,526 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ipv4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,526 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/auto_capture_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,527 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/collect_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,527 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/hard_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,527 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/add_ldap_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,527 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_psu_peak.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,527 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/backplane_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,528 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/download_auto_screenshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,528 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/collect_blackbox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,528 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,528 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/onboard_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,528 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/pdisk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,529 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/log_setting_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,529 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_bios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,529 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/cpu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,529 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/del_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,529 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/add_user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,530 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ldap_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,530 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_threshold.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,530 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ad_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,530 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,530 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ntp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,531 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,531 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_smtp_dest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,531 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/alert_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,531 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_fan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,531 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/dns_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,532 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_power_budget.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,532 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_virtual_media.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,532 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,532 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/virtual_media_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,532 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/clear_event_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,533 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/temp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,533 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/power_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,533 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_psu_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,533 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,533 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_connect_media.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,534 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/self_test_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,534 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/fan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,534 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/preserve_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,534 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ad.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,534 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_fru.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,535 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ldisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,535 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_priv_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,535 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/system_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,535 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/ldisk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,535 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/edit_ncsi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,536 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/modules/power_budget_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/modules 2023-04-28 05:57:46,536 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/module_utils 2023-04-28 05:57:46,536 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/module_utils 2023-04-28 05:57:46,536 root INFO copying build/lib/ansible_collections/inspur/sm/plugins/module_utils/ism.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/plugins/module_utils 2023-04-28 05:57:46,536 root INFO copying build/lib/ansible_collections/inspur/sm/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,537 root INFO copying build/lib/ansible_collections/inspur/sm/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,537 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/meta 2023-04-28 05:57:46,537 root INFO copying build/lib/ansible_collections/inspur/sm/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/meta 2023-04-28 05:57:46,537 root INFO copying build/lib/ansible_collections/inspur/sm/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,538 root INFO copying build/lib/ansible_collections/inspur/sm/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,538 root INFO copying build/lib/ansible_collections/inspur/sm/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,538 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks 2023-04-28 05:57:46,538 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,538 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_user_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,539 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_priv_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,539 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-network_link_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,539 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-boot_image_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,539 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-raid_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,539 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-add_ldisk.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,540 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-del_session.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,540 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-temp_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,540 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-connect_media_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,540 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-system_log_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,540 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,541 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ldap_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,541 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-user_group_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,541 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_boot_option.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,541 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-restore.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,541 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-sensor_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,541 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-pdisk_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,542 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_manual_capture.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,542 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_pdisk.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,542 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_virtual_media.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,542 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ldisk_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,542 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-smtp_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,543 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_connect_media.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,543 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ipv6.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,543 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-add_ad_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,543 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-update_cpld.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,543 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_bios.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,544 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_network_link.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,544 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-collect_log.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,544 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-download_auto_screenshot.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,544 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-audit_log_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,544 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-event_log_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,545 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_kvm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,545 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-dns_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,545 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-fru_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,545 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ncsi_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,545 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-fw_verison_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,546 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ad_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,546 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-add_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,546 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-gpu_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,546 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-clear_system_log.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,546 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-alert_policy_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,547 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-network_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,547 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-service_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,547 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_fru.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,547 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-boot_option_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,547 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp_com.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,548 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_threshold.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,548 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-power_restore_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,548 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-reset_bmc.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,548 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldisk.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,548 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_status.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,548 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-kvm_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,549 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-pcie_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,549 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-del_ldap_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,549 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-collect_blackbox.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,549 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_service.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,549 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ntp_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,550 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_psu_peak.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,550 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-del_ad_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,550 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:46,550 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/overall/examples-user_overall.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:46,550 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/overall/examples-ad_overall.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:46,551 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/overall/examples-ldap_overall.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:46,551 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/overall/examples-system_info_overall.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules/overall 2023-04-28 05:57:46,551 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-bios_import.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,551 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ipv4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,551 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp_dest.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,552 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-log_setting_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,552 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-volt_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,552 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_dns.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,552 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ntp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,552 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_restore.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,553 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,553 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-user_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,553 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_pass_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,553 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_log_setting.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,553 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-bios_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,554 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-adapter_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,554 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-snmp_trap_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,554 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-reset_kvm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,554 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_network.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,554 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ad_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,555 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-clear_audit_log.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,555 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-backup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,555 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_budget.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,555 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-clear_event_log.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,555 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_media_instance.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,556 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldap.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,556 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-add_user_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,556 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-power_consumption_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,556 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ncsi.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,556 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-onboard_disk_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,557 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ad_group_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,557 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-del_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,557 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-del_user_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,557 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_boot_image.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,557 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-bios_export.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,558 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_alert_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,558 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ad_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,558 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-uid_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,558 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-fan_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,558 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_network_bond.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,559 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_vlan.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,559 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_uid.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,559 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ad.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,559 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-psu_peak_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,559 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-cpu_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,559 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_preserve_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,560 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_auto_capture.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,560 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-download_manual_screenshot.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,560 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-add_ldap_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,560 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ldap_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,561 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_event_log_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,561 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-server_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,561 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-network_bond_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,561 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-user_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,561 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-power_status_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,561 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-session_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,562 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-virtual_media_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,562 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-snmp_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,562 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-psu_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,562 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-event_log_policy_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,563 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-preserver_config_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,563 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-bmc_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,563 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-media_instance_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,563 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldap_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,563 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-auto_capture_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,564 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_psu_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,564 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_restore_factory_default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,564 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-ldap_group_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,564 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_snmp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,564 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_snmp_trap.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,565 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-update_fw.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,565 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-mem_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,565 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-power_budget_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,565 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-self_test_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,565 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-edit_fan.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,566 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-hard_disk_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,566 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-backplane_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,566 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-psu_config_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,566 root INFO copying build/lib/ansible_collections/inspur/sm/playbooks/modules/examples-threshold_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/playbooks/modules 2023-04-28 05:57:46,566 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:46,567 root INFO copying build/lib/ansible_collections/inspur/sm/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:46,567 root INFO copying build/lib/ansible_collections/inspur/sm/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:46,567 root INFO copying build/lib/ansible_collections/inspur/sm/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm/changelogs 2023-04-28 05:57:46,567 root INFO copying build/lib/ansible_collections/inspur/sm/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,567 root INFO copying build/lib/ansible_collections/inspur/sm/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,568 root INFO copying build/lib/ansible_collections/inspur/sm/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/sm 2023-04-28 05:57:46,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,568 root INFO copying build/lib/ansible_collections/inspur/ispim/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins 2023-04-28 05:57:46,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/doc_fragments 2023-04-28 05:57:46,568 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/doc_fragments/ism.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/doc_fragments 2023-04-28 05:57:46,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,569 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/pcie_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,569 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/snmp_trap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,569 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/fru_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,570 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/user_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,570 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/boot_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,570 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/power_consumption_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,570 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_snmp_trap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,570 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/bios_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,571 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_m6_log_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,571 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/clear_audit_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,571 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_auto_capture.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,571 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/media_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,571 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_alert_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,571 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/sensor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,572 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/add_ldisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,572 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/clear_system_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,572 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/event_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,572 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/update_cpld.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,572 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_smtp_com.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,573 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_event_log_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,573 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/fw_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,573 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,573 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/bmc_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,574 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ncsi_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,574 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,574 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/smtp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,574 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/power_restore_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,574 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/boot_option_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,574 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,575 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/psu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,575 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/del_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,575 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/event_log_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,575 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/gpu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,575 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,576 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_boot_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,576 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_ipv6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,576 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/snmp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,576 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_power_restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,576 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_restore_factory_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,577 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/download_manual_screenshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,577 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,577 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/mem_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,577 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_pdisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,577 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_manual_capture.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,578 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_kvm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,578 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,578 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/psu_peak_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,578 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_boot_option.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,578 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/adapter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,579 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/network_link_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,579 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/reset_bmc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,579 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ldap_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,579 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/raid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,579 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_media_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,580 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,580 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_network_bond.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,580 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/session_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,580 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,580 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_uid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,581 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/psu_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,581 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ldap_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,581 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_power_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,581 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/audit_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,581 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,582 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/uid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,582 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/threshold_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,582 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ad_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,582 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/reset_kvm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,582 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,583 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ad_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,583 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/update_fw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,583 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/volt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,583 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,583 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/bios_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,584 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/support_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,584 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/network_bond_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,584 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,584 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ldap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,584 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_network_link.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,585 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/kvm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,585 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/connect_media_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,585 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_log_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,585 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_preserve_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,585 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/bios_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,586 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ad_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,586 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_ipv4.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,586 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/auto_capture_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,586 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/collect_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,586 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/hard_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,587 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_psu_peak.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,587 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/backplane_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,587 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/download_auto_screenshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,587 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/collect_blackbox.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,587 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,588 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/onboard_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,588 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/pdisk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,588 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/log_setting_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,588 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_bios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,588 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/cpu_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,589 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_threshold.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,589 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,589 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ntp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,589 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,589 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_smtp_dest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,590 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/alert_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,590 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_fan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,590 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/dns_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,590 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_power_budget.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,590 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_virtual_media.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,591 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,591 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/virtual_media_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,591 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/clear_event_log.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,591 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/temp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,591 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/power_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,592 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_psu_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,592 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,592 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_connect_media.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,592 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/self_test_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,592 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/fan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,593 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/preserve_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,593 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_ad.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,593 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_fru.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,593 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_ldisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,593 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/system_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,594 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/ldisk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,594 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/edit_ncsi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,594 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/modules/power_budget_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/modules 2023-04-28 05:57:46,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/module_utils 2023-04-28 05:57:46,594 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/module_utils 2023-04-28 05:57:46,595 root INFO copying build/lib/ansible_collections/inspur/ispim/plugins/module_utils/ism.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/plugins/module_utils 2023-04-28 05:57:46,595 root INFO copying build/lib/ansible_collections/inspur/ispim/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,595 root INFO copying build/lib/ansible_collections/inspur/ispim/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,595 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/meta 2023-04-28 05:57:46,595 root INFO copying build/lib/ansible_collections/inspur/ispim/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/meta 2023-04-28 05:57:46,596 root INFO copying build/lib/ansible_collections/inspur/ispim/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,596 root INFO copying build/lib/ansible_collections/inspur/ispim/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,596 root INFO copying build/lib/ansible_collections/inspur/ispim/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,596 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:46,596 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/changelogs/fragments 2023-04-28 05:57:46,597 root INFO copying build/lib/ansible_collections/inspur/ispim/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/changelogs/fragments 2023-04-28 05:57:46,597 root INFO copying build/lib/ansible_collections/inspur/ispim/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:46,597 root INFO copying build/lib/ansible_collections/inspur/ispim/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:46,597 root INFO copying build/lib/ansible_collections/inspur/ispim/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim/changelogs 2023-04-28 05:57:46,597 root INFO copying build/lib/ansible_collections/inspur/ispim/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,598 root INFO copying build/lib/ansible_collections/inspur/ispim/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/inspur/ispim 2023-04-28 05:57:46,598 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk 2023-04-28 05:57:46,598 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,598 root INFO copying build/lib/ansible_collections/splunk/es/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,598 root INFO copying build/lib/ansible_collections/splunk/es/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,599 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins 2023-04-28 05:57:46,599 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,599 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/correlation_search_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,599 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/data_input_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,599 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_data_inputs_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,600 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_correlation_search_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,600 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_data_input_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,600 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_data_input_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,600 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/correlation_search.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,600 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_adaptive_response_notable_event.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,601 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_correlation_search.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,601 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_data_inputs_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,601 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_adaptive_response_notable_events.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,601 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/adaptive_response_notable_event.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,601 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/data_input_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,602 root INFO copying build/lib/ansible_collections/splunk/es/plugins/modules/splunk_correlation_searches.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/modules 2023-04-28 05:57:46,602 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:46,602 root INFO copying build/lib/ansible_collections/splunk/es/plugins/action/splunk_data_inputs_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:46,602 root INFO copying build/lib/ansible_collections/splunk/es/plugins/action/splunk_data_inputs_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:46,602 root INFO copying build/lib/ansible_collections/splunk/es/plugins/action/splunk_adaptive_response_notable_events.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:46,603 root INFO copying build/lib/ansible_collections/splunk/es/plugins/action/splunk_correlation_searches.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/action 2023-04-28 05:57:46,603 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/httpapi 2023-04-28 05:57:46,603 root INFO copying build/lib/ansible_collections/splunk/es/plugins/httpapi/splunk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/httpapi 2023-04-28 05:57:46,603 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/module_utils 2023-04-28 05:57:46,603 root INFO copying build/lib/ansible_collections/splunk/es/plugins/module_utils/splunk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/plugins/module_utils 2023-04-28 05:57:46,604 root INFO copying build/lib/ansible_collections/splunk/es/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,604 root INFO copying build/lib/ansible_collections/splunk/es/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,604 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/meta 2023-04-28 05:57:46,604 root INFO copying build/lib/ansible_collections/splunk/es/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/meta 2023-04-28 05:57:46,604 root INFO copying build/lib/ansible_collections/splunk/es/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,605 root INFO copying build/lib/ansible_collections/splunk/es/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,605 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/changelogs 2023-04-28 05:57:46,605 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/changelogs/fragments 2023-04-28 05:57:46,605 root INFO copying build/lib/ansible_collections/splunk/es/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/changelogs/fragments 2023-04-28 05:57:46,605 root INFO copying build/lib/ansible_collections/splunk/es/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/changelogs 2023-04-28 05:57:46,606 root INFO copying build/lib/ansible_collections/splunk/es/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es/changelogs 2023-04-28 05:57:46,606 root INFO copying build/lib/ansible_collections/splunk/es/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,606 root INFO copying build/lib/ansible_collections/splunk/es/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,606 root INFO copying build/lib/ansible_collections/splunk/es/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,606 root INFO copying build/lib/ansible_collections/splunk/es/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/splunk/es 2023-04-28 05:57:46,607 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch 2023-04-28 05:57:46,607 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,607 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,607 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,607 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/plugins 2023-04-28 05:57:46,608 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:46,608 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_db.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:46,608 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_bridge.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:46,608 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:46,608 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:46,608 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_bond.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/plugins/modules 2023-04-28 05:57:46,609 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,609 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,609 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/meta 2023-04-28 05:57:46,609 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/meta 2023-04-28 05:57:46,609 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,610 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:46,610 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:46,610 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:46,610 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch/changelogs 2023-04-28 05:57:46,611 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,611 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,611 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,611 root INFO copying build/lib/ansible_collections/openvswitch/openvswitch/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/openvswitch/openvswitch 2023-04-28 05:57:46,611 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark 2023-04-28 05:57:46,612 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,612 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/plugins 2023-04-28 05:57:46,612 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/plugins/lookup 2023-04-28 05:57:46,612 root INFO copying build/lib/ansible_collections/cyberark/conjur/plugins/lookup/conjur_variable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/plugins/lookup 2023-04-28 05:57:46,612 root INFO copying build/lib/ansible_collections/cyberark/conjur/secrets.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,612 root INFO copying build/lib/ansible_collections/cyberark/conjur/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,613 root INFO copying build/lib/ansible_collections/cyberark/conjur/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,613 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/meta 2023-04-28 05:57:46,613 root INFO copying build/lib/ansible_collections/cyberark/conjur/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/meta 2023-04-28 05:57:46,613 root INFO copying build/lib/ansible_collections/cyberark/conjur/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,613 root INFO copying build/lib/ansible_collections/cyberark/conjur/CHANGELOG.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,614 root INFO copying build/lib/ansible_collections/cyberark/conjur/SECURITY.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,614 root INFO copying build/lib/ansible_collections/cyberark/conjur/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,614 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:46,614 root INFO copying build/lib/ansible_collections/cyberark/conjur/ci/build_release -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:46,614 root INFO copying build/lib/ansible_collections/cyberark/conjur/ci/parse-changelog.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:46,615 root INFO copying build/lib/ansible_collections/cyberark/conjur/ci/publish_to_galaxy -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:46,615 root INFO copying build/lib/ansible_collections/cyberark/conjur/ci/test.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/ci 2023-04-28 05:57:46,615 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:46,615 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/test_app_centos 2023-04-28 05:57:46,615 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/test_app_centos/Dockerfile -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/test_app_centos 2023-04-28 05:57:46,616 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/test_app_ubuntu 2023-04-28 05:57:46,616 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/test_app_ubuntu/Dockerfile -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/test_app_ubuntu 2023-04-28 05:57:46,616 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/test_unit.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:46,616 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/policy 2023-04-28 05:57:46,616 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/policy/root.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/policy 2023-04-28 05:57:46,616 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/proxy 2023-04-28 05:57:46,617 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/proxy/default.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/proxy 2023-04-28 05:57:46,617 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/proxy/ssl.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/proxy 2023-04-28 05:57:46,617 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks 2023-04-28 05:57:46,617 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:46,617 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:46,618 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-playbook-v2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:46,618 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:46,618 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-v2.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup 2023-04-28 05:57:46,618 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks/conjur-identity-setup 2023-04-28 05:57:46,618 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/playbooks/conjur-identity-setup/conjur_role_playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev/playbooks/conjur-identity-setup 2023-04-28 05:57:46,618 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:46,619 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/docker-compose.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:46,619 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/Dockerfile -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:46,619 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/start.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:46,619 root INFO copying build/lib/ansible_collections/cyberark/conjur/dev/Dockerfile_nginx -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/dev 2023-04-28 05:57:46,619 root INFO copying build/lib/ansible_collections/cyberark/conjur/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,620 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/examples 2023-04-28 05:57:46,620 root INFO copying build/lib/ansible_collections/cyberark/conjur/examples/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/examples 2023-04-28 05:57:46,620 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles 2023-04-28 05:57:46,620 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity 2023-04-28 05:57:46,620 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,621 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/uninstall.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,621 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,621 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/summon-conjur.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,621 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/identity_check.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,621 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/identity.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,622 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/summon.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,622 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks 2023-04-28 05:57:46,622 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/defaults 2023-04-28 05:57:46,622 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/defaults 2023-04-28 05:57:46,622 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity 2023-04-28 05:57:46,623 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,623 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_centos 2023-04-28 05:57:46,623 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_centos/Dockerfile -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_centos 2023-04-28 05:57:46,623 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_ubuntu 2023-04-28 05:57:46,623 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_ubuntu/Dockerfile -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_ubuntu 2023-04-28 05:57:46,623 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,624 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.dockerignore -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,624 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases 2023-04-28 05:57:46,624 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/misconfig-conjur-identity 2023-04-28 05:57:46,624 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/misconfig-conjur-identity/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/misconfig-conjur-identity 2023-04-28 05:57:46,624 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity 2023-04-28 05:57:46,625 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests 2023-04-28 05:57:46,625 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests 2023-04-28 05:57:46,625 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity 2023-04-28 05:57:46,625 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity 2023-04-28 05:57:46,625 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests 2023-04-28 05:57:46,625 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests 2023-04-28 05:57:46,626 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity 2023-04-28 05:57:46,626 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:46,626 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:46,626 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v 2023-04-28 05:57:46,626 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache 2023-04-28 05:57:46,627 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache/stepwise -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache 2023-04-28 05:57:46,627 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache/nodeids -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache 2023-04-28 05:57:46,627 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:46,627 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/CACHEDIR.TAG -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache 2023-04-28 05:57:46,627 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/policy 2023-04-28 05:57:46,628 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/policy/root.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/policy 2023-04-28 05:57:46,628 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy 2023-04-28 05:57:46,628 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy/default.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy 2023-04-28 05:57:46,628 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy/ssl.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy 2023-04-28 05:57:46,628 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,628 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-playbook-v2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,629 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,629 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/docker-compose.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,629 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/Dockerfile -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,630 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,630 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/Dockerfile_nginx -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,630 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-v2.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests 2023-04-28 05:57:46,630 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit 2023-04-28 05:57:46,630 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit/cleanup-conjur-identity -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit 2023-04-28 05:57:46,631 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit/configure-conjur-identity -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit 2023-04-28 05:57:46,631 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates 2023-04-28 05:57:46,631 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates/conjur.identity.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates 2023-04-28 05:57:46,631 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates/conjur.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates 2023-04-28 05:57:46,631 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/meta 2023-04-28 05:57:46,632 root INFO copying build/lib/ansible_collections/cyberark/conjur/roles/conjur_host_identity/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur/roles/conjur_host_identity/meta 2023-04-28 05:57:46,632 root INFO copying build/lib/ansible_collections/cyberark/conjur/Jenkinsfile -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,632 root INFO copying build/lib/ansible_collections/cyberark/conjur/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/conjur 2023-04-28 05:57:46,632 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas 2023-04-28 05:57:46,632 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/custom-cred-types 2023-04-28 05:57:46,633 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:46,633 root INFO copying build/lib/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:46,633 root INFO copying build/lib/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/injector.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:46,633 root INFO copying build/lib/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/input.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi 2023-04-28 05:57:46,633 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/plugins 2023-04-28 05:57:46,633 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:46,634 root INFO copying build/lib/ansible_collections/cyberark/pas/plugins/modules/cyberark_authentication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:46,634 root INFO copying build/lib/ansible_collections/cyberark/pas/plugins/modules/cyberark_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:46,634 root INFO copying build/lib/ansible_collections/cyberark/pas/plugins/modules/cyberark_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:46,634 root INFO copying build/lib/ansible_collections/cyberark/pas/plugins/modules/cyberark_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/plugins/modules 2023-04-28 05:57:46,635 root INFO copying build/lib/ansible_collections/cyberark/pas/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas 2023-04-28 05:57:46,635 root INFO copying build/lib/ansible_collections/cyberark/pas/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas 2023-04-28 05:57:46,635 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/meta 2023-04-28 05:57:46,635 root INFO copying build/lib/ansible_collections/cyberark/pas/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/meta 2023-04-28 05:57:46,635 root INFO copying build/lib/ansible_collections/cyberark/pas/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas 2023-04-28 05:57:46,636 root INFO copying build/lib/ansible_collections/cyberark/pas/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas 2023-04-28 05:57:46,636 root INFO copying build/lib/ansible_collections/cyberark/pas/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas 2023-04-28 05:57:46,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles 2023-04-28 05:57:46,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider 2023-04-28 05:57:46,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:46,636 root INFO copying build/lib/ansible_collections/cyberark/pas/roles/aimprovider/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:46,637 root INFO copying build/lib/ansible_collections/cyberark/pas/roles/aimprovider/tasks/uninstallAIMProvider.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:46,637 root INFO copying build/lib/ansible_collections/cyberark/pas/roles/aimprovider/tasks/installAIMProvider.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider/tasks 2023-04-28 05:57:46,637 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider/defaults 2023-04-28 05:57:46,637 root INFO copying build/lib/ansible_collections/cyberark/pas/roles/aimprovider/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider/defaults 2023-04-28 05:57:46,637 root INFO copying build/lib/ansible_collections/cyberark/pas/roles/aimprovider/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cyberark/pas/roles/aimprovider 2023-04-28 05:57:46,638 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco 2023-04-28 05:57:46,638 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs 2023-04-28 05:57:46,638 root INFO copying build/lib/ansible_collections/cisco/ucs/Development.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs 2023-04-28 05:57:46,638 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins 2023-04-28 05:57:46,638 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins 2023-04-28 05:57:46,639 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/doc_fragments 2023-04-28 05:57:46,639 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/doc_fragments/ucs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/doc_fragments 2023-04-28 05:57:46,639 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,639 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_managed_objects.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,639 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,639 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_uuid_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,640 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_vnic_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,640 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_disk_group_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,640 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_timezone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,640 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_lan_connectivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,640 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_graphics_card_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,641 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_scrub_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,641 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_mac_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,641 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_dns_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,641 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_association.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,642 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_serial_over_lan_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,642 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_system_qos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,642 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_vlan_find.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,642 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_vlan_to_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,642 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,642 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_server_maintenance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,643 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_wwn_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,643 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_vsans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,643 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_from_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,643 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_san_connectivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,644 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_sp_vnic_order.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,644 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,644 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_storage_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,644 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_org.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,644 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_vhba_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,645 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_ip_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,645 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/modules/ucs_ntp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/modules 2023-04-28 05:57:46,645 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/module_utils 2023-04-28 05:57:46,645 root INFO copying build/lib/ansible_collections/cisco/ucs/plugins/module_utils/ucs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/plugins/module_utils 2023-04-28 05:57:46,645 root INFO copying build/lib/ansible_collections/cisco/ucs/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs 2023-04-28 05:57:46,646 root INFO copying build/lib/ansible_collections/cisco/ucs/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs 2023-04-28 05:57:46,646 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/meta 2023-04-28 05:57:46,646 root INFO copying build/lib/ansible_collections/cisco/ucs/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/meta 2023-04-28 05:57:46,646 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,646 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_timezone.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,647 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_vlan_find.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,647 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_service_profile_association.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,647 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_vnic_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,647 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_ip_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,647 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_wwn_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,648 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_lan_connectivity.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,648 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/sandbox_inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,648 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/example_playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,648 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_service_profile_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,648 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_mac_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,649 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,649 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_uuid_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,649 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_query.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,649 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_managed_objects.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,649 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_scrub_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,650 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_service_profile_from_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,650 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_storage_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,650 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_sp_vnic_order.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,650 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_system_qos.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,650 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_vlan_to_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,650 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_disk_group_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,651 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_san_connectivity.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,651 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_vhba_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,651 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_ntp_server.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,651 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_graphics_card_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,652 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/server_deploy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,652 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_dns_server.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,652 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/fw_download_config_hfp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,652 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_vlans.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,652 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_serial_over_lan_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,653 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_server_maintenance.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,653 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_org.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,653 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles 2023-04-28 05:57:46,653 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers 2023-04-28 05:57:46,653 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates 2023-04-28 05:57:46,653 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates/tasks 2023-04-28 05:57:46,654 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates/tasks 2023-04-28 05:57:46,654 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/defaults 2023-04-28 05:57:46,654 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/defaults/tasks 2023-04-28 05:57:46,654 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/defaults/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/defaults/tasks 2023-04-28 05:57:46,654 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles 2023-04-28 05:57:46,655 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles/tasks 2023-04-28 05:57:46,655 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles/tasks 2023-04-28 05:57:46,655 root INFO copying build/lib/ansible_collections/cisco/ucs/playbooks/ucs_vsans.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/playbooks 2023-04-28 05:57:46,655 root INFO copying build/lib/ansible_collections/cisco/ucs/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs 2023-04-28 05:57:46,655 root INFO copying build/lib/ansible_collections/cisco/ucs/LICENSE.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs 2023-04-28 05:57:46,656 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/misc 2023-04-28 05:57:46,656 root INFO copying build/lib/ansible_collections/cisco/ucs/misc/Impact DNW07 UCS Ansible Collection Lab Guide.pdf -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/misc 2023-04-28 05:57:46,657 root INFO copying build/lib/ansible_collections/cisco/ucs/misc/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs/misc 2023-04-28 05:57:46,657 root INFO copying build/lib/ansible_collections/cisco/ucs/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ucs 2023-04-28 05:57:46,657 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci 2023-04-28 05:57:46,657 root INFO copying build/lib/ansible_collections/cisco/aci/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci 2023-04-28 05:57:46,657 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins 2023-04-28 05:57:46,658 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:46,658 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/doc_fragments/aci.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:46,658 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:46,658 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/doc_fragments/annotation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:46,658 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/doc_fragments/owner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/doc_fragments 2023-04-28 05:57:46,659 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,659 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_blacklist.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,659 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_epg_to_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,659 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_contract_subject_to_service_graph.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,659 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vzany_to_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,660 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_bulk_static_binding_to_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,660 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_rest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,660 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_snmp_client_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,660 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,660 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_interface_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,661 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_maintenance_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,661 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,661 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_switch_policy_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,661 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_dns_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,661 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,662 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l2out_extepg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,662 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_static_routes_nexthop.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,662 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,662 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_bgp_asn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,662 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_ssh_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,663 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,663 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_bgp_rr_asn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,663 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_leaf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,663 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,664 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_switch_block.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,664 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_domain_to_vlan_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,664 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,664 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,664 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_interface_secondary_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,665 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,665 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_ntp_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,665 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_route_tag_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,665 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,665 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_contract_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,666 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vlan_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,666 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,666 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_syslog_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,666 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_taboo_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,666 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_policy_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,667 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_node_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,667 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_node_mgmt_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,667 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_firmware_source.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,667 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_extepg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,667 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_vpn_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,668 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_cdp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,668 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vmm_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,668 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_static_node_mgmt_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,668 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,668 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_interface_path.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,669 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_access_port_to_interface_policy_leaf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,669 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,669 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_snmp_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,669 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,670 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_ntp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,670 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_mcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,670 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_igmp_interface_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,670 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_bgp_peer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,670 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_ctx_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,671 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l2out_extepg_to_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,671 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_esg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,671 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_access_span_dst_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,671 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_access_span_filter_group_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,671 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_external_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,672 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_snmp_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,672 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,672 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_profile_ospf_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,672 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_dst_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,672 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_ap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,673 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_contract_subject_to_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,673 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,673 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,673 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_switch_policy_leaf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,674 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_port_channel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,674 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_encap_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,674 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_bd_dhcp_label.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,674 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_domain_to_encap_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,674 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,675 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_custom_privilege.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,675 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_l2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,675 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_access_port_block_to_access_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,675 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,675 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_firmware_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,676 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group_to_dst_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,676 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_contract_subject.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,676 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_dhcp_relay.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,676 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_maintenance_group_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,676 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vmm_vswitch_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,677 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_pod_policy_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,677 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_node_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,677 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group_src.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,677 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_extepg_to_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,677 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_syslog_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,678 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_vpc_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,678 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tenant.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,678 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,678 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,678 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_extsubnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,679 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_bd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,679 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,679 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_bd_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,679 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,680 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vmm_uplink_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,680 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_link_level.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,680 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_dns_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,680 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_breakout_port_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,680 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_aws_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,681 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,681 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,681 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,681 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,681 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_bgp_rr_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,682 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_snmp_community_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,682 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_selector_to_switch_policy_leaf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,682 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tenant_action_rule_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,682 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_epg_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,682 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_dns_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,683 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,683 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_profile_fex_policy_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,683 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_switch_leaf_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,683 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l2out.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,684 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_scheduler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,684 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,684 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_maintenance_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,684 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_epg_monitoring_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,684 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_esg_epg_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,685 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_external_epg_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,685 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_leaf_switch_assoc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,685 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract_master.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,685 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_config_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,685 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,686 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_access_span_filter_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,686 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_config_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,686 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_spine_switch_assoc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,686 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_fc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,687 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_access_sub_port_block_to_access_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,687 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,687 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_config_export_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,687 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_syslog_remote_dest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,687 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_static_binding_to_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,688 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_esg_contract_master.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,688 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_fabric_spine_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,688 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_firmware_group_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,688 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_tenant_ep_retention_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,688 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aaa_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,689 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,689 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aep_to_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,689 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_spanning_tree.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,689 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vmm_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,689 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aep.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,690 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_switch_policy_vpc_protection_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,690 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vlan_pool_encap_block.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,690 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_filter_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,690 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_description.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,691 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_aep_to_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,691 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_vmm_uplink.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,691 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_cloud_cidr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,691 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_dhcp_relay_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,691 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_encap_pool_range.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,692 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_esg_tag_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,692 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_port_security.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,692 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_ap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,692 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_firmware_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,692 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_esg_ip_subnet_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,693 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/modules/aci_bd_to_l3out.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/modules 2023-04-28 05:57:46,693 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:46,693 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/module_utils/aci.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:46,693 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:46,694 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/module_utils/constants.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/module_utils 2023-04-28 05:57:46,694 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/lookup 2023-04-28 05:57:46,694 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/lookup/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/lookup 2023-04-28 05:57:46,694 root INFO copying build/lib/ansible_collections/cisco/aci/plugins/lookup/interface_range.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/plugins/lookup 2023-04-28 05:57:46,694 root INFO copying build/lib/ansible_collections/cisco/aci/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci 2023-04-28 05:57:46,694 root INFO copying build/lib/ansible_collections/cisco/aci/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci 2023-04-28 05:57:46,695 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/meta 2023-04-28 05:57:46,695 root INFO copying build/lib/ansible_collections/cisco/aci/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/meta 2023-04-28 05:57:46,695 root INFO copying build/lib/ansible_collections/cisco/aci/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci 2023-04-28 05:57:46,696 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:46,696 root INFO copying build/lib/ansible_collections/cisco/aci/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:46,696 root INFO copying build/lib/ansible_collections/cisco/aci/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:46,696 root INFO copying build/lib/ansible_collections/cisco/aci/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:46,697 root INFO copying build/lib/ansible_collections/cisco/aci/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci/changelogs 2023-04-28 05:57:46,697 root INFO copying build/lib/ansible_collections/cisco/aci/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci 2023-04-28 05:57:46,697 root INFO copying build/lib/ansible_collections/cisco/aci/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/aci 2023-04-28 05:57:46,697 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso 2023-04-28 05:57:46,697 root INFO copying build/lib/ansible_collections/cisco/nso/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso 2023-04-28 05:57:46,698 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins 2023-04-28 05:57:46,698 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/doc_fragments 2023-04-28 05:57:46,698 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/doc_fragments/nso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/doc_fragments 2023-04-28 05:57:46,698 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:46,698 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/modules/nso_verify.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:46,698 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/modules/nso_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:46,699 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:46,699 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/modules/nso_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:46,699 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/modules/nso_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:46,699 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/modules/nso_show.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/modules 2023-04-28 05:57:46,699 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/module_utils 2023-04-28 05:57:46,700 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/module_utils 2023-04-28 05:57:46,700 root INFO copying build/lib/ansible_collections/cisco/nso/plugins/module_utils/nso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/plugins/module_utils 2023-04-28 05:57:46,700 root INFO copying build/lib/ansible_collections/cisco/nso/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso 2023-04-28 05:57:46,700 root INFO copying build/lib/ansible_collections/cisco/nso/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso 2023-04-28 05:57:46,700 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/meta 2023-04-28 05:57:46,701 root INFO copying build/lib/ansible_collections/cisco/nso/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/meta 2023-04-28 05:57:46,701 root INFO copying build/lib/ansible_collections/cisco/nso/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso 2023-04-28 05:57:46,701 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:46,701 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:46,701 root INFO copying build/lib/ansible_collections/cisco/nso/changelogs/fragments/1.0.2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:46,702 root INFO copying build/lib/ansible_collections/cisco/nso/changelogs/fragments/1.0.1.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:46,702 root INFO copying build/lib/ansible_collections/cisco/nso/changelogs/fragments/1.0.3.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs/fragments 2023-04-28 05:57:46,702 root INFO copying build/lib/ansible_collections/cisco/nso/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:46,702 root INFO copying build/lib/ansible_collections/cisco/nso/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:46,702 root INFO copying build/lib/ansible_collections/cisco/nso/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso/changelogs 2023-04-28 05:57:46,703 root INFO copying build/lib/ansible_collections/cisco/nso/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nso 2023-04-28 05:57:46,703 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,703 root INFO copying build/lib/ansible_collections/cisco/asa/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,703 root INFO copying build/lib/ansible_collections/cisco/asa/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,703 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins 2023-04-28 05:57:46,704 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/terminal 2023-04-28 05:57:46,704 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/terminal 2023-04-28 05:57:46,704 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/terminal/asa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/terminal 2023-04-28 05:57:46,704 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/doc_fragments 2023-04-28 05:57:46,704 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/doc_fragments 2023-04-28 05:57:46,704 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/doc_fragments/asa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/doc_fragments 2023-04-28 05:57:46,705 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:46,705 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/modules/asa_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:46,705 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/modules/asa_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:46,705 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:46,705 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/modules/asa_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:46,706 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/modules/asa_ogs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:46,706 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/modules/asa_acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/modules 2023-04-28 05:57:46,706 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/cliconf 2023-04-28 05:57:46,706 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/cliconf 2023-04-28 05:57:46,706 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/cliconf/asa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/cliconf 2023-04-28 05:57:46,707 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/action 2023-04-28 05:57:46,707 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/action 2023-04-28 05:57:46,707 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/action/asa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/action 2023-04-28 05:57:46,707 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils 2023-04-28 05:57:46,707 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils 2023-04-28 05:57:46,708 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network 2023-04-28 05:57:46,708 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa 2023-04-28 05:57:46,708 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:46,708 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:46,708 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/providers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:46,708 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers 2023-04-28 05:57:46,709 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts 2023-04-28 05:57:46,709 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs 2023-04-28 05:57:46,709 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs 2023-04-28 05:57:46,709 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/ogs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs 2023-04-28 05:57:46,709 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts 2023-04-28 05:57:46,710 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts 2023-04-28 05:57:46,710 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy 2023-04-28 05:57:46,710 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy 2023-04-28 05:57:46,710 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy 2023-04-28 05:57:46,710 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls 2023-04-28 05:57:46,710 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls 2023-04-28 05:57:46,711 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls 2023-04-28 05:57:46,711 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates 2023-04-28 05:57:46,711 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates 2023-04-28 05:57:46,711 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/ogs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates 2023-04-28 05:57:46,712 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils 2023-04-28 05:57:46,712 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils 2023-04-28 05:57:46,712 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils 2023-04-28 05:57:46,712 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa 2023-04-28 05:57:46,712 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config 2023-04-28 05:57:46,712 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs 2023-04-28 05:57:46,713 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs 2023-04-28 05:57:46,713 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/ogs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs 2023-04-28 05:57:46,713 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config 2023-04-28 05:57:46,713 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls 2023-04-28 05:57:46,713 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls 2023-04-28 05:57:46,714 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls 2023-04-28 05:57:46,714 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec 2023-04-28 05:57:46,714 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts 2023-04-28 05:57:46,714 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts 2023-04-28 05:57:46,714 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts 2023-04-28 05:57:46,715 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs 2023-04-28 05:57:46,715 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs 2023-04-28 05:57:46,715 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/ogs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs 2023-04-28 05:57:46,715 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec 2023-04-28 05:57:46,715 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls 2023-04-28 05:57:46,715 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls 2023-04-28 05:57:46,716 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls 2023-04-28 05:57:46,716 root INFO copying build/lib/ansible_collections/cisco/asa/plugins/module_utils/network/asa/asa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/plugins/module_utils/network/asa 2023-04-28 05:57:46,716 root INFO copying build/lib/ansible_collections/cisco/asa/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,716 root INFO copying build/lib/ansible_collections/cisco/asa/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,717 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/meta 2023-04-28 05:57:46,717 root INFO copying build/lib/ansible_collections/cisco/asa/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/meta 2023-04-28 05:57:46,717 root INFO copying build/lib/ansible_collections/cisco/asa/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,717 root INFO copying build/lib/ansible_collections/cisco/asa/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,717 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/changelogs 2023-04-28 05:57:46,717 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/changelogs/fragments 2023-04-28 05:57:46,718 root INFO copying build/lib/ansible_collections/cisco/asa/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/changelogs/fragments 2023-04-28 05:57:46,718 root INFO copying build/lib/ansible_collections/cisco/asa/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/changelogs 2023-04-28 05:57:46,718 root INFO copying build/lib/ansible_collections/cisco/asa/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa/changelogs 2023-04-28 05:57:46,718 root INFO copying build/lib/ansible_collections/cisco/asa/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,718 root INFO copying build/lib/ansible_collections/cisco/asa/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,719 root INFO copying build/lib/ansible_collections/cisco/asa/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,719 root INFO copying build/lib/ansible_collections/cisco/asa/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/asa 2023-04-28 05:57:46,719 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki 2023-04-28 05:57:46,719 root INFO copying build/lib/ansible_collections/cisco/meraki/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki 2023-04-28 05:57:46,719 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins 2023-04-28 05:57:46,720 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/doc_fragments 2023-04-28 05:57:46,720 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/doc_fragments 2023-04-28 05:57:46,720 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/doc_fragments/meraki.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/doc_fragments 2023-04-28 05:57:46,720 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,720 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,721 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l2_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,721 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_config_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,721 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,721 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,721 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_content_filtering.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,722 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mr_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,722 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_stack_l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,722 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_webhook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,722 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,722 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,723 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mr_radio.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,723 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_alert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,723 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,723 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_organization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,723 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mr_l3_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,724 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_malware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,724 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_third_party_vpn_peers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,724 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_network_vlan_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,724 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_uplink_bandwidth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,725 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_management_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,725 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,725 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_nat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,725 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_access_policies.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,725 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_site_to_site_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,726 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_webhook_payload_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,726 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_stack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,726 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_intrusion_prevention.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,726 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l3_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,726 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mr_rf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,727 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,727 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mr_ssid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,727 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_network_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,727 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_storm_control.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,727 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_firewalled_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,728 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_action_batch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,728 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mr_l7_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,728 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_switchport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,728 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_access_list.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,729 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,729 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,729 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_ms_link_aggregation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,729 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_site_to_site_vpn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,729 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l7_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/modules 2023-04-28 05:57:46,730 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/module_utils 2023-04-28 05:57:46,730 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/module_utils/network 2023-04-28 05:57:46,730 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki 2023-04-28 05:57:46,730 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki 2023-04-28 05:57:46,730 root INFO copying build/lib/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/meraki.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki 2023-04-28 05:57:46,731 root INFO copying build/lib/ansible_collections/cisco/meraki/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki 2023-04-28 05:57:46,731 root INFO copying build/lib/ansible_collections/cisco/meraki/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki 2023-04-28 05:57:46,731 root INFO copying build/lib/ansible_collections/cisco/meraki/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki 2023-04-28 05:57:46,731 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/meta 2023-04-28 05:57:46,731 root INFO copying build/lib/ansible_collections/cisco/meraki/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/meta 2023-04-28 05:57:46,732 root INFO copying build/lib/ansible_collections/cisco/meraki/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/meta 2023-04-28 05:57:46,732 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:46,732 root INFO copying build/lib/ansible_collections/cisco/meraki/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:46,732 root INFO copying build/lib/ansible_collections/cisco/meraki/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:46,732 root INFO copying build/lib/ansible_collections/cisco/meraki/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/changelogs 2023-04-28 05:57:46,733 root INFO copying build/lib/ansible_collections/cisco/meraki/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki 2023-04-28 05:57:46,733 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/scripts 2023-04-28 05:57:46,733 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:46,733 root INFO copying build/lib/ansible_collections/cisco/meraki/scripts/sublime-build/build.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:46,733 root INFO copying build/lib/ansible_collections/cisco/meraki/scripts/sublime-build/build.py.generic -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:46,734 root INFO copying build/lib/ansible_collections/cisco/meraki/scripts/sublime-build/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki/scripts/sublime-build 2023-04-28 05:57:46,734 root INFO copying build/lib/ansible_collections/cisco/meraki/contributing.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/meraki 2023-04-28 05:57:46,734 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,734 root INFO copying build/lib/ansible_collections/cisco/mso/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,734 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins 2023-04-28 05:57:46,735 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/doc_fragments 2023-04-28 05:57:46,735 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/doc_fragments/modules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/doc_fragments 2023-04-28 05:57:46,735 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/.DS_Store -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins 2023-04-28 05:57:46,735 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,735 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_l3out.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,736 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_service_node_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,736 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,736 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_remote_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,736 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,736 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,737 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,737 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_l3out.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,737 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,737 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,737 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_backup_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,738 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_dhcp_relay_policy_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,738 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_contract_service_graph.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,738 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,738 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,738 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_dhcp_option_policy_option.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,739 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_staticleaf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,739 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,739 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_tenant_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,739 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_service_graph.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,739 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,740 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_dhcp_relay_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,740 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,740 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_bulk_staticport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,740 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,741 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_externalepg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,741 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,741 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_filter_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,741 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,741 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,742 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_migrate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,742 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,742 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,742 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_rest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,742 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_label.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,743 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_external_epg_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,743 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,743 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/ndo_schema_template_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,743 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_service_graph.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,743 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,744 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_cidr_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,744 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_cidr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,744 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,744 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_deploy_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,744 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_tenant.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,745 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,745 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_contract_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,745 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,745 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,745 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,746 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,746 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_vrf_contract.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,746 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_external_epg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,746 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,746 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_selector.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,747 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,747 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd_dhcp_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,747 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,747 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_staticport.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,748 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,748 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_hub_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,748 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,748 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,748 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_dhcp_option_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,749 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_template_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,749 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd_l3out.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/modules 2023-04-28 05:57:46,749 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/httpapi 2023-04-28 05:57:46,749 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/httpapi/mso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/httpapi 2023-04-28 05:57:46,749 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:46,749 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/module_utils/mso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:46,750 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/module_utils/constants.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:46,750 root INFO copying build/lib/ansible_collections/cisco/mso/plugins/module_utils/schema.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/plugins/module_utils 2023-04-28 05:57:46,750 root INFO copying build/lib/ansible_collections/cisco/mso/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,750 root INFO copying build/lib/ansible_collections/cisco/mso/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,751 root INFO copying build/lib/ansible_collections/cisco/mso/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,751 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/meta 2023-04-28 05:57:46,751 root INFO copying build/lib/ansible_collections/cisco/mso/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/meta 2023-04-28 05:57:46,751 root INFO copying build/lib/ansible_collections/cisco/mso/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,752 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:46,752 root INFO copying build/lib/ansible_collections/cisco/mso/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:46,752 root INFO copying build/lib/ansible_collections/cisco/mso/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:46,752 root INFO copying build/lib/ansible_collections/cisco/mso/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:46,752 root INFO copying build/lib/ansible_collections/cisco/mso/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso/changelogs 2023-04-28 05:57:46,753 root INFO copying build/lib/ansible_collections/cisco/mso/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,753 root INFO copying build/lib/ansible_collections/cisco/mso/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/mso 2023-04-28 05:57:46,753 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,753 root INFO copying build/lib/ansible_collections/cisco/nxos/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,753 root INFO copying build/lib/ansible_collections/cisco/nxos/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,754 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins 2023-04-28 05:57:46,754 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/terminal 2023-04-28 05:57:46,754 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/terminal/nxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/terminal 2023-04-28 05:57:46,754 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/terminal 2023-04-28 05:57:46,755 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/filter 2023-04-28 05:57:46,755 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/filter 2023-04-28 05:57:46,755 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/doc_fragments 2023-04-28 05:57:46,755 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/doc_fragments/nxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/doc_fragments 2023-04-28 05:57:46,755 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/doc_fragments 2023-04-28 05:57:46,756 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/netconf 2023-04-28 05:57:46,756 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/netconf/nxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/netconf 2023-04-28 05:57:46,756 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/netconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/netconf 2023-04-28 05:57:46,756 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/inventory 2023-04-28 05:57:46,756 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/inventory 2023-04-28 05:57:46,757 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,757 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,757 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_feature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,757 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vpc_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,757 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,757 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,758 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,758 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,758 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_zone_zoneset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,758 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,759 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,759 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_nxapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,759 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,759 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,760 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,760 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_aaa_server_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,760 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vrrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,760 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,760 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_pim_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,761 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,761 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,761 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_udld.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,761 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,761 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bfd_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,762 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,762 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_evpn_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,762 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,763 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,763 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,763 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,763 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,763 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,764 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_install_os.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,764 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,764 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,764 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vrf_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,764 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vxlan_vtep_vni.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,765 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,765 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_pim_rp_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,765 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_rpm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,765 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,766 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vxlan_vtep.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,766 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,766 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:46,766 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/storage/nxos_zone_zoneset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:46,767 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/storage/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:46,767 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/storage/nxos_vsan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:46,767 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/storage/nxos_devicealias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules/storage 2023-04-28 05:57:46,767 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_telemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,767 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,768 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,768 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_evpn_vni.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,768 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,768 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,768 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_hsrp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,769 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vsan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,769 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,769 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_overlay_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,769 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_contact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,769 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,770 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,770 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,770 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_hsrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,770 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_devicealias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,771 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,771 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,771 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,771 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,771 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_igmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,772 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_gir_profile_management.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,772 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,772 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_udld_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,772 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,772 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_igmp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,773 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,773 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_aaa_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,773 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,773 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_gir.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,774 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_igmp_snooping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,774 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,774 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,774 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,774 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_traps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,775 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,775 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vrf_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,775 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,775 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,775 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,776 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,776 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_file_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,776 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_bfd_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,776 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,777 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/modules/nxos_pim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/modules 2023-04-28 05:57:46,777 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/cliconf 2023-04-28 05:57:46,777 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/cliconf/nxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/cliconf 2023-04-28 05:57:46,777 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/cliconf 2023-04-28 05:57:46,777 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,778 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/hsrp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,778 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/nxapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,778 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,778 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,778 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,779 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bgp_neighbor_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,779 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snmp_traps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,779 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ospf_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,779 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,779 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,780 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vrf_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,780 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,780 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,780 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,780 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/nxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,781 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/igmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,781 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,781 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vxlan_vtep.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,781 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vxlan_vtep_vni.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,781 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,782 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,782 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/rpm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,782 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,782 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,782 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/pim_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,783 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vpc_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,783 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,783 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/interface_ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,783 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/igmp_snooping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,783 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,784 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bfd_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,784 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ntp_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,784 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/reboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,784 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,784 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snmp_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,785 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vtp_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,785 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/zone_zoneset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,785 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/telemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,785 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,785 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,786 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,786 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/aaa_server_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,786 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bgp_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,786 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snmp_contact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,786 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/gir_profile_management.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,787 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,787 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,787 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/acl_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,787 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ntp_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,787 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,788 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,788 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,788 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,788 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/pim_rp_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,788 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,789 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/feature.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,789 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snmp_community.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,789 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vtp_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,789 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/install_os.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,789 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,790 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,790 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snmp_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,790 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,790 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,791 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,791 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/pim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,791 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bgp_neighbor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,791 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/gir.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,791 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/aaa_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,792 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,792 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vrf_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,792 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/udld_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,792 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/file_copy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,792 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,793 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,793 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,793 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/udld.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,793 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,793 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/evpn_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,794 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,794 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/igmp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,794 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vtp_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,794 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/devicealias.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,794 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,795 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,795 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/bfd_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,795 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,795 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,795 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/l2_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,796 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,796 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,796 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/overlay_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,796 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,796 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vsan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,797 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/smu.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,797 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/hsrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,797 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,797 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/evpn_vni.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,797 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,798 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/snmp_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,798 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/vrrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,798 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/action/ospf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/action 2023-04-28 05:57:46,798 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/httpapi 2023-04-28 05:57:46,798 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/httpapi/nxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/httpapi 2023-04-28 05:57:46,799 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/httpapi/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/httpapi 2023-04-28 05:57:46,799 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils 2023-04-28 05:57:46,799 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils 2023-04-28 05:57:46,799 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network 2023-04-28 05:57:46,799 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network 2023-04-28 05:57:46,800 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos 2023-04-28 05:57:46,800 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/nxos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos 2023-04-28 05:57:46,800 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts 2023-04-28 05:57:46,800 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces 2023-04-28 05:57:46,800 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/bfd_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces 2023-04-28 05:57:46,801 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces 2023-04-28 05:57:46,801 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans 2023-04-28 05:57:46,801 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans 2023-04-28 05:57:46,801 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans 2023-04-28 05:57:46,801 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes 2023-04-28 05:57:46,802 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes 2023-04-28 05:57:46,802 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes 2023-04-28 05:57:46,802 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2 2023-04-28 05:57:46,802 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2 2023-04-28 05:57:46,802 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2 2023-04-28 05:57:46,802 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts 2023-04-28 05:57:46,803 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces 2023-04-28 05:57:46,803 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces 2023-04-28 05:57:46,803 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces 2023-04-28 05:57:46,803 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family 2023-04-28 05:57:46,803 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family 2023-04-28 05:57:46,804 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family 2023-04-28 05:57:46,804 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global 2023-04-28 05:57:46,804 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global 2023-04-28 05:57:46,804 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global 2023-04-28 05:57:46,804 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces 2023-04-28 05:57:46,805 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces 2023-04-28 05:57:46,805 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces 2023-04-28 05:57:46,805 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts 2023-04-28 05:57:46,805 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps 2023-04-28 05:57:46,805 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps 2023-04-28 05:57:46,806 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps 2023-04-28 05:57:46,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces 2023-04-28 05:57:46,806 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces 2023-04-28 05:57:46,806 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces 2023-04-28 05:57:46,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists 2023-04-28 05:57:46,806 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists 2023-04-28 05:57:46,807 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists 2023-04-28 05:57:46,807 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname 2023-04-28 05:57:46,807 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname 2023-04-28 05:57:46,807 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname 2023-04-28 05:57:46,807 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server 2023-04-28 05:57:46,808 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server 2023-04-28 05:57:46,808 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server 2023-04-28 05:57:46,808 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces 2023-04-28 05:57:46,808 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces 2023-04-28 05:57:46,808 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces 2023-04-28 05:57:46,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces 2023-04-28 05:57:46,809 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces 2023-04-28 05:57:46,809 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces 2023-04-28 05:57:46,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global 2023-04-28 05:57:46,809 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global 2023-04-28 05:57:46,809 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global 2023-04-28 05:57:46,810 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces 2023-04-28 05:57:46,810 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces 2023-04-28 05:57:46,810 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces 2023-04-28 05:57:46,810 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry 2023-04-28 05:57:46,810 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/telemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry 2023-04-28 05:57:46,811 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry 2023-04-28 05:57:46,811 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy 2023-04-28 05:57:46,811 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy 2023-04-28 05:57:46,811 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy 2023-04-28 05:57:46,811 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces 2023-04-28 05:57:46,812 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces 2023-04-28 05:57:46,812 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces 2023-04-28 05:57:46,812 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global 2023-04-28 05:57:46,812 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global 2023-04-28 05:57:46,812 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global 2023-04-28 05:57:46,812 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family 2023-04-28 05:57:46,813 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family 2023-04-28 05:57:46,813 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family 2023-04-28 05:57:46,813 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global 2023-04-28 05:57:46,813 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global 2023-04-28 05:57:46,813 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global 2023-04-28 05:57:46,814 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces 2023-04-28 05:57:46,814 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/hsrp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces 2023-04-28 05:57:46,814 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces 2023-04-28 05:57:46,814 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces 2023-04-28 05:57:46,814 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces 2023-04-28 05:57:46,814 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces 2023-04-28 05:57:46,815 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp 2023-04-28 05:57:46,815 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp 2023-04-28 05:57:46,815 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp 2023-04-28 05:57:46,815 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3 2023-04-28 05:57:46,815 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3 2023-04-28 05:57:46,816 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3 2023-04-28 05:57:46,816 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls 2023-04-28 05:57:46,816 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls 2023-04-28 05:57:46,816 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls 2023-04-28 05:57:46,816 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,817 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,817 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,817 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,817 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,818 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,818 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,818 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,818 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,818 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,819 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,819 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,819 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,819 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates 2023-04-28 05:57:46,820 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref 2023-04-28 05:57:46,820 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref 2023-04-28 05:57:46,820 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry 2023-04-28 05:57:46,820 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/telemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry 2023-04-28 05:57:46,820 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry 2023-04-28 05:57:46,821 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils 2023-04-28 05:57:46,821 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils 2023-04-28 05:57:46,821 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils 2023-04-28 05:57:46,821 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry 2023-04-28 05:57:46,821 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/telemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry 2023-04-28 05:57:46,822 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry 2023-04-28 05:57:46,822 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos 2023-04-28 05:57:46,822 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config 2023-04-28 05:57:46,822 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces 2023-04-28 05:57:46,822 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/bfd_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces 2023-04-28 05:57:46,822 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces 2023-04-28 05:57:46,823 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans 2023-04-28 05:57:46,823 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans 2023-04-28 05:57:46,823 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans 2023-04-28 05:57:46,823 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes 2023-04-28 05:57:46,823 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes 2023-04-28 05:57:46,824 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes 2023-04-28 05:57:46,824 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2 2023-04-28 05:57:46,824 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2 2023-04-28 05:57:46,824 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2 2023-04-28 05:57:46,824 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces 2023-04-28 05:57:46,825 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces 2023-04-28 05:57:46,825 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces 2023-04-28 05:57:46,825 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family 2023-04-28 05:57:46,825 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family 2023-04-28 05:57:46,825 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family 2023-04-28 05:57:46,826 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global 2023-04-28 05:57:46,826 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global 2023-04-28 05:57:46,826 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global 2023-04-28 05:57:46,826 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces 2023-04-28 05:57:46,826 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces 2023-04-28 05:57:46,827 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces 2023-04-28 05:57:46,827 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config 2023-04-28 05:57:46,827 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps 2023-04-28 05:57:46,827 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps 2023-04-28 05:57:46,827 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps 2023-04-28 05:57:46,828 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces 2023-04-28 05:57:46,828 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces 2023-04-28 05:57:46,828 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces 2023-04-28 05:57:46,828 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists 2023-04-28 05:57:46,828 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists 2023-04-28 05:57:46,828 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists 2023-04-28 05:57:46,829 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname 2023-04-28 05:57:46,829 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname 2023-04-28 05:57:46,829 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname 2023-04-28 05:57:46,829 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server 2023-04-28 05:57:46,829 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server 2023-04-28 05:57:46,830 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server 2023-04-28 05:57:46,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces 2023-04-28 05:57:46,830 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces 2023-04-28 05:57:46,830 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces 2023-04-28 05:57:46,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces 2023-04-28 05:57:46,831 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces 2023-04-28 05:57:46,831 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces 2023-04-28 05:57:46,831 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global 2023-04-28 05:57:46,831 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global 2023-04-28 05:57:46,831 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global 2023-04-28 05:57:46,832 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces 2023-04-28 05:57:46,832 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces 2023-04-28 05:57:46,832 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces 2023-04-28 05:57:46,832 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry 2023-04-28 05:57:46,832 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/telemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry 2023-04-28 05:57:46,833 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry 2023-04-28 05:57:46,833 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces 2023-04-28 05:57:46,833 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces 2023-04-28 05:57:46,833 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces 2023-04-28 05:57:46,833 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global 2023-04-28 05:57:46,833 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global 2023-04-28 05:57:46,834 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global 2023-04-28 05:57:46,834 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family 2023-04-28 05:57:46,834 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family 2023-04-28 05:57:46,834 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family 2023-04-28 05:57:46,835 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global 2023-04-28 05:57:46,835 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global 2023-04-28 05:57:46,835 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global 2023-04-28 05:57:46,835 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces 2023-04-28 05:57:46,835 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/hsrp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces 2023-04-28 05:57:46,835 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces 2023-04-28 05:57:46,836 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces 2023-04-28 05:57:46,836 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces 2023-04-28 05:57:46,836 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces 2023-04-28 05:57:46,836 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp 2023-04-28 05:57:46,836 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp 2023-04-28 05:57:46,837 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp 2023-04-28 05:57:46,837 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3 2023-04-28 05:57:46,837 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3 2023-04-28 05:57:46,837 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3 2023-04-28 05:57:46,837 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls 2023-04-28 05:57:46,837 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls 2023-04-28 05:57:46,838 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls 2023-04-28 05:57:46,838 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec 2023-04-28 05:57:46,838 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces 2023-04-28 05:57:46,838 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/bfd_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces 2023-04-28 05:57:46,838 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces 2023-04-28 05:57:46,839 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans 2023-04-28 05:57:46,839 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans 2023-04-28 05:57:46,839 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans 2023-04-28 05:57:46,839 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes 2023-04-28 05:57:46,839 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes 2023-04-28 05:57:46,840 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes 2023-04-28 05:57:46,840 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts 2023-04-28 05:57:46,840 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts 2023-04-28 05:57:46,840 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts 2023-04-28 05:57:46,840 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2 2023-04-28 05:57:46,841 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2 2023-04-28 05:57:46,841 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2 2023-04-28 05:57:46,841 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces 2023-04-28 05:57:46,841 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces 2023-04-28 05:57:46,841 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces 2023-04-28 05:57:46,842 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family 2023-04-28 05:57:46,842 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family 2023-04-28 05:57:46,842 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family 2023-04-28 05:57:46,842 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global 2023-04-28 05:57:46,842 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global 2023-04-28 05:57:46,842 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global 2023-04-28 05:57:46,843 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces 2023-04-28 05:57:46,843 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces 2023-04-28 05:57:46,843 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces 2023-04-28 05:57:46,843 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec 2023-04-28 05:57:46,843 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps 2023-04-28 05:57:46,844 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps 2023-04-28 05:57:46,844 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps 2023-04-28 05:57:46,844 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces 2023-04-28 05:57:46,844 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces 2023-04-28 05:57:46,844 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces 2023-04-28 05:57:46,845 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists 2023-04-28 05:57:46,845 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists 2023-04-28 05:57:46,845 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists 2023-04-28 05:57:46,845 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname 2023-04-28 05:57:46,845 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname 2023-04-28 05:57:46,845 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname 2023-04-28 05:57:46,846 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server 2023-04-28 05:57:46,846 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server 2023-04-28 05:57:46,846 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server 2023-04-28 05:57:46,846 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces 2023-04-28 05:57:46,846 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces 2023-04-28 05:57:46,847 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces 2023-04-28 05:57:46,847 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces 2023-04-28 05:57:46,847 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces 2023-04-28 05:57:46,847 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces 2023-04-28 05:57:46,847 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global 2023-04-28 05:57:46,848 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global 2023-04-28 05:57:46,848 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global 2023-04-28 05:57:46,848 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces 2023-04-28 05:57:46,848 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces 2023-04-28 05:57:46,848 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces 2023-04-28 05:57:46,848 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry 2023-04-28 05:57:46,849 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/telemetry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry 2023-04-28 05:57:46,849 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry 2023-04-28 05:57:46,849 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces 2023-04-28 05:57:46,849 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces 2023-04-28 05:57:46,849 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces 2023-04-28 05:57:46,850 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global 2023-04-28 05:57:46,850 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global 2023-04-28 05:57:46,850 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global 2023-04-28 05:57:46,850 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family 2023-04-28 05:57:46,850 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family 2023-04-28 05:57:46,851 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family 2023-04-28 05:57:46,851 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global 2023-04-28 05:57:46,851 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global 2023-04-28 05:57:46,851 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global 2023-04-28 05:57:46,851 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces 2023-04-28 05:57:46,852 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/hsrp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces 2023-04-28 05:57:46,852 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces 2023-04-28 05:57:46,852 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces 2023-04-28 05:57:46,852 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces 2023-04-28 05:57:46,852 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces 2023-04-28 05:57:46,853 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp 2023-04-28 05:57:46,853 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp 2023-04-28 05:57:46,853 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp 2023-04-28 05:57:46,853 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3 2023-04-28 05:57:46,853 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3 2023-04-28 05:57:46,853 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3 2023-04-28 05:57:46,854 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls 2023-04-28 05:57:46,854 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls 2023-04-28 05:57:46,854 root INFO copying build/lib/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls 2023-04-28 05:57:46,854 root INFO copying build/lib/ansible_collections/cisco/nxos/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,855 root INFO copying build/lib/ansible_collections/cisco/nxos/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,855 root INFO copying build/lib/ansible_collections/cisco/nxos/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,856 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/meta 2023-04-28 05:57:46,856 root INFO copying build/lib/ansible_collections/cisco/nxos/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/meta 2023-04-28 05:57:46,856 root INFO copying build/lib/ansible_collections/cisco/nxos/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,856 root INFO copying build/lib/ansible_collections/cisco/nxos/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,856 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/changelogs 2023-04-28 05:57:46,857 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/changelogs/fragments 2023-04-28 05:57:46,857 root INFO copying build/lib/ansible_collections/cisco/nxos/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/changelogs/fragments 2023-04-28 05:57:46,857 root INFO copying build/lib/ansible_collections/cisco/nxos/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/changelogs 2023-04-28 05:57:46,857 root INFO copying build/lib/ansible_collections/cisco/nxos/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos/changelogs 2023-04-28 05:57:46,857 root INFO copying build/lib/ansible_collections/cisco/nxos/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,858 root INFO copying build/lib/ansible_collections/cisco/nxos/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,858 root INFO copying build/lib/ansible_collections/cisco/nxos/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,858 root INFO copying build/lib/ansible_collections/cisco/nxos/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/nxos 2023-04-28 05:57:46,858 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,858 root INFO copying build/lib/ansible_collections/cisco/ios/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,859 root INFO copying build/lib/ansible_collections/cisco/ios/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,859 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins 2023-04-28 05:57:46,859 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/terminal 2023-04-28 05:57:46,859 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/terminal/ios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/terminal 2023-04-28 05:57:46,859 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/terminal 2023-04-28 05:57:46,860 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/filter 2023-04-28 05:57:46,860 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/filter 2023-04-28 05:57:46,860 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/doc_fragments 2023-04-28 05:57:46,860 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/doc_fragments/ios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/doc_fragments 2023-04-28 05:57:46,860 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/doc_fragments 2023-04-28 05:57:46,860 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/inventory 2023-04-28 05:57:46,861 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/inventory 2023-04-28 05:57:46,861 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,861 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,861 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,861 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,862 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,862 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,862 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,862 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,862 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,863 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,863 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,863 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,863 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,864 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,864 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,864 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,864 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,865 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,865 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,865 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,865 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,866 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,866 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,866 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,866 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,867 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,867 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,867 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,867 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,868 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,868 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,868 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,868 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,869 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,869 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,869 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,869 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,869 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/modules/ios_lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/modules 2023-04-28 05:57:46,870 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/cliconf 2023-04-28 05:57:46,870 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/cliconf/ios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/cliconf 2023-04-28 05:57:46,870 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/cliconf 2023-04-28 05:57:46,870 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,870 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,871 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,871 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/ios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,871 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,871 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,871 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,872 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,872 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,872 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,872 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,872 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,873 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,873 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,873 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,873 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,873 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,874 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,874 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,874 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,874 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,874 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,875 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,875 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,875 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,875 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,875 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,876 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,876 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,876 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,876 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,876 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,877 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,877 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,877 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,877 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,877 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,877 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,878 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/action/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/action 2023-04-28 05:57:46,878 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils 2023-04-28 05:57:46,878 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils 2023-04-28 05:57:46,878 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network 2023-04-28 05:57:46,878 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network 2023-04-28 05:57:46,879 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios 2023-04-28 05:57:46,879 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/ios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios 2023-04-28 05:57:46,879 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:46,880 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:46,880 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/providers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:46,880 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli 2023-04-28 05:57:46,880 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli 2023-04-28 05:57:46,880 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config 2023-04-28 05:57:46,880 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:46,881 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:46,881 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:46,881 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:46,881 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/process.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp 2023-04-28 05:57:46,881 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config 2023-04-28 05:57:46,882 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config 2023-04-28 05:57:46,882 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers 2023-04-28 05:57:46,882 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts 2023-04-28 05:57:46,882 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans 2023-04-28 05:57:46,882 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans 2023-04-28 05:57:46,883 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans 2023-04-28 05:57:46,883 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes 2023-04-28 05:57:46,883 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes 2023-04-28 05:57:46,883 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes 2023-04-28 05:57:46,883 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2 2023-04-28 05:57:46,884 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2 2023-04-28 05:57:46,884 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2 2023-04-28 05:57:46,884 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts 2023-04-28 05:57:46,884 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces 2023-04-28 05:57:46,884 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces 2023-04-28 05:57:46,884 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces 2023-04-28 05:57:46,885 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family 2023-04-28 05:57:46,885 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family 2023-04-28 05:57:46,885 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family 2023-04-28 05:57:46,885 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global 2023-04-28 05:57:46,885 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global 2023-04-28 05:57:46,886 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global 2023-04-28 05:57:46,886 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces 2023-04-28 05:57:46,886 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces 2023-04-28 05:57:46,886 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces 2023-04-28 05:57:46,886 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts 2023-04-28 05:57:46,887 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps 2023-04-28 05:57:46,887 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps 2023-04-28 05:57:46,887 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps 2023-04-28 05:57:46,887 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces 2023-04-28 05:57:46,887 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces 2023-04-28 05:57:46,887 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces 2023-04-28 05:57:46,888 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists 2023-04-28 05:57:46,888 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists 2023-04-28 05:57:46,888 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists 2023-04-28 05:57:46,888 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname 2023-04-28 05:57:46,888 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname 2023-04-28 05:57:46,889 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname 2023-04-28 05:57:46,889 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server 2023-04-28 05:57:46,889 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server 2023-04-28 05:57:46,889 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server 2023-04-28 05:57:46,889 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces 2023-04-28 05:57:46,890 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces 2023-04-28 05:57:46,890 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces 2023-04-28 05:57:46,890 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces 2023-04-28 05:57:46,890 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces 2023-04-28 05:57:46,890 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces 2023-04-28 05:57:46,890 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global 2023-04-28 05:57:46,891 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global 2023-04-28 05:57:46,891 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global 2023-04-28 05:57:46,891 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces 2023-04-28 05:57:46,891 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces 2023-04-28 05:57:46,891 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces 2023-04-28 05:57:46,892 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy 2023-04-28 05:57:46,892 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy 2023-04-28 05:57:46,892 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy 2023-04-28 05:57:46,892 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces 2023-04-28 05:57:46,892 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces 2023-04-28 05:57:46,893 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces 2023-04-28 05:57:46,893 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global 2023-04-28 05:57:46,893 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global 2023-04-28 05:57:46,893 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global 2023-04-28 05:57:46,893 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global 2023-04-28 05:57:46,893 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global 2023-04-28 05:57:46,894 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global 2023-04-28 05:57:46,894 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces 2023-04-28 05:57:46,894 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces 2023-04-28 05:57:46,894 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces 2023-04-28 05:57:46,894 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp 2023-04-28 05:57:46,895 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp 2023-04-28 05:57:46,895 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp 2023-04-28 05:57:46,895 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3 2023-04-28 05:57:46,895 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3 2023-04-28 05:57:46,895 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3 2023-04-28 05:57:46,896 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls 2023-04-28 05:57:46,896 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls 2023-04-28 05:57:46,896 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls 2023-04-28 05:57:46,896 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,896 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,897 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,897 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,897 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,897 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,898 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,898 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,898 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,898 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,898 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,899 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,899 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,899 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,899 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,900 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,900 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,900 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,901 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,901 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,901 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates 2023-04-28 05:57:46,901 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils 2023-04-28 05:57:46,901 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils 2023-04-28 05:57:46,902 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils 2023-04-28 05:57:46,902 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios 2023-04-28 05:57:46,902 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config 2023-04-28 05:57:46,902 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans 2023-04-28 05:57:46,902 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans 2023-04-28 05:57:46,903 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans 2023-04-28 05:57:46,903 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes 2023-04-28 05:57:46,903 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes 2023-04-28 05:57:46,903 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes 2023-04-28 05:57:46,903 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2 2023-04-28 05:57:46,904 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2 2023-04-28 05:57:46,904 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2 2023-04-28 05:57:46,904 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces 2023-04-28 05:57:46,904 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces 2023-04-28 05:57:46,904 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces 2023-04-28 05:57:46,905 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family 2023-04-28 05:57:46,905 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family 2023-04-28 05:57:46,905 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family 2023-04-28 05:57:46,905 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global 2023-04-28 05:57:46,905 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global 2023-04-28 05:57:46,906 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global 2023-04-28 05:57:46,906 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces 2023-04-28 05:57:46,906 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces 2023-04-28 05:57:46,906 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces 2023-04-28 05:57:46,906 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config 2023-04-28 05:57:46,907 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps 2023-04-28 05:57:46,907 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps 2023-04-28 05:57:46,907 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps 2023-04-28 05:57:46,907 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces 2023-04-28 05:57:46,907 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces 2023-04-28 05:57:46,907 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces 2023-04-28 05:57:46,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists 2023-04-28 05:57:46,908 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists 2023-04-28 05:57:46,908 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists 2023-04-28 05:57:46,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname 2023-04-28 05:57:46,908 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname 2023-04-28 05:57:46,909 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname 2023-04-28 05:57:46,909 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server 2023-04-28 05:57:46,909 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server 2023-04-28 05:57:46,909 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server 2023-04-28 05:57:46,909 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces 2023-04-28 05:57:46,910 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces 2023-04-28 05:57:46,910 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces 2023-04-28 05:57:46,910 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces 2023-04-28 05:57:46,910 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces 2023-04-28 05:57:46,910 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces 2023-04-28 05:57:46,911 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global 2023-04-28 05:57:46,911 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global 2023-04-28 05:57:46,911 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global 2023-04-28 05:57:46,911 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces 2023-04-28 05:57:46,911 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces 2023-04-28 05:57:46,911 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces 2023-04-28 05:57:46,912 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces 2023-04-28 05:57:46,912 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces 2023-04-28 05:57:46,912 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces 2023-04-28 05:57:46,912 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global 2023-04-28 05:57:46,912 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global 2023-04-28 05:57:46,913 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global 2023-04-28 05:57:46,913 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global 2023-04-28 05:57:46,913 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global 2023-04-28 05:57:46,913 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global 2023-04-28 05:57:46,913 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces 2023-04-28 05:57:46,914 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces 2023-04-28 05:57:46,914 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces 2023-04-28 05:57:46,914 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp 2023-04-28 05:57:46,914 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp 2023-04-28 05:57:46,914 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp 2023-04-28 05:57:46,915 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3 2023-04-28 05:57:46,915 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3 2023-04-28 05:57:46,915 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3 2023-04-28 05:57:46,915 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping 2023-04-28 05:57:46,915 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping 2023-04-28 05:57:46,916 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping 2023-04-28 05:57:46,916 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls 2023-04-28 05:57:46,916 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls 2023-04-28 05:57:46,916 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls 2023-04-28 05:57:46,916 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec 2023-04-28 05:57:46,916 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans 2023-04-28 05:57:46,917 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans 2023-04-28 05:57:46,917 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans 2023-04-28 05:57:46,917 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes 2023-04-28 05:57:46,917 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes 2023-04-28 05:57:46,917 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes 2023-04-28 05:57:46,918 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts 2023-04-28 05:57:46,918 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts 2023-04-28 05:57:46,918 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts 2023-04-28 05:57:46,918 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2 2023-04-28 05:57:46,918 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2 2023-04-28 05:57:46,919 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2 2023-04-28 05:57:46,919 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces 2023-04-28 05:57:46,919 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces 2023-04-28 05:57:46,919 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces 2023-04-28 05:57:46,919 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family 2023-04-28 05:57:46,919 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family 2023-04-28 05:57:46,920 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family 2023-04-28 05:57:46,920 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global 2023-04-28 05:57:46,920 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global 2023-04-28 05:57:46,920 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global 2023-04-28 05:57:46,921 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces 2023-04-28 05:57:46,921 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces 2023-04-28 05:57:46,921 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces 2023-04-28 05:57:46,921 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec 2023-04-28 05:57:46,921 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps 2023-04-28 05:57:46,921 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps 2023-04-28 05:57:46,922 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps 2023-04-28 05:57:46,922 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces 2023-04-28 05:57:46,922 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces 2023-04-28 05:57:46,922 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces 2023-04-28 05:57:46,922 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists 2023-04-28 05:57:46,923 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists 2023-04-28 05:57:46,923 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists 2023-04-28 05:57:46,923 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname 2023-04-28 05:57:46,923 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname 2023-04-28 05:57:46,923 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname 2023-04-28 05:57:46,924 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server 2023-04-28 05:57:46,924 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server 2023-04-28 05:57:46,924 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server 2023-04-28 05:57:46,924 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces 2023-04-28 05:57:46,924 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces 2023-04-28 05:57:46,924 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces 2023-04-28 05:57:46,925 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces 2023-04-28 05:57:46,925 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces 2023-04-28 05:57:46,925 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces 2023-04-28 05:57:46,925 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global 2023-04-28 05:57:46,925 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global 2023-04-28 05:57:46,926 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global 2023-04-28 05:57:46,926 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces 2023-04-28 05:57:46,926 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces 2023-04-28 05:57:46,926 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces 2023-04-28 05:57:46,926 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces 2023-04-28 05:57:46,927 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces 2023-04-28 05:57:46,927 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces 2023-04-28 05:57:46,927 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global 2023-04-28 05:57:46,927 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global 2023-04-28 05:57:46,927 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global 2023-04-28 05:57:46,928 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global 2023-04-28 05:57:46,928 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global 2023-04-28 05:57:46,928 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global 2023-04-28 05:57:46,928 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces 2023-04-28 05:57:46,928 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces 2023-04-28 05:57:46,928 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces 2023-04-28 05:57:46,929 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp 2023-04-28 05:57:46,929 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp 2023-04-28 05:57:46,929 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp 2023-04-28 05:57:46,929 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3 2023-04-28 05:57:46,929 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3 2023-04-28 05:57:46,930 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3 2023-04-28 05:57:46,930 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping 2023-04-28 05:57:46,930 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping 2023-04-28 05:57:46,930 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping 2023-04-28 05:57:46,930 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls 2023-04-28 05:57:46,931 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls 2023-04-28 05:57:46,931 root INFO copying build/lib/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls 2023-04-28 05:57:46,931 root INFO copying build/lib/ansible_collections/cisco/ios/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,931 root INFO copying build/lib/ansible_collections/cisco/ios/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,932 root INFO copying build/lib/ansible_collections/cisco/ios/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,932 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/meta 2023-04-28 05:57:46,932 root INFO copying build/lib/ansible_collections/cisco/ios/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/meta 2023-04-28 05:57:46,932 root INFO copying build/lib/ansible_collections/cisco/ios/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,933 root INFO copying build/lib/ansible_collections/cisco/ios/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,933 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/changelogs 2023-04-28 05:57:46,933 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/changelogs/fragments 2023-04-28 05:57:46,933 root INFO copying build/lib/ansible_collections/cisco/ios/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/changelogs/fragments 2023-04-28 05:57:46,933 root INFO copying build/lib/ansible_collections/cisco/ios/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/changelogs 2023-04-28 05:57:46,934 root INFO copying build/lib/ansible_collections/cisco/ios/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios/changelogs 2023-04-28 05:57:46,934 root INFO copying build/lib/ansible_collections/cisco/ios/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,934 root INFO copying build/lib/ansible_collections/cisco/ios/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,934 root INFO copying build/lib/ansible_collections/cisco/ios/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,934 root INFO copying build/lib/ansible_collections/cisco/ios/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ios 2023-04-28 05:57:46,935 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:46,935 root INFO copying build/lib/ansible_collections/cisco/iosxr/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:46,935 root INFO copying build/lib/ansible_collections/cisco/iosxr/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:46,935 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins 2023-04-28 05:57:46,935 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/sub_plugins 2023-04-28 05:57:46,936 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc 2023-04-28 05:57:46,936 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb 2023-04-28 05:57:46,936 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/ems_grpc_pb2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb 2023-04-28 05:57:46,936 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb 2023-04-28 05:57:46,936 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc 2023-04-28 05:57:46,937 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/iosxr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc 2023-04-28 05:57:46,937 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/terminal 2023-04-28 05:57:46,937 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/terminal 2023-04-28 05:57:46,937 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/terminal/iosxr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/terminal 2023-04-28 05:57:46,937 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/filter 2023-04-28 05:57:46,938 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/filter 2023-04-28 05:57:46,938 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/doc_fragments 2023-04-28 05:57:46,938 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/doc_fragments 2023-04-28 05:57:46,938 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/doc_fragments/iosxr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/doc_fragments 2023-04-28 05:57:46,938 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/netconf 2023-04-28 05:57:46,938 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/netconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/netconf 2023-04-28 05:57:46,939 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/netconf/iosxr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/netconf 2023-04-28 05:57:46,939 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/inventory 2023-04-28 05:57:46,939 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/inventory 2023-04-28 05:57:46,939 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,939 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,940 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,940 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,940 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,940 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,941 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,941 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,941 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,941 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,942 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,942 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,942 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,942 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,942 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,943 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,943 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,943 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,943 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,944 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,944 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,944 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,944 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,945 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,945 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,945 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,945 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,946 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,946 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,946 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,946 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,946 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,947 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,947 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/modules/iosxr_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/modules 2023-04-28 05:57:46,947 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/cliconf 2023-04-28 05:57:46,947 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/cliconf 2023-04-28 05:57:46,947 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/cliconf/iosxr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/cliconf 2023-04-28 05:57:46,948 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,948 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,948 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,948 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,948 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,949 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,949 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,949 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,949 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,949 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,950 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,950 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,950 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,950 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/netconf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,950 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,951 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,951 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,951 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,951 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,951 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,952 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,952 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,952 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,952 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,952 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,953 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,953 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/iosxr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,953 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,953 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,953 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,954 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,954 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,954 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,954 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,954 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/action/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/action 2023-04-28 05:57:46,955 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils 2023-04-28 05:57:46,955 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils 2023-04-28 05:57:46,955 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network 2023-04-28 05:57:46,955 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network 2023-04-28 05:57:46,955 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr 2023-04-28 05:57:46,955 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:46,956 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:46,956 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/providers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:46,956 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli 2023-04-28 05:57:46,956 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli 2023-04-28 05:57:46,956 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config 2023-04-28 05:57:46,956 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:46,957 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:46,957 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:46,957 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:46,957 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/process.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp 2023-04-28 05:57:46,957 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config 2023-04-28 05:57:46,958 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers 2023-04-28 05:57:46,958 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts 2023-04-28 05:57:46,958 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes 2023-04-28 05:57:46,958 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes 2023-04-28 05:57:46,958 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes 2023-04-28 05:57:46,959 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2 2023-04-28 05:57:46,959 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2 2023-04-28 05:57:46,959 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2 2023-04-28 05:57:46,959 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts 2023-04-28 05:57:46,959 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces 2023-04-28 05:57:46,960 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces 2023-04-28 05:57:46,960 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces 2023-04-28 05:57:46,960 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family 2023-04-28 05:57:46,960 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family 2023-04-28 05:57:46,960 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family 2023-04-28 05:57:46,961 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global 2023-04-28 05:57:46,961 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global 2023-04-28 05:57:46,961 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global 2023-04-28 05:57:46,961 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces 2023-04-28 05:57:46,961 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces 2023-04-28 05:57:46,961 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces 2023-04-28 05:57:46,962 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts 2023-04-28 05:57:46,962 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces 2023-04-28 05:57:46,962 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces 2023-04-28 05:57:46,962 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces 2023-04-28 05:57:46,962 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists 2023-04-28 05:57:46,963 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists 2023-04-28 05:57:46,963 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists 2023-04-28 05:57:46,963 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname 2023-04-28 05:57:46,963 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname 2023-04-28 05:57:46,963 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname 2023-04-28 05:57:46,964 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server 2023-04-28 05:57:46,964 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server 2023-04-28 05:57:46,964 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server 2023-04-28 05:57:46,964 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces 2023-04-28 05:57:46,964 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces 2023-04-28 05:57:46,964 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces 2023-04-28 05:57:46,965 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces 2023-04-28 05:57:46,965 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces 2023-04-28 05:57:46,965 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces 2023-04-28 05:57:46,965 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global 2023-04-28 05:57:46,965 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global 2023-04-28 05:57:46,966 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global 2023-04-28 05:57:46,966 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces 2023-04-28 05:57:46,966 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces 2023-04-28 05:57:46,966 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces 2023-04-28 05:57:46,966 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy 2023-04-28 05:57:46,967 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy 2023-04-28 05:57:46,967 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy 2023-04-28 05:57:46,967 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces 2023-04-28 05:57:46,967 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces 2023-04-28 05:57:46,967 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces 2023-04-28 05:57:46,968 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global 2023-04-28 05:57:46,968 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global 2023-04-28 05:57:46,968 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global 2023-04-28 05:57:46,968 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family 2023-04-28 05:57:46,968 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family 2023-04-28 05:57:46,968 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family 2023-04-28 05:57:46,969 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global 2023-04-28 05:57:46,969 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global 2023-04-28 05:57:46,969 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global 2023-04-28 05:57:46,969 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces 2023-04-28 05:57:46,969 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces 2023-04-28 05:57:46,970 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces 2023-04-28 05:57:46,970 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp 2023-04-28 05:57:46,970 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp 2023-04-28 05:57:46,970 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp 2023-04-28 05:57:46,970 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3 2023-04-28 05:57:46,970 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3 2023-04-28 05:57:46,971 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3 2023-04-28 05:57:46,971 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls 2023-04-28 05:57:46,971 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls 2023-04-28 05:57:46,971 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls 2023-04-28 05:57:46,972 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,972 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,972 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,972 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,972 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,973 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,973 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,973 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,973 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,974 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,974 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,974 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,974 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,975 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,975 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates 2023-04-28 05:57:46,975 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils 2023-04-28 05:57:46,975 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils 2023-04-28 05:57:46,976 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils 2023-04-28 05:57:46,976 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr 2023-04-28 05:57:46,976 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config 2023-04-28 05:57:46,976 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes 2023-04-28 05:57:46,976 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes 2023-04-28 05:57:46,977 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes 2023-04-28 05:57:46,977 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2 2023-04-28 05:57:46,977 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2 2023-04-28 05:57:46,977 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2 2023-04-28 05:57:46,977 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces 2023-04-28 05:57:46,978 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces 2023-04-28 05:57:46,978 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces 2023-04-28 05:57:46,978 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family 2023-04-28 05:57:46,978 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family 2023-04-28 05:57:46,978 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family 2023-04-28 05:57:46,979 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global 2023-04-28 05:57:46,979 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global 2023-04-28 05:57:46,979 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global 2023-04-28 05:57:46,979 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces 2023-04-28 05:57:46,979 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces 2023-04-28 05:57:46,980 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces 2023-04-28 05:57:46,980 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config 2023-04-28 05:57:46,980 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces 2023-04-28 05:57:46,980 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces 2023-04-28 05:57:46,980 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces 2023-04-28 05:57:46,981 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists 2023-04-28 05:57:46,981 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists 2023-04-28 05:57:46,981 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists 2023-04-28 05:57:46,981 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname 2023-04-28 05:57:46,981 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname 2023-04-28 05:57:46,981 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname 2023-04-28 05:57:46,982 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server 2023-04-28 05:57:46,982 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server 2023-04-28 05:57:46,982 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server 2023-04-28 05:57:46,982 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces 2023-04-28 05:57:46,982 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces 2023-04-28 05:57:46,983 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces 2023-04-28 05:57:46,983 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces 2023-04-28 05:57:46,983 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces 2023-04-28 05:57:46,983 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces 2023-04-28 05:57:46,983 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global 2023-04-28 05:57:46,984 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global 2023-04-28 05:57:46,984 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global 2023-04-28 05:57:46,984 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces 2023-04-28 05:57:46,984 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces 2023-04-28 05:57:46,984 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces 2023-04-28 05:57:46,985 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces 2023-04-28 05:57:46,985 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces 2023-04-28 05:57:46,985 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces 2023-04-28 05:57:46,985 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global 2023-04-28 05:57:46,985 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global 2023-04-28 05:57:46,985 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global 2023-04-28 05:57:46,986 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family 2023-04-28 05:57:46,986 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family 2023-04-28 05:57:46,986 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family 2023-04-28 05:57:46,986 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global 2023-04-28 05:57:46,986 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global 2023-04-28 05:57:46,987 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global 2023-04-28 05:57:46,987 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces 2023-04-28 05:57:46,987 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces 2023-04-28 05:57:46,987 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces 2023-04-28 05:57:46,987 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp 2023-04-28 05:57:46,988 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp 2023-04-28 05:57:46,988 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp 2023-04-28 05:57:46,988 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3 2023-04-28 05:57:46,988 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3 2023-04-28 05:57:46,988 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3 2023-04-28 05:57:46,989 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping 2023-04-28 05:57:46,989 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping 2023-04-28 05:57:46,989 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping 2023-04-28 05:57:46,989 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls 2023-04-28 05:57:46,989 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls 2023-04-28 05:57:46,989 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls 2023-04-28 05:57:46,990 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec 2023-04-28 05:57:46,990 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes 2023-04-28 05:57:46,990 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes 2023-04-28 05:57:46,990 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes 2023-04-28 05:57:46,990 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts 2023-04-28 05:57:46,991 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts 2023-04-28 05:57:46,991 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts 2023-04-28 05:57:46,991 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2 2023-04-28 05:57:46,991 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2 2023-04-28 05:57:46,991 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2 2023-04-28 05:57:46,992 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces 2023-04-28 05:57:46,992 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces 2023-04-28 05:57:46,992 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces 2023-04-28 05:57:46,992 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family 2023-04-28 05:57:46,992 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family 2023-04-28 05:57:46,993 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family 2023-04-28 05:57:46,993 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global 2023-04-28 05:57:46,993 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global 2023-04-28 05:57:46,993 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global 2023-04-28 05:57:46,993 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces 2023-04-28 05:57:46,993 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces 2023-04-28 05:57:46,994 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces 2023-04-28 05:57:46,994 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec 2023-04-28 05:57:46,994 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces 2023-04-28 05:57:46,994 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces 2023-04-28 05:57:46,994 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces 2023-04-28 05:57:46,995 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists 2023-04-28 05:57:46,995 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists 2023-04-28 05:57:46,995 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists 2023-04-28 05:57:46,995 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname 2023-04-28 05:57:46,995 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname 2023-04-28 05:57:46,996 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname 2023-04-28 05:57:46,996 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server 2023-04-28 05:57:46,996 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server 2023-04-28 05:57:46,996 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server 2023-04-28 05:57:46,996 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces 2023-04-28 05:57:46,997 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces 2023-04-28 05:57:46,997 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces 2023-04-28 05:57:46,997 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces 2023-04-28 05:57:46,997 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces 2023-04-28 05:57:46,997 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces 2023-04-28 05:57:46,998 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global 2023-04-28 05:57:46,998 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global 2023-04-28 05:57:46,998 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global 2023-04-28 05:57:46,998 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces 2023-04-28 05:57:46,998 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces 2023-04-28 05:57:46,998 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces 2023-04-28 05:57:46,999 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces 2023-04-28 05:57:46,999 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces 2023-04-28 05:57:46,999 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces 2023-04-28 05:57:46,999 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global 2023-04-28 05:57:46,999 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global 2023-04-28 05:57:47,000 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global 2023-04-28 05:57:47,000 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family 2023-04-28 05:57:47,000 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family 2023-04-28 05:57:47,000 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/bgp_neighbor_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family 2023-04-28 05:57:47,001 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global 2023-04-28 05:57:47,001 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global 2023-04-28 05:57:47,001 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global 2023-04-28 05:57:47,001 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces 2023-04-28 05:57:47,001 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces 2023-04-28 05:57:47,001 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces 2023-04-28 05:57:47,002 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp 2023-04-28 05:57:47,002 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp 2023-04-28 05:57:47,002 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp 2023-04-28 05:57:47,002 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3 2023-04-28 05:57:47,002 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3 2023-04-28 05:57:47,003 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3 2023-04-28 05:57:47,003 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping 2023-04-28 05:57:47,003 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping 2023-04-28 05:57:47,003 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping 2023-04-28 05:57:47,004 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls 2023-04-28 05:57:47,004 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls 2023-04-28 05:57:47,004 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls 2023-04-28 05:57:47,004 root INFO copying build/lib/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/iosxr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr 2023-04-28 05:57:47,005 root INFO copying build/lib/ansible_collections/cisco/iosxr/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,005 root INFO copying build/lib/ansible_collections/cisco/iosxr/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,006 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/meta 2023-04-28 05:57:47,006 root INFO copying build/lib/ansible_collections/cisco/iosxr/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/meta 2023-04-28 05:57:47,006 root INFO copying build/lib/ansible_collections/cisco/iosxr/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,006 root INFO copying build/lib/ansible_collections/cisco/iosxr/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,006 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/changelogs 2023-04-28 05:57:47,007 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/changelogs/fragments 2023-04-28 05:57:47,007 root INFO copying build/lib/ansible_collections/cisco/iosxr/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/changelogs/fragments 2023-04-28 05:57:47,007 root INFO copying build/lib/ansible_collections/cisco/iosxr/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/changelogs 2023-04-28 05:57:47,007 root INFO copying build/lib/ansible_collections/cisco/iosxr/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr/changelogs 2023-04-28 05:57:47,007 root INFO copying build/lib/ansible_collections/cisco/iosxr/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,008 root INFO copying build/lib/ansible_collections/cisco/iosxr/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,008 root INFO copying build/lib/ansible_collections/cisco/iosxr/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,008 root INFO copying build/lib/ansible_collections/cisco/iosxr/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/iosxr 2023-04-28 05:57:47,008 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight 2023-04-28 05:57:47,008 root INFO copying build/lib/ansible_collections/cisco/intersight/Development.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight 2023-04-28 05:57:47,009 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins 2023-04-28 05:57:47,009 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins 2023-04-28 05:57:47,009 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/doc_fragments 2023-04-28 05:57:47,009 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/doc_fragments/intersight.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/doc_fragments 2023-04-28 05:57:47,009 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,009 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_rest_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,010 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_ntp_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,010 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_local_user_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,010 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_boot_order_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,010 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_target_claim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,011 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,011 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_imc_access_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,011 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_server_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,011 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/modules/intersight_virtual_media_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/modules 2023-04-28 05:57:47,011 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/module_utils 2023-04-28 05:57:47,012 root INFO copying build/lib/ansible_collections/cisco/intersight/plugins/module_utils/intersight.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/plugins/module_utils 2023-04-28 05:57:47,012 root INFO copying build/lib/ansible_collections/cisco/intersight/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight 2023-04-28 05:57:47,012 root INFO copying build/lib/ansible_collections/cisco/intersight/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight 2023-04-28 05:57:47,012 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/meta 2023-04-28 05:57:47,012 root INFO copying build/lib/ansible_collections/cisco/intersight/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/meta 2023-04-28 05:57:47,013 root INFO copying build/lib/ansible_collections/cisco/intersight/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/meta 2023-04-28 05:57:47,013 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,013 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/claim_device.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,013 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/pxe_boot.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,013 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_vm_hosts.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,013 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/hcl_status.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,014 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/example_inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,014 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/hyperflex_edge_cluster_profiles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,014 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/update_standalone_inventory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,014 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/os_install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,014 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/update_hx_inventory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,015 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_server_profile_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,015 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/vlans_to_file.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,015 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/only_new_server_profiles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,015 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/devnet_inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,015 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/firmware_direct_download.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,016 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/example_hx_host_vars -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,016 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/ova_workflow.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,016 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_server_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,016 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/update_all_inventory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,016 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/profile_with_buckets.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,017 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_boot_order_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,017 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_lan_connectivity_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,017 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_imc_access_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,017 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/deploy_server_profiles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,017 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/server_actions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,018 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_port_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,018 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/derive_profiles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,018 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/update_hx_edge_inventory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,018 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/example_imm_inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,018 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/cos_server_policies_and_profiles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,019 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/vault_intersight_server_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,019 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_local_user_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,019 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/server_firmware.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,019 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_domain_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,019 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/profile_inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles 2023-04-28 05:57:47,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/servers 2023-04-28 05:57:47,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/servers/actions 2023-04-28 05:57:47,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/servers/actions/tasks 2023-04-28 05:57:47,020 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/servers/actions/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/servers/actions/tasks 2023-04-28 05:57:47,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies 2023-04-28 05:57:47,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies 2023-04-28 05:57:47,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support 2023-04-28 05:57:47,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support/tasks 2023-04-28 05:57:47,021 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support/tasks 2023-04-28 05:57:47,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network 2023-04-28 05:57:47,022 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network/tasks 2023-04-28 05:57:47,022 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network/tasks 2023-04-28 05:57:47,022 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version 2023-04-28 05:57:47,022 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version/tasks 2023-04-28 05:57:47,022 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version/tasks 2023-04-28 05:57:47,022 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential 2023-04-28 05:57:47,023 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential/tasks 2023-04-28 05:57:47,023 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential/tasks 2023-04-28 05:57:47,023 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc 2023-04-28 05:57:47,023 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc/tasks 2023-04-28 05:57:47,023 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc/tasks 2023-04-28 05:57:47,024 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile 2023-04-28 05:57:47,024 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/tasks 2023-04-28 05:57:47,024 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/tasks 2023-04-28 05:57:47,024 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/defaults 2023-04-28 05:57:47,024 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/defaults 2023-04-28 05:57:47,025 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi 2023-04-28 05:57:47,025 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi/tasks 2023-04-28 05:57:47,025 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi/tasks 2023-04-28 05:57:47,025 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network 2023-04-28 05:57:47,025 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network/tasks 2023-04-28 05:57:47,025 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network/tasks 2023-04-28 05:57:47,026 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version 2023-04-28 05:57:47,026 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version/tasks 2023-04-28 05:57:47,026 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version/tasks 2023-04-28 05:57:47,026 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles 2023-04-28 05:57:47,026 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles/tasks 2023-04-28 05:57:47,026 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles/tasks 2023-04-28 05:57:47,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy 2023-04-28 05:57:47,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy/tasks 2023-04-28 05:57:47,027 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy/tasks 2023-04-28 05:57:47,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage 2023-04-28 05:57:47,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage/tasks 2023-04-28 05:57:47,028 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage/tasks 2023-04-28 05:57:47,028 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy 2023-04-28 05:57:47,028 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy/tasks 2023-04-28 05:57:47,028 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy/tasks 2023-04-28 05:57:47,028 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config 2023-04-28 05:57:47,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config/tasks 2023-04-28 05:57:47,029 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config/tasks 2023-04-28 05:57:47,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter 2023-04-28 05:57:47,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter/tasks 2023-04-28 05:57:47,029 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter/tasks 2023-04-28 05:57:47,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage 2023-04-28 05:57:47,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage/tasks 2023-04-28 05:57:47,030 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage/tasks 2023-04-28 05:57:47,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config 2023-04-28 05:57:47,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config/tasks 2023-04-28 05:57:47,030 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config/tasks 2023-04-28 05:57:47,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile 2023-04-28 05:57:47,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/tasks 2023-04-28 05:57:47,031 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/tasks 2023-04-28 05:57:47,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/defaults 2023-04-28 05:57:47,031 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/defaults 2023-04-28 05:57:47,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org 2023-04-28 05:57:47,032 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org/tasks 2023-04-28 05:57:47,032 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org/tasks 2023-04-28 05:57:47,032 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies 2023-04-28 05:57:47,032 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies/tasks 2023-04-28 05:57:47,032 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies/tasks 2023-04-28 05:57:47,032 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_eth_network.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,033 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/servers_to_file.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,033 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/hyperflex_cluster_profiles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,033 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_ntp_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,033 root INFO copying build/lib/ansible_collections/cisco/intersight/playbooks/intersight_virtual_media_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/playbooks 2023-04-28 05:57:47,033 root INFO copying build/lib/ansible_collections/cisco/intersight/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight 2023-04-28 05:57:47,034 root INFO copying build/lib/ansible_collections/cisco/intersight/LICENSE.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight 2023-04-28 05:57:47,034 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/misc 2023-04-28 05:57:47,034 root INFO copying build/lib/ansible_collections/cisco/intersight/misc/CL2020 EMEAR DEVWKS-1542 Intersight Ansible Lab Guide.pdf -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/misc 2023-04-28 05:57:47,036 root INFO copying build/lib/ansible_collections/cisco/intersight/misc/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight/misc 2023-04-28 05:57:47,036 root INFO copying build/lib/ansible_collections/cisco/intersight/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/intersight 2023-04-28 05:57:47,036 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac 2023-04-28 05:57:47,036 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins 2023-04-28 05:57:47,037 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins 2023-04-28 05:57:47,037 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:47,037 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:47,037 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments/intent_params.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:47,037 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments/module_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:47,038 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/doc_fragments/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/doc_fragments 2023-04-28 05:57:47,038 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,038 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_equipment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,038 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_site_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,039 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag_member_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,039 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reports_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,039 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_workflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,039 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/client_detail_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,039 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,040 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reports_view_group_view_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,040 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,040 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/snmp_properties_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,040 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,041 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/swim_trigger_activation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,041 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/topology_site_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,041 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/cli_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,041 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/assign_device_to_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,041 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/topology_network_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,042 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/integration_settings_instances_itsm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,042 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/credential_to_site_by_siteid_create_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,042 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_credential_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,042 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/system_performance_historical_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,042 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,043 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/lan_automation_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,043 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_snmp_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,043 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_config_preview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,043 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_authorize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,043 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_border_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,044 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_provision_ssid_delete_reprovision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,044 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,044 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/projects_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,044 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,044 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/netconf_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,045 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_syslog_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,045 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/nfv_provision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,045 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_artifact_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,045 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,045 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/app_policy_default_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,046 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_term_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,046 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/global_credential_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,046 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,046 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/client_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,046 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/applications_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,047 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/endpoint_analytics_profiling_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,047 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/lan_automation_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,047 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,047 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/snmp_properties.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,047 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,048 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/snmpv2_write_community_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,048 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_provision_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,048 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/topology_physical_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,048 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/transit_peer_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,048 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_with_snmp_v3_des_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,049 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/interface_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,049 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sensor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,049 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/disasterrecovery_system_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,049 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/golden_image_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,049 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_claim_to_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,050 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/file_namespaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,050 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/itsm_cmdb_sync_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,050 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_accesspoint_configuration_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,050 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,050 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_email_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,051 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/file_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,051 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,051 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_config_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,051 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/itsm_integration_events_retry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,051 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,052 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_config_connector_types_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,052 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/client_proximity_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,052 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/interface_network_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,052 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,052 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_deregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,053 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_range_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,053 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_configurations_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,053 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/template_intent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,053 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/command_runner_run_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,053 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/compliance_device_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,054 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/disassociate_site_to_network_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,054 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_design_floormap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,054 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,054 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/qos_device_interface_info_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,054 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,055 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,055 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/task_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,055 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/service_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,055 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_custom_prompt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,055 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_dynamic_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,056 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_version_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,056 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_user_defined_field.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,056 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/application_sets_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,056 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_vlan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,056 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_devices_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,057 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/task_operation_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,057 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_interface_poe_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,057 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/integration_settings_instances_itsm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,057 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/path_trace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,057 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_authentication_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,058 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_replacement.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,058 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/app_policy_intent_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,058 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_claim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,058 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_linecard_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,058 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_global_polling_interval_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,059 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_interface_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,059 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_interface_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,059 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag_membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,059 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_authentication_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,059 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_user_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,060 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_device_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,060 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_import_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,060 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/path_trace_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,060 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_artifact_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,061 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,061 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/snmpv3_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,061 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_user_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,061 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,061 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/profiling_rules_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,062 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_multicast_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,062 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,062 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/security_advisories_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,062 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_email_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,062 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_email_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,063 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,063 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/swim_intent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,063 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_export_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,063 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_multicast.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,064 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/endpoint_analytics_profiling_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,064 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/system_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,064 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/role_permissions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,064 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,064 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_provision_device_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,065 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,065 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,065 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,065 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,065 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_ip_pool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,066 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_device_license_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,066 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_accespoint_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,066 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/swim_trigger_distribution.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,066 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,066 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/eox_status_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,067 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/nfv_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,067 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,067 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_project_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,067 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,067 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,068 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,068 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_edge_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,068 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/templates_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,068 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_interface_neighbor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,068 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,069 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_rest_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,069 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,069 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_device_deregistration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,069 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_interface_ospf_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,070 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,070 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,070 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_control_plane_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,070 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/topology_vlan_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,070 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/global_credential_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,071 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/security_advisories_ids_per_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,071 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,071 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,071 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sensor_test_run.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,071 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/application_sets_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,072 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,072 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_provision_access_point.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,072 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/lan_automation_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,072 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sp_profile_delete_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,072 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,073 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_device_license_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,073 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/profiling_rules_in_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,073 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_reboot_apreboot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,073 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/qos_device_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,073 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_inventory_insight_link_mismatch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,074 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_history_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,074 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,074 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_reboot_apreboot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,074 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sensor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,074 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,075 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/syslog_config_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,075 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,075 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/compliance_device_details_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,075 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/transit_peer_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,075 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_control_plane_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,076 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_credential_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,076 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/business_sda_hostonboarding_ssid_ippool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,076 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/system_performance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,076 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/platform_release_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,076 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_email_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,077 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/snmpv2_read_community_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,077 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_job_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,077 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/global_pool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,077 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_assign_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,077 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,078 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/disasterrecovery_system_operationstatus_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,078 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/compliance_device_status_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,078 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_device_registration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,078 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,078 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/interface_network_device_detail_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,079 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_export_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,079 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,079 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,079 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,079 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/nfv_provision_details.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,080 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/swim_import_via_url.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,080 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/syslog_config_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,080 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_update_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,080 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/security_advisories_devices_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,080 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/topology_layer_3_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,081 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/file_namespace_files_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,081 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_replacement_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,081 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/execute_suggested_actions_commands.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,081 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,081 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/authentication_import_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,082 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,082 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,082 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,082 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/threat_summary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,083 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/service_provider_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,083 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/issues_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,083 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_sensor_test_results_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,083 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,083 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_access_point_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,084 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_email_config_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,084 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/golden_tag_image_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,084 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/global_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,084 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/eox_status_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,084 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,085 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_provision_ssid_create_provision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,085 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,085 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,085 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_workflow_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,085 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/applications_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,086 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_smart_account_domains_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,086 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/swim_image_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,086 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/service_provider_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,086 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_virtual_account_change.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,086 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_global_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,087 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reports_executions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,087 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,087 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_parent_records_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,087 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/topology_layer_2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,088 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_assign_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,088 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_lexicographically_sorted_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,088 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_syslog_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,088 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/app_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,088 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/dnac_packages_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,089 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag_member_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,089 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_add.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,089 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,089 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/global_credential_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,089 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,090 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_polling_interval_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,090 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/users_external_servers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,090 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,090 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/user_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,090 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_module_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,091 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_dynamic_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,091 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_meraki_organization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,091 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/security_advisories_per_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,091 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_series_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,091 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,092 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sensor_test_template_duplicate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,092 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/http_write_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,092 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/nfv_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,092 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/business_sda_wireless_controller_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,092 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/authentication_policy_servers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,093 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_reset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,093 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,093 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_device_role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,093 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/compliance_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,093 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_rf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,094 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/business_sda_hostonboarding_ssid_ippool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,094 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/dnacaap_management_execution_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,094 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_syslog_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,094 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/applications_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,095 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_usage_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,095 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_webhook_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,095 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_provision_device_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,095 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_series_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,095 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/interface_operation_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,096 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/reports_view_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,096 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_credential_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,096 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/business_sda_virtual_network_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,096 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_credential_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,096 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/buildings_planned_access_points_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,097 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/lan_automation_log_by_serial_number_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,097 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_edge_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,097 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,097 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_stack_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,097 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/threat_detail_count.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,098 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,098 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/qos_device_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,098 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/template_preview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,098 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/lan_automation_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,098 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/service_provider_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,099 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_border_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,099 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/associate_site_to_network_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,099 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/global_credential_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,099 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_module_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,099 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_replacement_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,100 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,100 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/roles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,100 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/planned_access_points_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,100 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/security_advisories_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,100 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/compliance_device_by_id_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,101 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_import_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,101 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_ip_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,101 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_supervisor_card_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,101 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/discovery_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,101 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_wireless_lan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,102 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_email.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,102 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,102 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/interface_network_device_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,102 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,102 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,103 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,103 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/service_provider_profile_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,103 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_smart_account_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,103 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/file_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,104 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_global_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,104 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,104 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_intent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,104 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,104 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/service_provider_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,105 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,105 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_functional_capability_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,105 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_by_serial_number_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,105 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/applications.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,105 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/threat_detail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,106 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_user_defined_field_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,106 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_sync_result_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,106 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/dna_command_runner_keywords_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,106 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_enterprise_ssid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,106 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/lan_automation_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,107 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_device_unclaim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,107 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_intent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,107 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_provision_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,107 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_chassis_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,108 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,108 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/system_health_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,108 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag_member_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,108 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/nfv_provision_detail_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,108 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_custom_prompt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,109 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/client_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,109 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_syslog_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,109 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_enterprise_ssid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,109 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/configuration_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,109 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/business_sda_wireless_controller_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,110 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_fabric_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,110 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_psk_override.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,110 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/global_credential_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,110 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_webhook_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,110 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/application_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,111 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,111 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/compliance_check_run.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,111 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/platform_nodes_configuration_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,111 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/task_tree_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,111 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_api_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,112 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_family_identifiers_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,112 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_rest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,112 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,112 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/issues_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,112 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_design_floormap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,113 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/task_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,113 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_register_for_wsa_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,113 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/wireless_rf_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,113 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/swim_import_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,113 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_accounts_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,114 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/tag_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,114 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_poe_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,114 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/authentication_import_certificate_p12.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,114 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_access_point.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,114 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_replacement_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,115 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_rest_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,115 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/golden_tag_image_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,115 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/event_email_config_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,115 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,115 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/sensor_test_template_edit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,116 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/network_device_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,116 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_workflow_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,116 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/pnp_server_profile_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,116 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/http_read_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,116 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,117 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/site_membership_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,117 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/device_interface_isis_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,117 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/itsm_integration_events_failed_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,117 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/accesspoint_configuration_details_by_task_id_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,118 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/modules/license_virtual_account_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/modules 2023-04-28 05:57:47,118 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins 2023-04-28 05:57:47,118 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:47,118 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/plugin_utils/exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:47,118 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/plugin_utils/dnac.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:47,118 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/plugin_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/plugin_utils 2023-04-28 05:57:47,119 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,119 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_equipment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,119 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_site_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,120 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag_member_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,120 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reports_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,120 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_workflow.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,120 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/client_detail_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,120 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,121 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reports_view_group_view_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,121 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,121 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/snmp_properties_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,121 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,121 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/swim_trigger_activation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,122 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/topology_site_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,122 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/cli_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,122 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/assign_device_to_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,122 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/topology_network_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,122 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/integration_settings_instances_itsm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,123 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/credential_to_site_by_siteid_create_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,123 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_credential_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,123 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/system_performance_historical_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,123 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,123 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/lan_automation_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,124 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_snmp_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,124 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_config_preview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,124 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_authorize.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,124 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_border_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,124 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_provision_ssid_delete_reprovision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,125 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,125 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/projects_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,125 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,125 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/netconf_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,125 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_syslog_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,126 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/nfv_provision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,126 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_artifact_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,126 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,126 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/app_policy_default_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,126 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_term_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,127 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/global_credential_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,127 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,127 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/client_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,127 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/applications_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,127 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/endpoint_analytics_profiling_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,128 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/lan_automation_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,128 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,128 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/snmp_properties.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,128 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,128 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/snmpv2_write_community_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,129 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_provision_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,129 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/topology_physical_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,129 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/transit_peer_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,130 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_with_snmp_v3_des_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,130 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/interface_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,130 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sensor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,130 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/disasterrecovery_system_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,130 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/golden_image_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,131 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_claim_to_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,131 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/file_namespaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,131 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/itsm_cmdb_sync_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,131 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_accesspoint_configuration_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,131 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,132 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_email_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,132 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/file_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,132 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,132 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_config_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,132 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/itsm_integration_events_retry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,133 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,133 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_config_connector_types_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,133 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/client_proximity_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,133 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/interface_network_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,133 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,134 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_deregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,134 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_range_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,134 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_configurations_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,134 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/command_runner_run_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,134 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/compliance_device_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,135 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/disassociate_site_to_network_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,135 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_design_floormap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,135 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,135 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/qos_device_interface_info_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,135 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,136 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,136 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/task_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,136 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/service_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,136 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_custom_prompt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,136 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_dynamic_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,137 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_version_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,137 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_user_defined_field.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,137 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/application_sets_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,137 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_vlan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,137 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_devices_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,138 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/task_operation_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,138 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_interface_poe_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,138 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/integration_settings_instances_itsm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,138 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/path_trace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,139 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_authentication_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,139 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_replacement.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,139 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/app_policy_intent_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,139 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_claim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,139 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_linecard_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,140 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_global_polling_interval_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,140 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_interface_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,140 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_interface_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,140 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag_membership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,140 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_authentication_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,141 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_user_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,141 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_device_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,141 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_import_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,141 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/path_trace_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,141 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_artifact_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,142 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,142 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/snmpv3_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,142 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_user_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,142 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,142 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/profiling_rules_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,143 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_multicast_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,143 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,143 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/security_advisories_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,143 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_email_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,143 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_details_email_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,144 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,144 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_export_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,144 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_multicast.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,144 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/endpoint_analytics_profiling_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,144 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/system_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,145 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/role_permissions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,145 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,145 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_provision_device_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,145 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,145 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,146 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,146 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,146 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_ip_pool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,146 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_device_license_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,147 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_accespoint_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,147 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/swim_trigger_distribution.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,147 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,147 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/eox_status_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,147 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/nfv_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,148 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,148 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_project_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,148 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,148 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,148 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,149 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_edge_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,149 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/templates_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,149 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_interface_neighbor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,149 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,149 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_rest_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,150 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,150 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_device_deregistration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,150 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_interface_ospf_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,150 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,150 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,151 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_control_plane_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,151 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/topology_vlan_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,151 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/global_credential_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,151 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/security_advisories_ids_per_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,151 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,152 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sensor_test_run.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,152 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/application_sets_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,152 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,152 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_provision_access_point.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,152 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/lan_automation_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,153 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sp_profile_delete_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,153 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,153 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_device_license_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,153 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/profiling_rules_in_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,153 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/qos_device_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,154 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_inventory_insight_link_mismatch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,154 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_history_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,154 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,154 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_reboot_apreboot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,154 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sensor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,155 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,155 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/syslog_config_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,155 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,155 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/compliance_device_details_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,156 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/transit_peer_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,156 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_control_plane_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,156 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_credential_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,156 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/business_sda_hostonboarding_ssid_ippool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,156 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/system_performance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,157 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/platform_release_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,157 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_email_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,157 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/snmpv2_read_community_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,157 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_job_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,157 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/global_pool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,158 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_assign_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,158 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,158 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/disasterrecovery_system_operationstatus_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,158 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/compliance_device_status_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,158 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_device_registration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,159 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,159 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/interface_network_device_detail_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,159 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_export_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,159 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,159 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,160 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,160 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/nfv_provision_details.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,160 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/swim_import_via_url.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,160 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/syslog_config_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,160 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_update_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,161 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/security_advisories_devices_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,161 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/topology_layer_3_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,161 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/file_namespace_files_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,161 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_replacement_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,161 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/execute_suggested_actions_commands.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,162 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,162 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/authentication_import_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,162 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,162 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,162 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,163 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/threat_summary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,163 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/service_provider_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,163 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/issues_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,163 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_sensor_test_results_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,163 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,164 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_access_point_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,164 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_email_config_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,164 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/golden_tag_image_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,164 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/global_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,164 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/eox_status_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,165 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,165 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_provision_ssid_create_provision.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,165 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reports.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,165 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,165 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_workflow_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,166 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/applications_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,166 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_smart_account_domains_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,166 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/swim_image_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,166 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/service_provider_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,166 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_virtual_account_change.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,167 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_global_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,167 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reports_executions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,167 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,167 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_parent_records_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,168 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/topology_layer_2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,168 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_assign_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,168 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_lexicographically_sorted_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,168 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_syslog_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,168 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/app_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,169 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/dnac_packages_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,169 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag_member_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,169 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_add.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,169 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,169 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/global_credential_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,170 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,170 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_polling_interval_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,170 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/users_external_servers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,170 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,170 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/user_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,171 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_module_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,171 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_dynamic_interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,171 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_meraki_organization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,171 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/security_advisories_per_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,171 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_series_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,172 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,172 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sensor_test_template_duplicate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,172 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/http_write_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,172 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/nfv_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,172 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/business_sda_wireless_controller_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,173 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/authentication_policy_servers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,173 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_reset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,173 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,173 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_device_role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,173 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/compliance_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,174 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_rf_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,174 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/business_sda_hostonboarding_ssid_ippool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,174 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/dnacaap_management_execution_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,174 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_details_syslog_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,174 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/applications_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,175 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_usage_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,175 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_webhook_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,175 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_provision_device_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,175 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_series_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,176 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/interface_operation_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,176 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/reports_view_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,176 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_credential_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,176 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/business_sda_virtual_network_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,176 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_credential_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,177 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/buildings_planned_access_points_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,177 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/lan_automation_log_by_serial_number_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,177 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_edge_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,177 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,177 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_stack_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,178 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/threat_detail_count.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,178 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,178 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/qos_device_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,178 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/template_preview.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,178 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/lan_automation_log_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,179 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/service_provider_v2_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,179 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_border_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,179 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/associate_site_to_network_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,179 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/global_credential_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,179 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_module_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,180 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_replacement_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,180 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/interface_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,180 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/roles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,180 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/planned_access_points_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,180 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/security_advisories_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,181 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/compliance_device_by_id_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,181 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_import_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,181 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_ip_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,181 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_supervisor_card_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,181 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/discovery_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,182 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_wireless_lan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,182 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_email.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,182 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,182 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/interface_network_device_range_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,182 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_virtual_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,183 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,183 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,183 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/service_provider_profile_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,183 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_smart_account_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,183 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/file_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,184 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_global_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,184 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,184 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,184 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/service_provider_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,184 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,185 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_functional_capability_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,185 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_by_serial_number_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,185 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/applications.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,185 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/threat_detail.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,185 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_user_defined_field_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,186 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_sync_result_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,186 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/dna_command_runner_keywords_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,186 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_enterprise_ssid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,186 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/lan_automation_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,187 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_device_unclaim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,187 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_provision_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,187 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_chassis_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,187 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,187 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/system_health_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,188 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag_member_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,188 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/nfv_provision_detail_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,188 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_custom_prompt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,188 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/client_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,188 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_syslog_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,189 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_enterprise_ssid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,189 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/configuration_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,189 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/business_sda_wireless_controller_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,189 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_fabric_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,189 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_psk_override.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,190 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/global_credential_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,190 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_webhook_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,190 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/application_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,190 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_health_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,190 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/compliance_check_run.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,191 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/platform_nodes_configuration_summary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,191 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/task_tree_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,191 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_api_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,191 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_family_identifiers_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,191 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_rest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,192 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_device_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,192 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/issues_enrichment_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,192 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_design_floormap_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,192 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/task_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,192 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_register_for_wsa_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,193 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/wireless_rf_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,193 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/swim_import_local.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,193 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_virtual_accounts_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,193 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/tag_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,193 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_poe_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,194 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/authentication_import_certificate_p12.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,194 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_access_point.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,194 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_replacement_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,194 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_subscription_details_rest_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,194 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/golden_tag_image_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,195 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/event_email_config_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,195 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,195 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/sensor_test_template_edit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,195 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/network_device_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,195 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_workflow_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,196 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/pnp_server_profile_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,196 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/http_read_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,196 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,196 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/site_membership_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,196 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/device_interface_isis_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,197 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/itsm_integration_events_failed_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,197 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/accesspoint_configuration_details_by_task_id_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,197 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/action/license_virtual_account_details_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/action 2023-04-28 05:57:47,197 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:47,197 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/module_utils/exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:47,198 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/module_utils/dnac.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:47,198 root INFO copying build/lib/ansible_collections/cisco/dnac/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/plugins/module_utils 2023-04-28 05:57:47,198 root INFO copying build/lib/ansible_collections/cisco/dnac/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac 2023-04-28 05:57:47,198 root INFO copying build/lib/ansible_collections/cisco/dnac/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac 2023-04-28 05:57:47,199 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/meta 2023-04-28 05:57:47,199 root INFO copying build/lib/ansible_collections/cisco/dnac/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/meta 2023-04-28 05:57:47,199 root INFO copying build/lib/ansible_collections/cisco/dnac/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac 2023-04-28 05:57:47,199 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,200 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/credentials.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,200 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/credentials.template -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,200 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/sda_fabric_site.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,200 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/pnp_device.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,200 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/configuration_template_version_create.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,201 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/import_image_file.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,201 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/wireless_enterprise_ssid.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,201 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/reserve_ip_subpool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,201 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/global_credentials_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,201 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/sda_fabric.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,201 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/global_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,202 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/tag.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,202 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/hosts -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,202 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/network_device_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,202 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,202 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/test_swim_module.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,203 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/command_runner_run_command.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,203 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/download_device_cmd_runner_output.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,203 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/authentication_import.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,203 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/device_details.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,203 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks/files 2023-04-28 05:57:47,204 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/files/test.template -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks/files 2023-04-28 05:57:47,204 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/applications.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,204 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/reports_executions_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,204 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/template_pnp_intent.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,204 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/image_details.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,205 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/network_device_custom_prompt_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,205 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/global_credentials.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,205 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/application_set_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,205 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/sda_virtual_network_v2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,205 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/application_sets.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,206 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/discovery.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,206 root INFO copying build/lib/ansible_collections/cisco/dnac/playbooks/network_device_update_role.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/playbooks 2023-04-28 05:57:47,206 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/changelogs 2023-04-28 05:57:47,206 root INFO copying build/lib/ansible_collections/cisco/dnac/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac/changelogs 2023-04-28 05:57:47,206 root INFO copying build/lib/ansible_collections/cisco/dnac/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac 2023-04-28 05:57:47,207 root INFO copying build/lib/ansible_collections/cisco/dnac/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac 2023-04-28 05:57:47,207 root INFO copying build/lib/ansible_collections/cisco/dnac/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/dnac 2023-04-28 05:57:47,207 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,207 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins 2023-04-28 05:57:47,207 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:47,208 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:47,208 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/doc_fragments/module_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:47,208 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/doc_fragments/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/doc_fragments 2023-04-28 05:57:47,208 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,209 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,209 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,209 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,209 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_register.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,209 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/rest_id_store.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,210 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/hotpatch_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,210 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_authentication_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,210 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trusted_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,210 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_bindings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,210 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_smart_state_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,211 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_services_profiler_probe_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,211 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,211 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_trusted_domains_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,211 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_authentication_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,211 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/system_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,212 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/backup_cancel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,212 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/portal_global_setting_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,212 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_device_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,212 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_user_group_by_username_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,212 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/backup_restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,213 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/system_certificate_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,213 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_service_unregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,213 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pan_ha_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,213 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoint_by_mac_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,213 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/admin_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,214 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/identity_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,214 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,214 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,214 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,214 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_deny.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,215 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_ssid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,215 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,215 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_egress_matrices_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,215 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_external_servers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,215 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,216 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,216 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,216 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,216 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,216 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_device_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,217 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,217 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,217 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/hotpatch_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,217 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/proxy_connection_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,217 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,218 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_posture_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,218 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_authorization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,218 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attribute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,218 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_connections_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,218 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sponsored_guest_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,219 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_active_list_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,219 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,219 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/filter_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,219 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_performances_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,219 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_promotion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,220 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/telemetry_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,220 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_email.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,220 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,220 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_service_register.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,220 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/csr_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,221 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_service_lookup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,221 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sgt_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,221 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_leave_domain_with_all_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,221 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_session_for_recovery_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,221 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,222 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_by_os_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,222 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,222 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,222 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,222 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trusted_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,223 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_authorization_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,223 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/allowed_protocols_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,223 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_primary_to_standalone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,223 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_reauthentication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,224 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_acl_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,224 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,224 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,224 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_node_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,224 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_policy_set_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,224 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,225 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_command_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,225 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,225 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/patch_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,225 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/transport_gateway_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,225 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,226 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,226 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,226 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_join_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,226 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_authorization_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,226 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/portal_theme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,227 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/renew_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,227 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_deployment_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,227 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,227 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_endpoint_clear.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,227 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_network_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,228 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,228 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,228 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_authorization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,228 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_profiler_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,229 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_group_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,229 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_group_node_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,229 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,229 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_server_sequence_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,229 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_failures_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,230 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_time_date_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,230 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,230 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/backup_schedule_config_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,230 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_external_servers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,230 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sponsor_group_member_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,231 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sponsor_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,231 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sponsor_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,231 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/authorization_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,231 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/personas_check_standalone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,231 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_identity_stores_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,232 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/csr_export_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,232 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,232 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/internal_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,232 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_authentication_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,232 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/px_grid_node_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,233 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/allowed_protocols.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,233 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,233 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,233 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_access_secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,233 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/internal_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,234 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_connections_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,234 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_change_sponsor_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,234 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_authorization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,234 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_network_condition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,234 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,235 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,235 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/hotspot_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,235 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/support_bundle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,235 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_policy_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,236 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_secondary_to_primary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,236 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,236 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_disconnect_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,236 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_tier_state_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,236 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,237 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,237 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,237 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/byod_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,237 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_network_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,237 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_by_nas_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,238 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_session_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,238 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,238 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_delete_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,238 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_clear_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,238 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_leave_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,239 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_nbar_app.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,239 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_sessions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,239 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/support_bundle_download.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,239 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_connections.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,239 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/downloadable_acl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,240 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,240 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_vpns_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,240 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_location_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,240 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,240 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,241 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_services_profiler_probe_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,241 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_acl_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,241 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_standalone_to_primary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,241 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trusted_certificate_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,241 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,242 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,242 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_device_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,242 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_service_names_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,242 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,243 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_sessions_by_session_id_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,243 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/bind_signed_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,243 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_release_rejected_endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,243 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/px_grid_node_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,243 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,244 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/transport_gateway_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,244 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/hotspot_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,244 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/my_device_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,244 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,244 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,245 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/aci_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,245 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_services_interfaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,245 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/system_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,245 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,245 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pan_ha_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,246 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,246 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sgt_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,246 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/personas_register_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,246 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_reset_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,246 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,247 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/backup_schedule_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,247 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,247 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/deployment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,247 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/system_certificate_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,247 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_eval_license_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,248 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_security_group_acls_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,248 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,248 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/proxy_connection_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,248 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_vpns_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,248 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/radius_server_sequence_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,249 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_profiles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,249 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/system_certificate_export_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,249 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/personas_promote_primary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,249 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/portal_global_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,249 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_time_date_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,250 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_session_by_mac_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,250 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,250 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,250 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_user_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,250 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_command_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,251 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,251 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/system_config_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,251 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_device_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,251 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/native_supplicant_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,251 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,252 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,252 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_by_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,252 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,252 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,252 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/downloadable_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,253 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_egress_policies_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,253 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,253 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_nbar_app_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,253 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_join_domain_with_all_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,254 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_security_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,254 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_command_sets_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,254 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_service_name_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,254 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,255 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_connection_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,255 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,255 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,255 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_authentication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,255 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_group_node_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,256 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/support_bundle_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,256 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/self_registered_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,256 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,256 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_tier_state_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,257 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/my_device_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,257 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tasks_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,257 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,257 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sponsored_guest_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,257 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sgt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,258 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_smtp_notification_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,258 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_account_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,258 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,258 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_authentication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,258 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules_reset_hitcounts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,259 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/px_grid_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,259 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,259 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,259 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_reinstate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,259 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sms_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,260 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/native_supplicant_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,260 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_account_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,260 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_type_sms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,260 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,260 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,261 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,261 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,261 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/patch_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,261 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_endpoint_apply.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,262 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,262 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/threat_vulnerabilities_clear.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,262 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,262 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,262 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,263 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/rest_id_store_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,263 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,263 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,263 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attribute_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,263 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_replication_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,264 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_is_user_member_of_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,264 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/id_store_sequence_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,264 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/certificate_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,264 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_policy_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,264 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_time_date_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,265 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,265 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_network_condition_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,265 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_vpns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,265 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/identity_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,265 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,266 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,266 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_account_activate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,266 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,266 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,266 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,267 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/csr_generate_intermediate_ca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,267 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/external_radius_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,267 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_ssid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,267 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/authorization_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,267 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_healths_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,268 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/resource_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,268 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sponsor_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,268 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_registration_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,268 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_profiles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,268 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/ise_root_ca_regenerate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,269 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,269 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,269 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_services_sxp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,269 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/aci_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,269 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,270 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,270 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_auth_list_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,270 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/portal_theme_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,270 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/repository_files_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,271 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_smart_state_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,271 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,271 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,271 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_smtp_notification_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,271 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/personas_update_roles_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,272 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,272 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sgt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,272 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,272 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,272 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_connections_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,273 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pan_ha.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,273 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,273 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/self_registered_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,273 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_deployment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,274 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/id_store_sequence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,274 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,274 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/filter_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,274 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_dictionary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,274 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/aci_bindings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,275 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,275 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/backup_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,275 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/px_grid_settings_auto_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,275 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/hotpatch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,275 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_time_date_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,276 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_active_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,276 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_by_mac_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,276 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/repository_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,276 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_endpoint_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,276 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,277 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_service_reregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,277 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sponsor_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,277 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/csr_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,277 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,277 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_suspend.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,278 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/backup_last_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,278 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,278 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_deregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,278 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,278 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_policy_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,279 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_acl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,279 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/personas_export_certs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,279 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_endpoint_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,279 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/session_service_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,279 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_get_rejected_endpoints_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,280 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_type_email.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,280 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_set_all_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,280 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/node_services_sxp_interfaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,280 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_session_by_username_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,280 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trusted_certificate_export_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,281 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_failure_reasons_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,281 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/selfsigned_certificate_generate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,281 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/csr_generate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,281 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_registration_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,281 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/anc_endpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,282 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/certificate_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,282 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_groups_by_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,282 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/byod_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,282 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_settings_auto_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,282 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,283 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_user_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,283 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/pxgrid_node_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,283 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,283 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,283 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/endpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,284 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/device_administration_profiles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,284 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_security_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,284 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/external_radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,284 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/profiler_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,285 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,285 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/active_directory_add_groups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,285 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/certificate_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,285 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/licensing_feature_to_tier_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,285 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/radius_server_sequence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,286 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,286 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/aci_test_connectivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,286 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/network_access_identity_stores_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,286 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/patch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,286 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/tacacs_server_sequence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,287 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,287 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/sxp_vpns_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,287 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/guest_user_sms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,287 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/modules/mnt_athentication_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/modules 2023-04-28 05:57:47,287 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:47,288 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/plugin_utils/exceptions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:47,288 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/plugin_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:47,288 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/plugin_utils/personas_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:47,288 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/plugin_utils/ise.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/plugin_utils 2023-04-28 05:57:47,289 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,289 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,289 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_policy_set_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,289 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,289 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_register.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,290 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/rest_id_store.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,290 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/hotpatch_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,290 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_authentication_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,290 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trusted_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,290 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_bindings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,291 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_smart_state_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,291 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_services_profiler_probe_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,291 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,291 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_trusted_domains_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,291 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_authentication_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,292 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/system_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,292 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/backup_cancel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,292 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/portal_global_setting_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,292 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_device_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,292 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_user_group_by_username_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,293 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/backup_restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,293 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/system_certificate_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,293 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_service_unregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,293 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pan_ha_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,293 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_endpoint_by_mac_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,294 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/admin_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,294 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/identity_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,294 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,294 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,294 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,295 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_deny.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,295 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_ssid_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,295 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,295 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_egress_matrices_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,295 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_external_servers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,296 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,296 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,296 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,296 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,296 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,297 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_device_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,297 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,297 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,297 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/hotpatch_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,297 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/proxy_connection_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,298 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,298 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_posture_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,298 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_authorization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,298 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attribute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,298 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_connections_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,299 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sponsored_guest_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,299 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_active_list_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,299 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_local_bindings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,299 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/filter_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,299 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_performances_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,300 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_promotion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,300 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/telemetry_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,300 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_email.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,300 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,300 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_service_register.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,301 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/csr_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,301 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_service_lookup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,301 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sgt_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,301 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_leave_domain_with_all_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,301 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_session_for_recovery_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,302 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,302 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_by_os_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,302 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,302 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,302 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_authentication_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,303 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trusted_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,303 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_authorization_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,303 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/allowed_protocols_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,303 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_primary_to_standalone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,304 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_reauthentication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,304 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_acl_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,304 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_group_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,304 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_authentication_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,304 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_node_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,305 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_policy_set_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,305 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,305 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_command_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,305 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,305 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/patch_install.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,306 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/transport_gateway_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,306 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,306 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,306 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,306 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_join_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,307 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_authorization_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,307 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/portal_theme.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,307 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/renew_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,307 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_deployment_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,307 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,308 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_endpoint_clear.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,308 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_network_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,308 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,308 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,308 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_authorization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,309 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_profiler_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,309 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_group_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,309 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_group_node_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,309 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,309 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_server_sequence_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,310 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_failures_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,310 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_time_date_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,310 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,310 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/backup_schedule_config_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,311 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_external_servers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,311 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sponsor_group_member_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,311 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sponsor_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,311 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sponsor_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,311 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/authorization_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,312 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/personas_check_standalone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,312 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_identity_stores_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,312 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/csr_export_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,312 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,312 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/internal_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,313 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_authentication_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,313 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/px_grid_node_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,313 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/allowed_protocols.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,313 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,313 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,314 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_access_secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,314 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/internal_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,314 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_connections_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,314 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_change_sponsor_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,314 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_authorization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,315 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_network_condition.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,315 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,315 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,315 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/hotspot_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,315 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/support_bundle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,316 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_policy_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,316 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_secondary_to_primary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,316 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,316 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_disconnect_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,316 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_tier_state_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,317 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,317 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,317 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_clone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,317 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/byod_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,317 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_network_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,318 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_by_nas_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,318 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_session_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,318 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,318 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_delete_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,319 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_clear_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,319 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_leave_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,319 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_nbar_app.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,319 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_sessions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,319 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/support_bundle_download.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,320 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_connections.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,320 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/downloadable_acl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,320 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,320 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_vpns_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,320 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_location_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,321 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,321 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,321 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_services_profiler_probe_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,321 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_acl_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,321 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_standalone_to_primary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,322 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trusted_certificate_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,322 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,322 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,322 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_device_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,322 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_service_names_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,323 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,323 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_sessions_by_session_id_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,323 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/bind_signed_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,323 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_release_rejected_endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,323 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/px_grid_node_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,324 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,324 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/transport_gateway_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,324 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/hotspot_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,324 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/my_device_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,324 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,325 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/aci_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,325 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_services_interfaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,325 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/system_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,325 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,326 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pan_ha_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,326 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_by_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,326 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sgt_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,326 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/personas_register_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,326 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_reset_password.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,327 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,327 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/backup_schedule_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,327 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,327 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/deployment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,327 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/system_certificate_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,328 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_eval_license_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,328 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_security_group_acls_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,328 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,328 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/proxy_connection_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,328 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_vpns_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,329 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/radius_server_sequence_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,329 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_profiles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,329 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/system_certificate_export_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,329 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/personas_promote_primary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,329 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/portal_global_setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,330 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_time_date_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,330 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_session_by_mac_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,330 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_group_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,330 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_authentication_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,330 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_user_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,331 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_command_sets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,331 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_dictionary_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,331 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/system_config_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,331 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_device_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,331 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/native_supplicant_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,332 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,332 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,332 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_by_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,332 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,332 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,333 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/downloadable_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,333 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_egress_policies_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,333 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,333 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_nbar_app_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,334 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_join_domain_with_all_nodes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,334 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_security_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,334 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_command_sets_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,334 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_service_name_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,334 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,335 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_connection_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,335 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,335 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,335 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_authentication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,335 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_group_node_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,336 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/support_bundle_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,336 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/self_registered_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,336 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,336 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_tier_state_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,336 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/my_device_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,337 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tasks_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,337 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,337 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sponsored_guest_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,337 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sgt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,337 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_smtp_notification_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,338 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_account_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,338 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/egress_matrix_cell.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,338 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_authentication_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,338 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules_reset_hitcounts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,338 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/px_grid_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,339 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_authorization_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,339 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,339 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_reinstate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,339 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sms_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,339 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/native_supplicant_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,340 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_account_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,340 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_type_sms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,340 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,340 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,340 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,341 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,341 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/patch_rollback.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,341 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_endpoint_apply.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,341 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,342 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/threat_vulnerabilities_clear.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,342 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,342 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,342 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,342 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/rest_id_store_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,343 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,343 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,343 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attribute_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,343 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_replication_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,343 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_is_user_member_of_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,344 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/id_store_sequence_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,344 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/certificate_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,344 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_policy_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,344 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_time_date_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,344 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,345 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_network_condition_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,345 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_vpns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,345 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/identity_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,345 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_conditions_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,345 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy_all.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,346 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_account_activate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,346 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,346 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,346 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,347 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/csr_generate_intermediate_ca.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,347 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/external_radius_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,347 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_ssid.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,347 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/authorization_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,347 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_healths_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,348 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/resource_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,348 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sponsor_portal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,348 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_registration_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,348 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_profiles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,348 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/ise_root_ca_regenerate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,349 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,349 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,349 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_services_sxp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,349 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/aci_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,349 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,350 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,350 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_auth_list_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,350 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/portal_theme_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,350 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/repository_files_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,350 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_smart_state_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,351 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,351 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,351 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_smtp_notification_settings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,351 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/personas_update_roles_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,351 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,352 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sgt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,352 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,352 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,352 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_connections_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,352 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pan_ha.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,353 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,353 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/self_registered_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,353 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_deployment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,353 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/id_store_sequence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,354 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_policy_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,354 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/filter_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,354 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_dictionary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,354 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/aci_bindings_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,354 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_policy_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,355 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/backup_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,355 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/px_grid_settings_auto_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,355 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/hotpatch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,355 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_time_date_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,355 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_active_count_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,356 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_by_mac_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,356 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/repository_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,356 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_endpoint_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,356 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_authorization_rules_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,356 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_service_reregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,357 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sponsor_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,357 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/csr_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,357 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,357 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_suspend.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,357 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/backup_last_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,358 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_conditions.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,358 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_deregister.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,358 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,358 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_policy_bulk_monitor_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,358 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_acl_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,359 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/personas_export_certs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,359 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_endpoint_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,359 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/session_service_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,359 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_get_rejected_endpoints_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,359 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_type_email.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,360 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_set_all_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,360 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/node_services_sxp_interfaces_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,360 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_session_by_username_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,360 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trusted_certificate_export_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,360 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_failure_reasons_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,361 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/selfsigned_certificate_generate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,361 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/csr_generate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,361 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_registration_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,361 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/anc_endpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,361 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/certificate_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,362 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_groups_by_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,362 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/byod_portal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,362 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_settings_auto_approve.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,362 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_authorization_reset_hitcount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,363 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_user_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,363 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/pxgrid_node_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,363 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,363 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_delete.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,363 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/endpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,364 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/device_administration_profiles_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,364 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_security_groups_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,364 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/external_radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,364 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/profiler_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,364 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,365 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/active_directory_add_groups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,365 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/certificate_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,365 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/licensing_feature_to_tier_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,365 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/radius_server_sequence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,365 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,366 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/aci_test_connectivity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,366 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/network_access_identity_stores_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,366 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/patch_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,366 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/tacacs_server_sequence.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,367 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_create.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,367 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/sxp_vpns_bulk_request.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,367 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/guest_user_sms.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,367 root INFO copying build/lib/ansible_collections/cisco/ise/plugins/action/mnt_athentication_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/plugins/action 2023-04-28 05:57:47,367 root INFO copying build/lib/ansible_collections/cisco/ise/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,368 root INFO copying build/lib/ansible_collections/cisco/ise/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,368 root INFO copying build/lib/ansible_collections/cisco/ise/hosts -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,368 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/meta 2023-04-28 05:57:47,368 root INFO copying build/lib/ansible_collections/cisco/ise/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/meta 2023-04-28 05:57:47,369 root INFO copying build/lib/ansible_collections/cisco/ise/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,369 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,369 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/credentials.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,369 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/credentials.template -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,369 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/byod_portal.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,370 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/trustsec_vn_vlan_mapping.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,370 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/sponsor_portal.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,370 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/backup_restore.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,370 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_conditions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,371 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/backup_schedule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,371 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/support_bundle.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,371 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/my_device_portal.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,371 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/playbookstest.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,371 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/device_administration_time_date_conditions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,371 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/active_directory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,372 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/trustsec_nbarapp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,372 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/certificate_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,372 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/allowed_protocols.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,372 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/egress_matrix_cell.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,372 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_device_group_deparments.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,373 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/endpoint.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,373 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks/vars 2023-04-28 05:57:47,373 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/vars/device_administration_time_date_conditions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks/vars 2023-04-28 05:57:47,373 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/hosts -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,373 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/filter_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,374 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_dictionary_attribute.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,374 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/internal_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,374 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/native_supplicant_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,374 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_authorization_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,374 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/downloadable_acl.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,375 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/deployment_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,375 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/azure_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,375 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/profiler-services.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,375 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_dictionary.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,375 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/portal_global_setting.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,376 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/device_administration_authorization_exception_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,376 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/device_administration_policy_set.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,376 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/backup_create.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,376 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/b.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,376 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/device_administration_network_conditions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,377 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/aci_settings.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,377 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_device_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,377 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_device.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,377 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/system_certificate.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,377 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/identity_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,378 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/trustsec_sg_vn_mapping.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,378 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/csr_export.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,378 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/authorization_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,378 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_authentication_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,378 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/device_administration_authorization_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,378 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_authorization_exception_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,379 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/endpoint_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,379 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_network_condition.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,379 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/device_administration_authorization_global_exception_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,380 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/portal_theme.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,380 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/personas_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,380 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_authorization_global_exception_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,380 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/anc_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,380 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/certificates.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,381 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_time_date_conditions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,381 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/trustsec_vn.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,381 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/certificate_management.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,381 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/device_administration_authentication_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,382 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks/group_vars 2023-04-28 05:57:47,382 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/group_vars/ise_servers -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks/group_vars 2023-04-28 05:57:47,382 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/network_access_policy_set.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,382 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/aws_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,382 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/radius_server_sequence.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,382 root INFO copying build/lib/ansible_collections/cisco/ise/playbooks/endpoint_certificate.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/playbooks 2023-04-28 05:57:47,383 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/changelogs 2023-04-28 05:57:47,383 root INFO copying build/lib/ansible_collections/cisco/ise/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/changelogs 2023-04-28 05:57:47,383 root INFO copying build/lib/ansible_collections/cisco/ise/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,383 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles 2023-04-28 05:57:47,384 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment 2023-04-28 05:57:47,384 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:47,384 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks/large_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:47,384 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks/small_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:47,384 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:47,384 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tasks/medium_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tasks 2023-04-28 05:57:47,385 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/defaults 2023-04-28 05:57:47,385 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/defaults 2023-04-28 05:57:47,385 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/handlers 2023-04-28 05:57:47,385 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/handlers 2023-04-28 05:57:47,385 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment 2023-04-28 05:57:47,386 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tests 2023-04-28 05:57:47,386 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tests 2023-04-28 05:57:47,386 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/tests 2023-04-28 05:57:47,386 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/vars 2023-04-28 05:57:47,386 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/vars 2023-04-28 05:57:47,387 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/meta 2023-04-28 05:57:47,387 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment/meta 2023-04-28 05:57:47,387 root INFO copying build/lib/ansible_collections/cisco/ise/roles/personas_deployment/.travis.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/personas_deployment 2023-04-28 05:57:47,387 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment 2023-04-28 05:57:47,387 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks 2023-04-28 05:57:47,387 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks 2023-04-28 05:57:47,388 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:47,388 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/large_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:47,388 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/single_node.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:47,388 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/aws.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:47,388 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/small_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:47,389 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/medium_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws 2023-04-28 05:57:47,389 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/defaults 2023-04-28 05:57:47,389 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment/defaults 2023-04-28 05:57:47,389 root INFO copying build/lib/ansible_collections/cisco/ise/roles/aws_deployment/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise/roles/aws_deployment 2023-04-28 05:57:47,389 root INFO copying build/lib/ansible_collections/cisco/ise/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,390 root INFO copying build/lib/ansible_collections/cisco/ise/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/cisco/ise 2023-04-28 05:57:47,390 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms 2023-04-28 05:57:47,390 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,390 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,390 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins 2023-04-28 05:57:47,391 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments 2023-04-28 05:57:47,391 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments/common_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments 2023-04-28 05:57:47,391 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/inventory 2023-04-28 05:57:47,391 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/inventory/icinga_director_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/inventory 2023-04-28 05:57:47,391 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,392 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,392 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_apply_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,392 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_serviceset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,392 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,392 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,393 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,393 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,393 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_endpoint_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,393 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,393 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,394 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,394 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,394 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,394 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_servicegroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,394 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,395 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,395 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,395 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,395 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_servicegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,395 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,395 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,396 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,396 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,396 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,396 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,397 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,397 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_apply.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,397 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_hostgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,397 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_hostgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,397 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,398 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_scheduled_downtime.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,398 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,398 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,398 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,398 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,399 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,399 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,399 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/modules 2023-04-28 05:57:47,399 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/module_utils 2023-04-28 05:57:47,399 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/plugins/module_utils/icinga.py -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/plugins/module_utils 2023-04-28 05:57:47,400 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,400 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,400 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/meta 2023-04-28 05:57:47,400 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/meta 2023-04-28 05:57:47,400 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,401 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/CHANGELOG.md -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,401 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,401 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/renovate.json -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,401 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,401 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:47,402 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:47,402 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:47,402 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/changelogs 2023-04-28 05:57:47,402 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director 2023-04-28 05:57:47,402 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,403 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_service.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,403 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,403 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_serviceset.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,403 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,403 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_hostgroup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,404 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_group_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,404 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_scheduled_downtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,404 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,404 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_zone.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,404 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,404 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_endpoint.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,405 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_servicegroup_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,405 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,405 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,405 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_endpoint_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,405 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,406 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_zone_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,406 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_host.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,406 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,406 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,406 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_apply.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,407 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_hostgroup_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,407 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_template_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,407 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,407 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,407 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_template_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,408 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_command.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,408 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,408 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,408 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,408 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_apply_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,409 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,409 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_template_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,409 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_template_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,409 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_template_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,409 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,410 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_servicegroup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,410 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_template_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/examples 2023-04-28 05:57:47,410 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles 2023-04-28 05:57:47,410 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga 2023-04-28 05:57:47,410 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,410 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,411 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_serviceset.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,411 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,411 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_hostgroup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,411 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_scheduled_downtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,411 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_notification.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,412 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_zone.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,412 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_endpoint.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,412 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,412 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_command_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,412 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_host_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,413 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_host.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,413 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_user_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,413 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service_apply.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,413 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,413 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_command.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,414 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_notification_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,414 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_timeperiod.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,414 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_servicegroup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks 2023-04-28 05:57:47,414 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/defaults 2023-04-28 05:57:47,414 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/defaults 2023-04-28 05:57:47,415 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga 2023-04-28 05:57:47,415 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/meta 2023-04-28 05:57:47,415 root INFO copying build/lib/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/meta 2023-04-28 05:57:47,415 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point 2023-04-28 05:57:47,415 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt 2023-04-28 05:57:47,416 root INFO copying build/lib/ansible_collections/check_point/mgmt/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt 2023-04-28 05:57:47,416 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins 2023-04-28 05:57:47,416 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:47,416 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_objects_action_module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:47,416 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_objects.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:47,417 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:47,417 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_commands.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/doc_fragments 2023-04-28 05:57:47,417 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,417 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_reject_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,417 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_administrator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,418 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_threat_advanced_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,418 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_smtp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,418 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,418 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_feed_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,418 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dynamic_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,419 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_udp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,419 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_cluster_members_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,419 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_run_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,419 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_nat_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,419 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,420 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_rules_batch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,420 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_assign_global_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,420 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_disconnect_cloud_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,420 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_api_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,420 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_package_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,421 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_trusted_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,421 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,421 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_trusted_client_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,421 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_administrator_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,421 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,422 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_category_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,422 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_exception_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,422 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster_profile_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,422 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_run_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,422 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,423 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,423 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_multicast_address_range.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,423 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,423 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_permissions_profile_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,424 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_rpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,424 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_rules_batch.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,424 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_idp_to_domain_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,424 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_address_range.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,424 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dns_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,425 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_smtp_server_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,425 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_time.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,425 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_session_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,425 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp6_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,425 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_cloud_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,426 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_wildcard_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,426 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_provisioning_profile_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,426 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_get_platform.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,426 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_dce_rpc_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,426 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_run_ips_update.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,427 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_data_center_object_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,427 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_group_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,427 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_discard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,427 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,427 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_rule_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,428 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,428 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_interoperable_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,428 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,428 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_verify_software_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,428 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway_profile_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,429 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_check_network_feed.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,429 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,429 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_global_assignment_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,429 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,429 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_threat_advanced_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,430 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_section.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,430 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_other.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,430 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_nat_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,430 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,430 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_software_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,431 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_category.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,431 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_rpc_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,431 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_gateway_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,431 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_meshed_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,431 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_uninstall_software_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,432 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_nat_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,432 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_lsm_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,432 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_role_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,432 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_exception_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,432 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_identity_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,433 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_tcp_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,433 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dynamic_object_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,433 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rule_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,433 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_cluster_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,433 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,434 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_udp_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,434 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_servers_and_processes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,434 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_nat_section.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,434 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_mds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,434 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_task.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,435 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_access_section.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,435 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_security_zone_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,435 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_interoperable_device_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,435 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_global_properties.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,436 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,436 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_other_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,436 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_idp_default_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,436 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_layer_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,437 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_reset_sic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,437 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_api_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,437 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_tcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,437 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dns_domain_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,437 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,438 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_mds_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,438 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_protection_override.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,438 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,438 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_dce_rpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,438 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_exception_group_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,439 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_wildcard.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,439 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,439 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_lsm_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,439 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_global_properties.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,439 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_layer_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,440 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_data_center_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,440 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_logs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,440 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_connect_cloud_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,440 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_publish.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,440 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,441 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,441 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_star_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,441 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_feed.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,441 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_profile_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,441 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,442 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_indicator_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,442 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_sctp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,442 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,442 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_tasks.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,442 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_submit_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,443 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,443 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_nat_rule_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,443 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_https_section.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,443 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_group_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,444 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_put_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,444 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_with_exclusion_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,444 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_to_domain_assignment_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,444 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_indicator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,444 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,445 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_tag_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,445 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_sctp_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,445 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_data_center_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,445 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_approve_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,445 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_verify_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,446 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_check_threat_ioc_feed.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,446 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,446 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_layer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,446 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_md_permissions_profile_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,446 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_exception.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,447 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,447 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_global_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,447 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_multicast_address_range_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,447 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_session.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,448 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_test_sic_status.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,448 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_administrator_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,448 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_layer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,448 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,448 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_objects_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,449 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_security_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,449 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_address_range_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,449 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_host_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,449 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_star.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,449 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_with_exclusion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,450 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_software_package_details.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,450 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_nat_section.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,450 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_update_provisioned_satellites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,450 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_identity_tag_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,450 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_package.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,451 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_administrator_group_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,451 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_permissions_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,451 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_idp_default_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,451 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_repository_script_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,452 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_repository_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,452 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_time_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,452 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_https_section.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,452 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,452 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_md_permissions_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,453 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,453 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_meshed.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,453 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/modules 2023-04-28 05:57:47,453 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/action 2023-04-28 05:57:47,453 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/action/cp_mgmt_access_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/action 2023-04-28 05:57:47,454 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/httpapi 2023-04-28 05:57:47,454 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/httpapi/checkpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/httpapi 2023-04-28 05:57:47,454 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/module_utils 2023-04-28 05:57:47,454 root INFO copying build/lib/ansible_collections/check_point/mgmt/plugins/module_utils/checkpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/plugins/module_utils 2023-04-28 05:57:47,454 root INFO copying build/lib/ansible_collections/check_point/mgmt/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt 2023-04-28 05:57:47,455 root INFO copying build/lib/ansible_collections/check_point/mgmt/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt 2023-04-28 05:57:47,455 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/meta 2023-04-28 05:57:47,455 root INFO copying build/lib/ansible_collections/check_point/mgmt/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/meta 2023-04-28 05:57:47,455 root INFO copying build/lib/ansible_collections/check_point/mgmt/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/meta 2023-04-28 05:57:47,455 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:47,456 root INFO copying build/lib/ansible_collections/check_point/mgmt/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:47,456 root INFO copying build/lib/ansible_collections/check_point/mgmt/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:47,456 root INFO copying build/lib/ansible_collections/check_point/mgmt/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt/changelogs 2023-04-28 05:57:47,456 root INFO copying build/lib/ansible_collections/check_point/mgmt/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/check_point/mgmt 2023-04-28 05:57:47,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe 2023-04-28 05:57:47,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble 2023-04-28 05:57:47,457 root INFO copying build/lib/ansible_collections/hpe/nimble/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble 2023-04-28 05:57:47,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins 2023-04-28 05:57:47,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/doc_fragments 2023-04-28 05:57:47,457 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/doc_fragments/hpe_nimble.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/doc_fragments 2023-04-28 05:57:47,458 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,458 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_protection_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,458 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,458 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_initiator_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,458 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_partner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,459 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,459 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,459 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_chap_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,459 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,459 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_volume_collection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,460 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_encryption.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,460 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,460 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_user_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,460 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_performance_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,461 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,461 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_access_control_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,461 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_protection_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,461 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,461 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,462 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_shelf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,462 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_snapshot_collection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,462 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_fc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,462 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_array.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/modules 2023-04-28 05:57:47,463 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/module_utils 2023-04-28 05:57:47,463 root INFO copying build/lib/ansible_collections/hpe/nimble/plugins/module_utils/hpe_nimble.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/plugins/module_utils 2023-04-28 05:57:47,463 root INFO copying build/lib/ansible_collections/hpe/nimble/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble 2023-04-28 05:57:47,463 root INFO copying build/lib/ansible_collections/hpe/nimble/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble 2023-04-28 05:57:47,463 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/meta 2023-04-28 05:57:47,463 root INFO copying build/lib/ansible_collections/hpe/nimble/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/meta 2023-04-28 05:57:47,464 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/changelogs 2023-04-28 05:57:47,464 root INFO copying build/lib/ansible_collections/hpe/nimble/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/changelogs 2023-04-28 05:57:47,464 root INFO copying build/lib/ansible_collections/hpe/nimble/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble/changelogs 2023-04-28 05:57:47,464 root INFO copying build/lib/ansible_collections/hpe/nimble/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble 2023-04-28 05:57:47,464 root INFO copying build/lib/ansible_collections/hpe/nimble/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble 2023-04-28 05:57:47,465 root INFO copying build/lib/ansible_collections/hpe/nimble/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/hpe/nimble 2023-04-28 05:57:47,465 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos 2023-04-28 05:57:47,465 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,465 root INFO copying build/lib/ansible_collections/vyos/vyos/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,465 root INFO copying build/lib/ansible_collections/vyos/vyos/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,466 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins 2023-04-28 05:57:47,466 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/terminal 2023-04-28 05:57:47,466 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/terminal/vyos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/terminal 2023-04-28 05:57:47,466 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/terminal 2023-04-28 05:57:47,466 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/filter 2023-04-28 05:57:47,466 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/filter 2023-04-28 05:57:47,467 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/doc_fragments 2023-04-28 05:57:47,467 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/doc_fragments/vyos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/doc_fragments 2023-04-28 05:57:47,467 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/doc_fragments 2023-04-28 05:57:47,467 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/inventory 2023-04-28 05:57:47,467 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/inventory 2023-04-28 05:57:47,468 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,468 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,468 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,468 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,468 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,469 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,469 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,469 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,469 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,470 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,470 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,470 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,470 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,471 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,471 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,471 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,471 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,472 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,472 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,472 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,472 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,472 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,472 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,473 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,473 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,473 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,473 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,474 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,474 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,474 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,474 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/modules/vyos_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/modules 2023-04-28 05:57:47,475 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/cliconf 2023-04-28 05:57:47,475 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/cliconf/vyos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/cliconf 2023-04-28 05:57:47,475 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/cliconf 2023-04-28 05:57:47,475 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,475 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,475 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,476 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,476 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,476 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,477 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,477 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,477 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,477 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/lldp_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,477 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,478 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,478 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,478 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,478 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/vyos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,478 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,479 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,479 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/ping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,479 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,479 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,479 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,479 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,480 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/firewall_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,480 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,480 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,480 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,480 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,481 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/firewall_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,481 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,481 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,481 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,481 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,482 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,482 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,482 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/firewall_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,482 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,482 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,483 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/action/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/action 2023-04-28 05:57:47,483 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils 2023-04-28 05:57:47,483 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils 2023-04-28 05:57:47,483 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network 2023-04-28 05:57:47,483 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network 2023-04-28 05:57:47,483 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos 2023-04-28 05:57:47,484 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts 2023-04-28 05:57:47,484 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes 2023-04-28 05:57:47,484 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes 2023-04-28 05:57:47,484 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes 2023-04-28 05:57:47,484 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2 2023-04-28 05:57:47,485 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2 2023-04-28 05:57:47,485 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2 2023-04-28 05:57:47,485 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts 2023-04-28 05:57:47,485 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces 2023-04-28 05:57:47,485 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces 2023-04-28 05:57:47,486 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces 2023-04-28 05:57:47,486 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family 2023-04-28 05:57:47,486 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family 2023-04-28 05:57:47,486 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family 2023-04-28 05:57:47,486 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules 2023-04-28 05:57:47,487 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules 2023-04-28 05:57:47,487 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/firewall_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules 2023-04-28 05:57:47,487 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global 2023-04-28 05:57:47,487 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global 2023-04-28 05:57:47,487 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global 2023-04-28 05:57:47,488 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces 2023-04-28 05:57:47,488 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces 2023-04-28 05:57:47,488 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces 2023-04-28 05:57:47,488 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts 2023-04-28 05:57:47,488 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global 2023-04-28 05:57:47,488 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global 2023-04-28 05:57:47,489 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/firewall_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global 2023-04-28 05:57:47,489 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps 2023-04-28 05:57:47,489 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps 2023-04-28 05:57:47,489 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps 2023-04-28 05:57:47,489 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces 2023-04-28 05:57:47,490 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces 2023-04-28 05:57:47,490 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces 2023-04-28 05:57:47,490 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists 2023-04-28 05:57:47,490 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists 2023-04-28 05:57:47,490 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists 2023-04-28 05:57:47,491 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname 2023-04-28 05:57:47,491 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname 2023-04-28 05:57:47,491 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname 2023-04-28 05:57:47,491 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server 2023-04-28 05:57:47,491 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server 2023-04-28 05:57:47,491 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server 2023-04-28 05:57:47,492 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces 2023-04-28 05:57:47,492 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces 2023-04-28 05:57:47,492 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces 2023-04-28 05:57:47,492 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global 2023-04-28 05:57:47,492 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global 2023-04-28 05:57:47,493 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global 2023-04-28 05:57:47,493 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy 2023-04-28 05:57:47,493 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy 2023-04-28 05:57:47,493 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy 2023-04-28 05:57:47,493 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global 2023-04-28 05:57:47,493 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global 2023-04-28 05:57:47,494 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global 2023-04-28 05:57:47,494 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global 2023-04-28 05:57:47,494 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global 2023-04-28 05:57:47,494 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global 2023-04-28 05:57:47,494 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces 2023-04-28 05:57:47,495 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces 2023-04-28 05:57:47,495 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces 2023-04-28 05:57:47,495 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces 2023-04-28 05:57:47,495 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces 2023-04-28 05:57:47,495 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/firewall_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces 2023-04-28 05:57:47,496 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3 2023-04-28 05:57:47,496 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3 2023-04-28 05:57:47,496 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3 2023-04-28 05:57:47,496 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,496 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,497 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,497 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,497 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,497 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,497 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,498 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,498 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,498 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,498 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates 2023-04-28 05:57:47,499 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/vyos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos 2023-04-28 05:57:47,499 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils 2023-04-28 05:57:47,499 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils 2023-04-28 05:57:47,499 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils 2023-04-28 05:57:47,499 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos 2023-04-28 05:57:47,500 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config 2023-04-28 05:57:47,500 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes 2023-04-28 05:57:47,500 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes 2023-04-28 05:57:47,500 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes 2023-04-28 05:57:47,500 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2 2023-04-28 05:57:47,501 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2 2023-04-28 05:57:47,501 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2 2023-04-28 05:57:47,501 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces 2023-04-28 05:57:47,501 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces 2023-04-28 05:57:47,501 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces 2023-04-28 05:57:47,502 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family 2023-04-28 05:57:47,502 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family 2023-04-28 05:57:47,502 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family 2023-04-28 05:57:47,502 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules 2023-04-28 05:57:47,502 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules 2023-04-28 05:57:47,502 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/firewall_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules 2023-04-28 05:57:47,503 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global 2023-04-28 05:57:47,503 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global 2023-04-28 05:57:47,503 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global 2023-04-28 05:57:47,503 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces 2023-04-28 05:57:47,503 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces 2023-04-28 05:57:47,504 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces 2023-04-28 05:57:47,504 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config 2023-04-28 05:57:47,504 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global 2023-04-28 05:57:47,505 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global 2023-04-28 05:57:47,505 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/firewall_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global 2023-04-28 05:57:47,505 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps 2023-04-28 05:57:47,505 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps 2023-04-28 05:57:47,505 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps 2023-04-28 05:57:47,506 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces 2023-04-28 05:57:47,506 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces 2023-04-28 05:57:47,506 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces 2023-04-28 05:57:47,506 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists 2023-04-28 05:57:47,506 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists 2023-04-28 05:57:47,507 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists 2023-04-28 05:57:47,507 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname 2023-04-28 05:57:47,507 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname 2023-04-28 05:57:47,507 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname 2023-04-28 05:57:47,507 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server 2023-04-28 05:57:47,507 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server 2023-04-28 05:57:47,508 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server 2023-04-28 05:57:47,508 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces 2023-04-28 05:57:47,508 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces 2023-04-28 05:57:47,508 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces 2023-04-28 05:57:47,508 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global 2023-04-28 05:57:47,509 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global 2023-04-28 05:57:47,509 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global 2023-04-28 05:57:47,509 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global 2023-04-28 05:57:47,509 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global 2023-04-28 05:57:47,509 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global 2023-04-28 05:57:47,510 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global 2023-04-28 05:57:47,510 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global 2023-04-28 05:57:47,510 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global 2023-04-28 05:57:47,510 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces 2023-04-28 05:57:47,510 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces 2023-04-28 05:57:47,510 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces 2023-04-28 05:57:47,511 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces 2023-04-28 05:57:47,511 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces 2023-04-28 05:57:47,511 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/firewall_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces 2023-04-28 05:57:47,511 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3 2023-04-28 05:57:47,511 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3 2023-04-28 05:57:47,512 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3 2023-04-28 05:57:47,512 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec 2023-04-28 05:57:47,512 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes 2023-04-28 05:57:47,512 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes 2023-04-28 05:57:47,512 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes 2023-04-28 05:57:47,513 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts 2023-04-28 05:57:47,513 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts 2023-04-28 05:57:47,513 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts 2023-04-28 05:57:47,513 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2 2023-04-28 05:57:47,513 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2 2023-04-28 05:57:47,514 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2 2023-04-28 05:57:47,514 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces 2023-04-28 05:57:47,514 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces 2023-04-28 05:57:47,514 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces 2023-04-28 05:57:47,514 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family 2023-04-28 05:57:47,514 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family 2023-04-28 05:57:47,515 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family 2023-04-28 05:57:47,515 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules 2023-04-28 05:57:47,515 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules 2023-04-28 05:57:47,515 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/firewall_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules 2023-04-28 05:57:47,515 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global 2023-04-28 05:57:47,516 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global 2023-04-28 05:57:47,516 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global 2023-04-28 05:57:47,516 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces 2023-04-28 05:57:47,516 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces 2023-04-28 05:57:47,516 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces 2023-04-28 05:57:47,517 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec 2023-04-28 05:57:47,517 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global 2023-04-28 05:57:47,517 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global 2023-04-28 05:57:47,517 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/firewall_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global 2023-04-28 05:57:47,517 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps 2023-04-28 05:57:47,518 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps 2023-04-28 05:57:47,518 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps 2023-04-28 05:57:47,518 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces 2023-04-28 05:57:47,518 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces 2023-04-28 05:57:47,518 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces 2023-04-28 05:57:47,519 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists 2023-04-28 05:57:47,519 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists 2023-04-28 05:57:47,519 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists 2023-04-28 05:57:47,519 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname 2023-04-28 05:57:47,519 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname 2023-04-28 05:57:47,519 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname 2023-04-28 05:57:47,520 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server 2023-04-28 05:57:47,520 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server 2023-04-28 05:57:47,520 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server 2023-04-28 05:57:47,520 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces 2023-04-28 05:57:47,520 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces 2023-04-28 05:57:47,521 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces 2023-04-28 05:57:47,521 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global 2023-04-28 05:57:47,521 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global 2023-04-28 05:57:47,521 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global 2023-04-28 05:57:47,521 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global 2023-04-28 05:57:47,521 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global 2023-04-28 05:57:47,522 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global 2023-04-28 05:57:47,522 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global 2023-04-28 05:57:47,522 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global 2023-04-28 05:57:47,522 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global 2023-04-28 05:57:47,522 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces 2023-04-28 05:57:47,523 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces 2023-04-28 05:57:47,523 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces 2023-04-28 05:57:47,523 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces 2023-04-28 05:57:47,523 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces 2023-04-28 05:57:47,523 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/firewall_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces 2023-04-28 05:57:47,524 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3 2023-04-28 05:57:47,524 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3 2023-04-28 05:57:47,524 root INFO copying build/lib/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3 2023-04-28 05:57:47,524 root INFO copying build/lib/ansible_collections/vyos/vyos/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,524 root INFO copying build/lib/ansible_collections/vyos/vyos/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,525 root INFO copying build/lib/ansible_collections/vyos/vyos/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,525 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/meta 2023-04-28 05:57:47,525 root INFO copying build/lib/ansible_collections/vyos/vyos/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/meta 2023-04-28 05:57:47,525 root INFO copying build/lib/ansible_collections/vyos/vyos/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,526 root INFO copying build/lib/ansible_collections/vyos/vyos/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,526 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/changelogs 2023-04-28 05:57:47,526 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/changelogs/fragments 2023-04-28 05:57:47,526 root INFO copying build/lib/ansible_collections/vyos/vyos/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/changelogs/fragments 2023-04-28 05:57:47,526 root INFO copying build/lib/ansible_collections/vyos/vyos/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/changelogs 2023-04-28 05:57:47,527 root INFO copying build/lib/ansible_collections/vyos/vyos/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos/changelogs 2023-04-28 05:57:47,527 root INFO copying build/lib/ansible_collections/vyos/vyos/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,527 root INFO copying build/lib/ansible_collections/vyos/vyos/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,527 root INFO copying build/lib/ansible_collections/vyos/vyos/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,527 root INFO copying build/lib/ansible_collections/vyos/vyos/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/vyos/vyos 2023-04-28 05:57:47,528 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman 2023-04-28 05:57:47,528 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,528 root INFO copying build/lib/ansible_collections/theforeman/foreman/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,528 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins 2023-04-28 05:57:47,528 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/filter 2023-04-28 05:57:47,528 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/filter/foreman.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/filter 2023-04-28 05:57:47,529 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/filter/cp_label.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/filter 2023-04-28 05:57:47,529 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/doc_fragments 2023-04-28 05:57:47,529 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/doc_fragments/foreman.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/doc_fragments 2023-04-28 05:57:47,529 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/inventory 2023-04-28 05:57:47,529 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/inventory/foreman.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/inventory 2023-04-28 05:57:47,530 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/callback 2023-04-28 05:57:47,530 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/callback/foreman.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/callback 2023-04-28 05:57:47,530 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,530 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,530 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/host_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,531 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,531 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,531 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/hostgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,531 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/scc_product.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,531 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/discovery_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,532 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,532 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,532 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/subnet_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,532 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/realm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,532 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/sync_plan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,533 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,533 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/scap_tailoring_file.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,533 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/repository_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,533 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/puppetclasses_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,533 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/scc_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,534 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/smart_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,534 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/compute_resource.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,534 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,534 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,534 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/operatingsystem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,535 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/host_power.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,535 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/templates_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,535 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_export_library.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,535 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,535 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,536 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/host_collection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,536 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_upload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,536 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,536 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/hostgroup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,536 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/scap_content.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,537 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,537 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/setting_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,537 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/compute_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,537 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/global_parameter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,537 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/job_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,538 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/installation_medium.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,538 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/partition_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,538 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/http_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,538 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/job_invocation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,538 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/smart_class_parameter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,539 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/external_usergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,539 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/product.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,539 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/setting.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,539 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view_filter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,539 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/activation_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,540 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,540 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,540 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,540 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/organization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,541 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/lifecycle_environment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,541 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/hardware_model.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,541 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,541 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/subscription_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,541 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/redhat_manifest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,542 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/os_default_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,542 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/repository_sync.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,542 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,542 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/host_errata_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,542 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,543 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/repository_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,543 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/config_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,543 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/bookmark.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,543 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/usergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,543 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,544 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/repository_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,544 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_export_repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,544 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/auth_source_ldap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,544 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/architecture.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,544 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_export_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,545 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/compute_attribute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,545 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/provisioning_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,545 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/content_export_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,545 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/resource_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,545 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/organization_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,546 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/puppet_environment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,546 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/subscription_manifest.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,546 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/modules/host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/modules 2023-04-28 05:57:47,546 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:47,546 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/module_utils/_apypie.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:47,547 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/module_utils/foreman_helper.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:47,547 root INFO copying build/lib/ansible_collections/theforeman/foreman/plugins/module_utils/_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/plugins/module_utils 2023-04-28 05:57:47,547 root INFO copying build/lib/ansible_collections/theforeman/foreman/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,547 root INFO copying build/lib/ansible_collections/theforeman/foreman/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,548 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/meta 2023-04-28 05:57:47,548 root INFO copying build/lib/ansible_collections/theforeman/foreman/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/meta 2023-04-28 05:57:47,548 root INFO copying build/lib/ansible_collections/theforeman/foreman/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/meta 2023-04-28 05:57:47,548 root INFO copying build/lib/ansible_collections/theforeman/foreman/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,548 root INFO copying build/lib/ansible_collections/theforeman/foreman/PSF-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,549 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/changelogs 2023-04-28 05:57:47,549 root INFO copying build/lib/ansible_collections/theforeman/foreman/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/changelogs 2023-04-28 05:57:47,549 root INFO copying build/lib/ansible_collections/theforeman/foreman/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,549 root INFO copying build/lib/ansible_collections/theforeman/foreman/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,549 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles 2023-04-28 05:57:47,550 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/domains 2023-04-28 05:57:47,550 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/domains/tasks 2023-04-28 05:57:47,550 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/domains/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/domains/tasks 2023-04-28 05:57:47,550 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/domains/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/domains 2023-04-28 05:57:47,550 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/activation_keys 2023-04-28 05:57:47,551 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/activation_keys/tasks 2023-04-28 05:57:47,551 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/activation_keys/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/activation_keys/tasks 2023-04-28 05:57:47,551 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/activation_keys/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/activation_keys 2023-04-28 05:57:47,551 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup 2023-04-28 05:57:47,551 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:47,551 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/delete_cv_versions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:47,552 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/find_and_delete_unused_cv_versions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:47,552 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks 2023-04-28 05:57:47,552 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_version_cleanup 2023-04-28 05:57:47,552 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/operatingsystems 2023-04-28 05:57:47,552 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/operatingsystems/tasks 2023-04-28 05:57:47,553 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/operatingsystems/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/operatingsystems/tasks 2023-04-28 05:57:47,553 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/operatingsystems/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/operatingsystems 2023-04-28 05:57:47,553 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel 2023-04-28 05:57:47,553 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:47,553 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/sync.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:47,553 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/content_views.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:47,554 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/host_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:47,554 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/products_and_repos.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:47,554 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/activation_keys.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:47,554 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/tasks 2023-04-28 05:57:47,554 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/defaults 2023-04-28 05:57:47,555 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel/defaults 2023-04-28 05:57:47,555 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/convert2rhel/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/convert2rhel 2023-04-28 05:57:47,555 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/provisioning_templates 2023-04-28 05:57:47,555 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/provisioning_templates/tasks 2023-04-28 05:57:47,555 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/provisioning_templates/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/provisioning_templates/tasks 2023-04-28 05:57:47,556 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/provisioning_templates/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/provisioning_templates 2023-04-28 05:57:47,556 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/auth_sources_ldap 2023-04-28 05:57:47,556 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/auth_sources_ldap/tasks 2023-04-28 05:57:47,556 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/auth_sources_ldap/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/auth_sources_ldap/tasks 2023-04-28 05:57:47,556 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/auth_sources_ldap/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/auth_sources_ldap 2023-04-28 05:57:47,556 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_rhel 2023-04-28 05:57:47,557 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_rhel/tasks 2023-04-28 05:57:47,557 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_rhel/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_rhel/tasks 2023-04-28 05:57:47,557 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_rhel/defaults 2023-04-28 05:57:47,557 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_rhel/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_rhel/defaults 2023-04-28 05:57:47,557 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_rhel/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_rhel 2023-04-28 05:57:47,558 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/subnets 2023-04-28 05:57:47,558 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/subnets/tasks 2023-04-28 05:57:47,558 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/subnets/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/subnets/tasks 2023-04-28 05:57:47,558 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/subnets/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/subnets 2023-04-28 05:57:47,558 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/sync_plans 2023-04-28 05:57:47,558 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/sync_plans/tasks 2023-04-28 05:57:47,559 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/sync_plans/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/sync_plans/tasks 2023-04-28 05:57:47,559 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/sync_plans/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/sync_plans 2023-04-28 05:57:47,559 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_publish 2023-04-28 05:57:47,559 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_publish/tasks 2023-04-28 05:57:47,559 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_view_publish/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_publish/tasks 2023-04-28 05:57:47,560 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_view_publish/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_view_publish 2023-04-28 05:57:47,560 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/organizations 2023-04-28 05:57:47,560 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/organizations/tasks 2023-04-28 05:57:47,560 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/organizations/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/organizations/tasks 2023-04-28 05:57:47,560 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/organizations/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/organizations 2023-04-28 05:57:47,561 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_credentials 2023-04-28 05:57:47,561 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_credentials/tasks 2023-04-28 05:57:47,561 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_credentials/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_credentials/tasks 2023-04-28 05:57:47,561 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_credentials/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_credentials 2023-04-28 05:57:47,561 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_profiles 2023-04-28 05:57:47,561 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_profiles/tasks 2023-04-28 05:57:47,562 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/compute_profiles/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_profiles/tasks 2023-04-28 05:57:47,562 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/compute_profiles/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_profiles 2023-04-28 05:57:47,562 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_resources 2023-04-28 05:57:47,562 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_resources/tasks 2023-04-28 05:57:47,562 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/compute_resources/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_resources/tasks 2023-04-28 05:57:47,562 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/compute_resources/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/compute_resources 2023-04-28 05:57:47,563 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_views 2023-04-28 05:57:47,563 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_views/tasks 2023-04-28 05:57:47,563 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_views/tasks/_create_content_view.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_views/tasks 2023-04-28 05:57:47,563 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_views/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_views/tasks 2023-04-28 05:57:47,563 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/content_views/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/content_views 2023-04-28 05:57:47,564 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/manifest 2023-04-28 05:57:47,564 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/manifest/tasks 2023-04-28 05:57:47,564 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/manifest/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/manifest/tasks 2023-04-28 05:57:47,564 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/manifest/defaults 2023-04-28 05:57:47,564 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/manifest/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/manifest/defaults 2023-04-28 05:57:47,565 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/manifest/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/manifest 2023-04-28 05:57:47,565 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/settings 2023-04-28 05:57:47,565 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/settings/tasks 2023-04-28 05:57:47,565 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/settings/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/settings/tasks 2023-04-28 05:57:47,565 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/settings/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/settings 2023-04-28 05:57:47,565 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/hostgroups 2023-04-28 05:57:47,566 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/hostgroups/tasks 2023-04-28 05:57:47,566 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/hostgroups/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/hostgroups/tasks 2023-04-28 05:57:47,566 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/hostgroups/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/hostgroups 2023-04-28 05:57:47,566 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/lifecycle_environments 2023-04-28 05:57:47,566 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/lifecycle_environments/tasks 2023-04-28 05:57:47,567 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/lifecycle_environments/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/lifecycle_environments/tasks 2023-04-28 05:57:47,567 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/lifecycle_environments/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/lifecycle_environments 2023-04-28 05:57:47,567 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/repositories 2023-04-28 05:57:47,567 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/repositories/tasks 2023-04-28 05:57:47,567 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/repositories/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/repositories/tasks 2023-04-28 05:57:47,567 root INFO copying build/lib/ansible_collections/theforeman/foreman/roles/repositories/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman/roles/repositories 2023-04-28 05:57:47,568 root INFO copying build/lib/ansible_collections/theforeman/foreman/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/theforeman/foreman 2023-04-28 05:57:47,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox 2023-04-28 05:57:47,568 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,568 root INFO copying build/lib/ansible_collections/netbox/netbox/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,568 root INFO copying build/lib/ansible_collections/netbox/netbox/poetry.lock -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins 2023-04-28 05:57:47,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/doc_fragments 2023-04-28 05:57:47,569 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/doc_fragments/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/doc_fragments 2023-04-28 05:57:47,569 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/inventory 2023-04-28 05:57:47,570 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/inventory/nb_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/inventory 2023-04-28 05:57:47,570 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,570 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_contact.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,570 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_virtual_chassis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,571 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_virtual_machine.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,571 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_inventory_item_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,571 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_device_bay_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,571 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_aggregate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,571 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_rack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,572 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_ip_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,572 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_power_feed.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,572 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,572 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,572 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_console_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,573 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_prefix.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,573 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_vm_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,573 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_circuit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,573 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_circuit_termination.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,573 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_inventory_item.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,574 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_device_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,574 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_l2vpn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,574 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_front_port_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,574 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_provider_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,574 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_cable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,575 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_site_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,575 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_module_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,575 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_route_target.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,575 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_console_server_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,575 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_journal_entry.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,576 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_vlan_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,576 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_lan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,576 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_rack_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,576 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_webhook.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,576 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_cluster_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,577 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,577 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_power_outlet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,577 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_rear_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,577 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,577 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,578 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_site.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,578 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_export_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,578 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_device_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,578 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_power_outlet_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,578 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_power_panel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,579 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,579 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_asn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,579 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_contact_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,579 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_lan_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,579 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,580 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_console_port_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,580 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_platform.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,580 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_rear_port_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,580 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_tenant.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,580 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_power_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,581 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_cluster_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,581 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_custom_link.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,581 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_tenant_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,581 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_device_interface_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,581 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_power_port_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,582 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_console_server_port_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,582 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_fhrp_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,582 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_manufacturer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,582 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_front_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,582 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_device_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,583 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_device_bay.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,583 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_link.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,583 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_custom_field.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,583 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_ipam_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,583 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_service_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,584 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,584 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_config_context.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,584 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,584 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_rir.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,584 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,585 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_rack_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,585 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_contact_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,585 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/modules/netbox_circuit_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/modules 2023-04-28 05:57:47,585 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,585 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_circuits.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,586 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_secrets.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,586 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_tenancy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,586 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_ipam.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,586 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_virtualization.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,586 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_wireless.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,587 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,587 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_extras.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,587 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,587 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/module_utils/netbox_dcim.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/module_utils 2023-04-28 05:57:47,588 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/lookup 2023-04-28 05:57:47,588 root INFO copying build/lib/ansible_collections/netbox/netbox/plugins/lookup/nb_lookup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/plugins/lookup 2023-04-28 05:57:47,588 root INFO copying build/lib/ansible_collections/netbox/netbox/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,588 root INFO copying build/lib/ansible_collections/netbox/netbox/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,589 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/meta 2023-04-28 05:57:47,589 root INFO copying build/lib/ansible_collections/netbox/netbox/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/meta 2023-04-28 05:57:47,589 root INFO copying build/lib/ansible_collections/netbox/netbox/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/meta 2023-04-28 05:57:47,589 root INFO copying build/lib/ansible_collections/netbox/netbox/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,589 root INFO copying build/lib/ansible_collections/netbox/netbox/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,590 root INFO copying build/lib/ansible_collections/netbox/netbox/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,590 root INFO copying build/lib/ansible_collections/netbox/netbox/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,590 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:47,590 root INFO copying build/lib/ansible_collections/netbox/netbox/hacking/local-test.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:47,590 root INFO copying build/lib/ansible_collections/netbox/netbox/hacking/make-docs.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:47,590 root INFO copying build/lib/ansible_collections/netbox/netbox/hacking/black.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:47,591 root INFO copying build/lib/ansible_collections/netbox/netbox/hacking/build.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:47,591 root INFO copying build/lib/ansible_collections/netbox/netbox/hacking/update_test_inventories.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/hacking 2023-04-28 05:57:47,591 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs 2023-04-28 05:57:47,591 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:47,591 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/fragments/allow-jinja2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:47,592 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/fragments/serial_and_asset.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:47,592 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/fragments/.gitkeep -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:47,592 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/fragments/619-v3.0-ci-fixes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:47,592 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/fragments/issue-951.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:47,592 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/fragments/issue-558.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs/fragments 2023-04-28 05:57:47,593 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs 2023-04-28 05:57:47,593 root INFO copying build/lib/ansible_collections/netbox/netbox/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox/changelogs 2023-04-28 05:57:47,593 root INFO copying build/lib/ansible_collections/netbox/netbox/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,593 root INFO copying build/lib/ansible_collections/netbox/netbox/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/netbox/netbox 2023-04-28 05:57:47,593 root INFO copying build/lib/ansible_collections/ansible_release.py -> build/bdist.linux-x86_64/wheel/ansible_collections 2023-04-28 05:57:47,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt 2023-04-28 05:57:47,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,594 root INFO copying build/lib/ansible_collections/ovirt/ovirt/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,594 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/automation 2023-04-28 05:57:47,594 root INFO copying build/lib/ansible_collections/ovirt/ovirt/automation/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/automation 2023-04-28 05:57:47,595 root INFO copying build/lib/ansible_collections/ovirt/ovirt/automation/build.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/automation 2023-04-28 05:57:47,595 root INFO copying build/lib/ansible_collections/ovirt/ovirt/README-developers.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,595 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins 2023-04-28 05:57:47,595 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/test 2023-04-28 05:57:47,595 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/test/ovirt_proxied_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/test 2023-04-28 05:57:47,596 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,596 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/json_query.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,596 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/filtervalue.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,596 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/removesensitivevmdata.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,596 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipv6.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,596 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/convert_to_bytes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,597 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipsv6.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,597 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,597 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/json_query.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,597 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/get_ovf_disk_size.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,597 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipv4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,598 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmip.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,598 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/get_network_xml_to_dict.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,598 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/convert_to_bytes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,598 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipsv4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,598 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtdiff.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,599 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmips.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,599 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/filter/get_ovf_disk_size.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/filter 2023-04-28 05:57:47,599 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/doc_fragments 2023-04-28 05:57:47,599 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/doc_fragments/ovirt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/doc_fragments 2023-04-28 05:57:47,599 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/doc_fragments/ovirt_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/doc_fragments 2023-04-28 05:57:47,600 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/inventory 2023-04-28 05:57:47,600 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/inventory/ovirt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/inventory 2023-04-28 05:57:47,600 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/callback 2023-04-28 05:57:47,600 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/callback/stdout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/callback 2023-04-28 05:57:47,600 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,601 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,601 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_tag_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,601 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,601 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_event.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,601 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,602 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vmpool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,602 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,602 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,602 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,603 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,603 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vmpool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,603 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_qos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,603 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_quota_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,603 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vnic_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,604 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,604 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_nic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,604 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_connection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,604 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,604 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_datacenter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,605 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,605 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_instance_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,605 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_permission.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,605 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,605 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_system_option_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,606 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_external_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,606 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,606 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_scheduling_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,606 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_job.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,606 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,607 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,607 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,607 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_datacenter.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,607 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_label.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,608 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,608 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_permission_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,608 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,608 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_api_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,608 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,609 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,609 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm_os_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,609 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vnic_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,609 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_vm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,610 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,610 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,610 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,610 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,610 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,611 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_external_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,611 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,611 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,611 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_mac_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,611 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_pm.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,612 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,612 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_event_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,612 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,612 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_storage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,613 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_nic_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,613 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,613 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_label_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/modules 2023-04-28 05:57:47,613 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:47,613 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils/cloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:47,614 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils/ovirt.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:47,614 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:47,614 root INFO copying build/lib/ansible_collections/ovirt/ovirt/plugins/module_utils/version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/plugins/module_utils 2023-04-28 05:57:47,614 root INFO copying build/lib/ansible_collections/ovirt/ovirt/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,614 root INFO copying build/lib/ansible_collections/ovirt/ovirt/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,615 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:47,615 root INFO copying build/lib/ansible_collections/ovirt/ovirt/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:47,615 root INFO copying build/lib/ansible_collections/ovirt/ovirt/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:47,615 root INFO copying build/lib/ansible_collections/ovirt/ovirt/meta/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/meta 2023-04-28 05:57:47,615 root INFO copying build/lib/ansible_collections/ovirt/ovirt/ovirt-ansible-collection.spec.in -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,616 root INFO copying build/lib/ansible_collections/ovirt/ovirt/build.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,616 root INFO copying build/lib/ansible_collections/ovirt/ovirt/ovirt-ansible-collection-2.4.1.tar.gz -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,616 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/licenses 2023-04-28 05:57:47,617 root INFO copying build/lib/ansible_collections/ovirt/ovirt/licenses/GPL-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/licenses 2023-04-28 05:57:47,617 root INFO copying build/lib/ansible_collections/ovirt/ovirt/licenses/Apache-license.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/licenses 2023-04-28 05:57:47,617 root INFO copying build/lib/ansible_collections/ovirt/ovirt/ovirt-ansible-collection.spec -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,617 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:47,618 root INFO copying build/lib/ansible_collections/ovirt/ovirt/changelogs/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:47,618 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/changelogs/fragments 2023-04-28 05:57:47,618 root INFO copying build/lib/ansible_collections/ovirt/ovirt/changelogs/fragments/.placeholder -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/changelogs/fragments 2023-04-28 05:57:47,618 root INFO copying build/lib/ansible_collections/ovirt/ovirt/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:47,618 root INFO copying build/lib/ansible_collections/ovirt/ovirt/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/changelogs 2023-04-28 05:57:47,619 root INFO copying build/lib/ansible_collections/ovirt/ovirt/README.md.in -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,619 root INFO copying build/lib/ansible_collections/ovirt/ovirt/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,619 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/examples 2023-04-28 05:57:47,619 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/examples/filters 2023-04-28 05:57:47,619 root INFO copying build/lib/ansible_collections/ovirt/ovirt/examples/filters/vmips.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/examples/filters 2023-04-28 05:57:47,620 root INFO copying build/lib/ansible_collections/ovirt/ovirt/examples/filters/ovirtdiff.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/examples/filters 2023-04-28 05:57:47,620 root INFO copying build/lib/ansible_collections/ovirt/ovirt/examples/ovirt_ansible_collections.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/examples 2023-04-28 05:57:47,620 root INFO copying build/lib/ansible_collections/ovirt/ovirt/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,620 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles 2023-04-28 05:57:47,620 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra 2023-04-28 05:57:47,621 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:47,621 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/tasks/remove_infra.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:47,621 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:47,621 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/tasks/create_infra.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/tasks 2023-04-28 05:57:47,621 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/defaults 2023-04-28 05:57:47,621 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/defaults 2023-04-28 05:57:47,622 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra 2023-04-28 05:57:47,622 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/examples 2023-04-28 05:57:47,622 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/examples/vars 2023-04-28 05:57:47,622 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples/vars/ovirt_infra_vars.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/examples/vars 2023-04-28 05:57:47,622 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples/vars/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/examples/vars 2023-04-28 05:57:47,623 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples/ovirt_infra_destroy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/examples 2023-04-28 05:57:47,623 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/examples/ovirt_infra.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/examples 2023-04-28 05:57:47,623 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles 2023-04-28 05:57:47,623 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc 2023-04-28 05:57:47,623 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/tasks 2023-04-28 05:57:47,624 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/tasks 2023-04-28 05:57:47,624 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/defaults 2023-04-28 05:57:47,624 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/defaults 2023-04-28 05:57:47,624 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc 2023-04-28 05:57:47,624 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers 2023-04-28 05:57:47,625 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/tasks 2023-04-28 05:57:47,625 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/tasks 2023-04-28 05:57:47,625 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers 2023-04-28 05:57:47,625 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts 2023-04-28 05:57:47,625 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/tasks 2023-04-28 05:57:47,625 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/tasks 2023-04-28 05:57:47,626 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/defaults 2023-04-28 05:57:47,626 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/defaults 2023-04-28 05:57:47,626 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/hosts 2023-04-28 05:57:47,626 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters 2023-04-28 05:57:47,626 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/tasks 2023-04-28 05:57:47,627 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/tasks 2023-04-28 05:57:47,627 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/defaults 2023-04-28 05:57:47,627 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/defaults 2023-04-28 05:57:47,627 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters 2023-04-28 05:57:47,627 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions 2023-04-28 05:57:47,627 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/tasks 2023-04-28 05:57:47,628 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/tasks 2023-04-28 05:57:47,628 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/permissions 2023-04-28 05:57:47,628 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools 2023-04-28 05:57:47,628 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/tasks 2023-04-28 05:57:47,628 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/tasks 2023-04-28 05:57:47,629 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools 2023-04-28 05:57:47,629 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters 2023-04-28 05:57:47,629 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/tasks 2023-04-28 05:57:47,629 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/tasks 2023-04-28 05:57:47,630 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters 2023-04-28 05:57:47,630 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/vars 2023-04-28 05:57:47,630 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/vars 2023-04-28 05:57:47,630 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup 2023-04-28 05:57:47,630 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,631 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/vms.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,631 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/datacenter.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,631 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/vm_pools.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,631 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/disks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,631 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/cluster_and_hosts.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,632 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/templates.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,632 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,632 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/storages_pre.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,632 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/storages_last.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks 2023-04-28 05:57:47,632 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/defaults 2023-04-28 05:57:47,633 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/defaults 2023-04-28 05:57:47,633 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup 2023-04-28 05:57:47,633 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/storages 2023-04-28 05:57:47,633 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/storages/tasks 2023-04-28 05:57:47,633 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/storages/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/storages/tasks 2023-04-28 05:57:47,634 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/storages/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/storages 2023-04-28 05:57:47,634 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/networks 2023-04-28 05:57:47,634 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/networks/tasks 2023-04-28 05:57:47,634 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/networks/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/networks/tasks 2023-04-28 05:57:47,634 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/infra/roles/networks/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/infra/roles/networks 2023-04-28 05:57:47,634 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env 2023-04-28 05:57:47,635 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env/tasks 2023-04-28 05:57:47,635 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env/tasks 2023-04-28 05:57:47,635 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env/defaults 2023-04-28 05:57:47,635 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env/defaults 2023-04-28 05:57:47,635 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env 2023-04-28 05:57:47,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples 2023-04-28 05:57:47,636 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples/shutdown_env.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples 2023-04-28 05:57:47,636 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/shutdown_env/examples 2023-04-28 05:57:47,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template 2023-04-28 05:57:47,636 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:47,636 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks/empty.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:47,637 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:47,637 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks/glance_image.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:47,637 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/tasks/qcow2_image.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/tasks 2023-04-28 05:57:47,637 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/defaults 2023-04-28 05:57:47,637 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/defaults 2023-04-28 05:57:47,638 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template 2023-04-28 05:57:47,638 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/vars 2023-04-28 05:57:47,638 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/vars 2023-04-28 05:57:47,638 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/examples 2023-04-28 05:57:47,638 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/examples/ovirt_image_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/examples 2023-04-28 05:57:47,639 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/image_template/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/image_template/examples 2023-04-28 05:57:47,639 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup 2023-04-28 05:57:47,639 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:47,639 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/pre_install_checks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:47,639 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/restore_engine_from_file.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:47,640 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/engine_setup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:47,640 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:47,640 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tasks 2023-04-28 05:57:47,640 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/defaults 2023-04-28 05:57:47,640 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/defaults 2023-04-28 05:57:47,641 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup 2023-04-28 05:57:47,641 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,641 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,641 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/engine-upgrade.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,641 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-4.2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,641 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/containers-deploy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,642 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-upgrade-4.2-to-master.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,642 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-master.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,642 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,642 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,642 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/tests/engine-deploy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/tests 2023-04-28 05:57:47,643 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,643 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.5_upgrade.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,643 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.1_basic.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,643 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.2_basic.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,643 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.4_basic.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,644 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.3_upgrade.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,644 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.5_basic.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,644 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.3_basic.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,644 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.1_upgrade.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,644 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/basic_answerfile.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,645 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.4_upgrade.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,645 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.2_upgrade.txt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/templates 2023-04-28 05:57:47,645 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/vars 2023-04-28 05:57:47,645 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/vars 2023-04-28 05:57:47,645 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:47,646 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/examples/engine-upgrade.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:47,646 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:47,646 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/engine_setup/examples/engine-deploy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/engine_setup/examples 2023-04-28 05:57:47,646 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun 2023-04-28 05:57:47,646 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:47,646 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/fetch_hosts.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:47,647 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/remove_mpath_device.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:47,647 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks 2023-04-28 05:57:47,647 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/defaults 2023-04-28 05:57:47,647 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/defaults 2023-04-28 05:57:47,647 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun 2023-04-28 05:57:47,648 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples 2023-04-28 05:57:47,648 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples/remove_stale_lun.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples 2023-04-28 05:57:47,648 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples 2023-04-28 05:57:47,648 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery 2023-04-28 05:57:47,648 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:47,649 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/unregister_entities.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:47,649 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/run_unregistered_entities.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:47,649 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/generate_mapping.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:47,649 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:47,649 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,650 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_disks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,650 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/shutdown_vm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,650 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_invalid_filtered_master_domains.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,650 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/shutdown_vms.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,650 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,650 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_vms.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,651 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_domain_process.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,651 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_valid_filtered_master_domains.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,651 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/update_ovf_store.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean 2023-04-28 05:57:47,651 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean_engine.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:47,651 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover_engine.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks 2023-04-28 05:57:47,652 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,652 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_iscsi_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,652 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,652 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_nfs_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,652 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,653 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_vm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,653 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/run_vms.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,653 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_templates.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,653 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_fcp_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,653 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_glusterfs_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,654 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_vms.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,654 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/report_log_template.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,654 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_posixfs_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,654 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/print_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover 2023-04-28 05:57:47,654 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/defaults 2023-04-28 05:57:47,655 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/defaults 2023-04-28 05:57:47,655 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery 2023-04-28 05:57:47,655 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,655 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/dr.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,655 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,656 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/validator.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,656 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/vault_secret.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,656 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/bcolors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,656 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/fail_over.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,657 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_vars_test.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,657 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/fail_back.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,657 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/ovirt-dr -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,657 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_vars.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files 2023-04-28 05:57:47,657 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:47,657 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/dr_ovirt_setup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:47,658 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/disaster_recovery_vars.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:47,658 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/dr_play.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:47,658 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/ovirt_passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples 2023-04-28 05:57:47,658 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra 2023-04-28 05:57:47,658 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,659 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/create_inventory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,659 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/manage_state.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,659 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/create_vms.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,659 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/vm_state_present.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,659 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/vm_state_absent.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,660 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,660 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/affinity_labels.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,660 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/affinity_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/tasks 2023-04-28 05:57:47,660 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/defaults 2023-04-28 05:57:47,660 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/defaults 2023-04-28 05:57:47,661 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra 2023-04-28 05:57:47,661 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:47,661 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/examples/ovirt_vm_infra_inv.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:47,661 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/examples/ovirt_vm_infra.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:47,661 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/vm_infra/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/vm_infra/examples 2023-04-28 05:57:47,662 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup 2023-04-28 05:57:47,662 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,662 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fc_getdevices.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,662 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/apply_openscap_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,662 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/get_local_vm_disk_path.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,662 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_vlan_name.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,663 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_ip_prefix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,663 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/restore_backup.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,663 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_local_storage_pools.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,663 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_host_ip.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,663 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/restore_host_redeploy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,664 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:47,664 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/03_engine_initial_tasks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:47,664 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:47,664 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/02_create_local_vm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:47,664 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:47,665 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/04_engine_final_tasks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm 2023-04-28 05:57:47,665 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_machine.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,665 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_revoke.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,665 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/iscsi_getdevices.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,665 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_cloud_init_config.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,666 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,666 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_vcpus_count.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,666 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,666 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_gateway.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,666 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_services_status.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,667 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/002_validate_hostname_tasks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,667 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/define_variables.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,667 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_firewalld.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,667 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_data_center_name.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,667 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_memory_size.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,668 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_mac_address.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,668 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_network_test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks 2023-04-28 05:57:47,668 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_localvm_dir.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,668 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/final_clean.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,668 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/partial_execution.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,669 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_vlan_bond_mode.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,669 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/initial_clean.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,669 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/iscsi_discover.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,669 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/filter_unsupported_vlan_devices.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,669 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/full_execution.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,670 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/alter_libvirt_default_net_configuration.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,670 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/search_available_network_subnet.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,670 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_sso.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,670 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/add_engine_as_ansible_host.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,670 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,671 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pause_execution.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,671 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/get_appliance_dist.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,671 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:47,671 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:47,671 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/03_hosted_engine_final_tasks.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:47,672 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/02_engine_vm_configuration.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm 2023-04-28 05:57:47,672 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/ipv_switch.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,672 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_engine_logs.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,672 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/install_appliance.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,672 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/filter_team_devices.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,673 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/install_packages.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,673 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_storage_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks 2023-04-28 05:57:47,673 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks 2023-04-28 05:57:47,673 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_after_engine_setup 2023-04-28 05:57:47,673 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_after_engine_setup/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_after_engine_setup 2023-04-28 05:57:47,674 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup 2023-04-28 05:57:47,674 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup 2023-04-28 05:57:47,674 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup/add_host_storage_domain.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup 2023-04-28 05:57:47,674 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_before_engine_setup 2023-04-28 05:57:47,674 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_before_engine_setup/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_before_engine_setup 2023-04-28 05:57:47,674 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_add_host 2023-04-28 05:57:47,675 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_add_host/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_add_host 2023-04-28 05:57:47,675 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults 2023-04-28 05:57:47,675 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults 2023-04-28 05:57:47,675 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup 2023-04-28 05:57:47,675 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,676 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/meta-data.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,676 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-dhcp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,676 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/vm.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,676 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/fhanswers.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,676 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/version.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,677 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/user-data.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,677 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/network-config.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,677 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/network-config-dhcp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,677 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/hosted-engine.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,677 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-static-ipv6.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,678 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-static.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,678 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/broker.conf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates 2023-04-28 05:57:47,678 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/files 2023-04-28 05:57:47,678 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/files/35-allow-ansible-for-vdsm.rules -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/files 2023-04-28 05:57:47,678 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:47,678 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/hosted_engine_deploy_remotehost.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:47,679 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/required_networks_fix.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:47,679 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/hosted_engine_deploy_localhost.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:47,679 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/nfs_deployment.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:47,679 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:47,679 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/iscsi_deployment_remote.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples 2023-04-28 05:57:47,680 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories 2023-04-28 05:57:47,680 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,680 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks/rpm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,680 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks/rh-subscription.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,680 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,681 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks/search-pool-id.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,681 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks/backup-repos.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,681 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks/install-satellite-ca.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,681 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/tasks/satellite-subscription.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/tasks 2023-04-28 05:57:47,681 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/defaults 2023-04-28 05:57:47,682 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/defaults 2023-04-28 05:57:47,682 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories 2023-04-28 05:57:47,682 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,682 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.3.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,682 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,683 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/host_ppc_eus_4.4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,683 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.3.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,683 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/host_eus_4.4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,683 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.1.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,683 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_eus_4.4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,683 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,684 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.1.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,684 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/host_ppc_4.4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,684 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/default.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,684 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.1.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,684 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,685 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.4.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,685 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.3.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,685 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,685 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.2.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/vars 2023-04-28 05:57:47,685 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:47,686 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/examples/ovirt_repositories_subscription_manager.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:47,686 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/examples/ovirt_repositories_release_rpm.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:47,686 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/repositories/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/repositories/examples 2023-04-28 05:57:47,686 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade 2023-04-28 05:57:47,686 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:47,687 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/cluster_policy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:47,687 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/pinned_vms.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:47,687 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:47,687 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/upgrade.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:47,687 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/log_progress.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks 2023-04-28 05:57:47,688 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/defaults 2023-04-28 05:57:47,688 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/defaults 2023-04-28 05:57:47,688 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade 2023-04-28 05:57:47,688 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples 2023-04-28 05:57:47,688 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples/cluster_upgrade.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples 2023-04-28 05:57:47,689 root INFO copying build/lib/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples/passwords.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples 2023-04-28 05:57:47,689 root INFO copying build/lib/ansible_collections/ovirt/ovirt/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ovirt/ovirt 2023-04-28 05:57:47,689 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack 2023-04-28 05:57:47,689 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,689 root INFO copying build/lib/ansible_collections/openstack/cloud/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,690 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins 2023-04-28 05:57:47,690 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/doc_fragments 2023-04-28 05:57:47,690 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/doc_fragments 2023-04-28 05:57:47,690 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/doc_fragments/openstack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/doc_fragments 2023-04-28 05:57:47,690 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/inventory 2023-04-28 05:57:47,690 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/inventory 2023-04-28 05:57:47,691 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/inventory/openstack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/inventory 2023-04-28 05:57:47,691 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,691 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/catalog_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,691 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/object_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,691 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/federation_idp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,692 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/role_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,692 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/coe_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,692 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/federation_idp_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,692 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,692 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,693 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_coe_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,693 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,693 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/host_aggregate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,693 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,693 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,694 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/security_group_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,694 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,694 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,694 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_federation_protocol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,695 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,695 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/compute_flavor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,695 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/coe_cluster_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,695 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,695 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,696 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/keystone_federation_protocol_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,696 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/address_scope.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,696 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,696 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_user_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,696 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,697 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_stack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,697 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/stack_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,697 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/subnet_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,697 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,697 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/baremetal_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,698 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_port_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,698 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_flavor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,698 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,698 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,698 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/lb_health_monitor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,699 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,699 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/lb_listener.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,699 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,699 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,699 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_loadbalancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,700 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,700 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,700 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/floating_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,700 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/loadbalancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,701 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,701 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_identity_provider.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,701 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,701 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/keypair_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,701 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/baremetal_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,702 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,702 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/federation_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,702 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,702 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_server_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,702 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/group_assignment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,703 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,703 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,703 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_ironic_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,703 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/lb_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,703 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_client_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,704 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_floating_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,704 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/routers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,704 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,704 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/baremetal_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,704 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,705 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,705 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/baremetal_port_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,705 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_recordset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,705 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,705 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_federation_protocol_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,706 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_subnets_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,706 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keypair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,706 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_project_access.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,706 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,706 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,707 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/server_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,707 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_ironic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,707 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/dns_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,707 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/neutron_rbac_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,707 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/baremetal_inspect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,708 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_listener.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,708 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,708 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,708 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_ironic_inspect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,708 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/volume_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,709 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/volume_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,709 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/server_metadata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,709 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/security_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,709 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,709 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_server_metadata.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,710 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/project_access.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,710 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_user_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,710 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/project_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,710 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/server_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,711 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_nova_flavor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,711 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/volume_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,711 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,711 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,711 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/stack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,712 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,712 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,712 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/compute_flavor_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,712 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_project_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,712 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/volume_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,713 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,713 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,713 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/neutron_rbac_policies_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,713 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,713 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_coe_cluster_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,714 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_volume_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,714 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_networks_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,714 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/compute_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,714 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/lb_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,714 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,715 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/identity_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,715 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_server_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,715 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/volume_backup_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,715 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/security_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,715 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/server_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,716 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/federation_mapping.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,716 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/subnets_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,716 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/networks_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,716 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_server_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,716 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_security_group_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,717 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/floating_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,717 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/keypair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,717 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,717 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_mapping_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,718 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/keystone_federation_protocol.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,718 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_security_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,718 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_routers_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,718 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,718 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_router.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,719 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,719 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/baremetal_node_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,719 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/security_group_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,719 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/recordset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,719 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/port_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,720 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/router.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,720 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/dns_zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,720 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,720 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_nova_host_aggregate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,721 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_keystone_identity_provider_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,721 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/modules/os_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/modules 2023-04-28 05:57:47,721 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:47,721 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/module_utils/ironic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:47,721 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:47,721 root INFO copying build/lib/ansible_collections/openstack/cloud/plugins/module_utils/openstack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/plugins/module_utils 2023-04-28 05:57:47,722 root INFO copying build/lib/ansible_collections/openstack/cloud/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,722 root INFO copying build/lib/ansible_collections/openstack/cloud/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,722 root INFO copying build/lib/ansible_collections/openstack/cloud/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,722 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/meta 2023-04-28 05:57:47,723 root INFO copying build/lib/ansible_collections/openstack/cloud/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/meta 2023-04-28 05:57:47,723 root INFO copying build/lib/ansible_collections/openstack/cloud/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,723 root INFO copying build/lib/ansible_collections/openstack/cloud/setup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,723 root INFO copying build/lib/ansible_collections/openstack/cloud/CONTRIBUTING.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,724 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/scripts 2023-04-28 05:57:47,724 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/scripts/inventory 2023-04-28 05:57:47,724 root INFO copying build/lib/ansible_collections/openstack/cloud/scripts/inventory/openstack_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/scripts/inventory 2023-04-28 05:57:47,724 root INFO copying build/lib/ansible_collections/openstack/cloud/scripts/inventory/openstack.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud/scripts/inventory 2023-04-28 05:57:47,724 root INFO copying build/lib/ansible_collections/openstack/cloud/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,724 root INFO copying build/lib/ansible_collections/openstack/cloud/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/openstack/cloud 2023-04-28 05:57:47,725 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm 2023-04-28 05:57:47,725 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,725 root INFO copying build/lib/ansible_collections/ibm/qradar/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,725 root INFO copying build/lib/ansible_collections/ibm/qradar/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,725 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins 2023-04-28 05:57:47,726 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,726 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,726 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_offense_note.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,726 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_offense_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,726 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_log_source_management.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,727 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/offense_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,727 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/log_source_management.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,727 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_log_sources_management.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,727 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,727 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_analytics_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,728 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/offense_note.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,728 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,728 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,728 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_offense_action.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,728 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,729 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/qradar_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,729 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/modules/offense_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/modules 2023-04-28 05:57:47,729 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:47,729 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/action/qradar_log_sources_management.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:47,729 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/action/qradar_analytics_rules.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:47,729 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/action 2023-04-28 05:57:47,730 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/httpapi 2023-04-28 05:57:47,730 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/httpapi/qradar.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/httpapi 2023-04-28 05:57:47,730 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/module_utils 2023-04-28 05:57:47,730 root INFO copying build/lib/ansible_collections/ibm/qradar/plugins/module_utils/qradar.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/plugins/module_utils 2023-04-28 05:57:47,730 root INFO copying build/lib/ansible_collections/ibm/qradar/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,731 root INFO copying build/lib/ansible_collections/ibm/qradar/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,731 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/meta 2023-04-28 05:57:47,731 root INFO copying build/lib/ansible_collections/ibm/qradar/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/meta 2023-04-28 05:57:47,731 root INFO copying build/lib/ansible_collections/ibm/qradar/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,731 root INFO copying build/lib/ansible_collections/ibm/qradar/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,732 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/changelogs 2023-04-28 05:57:47,732 root INFO copying build/lib/ansible_collections/ibm/qradar/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/changelogs 2023-04-28 05:57:47,732 root INFO copying build/lib/ansible_collections/ibm/qradar/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar/changelogs 2023-04-28 05:57:47,732 root INFO copying build/lib/ansible_collections/ibm/qradar/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,732 root INFO copying build/lib/ansible_collections/ibm/qradar/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,733 root INFO copying build/lib/ansible_collections/ibm/qradar/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,733 root INFO copying build/lib/ansible_collections/ibm/qradar/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/qradar 2023-04-28 05:57:47,733 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:47,733 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins 2023-04-28 05:57:47,733 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins 2023-04-28 05:57:47,734 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,734 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_safeguarded_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,734 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_replication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,734 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_sra.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,734 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_vol_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,735 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_cloud_backups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,735 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_initial_setup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,735 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_provisioning_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,735 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_start_stop_replication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,736 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_switch_replication_direction.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,736 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_ownershipgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,736 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_snapshotpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,736 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_hostcluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,736 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,737 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_awss3_cloudaccount.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,737 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_flashcopy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,737 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_mdisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,737 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_replicationgroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,737 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_callhome.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,738 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_ip_partnership.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,738 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_auth.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,738 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,738 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_cv.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,739 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_consistgrp_flashcopy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,739 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,739 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_migration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,739 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_volumegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,739 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_replication_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,740 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_truststore_for_replication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,740 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,740 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_start_stop_flashcopy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,740 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,740 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svcinfo_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,741 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_restore_cloud_backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,741 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,741 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_portset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,741 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,742 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_complete_initial_setup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,742 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_mdiskgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,742 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_ssl_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,742 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_usergroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,742 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svctask_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,743 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_vdisk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,743 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_mirrored_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/modules 2023-04-28 05:57:47,743 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils 2023-04-28 05:57:47,743 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/ibm_svc_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils 2023-04-28 05:57:47,743 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/ibm_svc_ssh.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils 2023-04-28 05:57:47,744 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:47,744 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:47,744 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/meta 2023-04-28 05:57:47,744 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/meta 2023-04-28 05:57:47,744 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/meta 2023-04-28 05:57:47,745 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:47,745 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,745 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks/volume_migrate.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,745 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks/generic_ansible_sample.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,745 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks/generic_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,746 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks/volumegrp_create.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,746 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks/initial_setup_system_complete.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,746 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks/map_volume_to_host.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,746 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/playbooks/create_GMCV_in_CG.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/playbooks 2023-04-28 05:57:47,746 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/changelogs 2023-04-28 05:57:47,747 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/changelogs 2023-04-28 05:57:47,747 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:47,747 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/roles 2023-04-28 05:57:47,747 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/roles/place_holder -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize/roles 2023-04-28 05:57:47,747 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:47,748 root INFO copying build/lib/ansible_collections/ibm/spectrum_virtualize/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ibm/spectrum_virtualize 2023-04-28 05:57:47,748 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba 2023-04-28 05:57:47,748 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,748 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,748 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins 2023-04-28 05:57:47,749 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:47,749 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/sql_credentials.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:47,749 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:47,749 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/state.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments 2023-04-28 05:57:47,749 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,749 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,750 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/nonquery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,750 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/login.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,750 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/ag_replica.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,750 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/first_responder_kit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,750 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/sp_configure.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,751 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/install_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,751 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/database.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,751 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/availability_group.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,751 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/memory.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,751 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/restore.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,752 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/instance_info.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,752 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_category.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,752 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,752 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/sp_configure.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,752 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/sp_whoisactive.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,753 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/sa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,753 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/rg_workload_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,753 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/backup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,753 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/hadr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,753 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_category.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,754 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/dba_multitool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,754 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/first_responder_kit.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,754 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_schedule.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,755 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/spn.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,755 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/install_script.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,755 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/tcp_port.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,755 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/availability_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,755 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/rg_workload_group.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,756 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/backup.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,756 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/hadr.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,756 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/maintenance_solution.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,756 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/resource_governor.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,756 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/maintenance_solution.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,757 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/resource_governor.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,757 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/login.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,757 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_step.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,757 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,757 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/rg_resource_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,758 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_schedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,758 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,758 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/ag_listener.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,758 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/memory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,758 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/dba_multitool.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,759 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/sp_whoisactive.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,759 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/user.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,759 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/restore.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,759 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/spn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,759 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/nonquery.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,760 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/traceflag.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,760 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/ag_listener.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,760 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_step.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,760 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/ag_replica.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,760 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/rg_resource_pool.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,761 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/credential.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,761 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,761 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/sa.ps1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,761 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/traceflag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,761 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/tcp_port.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,762 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/modules/credential.py -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/modules 2023-04-28 05:57:47,762 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/module_utils 2023-04-28 05:57:47,762 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/plugins/module_utils/_SqlServerUtils.psm1 -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/plugins/module_utils 2023-04-28 05:57:47,762 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/MAINTAINERS -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,762 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,762 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,763 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/meta 2023-04-28 05:57:47,763 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/meta 2023-04-28 05:57:47,763 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,763 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/CODE_OF_CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,764 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,764 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/changelogs 2023-04-28 05:57:47,764 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/changelogs/fragments 2023-04-28 05:57:47,764 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/changelogs/fragments 2023-04-28 05:57:47,764 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/changelogs 2023-04-28 05:57:47,765 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver/changelogs 2023-04-28 05:57:47,765 root INFO copying build/lib/ansible_collections/lowlydba/sqlserver/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/lowlydba/sqlserver 2023-04-28 05:57:47,765 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr 2023-04-28 05:57:47,765 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,765 root INFO copying build/lib/ansible_collections/vultr/cloud/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins 2023-04-28 05:57:47,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/doc_fragments 2023-04-28 05:57:47,766 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/doc_fragments/vultr_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/doc_fragments 2023-04-28 05:57:47,766 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/doc_fragments 2023-04-28 05:57:47,766 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/inventory 2023-04-28 05:57:47,766 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/inventory/vultr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/inventory 2023-04-28 05:57:47,767 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,767 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/vpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,767 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/region_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,767 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/firewall_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,767 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,768 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/reserved_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,768 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/block_storage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,768 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/plan_metal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,768 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,768 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/startup_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,769 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,769 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/block_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,769 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,769 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/firewall_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,769 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/account_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,770 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/dns_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,770 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,770 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/startup_script_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,770 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/ssh_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,770 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/plan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,771 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/firewall_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,771 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/vpc_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,771 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,771 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/dns_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,771 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,771 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/ssh_key_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,772 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/os_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,772 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,772 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/modules/firewall_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/modules 2023-04-28 05:57:47,772 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/module_utils 2023-04-28 05:57:47,772 root INFO copying build/lib/ansible_collections/vultr/cloud/plugins/module_utils/vultr_v2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/plugins/module_utils 2023-04-28 05:57:47,773 root INFO copying build/lib/ansible_collections/vultr/cloud/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,773 root INFO copying build/lib/ansible_collections/vultr/cloud/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,773 root INFO copying build/lib/ansible_collections/vultr/cloud/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,773 root INFO copying build/lib/ansible_collections/vultr/cloud/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,774 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/meta 2023-04-28 05:57:47,774 root INFO copying build/lib/ansible_collections/vultr/cloud/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/meta 2023-04-28 05:57:47,774 root INFO copying build/lib/ansible_collections/vultr/cloud/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,774 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:47,774 root INFO copying build/lib/ansible_collections/vultr/cloud/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:47,775 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/changelogs/fragments 2023-04-28 05:57:47,775 root INFO copying build/lib/ansible_collections/vultr/cloud/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/changelogs/fragments 2023-04-28 05:57:47,775 root INFO copying build/lib/ansible_collections/vultr/cloud/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:47,775 root INFO copying build/lib/ansible_collections/vultr/cloud/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud/changelogs 2023-04-28 05:57:47,775 root INFO copying build/lib/ansible_collections/vultr/cloud/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/vultr/cloud 2023-04-28 05:57:47,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista 2023-04-28 05:57:47,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,776 root INFO copying build/lib/ansible_collections/arista/eos/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,776 root INFO copying build/lib/ansible_collections/arista/eos/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins 2023-04-28 05:57:47,776 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/terminal 2023-04-28 05:57:47,777 root INFO copying build/lib/ansible_collections/arista/eos/plugins/terminal/eos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/terminal 2023-04-28 05:57:47,777 root INFO copying build/lib/ansible_collections/arista/eos/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/terminal 2023-04-28 05:57:47,777 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/filter 2023-04-28 05:57:47,777 root INFO copying build/lib/ansible_collections/arista/eos/plugins/filter/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/filter 2023-04-28 05:57:47,777 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/inventory 2023-04-28 05:57:47,777 root INFO copying build/lib/ansible_collections/arista/eos/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/inventory 2023-04-28 05:57:47,778 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,778 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,778 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,778 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,779 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,779 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,779 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,779 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,779 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,780 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,780 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,780 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,780 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,780 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_eapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,781 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,781 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,781 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,781 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,782 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,782 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,782 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,782 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,783 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,783 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,783 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,783 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,784 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,784 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,784 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,784 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,784 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,785 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,785 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,785 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,785 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,785 root INFO copying build/lib/ansible_collections/arista/eos/plugins/modules/eos_lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/modules 2023-04-28 05:57:47,786 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/cliconf 2023-04-28 05:57:47,786 root INFO copying build/lib/ansible_collections/arista/eos/plugins/cliconf/eos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/cliconf 2023-04-28 05:57:47,786 root INFO copying build/lib/ansible_collections/arista/eos/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/cliconf 2023-04-28 05:57:47,786 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,786 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,787 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,787 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,787 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,787 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,787 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/eapi.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,788 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,788 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,788 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,788 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/vrf.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,788 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,789 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,789 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,789 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,789 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,789 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,790 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/eos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,790 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,790 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/lldp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,790 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/logging.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,790 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,790 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,791 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,791 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,791 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,791 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/static_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,791 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,792 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,792 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,792 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,792 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,792 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,793 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,793 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,793 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/l3_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,793 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,793 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/l2_interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,794 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,794 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,794 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/linkagg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,794 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,794 root INFO copying build/lib/ansible_collections/arista/eos/plugins/action/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/action 2023-04-28 05:57:47,795 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/httpapi 2023-04-28 05:57:47,795 root INFO copying build/lib/ansible_collections/arista/eos/plugins/httpapi/eos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/httpapi 2023-04-28 05:57:47,795 root INFO copying build/lib/ansible_collections/arista/eos/plugins/httpapi/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/httpapi 2023-04-28 05:57:47,795 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils 2023-04-28 05:57:47,795 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils 2023-04-28 05:57:47,795 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network 2023-04-28 05:57:47,796 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos 2023-04-28 05:57:47,796 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:47,796 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:47,796 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/providers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:47,796 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli 2023-04-28 05:57:47,797 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli 2023-04-28 05:57:47,797 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config 2023-04-28 05:57:47,797 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:47,797 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:47,797 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:47,797 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:47,798 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/process.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp 2023-04-28 05:57:47,798 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config 2023-04-28 05:57:47,798 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/module.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers 2023-04-28 05:57:47,798 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts 2023-04-28 05:57:47,799 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans 2023-04-28 05:57:47,799 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans 2023-04-28 05:57:47,799 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans 2023-04-28 05:57:47,799 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes 2023-04-28 05:57:47,799 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes 2023-04-28 05:57:47,799 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes 2023-04-28 05:57:47,800 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2 2023-04-28 05:57:47,800 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2 2023-04-28 05:57:47,800 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2 2023-04-28 05:57:47,800 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts 2023-04-28 05:57:47,801 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces 2023-04-28 05:57:47,801 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces 2023-04-28 05:57:47,801 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces 2023-04-28 05:57:47,801 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family 2023-04-28 05:57:47,801 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family 2023-04-28 05:57:47,801 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family 2023-04-28 05:57:47,802 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global 2023-04-28 05:57:47,802 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global 2023-04-28 05:57:47,802 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global 2023-04-28 05:57:47,802 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces 2023-04-28 05:57:47,802 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces 2023-04-28 05:57:47,803 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces 2023-04-28 05:57:47,803 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts 2023-04-28 05:57:47,803 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps 2023-04-28 05:57:47,803 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps 2023-04-28 05:57:47,803 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps 2023-04-28 05:57:47,804 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces 2023-04-28 05:57:47,804 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces 2023-04-28 05:57:47,804 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces 2023-04-28 05:57:47,804 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists 2023-04-28 05:57:47,804 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists 2023-04-28 05:57:47,804 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists 2023-04-28 05:57:47,805 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname 2023-04-28 05:57:47,805 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname 2023-04-28 05:57:47,805 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname 2023-04-28 05:57:47,805 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server 2023-04-28 05:57:47,805 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server 2023-04-28 05:57:47,806 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server 2023-04-28 05:57:47,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces 2023-04-28 05:57:47,806 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces 2023-04-28 05:57:47,806 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces 2023-04-28 05:57:47,806 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces 2023-04-28 05:57:47,806 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces 2023-04-28 05:57:47,807 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces 2023-04-28 05:57:47,807 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global 2023-04-28 05:57:47,807 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global 2023-04-28 05:57:47,807 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global 2023-04-28 05:57:47,807 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces 2023-04-28 05:57:47,808 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces 2023-04-28 05:57:47,808 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces 2023-04-28 05:57:47,808 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy 2023-04-28 05:57:47,808 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/base.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy 2023-04-28 05:57:47,808 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy 2023-04-28 05:57:47,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces 2023-04-28 05:57:47,809 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces 2023-04-28 05:57:47,809 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces 2023-04-28 05:57:47,809 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global 2023-04-28 05:57:47,809 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global 2023-04-28 05:57:47,809 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global 2023-04-28 05:57:47,810 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global 2023-04-28 05:57:47,810 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global 2023-04-28 05:57:47,810 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global 2023-04-28 05:57:47,810 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces 2023-04-28 05:57:47,810 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces 2023-04-28 05:57:47,811 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces 2023-04-28 05:57:47,811 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp 2023-04-28 05:57:47,811 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp 2023-04-28 05:57:47,811 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp 2023-04-28 05:57:47,811 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3 2023-04-28 05:57:47,812 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3 2023-04-28 05:57:47,812 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3 2023-04-28 05:57:47,812 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls 2023-04-28 05:57:47,812 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls 2023-04-28 05:57:47,812 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls 2023-04-28 05:57:47,813 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,813 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,813 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,813 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,814 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,814 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,814 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,814 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,814 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,815 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,815 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,815 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates 2023-04-28 05:57:47,815 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils 2023-04-28 05:57:47,816 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils 2023-04-28 05:57:47,816 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils 2023-04-28 05:57:47,816 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/eos.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos 2023-04-28 05:57:47,816 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos 2023-04-28 05:57:47,816 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config 2023-04-28 05:57:47,817 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans 2023-04-28 05:57:47,817 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans 2023-04-28 05:57:47,817 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans 2023-04-28 05:57:47,817 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes 2023-04-28 05:57:47,817 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes 2023-04-28 05:57:47,818 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes 2023-04-28 05:57:47,818 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2 2023-04-28 05:57:47,818 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2 2023-04-28 05:57:47,818 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2 2023-04-28 05:57:47,818 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces 2023-04-28 05:57:47,818 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces 2023-04-28 05:57:47,819 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces 2023-04-28 05:57:47,819 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family 2023-04-28 05:57:47,819 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family 2023-04-28 05:57:47,819 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family 2023-04-28 05:57:47,819 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global 2023-04-28 05:57:47,820 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global 2023-04-28 05:57:47,820 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global 2023-04-28 05:57:47,820 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces 2023-04-28 05:57:47,820 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces 2023-04-28 05:57:47,820 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces 2023-04-28 05:57:47,821 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config 2023-04-28 05:57:47,821 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps 2023-04-28 05:57:47,821 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps 2023-04-28 05:57:47,821 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps 2023-04-28 05:57:47,821 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces 2023-04-28 05:57:47,822 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces 2023-04-28 05:57:47,822 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces 2023-04-28 05:57:47,822 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists 2023-04-28 05:57:47,822 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists 2023-04-28 05:57:47,822 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists 2023-04-28 05:57:47,823 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname 2023-04-28 05:57:47,823 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname 2023-04-28 05:57:47,823 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname 2023-04-28 05:57:47,823 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server 2023-04-28 05:57:47,823 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server 2023-04-28 05:57:47,823 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server 2023-04-28 05:57:47,824 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces 2023-04-28 05:57:47,824 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces 2023-04-28 05:57:47,824 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces 2023-04-28 05:57:47,824 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces 2023-04-28 05:57:47,824 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces 2023-04-28 05:57:47,825 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces 2023-04-28 05:57:47,825 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global 2023-04-28 05:57:47,825 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global 2023-04-28 05:57:47,825 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global 2023-04-28 05:57:47,825 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces 2023-04-28 05:57:47,826 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces 2023-04-28 05:57:47,826 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces 2023-04-28 05:57:47,826 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces 2023-04-28 05:57:47,826 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces 2023-04-28 05:57:47,826 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces 2023-04-28 05:57:47,827 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global 2023-04-28 05:57:47,827 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global 2023-04-28 05:57:47,827 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global 2023-04-28 05:57:47,827 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global 2023-04-28 05:57:47,827 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global 2023-04-28 05:57:47,828 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global 2023-04-28 05:57:47,828 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces 2023-04-28 05:57:47,828 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces 2023-04-28 05:57:47,828 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces 2023-04-28 05:57:47,828 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp 2023-04-28 05:57:47,829 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp 2023-04-28 05:57:47,829 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp 2023-04-28 05:57:47,829 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3 2023-04-28 05:57:47,829 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3 2023-04-28 05:57:47,829 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3 2023-04-28 05:57:47,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls 2023-04-28 05:57:47,830 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls 2023-04-28 05:57:47,830 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls 2023-04-28 05:57:47,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec 2023-04-28 05:57:47,830 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans 2023-04-28 05:57:47,830 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans 2023-04-28 05:57:47,831 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans 2023-04-28 05:57:47,831 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes 2023-04-28 05:57:47,831 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes 2023-04-28 05:57:47,831 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes 2023-04-28 05:57:47,831 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts 2023-04-28 05:57:47,832 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts 2023-04-28 05:57:47,832 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts 2023-04-28 05:57:47,832 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2 2023-04-28 05:57:47,832 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2 2023-04-28 05:57:47,832 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/ospfv2.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2 2023-04-28 05:57:47,833 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces 2023-04-28 05:57:47,833 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces 2023-04-28 05:57:47,833 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces 2023-04-28 05:57:47,833 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family 2023-04-28 05:57:47,833 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/bgp_address_family.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family 2023-04-28 05:57:47,834 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family 2023-04-28 05:57:47,834 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global 2023-04-28 05:57:47,834 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/lldp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global 2023-04-28 05:57:47,834 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global 2023-04-28 05:57:47,834 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces 2023-04-28 05:57:47,834 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/lldp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces 2023-04-28 05:57:47,835 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces 2023-04-28 05:57:47,835 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec 2023-04-28 05:57:47,835 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps 2023-04-28 05:57:47,835 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/route_maps.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps 2023-04-28 05:57:47,835 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps 2023-04-28 05:57:47,836 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces 2023-04-28 05:57:47,836 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces 2023-04-28 05:57:47,836 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces 2023-04-28 05:57:47,836 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists 2023-04-28 05:57:47,836 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists 2023-04-28 05:57:47,836 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists 2023-04-28 05:57:47,837 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname 2023-04-28 05:57:47,837 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/hostname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname 2023-04-28 05:57:47,837 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname 2023-04-28 05:57:47,837 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server 2023-04-28 05:57:47,837 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server 2023-04-28 05:57:47,838 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/snmp_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server 2023-04-28 05:57:47,838 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces 2023-04-28 05:57:47,838 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces 2023-04-28 05:57:47,838 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces 2023-04-28 05:57:47,838 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces 2023-04-28 05:57:47,839 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces 2023-04-28 05:57:47,839 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces 2023-04-28 05:57:47,839 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global 2023-04-28 05:57:47,839 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global 2023-04-28 05:57:47,839 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/ntp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global 2023-04-28 05:57:47,840 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces 2023-04-28 05:57:47,840 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces 2023-04-28 05:57:47,840 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/acl_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces 2023-04-28 05:57:47,840 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces 2023-04-28 05:57:47,840 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/lacp_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces 2023-04-28 05:57:47,840 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces 2023-04-28 05:57:47,841 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global 2023-04-28 05:57:47,841 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global 2023-04-28 05:57:47,841 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/bgp_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global 2023-04-28 05:57:47,841 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global 2023-04-28 05:57:47,841 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global 2023-04-28 05:57:47,842 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/logging_global.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global 2023-04-28 05:57:47,842 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces 2023-04-28 05:57:47,842 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces 2023-04-28 05:57:47,842 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/ospf_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces 2023-04-28 05:57:47,842 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp 2023-04-28 05:57:47,843 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/lacp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp 2023-04-28 05:57:47,843 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp 2023-04-28 05:57:47,843 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3 2023-04-28 05:57:47,843 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3 2023-04-28 05:57:47,843 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/ospfv3.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3 2023-04-28 05:57:47,844 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls 2023-04-28 05:57:47,844 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls 2023-04-28 05:57:47,844 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/acls.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls 2023-04-28 05:57:47,844 root INFO copying build/lib/ansible_collections/arista/eos/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/plugins/module_utils/network 2023-04-28 05:57:47,844 root INFO copying build/lib/ansible_collections/arista/eos/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,845 root INFO copying build/lib/ansible_collections/arista/eos/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,845 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/meta 2023-04-28 05:57:47,845 root INFO copying build/lib/ansible_collections/arista/eos/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/meta 2023-04-28 05:57:47,846 root INFO copying build/lib/ansible_collections/arista/eos/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,846 root INFO copying build/lib/ansible_collections/arista/eos/pyproject.toml -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,846 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/changelogs 2023-04-28 05:57:47,846 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/changelogs/fragments 2023-04-28 05:57:47,846 root INFO copying build/lib/ansible_collections/arista/eos/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/changelogs/fragments 2023-04-28 05:57:47,847 root INFO copying build/lib/ansible_collections/arista/eos/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/changelogs 2023-04-28 05:57:47,847 root INFO copying build/lib/ansible_collections/arista/eos/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos/changelogs 2023-04-28 05:57:47,847 root INFO copying build/lib/ansible_collections/arista/eos/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,847 root INFO copying build/lib/ansible_collections/arista/eos/ignore-2.9.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,847 root INFO copying build/lib/ansible_collections/arista/eos/tox.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,848 root INFO copying build/lib/ansible_collections/arista/eos/bindep.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,848 root INFO copying build/lib/ansible_collections/arista/eos/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/arista/eos 2023-04-28 05:57:47,848 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google 2023-04-28 05:57:47,848 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,848 root INFO copying build/lib/ansible_collections/google/cloud/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,849 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins 2023-04-28 05:57:47,849 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/filter 2023-04-28 05:57:47,849 root INFO copying build/lib/ansible_collections/google/cloud/plugins/filter/gcp_kms_filters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/filter 2023-04-28 05:57:47,849 root INFO copying build/lib/ansible_collections/google/cloud/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins 2023-04-28 05:57:47,849 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/doc_fragments 2023-04-28 05:57:47,849 root INFO copying build/lib/ansible_collections/google/cloud/plugins/doc_fragments/gcp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/doc_fragments 2023-04-28 05:57:47,850 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/inventory 2023-04-28 05:57:47,850 root INFO copying build/lib/ansible_collections/google/cloud/plugins/inventory/gcp_compute.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/inventory 2023-04-28 05:57:47,850 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,850 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_route_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,851 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,851 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_bigquery_table.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,851 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_health_check_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,851 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_iam_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,852 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sql_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,852 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_kms_key_ring_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,852 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sql_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,852 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_router.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,852 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_global_forwarding_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,853 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_storage_default_object_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,853 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_kms_key_ring.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,853 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_vpn_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,853 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_pubsub_subscription_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,853 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_autoscaler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,854 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,854 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,854 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sourcerepo_repository.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,854 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_https_health_check_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,855 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,855 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_spanner_database_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,855 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_spanner_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,855 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_bucket_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,855 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,856 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_https_health_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,856 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_dns_resource_record_set.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,856 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,856 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_logging_metric_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,856 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_spanner_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,857 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudscheduler_job.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,857 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_http_health_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,857 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,857 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_bigtable_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,857 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_variable_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,858 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,858 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_appengine_firewall_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,858 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,858 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sourcerepo_repository_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,859 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_container_node_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,859 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_resourcemanager_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,859 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,859 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,860 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_serviceusage_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,860 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_node_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,860 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_bucket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,860 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,861 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_resource_policy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,861 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_container_cluster_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,861 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_resourcemanager_project_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,861 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_container_node_pool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,861 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_health_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,862 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_backend_service_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,862 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_global_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,862 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_subnetwork_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,862 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_firewall_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,863 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_manager_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,863 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_tpu_node_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,863 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,863 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,863 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_address_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,864 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_redis_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,864 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_disk_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,864 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_storage_object.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,864 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_tcp_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,865 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_bigquery_dataset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,865 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_mlengine_version_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,865 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_filestore_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,865 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_https_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,865 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_url_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,866 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_http_health_check_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,866 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_forwarding_rule_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,867 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_mlengine_model.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,867 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_global_address_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,867 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,867 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_pubsub_topic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,868 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_resource_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,868 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_serviceusage_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,868 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_url_map.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,869 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_spanner_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,869 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_ssl_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,869 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_variable.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,869 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_node_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,869 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_dns_managed_zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,870 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,870 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,870 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sql_database_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,870 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_bigtable_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,871 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sql_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,871 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_https_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,871 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_external_vpn_gateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,871 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,872 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_pubsub_topic_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,872 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_https_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,872 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_kms_crypto_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,872 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_appengine_firewall_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,872 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_health_check_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,873 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_node_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,873 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_url_map_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,873 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,873 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_dns_managed_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,874 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,874 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudtasks_queue.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,874 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_autoscaler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,874 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_http_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,875 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_network_endpoint_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,875 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_vpn_gateway_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,875 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_pubsub_subscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,875 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_container_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,876 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_external_vpn_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,876 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_http_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,876 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,876 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_backend_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,877 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,877 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_http_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,877 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_autoscaler_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,877 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_kms_crypto_key_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,877 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudscheduler_job_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,878 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_mlengine_model_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,878 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_bigquery_table_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,878 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudfunctions_cloud_function.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,878 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,879 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_dns_resource_record_set_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,879 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_disk.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,879 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudtasks_queue_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,880 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_snapshot_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,880 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,880 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_interconnect_attachment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,880 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,880 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudbuild_trigger_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,881 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudfunctions_cloud_function_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,881 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_pool_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,881 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sql_database.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,881 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_network_endpoint_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,882 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_storage_bucket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,882 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,882 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,882 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_http_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,882 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_cloudbuild_trigger.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,883 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,883 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,883 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_url_map_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,884 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_subnetwork.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,884 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,884 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_health_check.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,884 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_redis_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,885 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_interconnect_attachment_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,885 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sql_ssl_cert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,885 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_router_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,885 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_mlengine_version.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,885 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_autoscaler_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,886 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_sql_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,886 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_reservation.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,886 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_config_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,886 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_storage_bucket_access_control.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,887 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_tpu_node.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,887 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_vpn_tunnel.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,887 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_forwarding_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,887 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_reservation_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,888 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_vpn_tunnel_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,888 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_iam_role_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,888 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_instance_group_manager.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,888 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_filestore_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,888 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_logging_metric.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,889 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_ssl_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,889 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_bigquery_dataset_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,889 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_instance_group_manager_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,889 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_node_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,889 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_https_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,890 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_target_tcp_proxy_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,890 root INFO copying build/lib/ansible_collections/google/cloud/plugins/modules/gcp_compute_global_forwarding_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/modules 2023-04-28 05:57:47,890 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/module_utils 2023-04-28 05:57:47,890 root INFO copying build/lib/ansible_collections/google/cloud/plugins/module_utils/gcp_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/plugins/module_utils 2023-04-28 05:57:47,891 root INFO copying build/lib/ansible_collections/google/cloud/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,891 root INFO copying build/lib/ansible_collections/google/cloud/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,891 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/meta 2023-04-28 05:57:47,891 root INFO copying build/lib/ansible_collections/google/cloud/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/meta 2023-04-28 05:57:47,892 root INFO copying build/lib/ansible_collections/google/cloud/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,892 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule 2023-04-28 05:57:47,892 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:47,892 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcsfuse/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:47,893 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse/tests 2023-04-28 05:57:47,893 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcsfuse/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse/tests 2023-04-28 05:57:47,893 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcsfuse/verify.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:47,893 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcsfuse/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:47,893 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse/files 2023-04-28 05:57:47,893 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcsfuse/files/override.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse/files 2023-04-28 05:57:47,894 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcsfuse/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcsfuse 2023-04-28 05:57:47,894 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:47,894 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:47,894 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/archive_playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:47,894 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud/tests 2023-04-28 05:57:47,895 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/tests/test_default.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud/tests 2023-04-28 05:57:47,895 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/verify.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:47,895 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/converge.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:47,895 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/package_playbook.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:47,895 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud/files 2023-04-28 05:57:47,896 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/files/override.conf -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud/files 2023-04-28 05:57:47,896 root INFO copying build/lib/ansible_collections/google/cloud/molecule/gcloud/molecule.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/molecule/gcloud 2023-04-28 05:57:47,896 root INFO copying build/lib/ansible_collections/google/cloud/requirements-test.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,896 root INFO copying build/lib/ansible_collections/google/cloud/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,896 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/test-fixtures 2023-04-28 05:57:47,896 root INFO copying build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function.zip -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/test-fixtures 2023-04-28 05:57:47,897 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:47,897 root INFO copying build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function-source/main.py -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:47,897 root INFO copying build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function-source/build-function-zip.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:47,897 root INFO copying build/lib/ansible_collections/google/cloud/test-fixtures/cloud-function-source/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/test-fixtures/cloud-function-source 2023-04-28 05:57:47,897 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:47,898 root INFO copying build/lib/ansible_collections/google/cloud/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:47,898 root INFO copying build/lib/ansible_collections/google/cloud/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:47,898 root INFO copying build/lib/ansible_collections/google/cloud/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/changelogs 2023-04-28 05:57:47,898 root INFO copying build/lib/ansible_collections/google/cloud/MAINTAINING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,898 root INFO copying build/lib/ansible_collections/google/cloud/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,899 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/scripts 2023-04-28 05:57:47,899 root INFO copying build/lib/ansible_collections/google/cloud/scripts/cleanup-project.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/scripts 2023-04-28 05:57:47,899 root INFO copying build/lib/ansible_collections/google/cloud/scripts/bootstrap-project.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/scripts 2023-04-28 05:57:47,899 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles 2023-04-28 05:57:47,899 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb 2023-04-28 05:57:47,900 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/tasks 2023-04-28 05:57:47,900 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/tasks 2023-04-28 05:57:47,900 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/defaults 2023-04-28 05:57:47,900 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/defaults 2023-04-28 05:57:47,900 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb 2023-04-28 05:57:47,900 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/tests 2023-04-28 05:57:47,901 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/tests 2023-04-28 05:57:47,901 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/tests 2023-04-28 05:57:47,901 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/vars 2023-04-28 05:57:47,901 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/vars 2023-04-28 05:57:47,901 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/meta 2023-04-28 05:57:47,901 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcp_http_lb/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcp_http_lb/meta 2023-04-28 05:57:47,902 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse 2023-04-28 05:57:47,902 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/tasks 2023-04-28 05:57:47,902 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcsfuse/tasks/debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/tasks 2023-04-28 05:57:47,902 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcsfuse/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/tasks 2023-04-28 05:57:47,902 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/defaults 2023-04-28 05:57:47,903 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcsfuse/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/defaults 2023-04-28 05:57:47,903 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/handlers 2023-04-28 05:57:47,903 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcsfuse/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/handlers 2023-04-28 05:57:47,903 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcsfuse/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse 2023-04-28 05:57:47,903 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/vars 2023-04-28 05:57:47,904 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcsfuse/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/vars 2023-04-28 05:57:47,904 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/meta 2023-04-28 05:57:47,904 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcsfuse/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcsfuse/meta 2023-04-28 05:57:47,904 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud 2023-04-28 05:57:47,904 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks 2023-04-28 05:57:47,904 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:47,905 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/package/redhat.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:47,905 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/package/debian.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:47,905 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/package/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/package 2023-04-28 05:57:47,905 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks 2023-04-28 05:57:47,905 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:47,906 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/archive/archive_install.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:47,906 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/archive/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:47,906 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/tasks/archive/command_completion.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/tasks/archive 2023-04-28 05:57:47,906 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/defaults 2023-04-28 05:57:47,906 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/defaults 2023-04-28 05:57:47,907 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud 2023-04-28 05:57:47,907 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/vars 2023-04-28 05:57:47,907 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/vars 2023-04-28 05:57:47,907 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/meta 2023-04-28 05:57:47,907 root INFO copying build/lib/ansible_collections/google/cloud/roles/gcloud/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud/roles/gcloud/meta 2023-04-28 05:57:47,907 root INFO copying build/lib/ansible_collections/google/cloud/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/google/cloud 2023-04-28 05:57:47,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage 2023-04-28 05:57:47,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion 2023-04-28 05:57:47,908 root INFO copying build/lib/ansible_collections/purestorage/fusion/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion 2023-04-28 05:57:47,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins 2023-04-28 05:57:47,908 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/doc_fragments 2023-04-28 05:57:47,909 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/doc_fragments/purestorage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/doc_fragments 2023-04-28 05:57:47,909 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/inventory 2023-04-28 05:57:47,909 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/inventory 2023-04-28 05:57:47,909 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,909 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_hw.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,909 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_hap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,910 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_ts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,910 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_api_client.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,910 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_az.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,910 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_se.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,911 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,911 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_pg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,911 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_ni.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,911 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_ra.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,911 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,912 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_tenant.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,912 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_nig.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,912 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_array.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,912 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_ss.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,912 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_tn.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,913 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,913 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_pp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,913 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/modules/fusion_sc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/modules 2023-04-28 05:57:47,913 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,913 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/startup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,914 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/getters.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,914 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/fusion.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,914 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/networking.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,914 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/errors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,914 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/parsing.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,915 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/prerequisites.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,915 root INFO copying build/lib/ansible_collections/purestorage/fusion/plugins/module_utils/operations.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/plugins/module_utils 2023-04-28 05:57:47,915 root INFO copying build/lib/ansible_collections/purestorage/fusion/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion 2023-04-28 05:57:47,915 root INFO copying build/lib/ansible_collections/purestorage/fusion/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion 2023-04-28 05:57:47,915 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/meta 2023-04-28 05:57:47,916 root INFO copying build/lib/ansible_collections/purestorage/fusion/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/meta 2023-04-28 05:57:47,916 root INFO copying build/lib/ansible_collections/purestorage/fusion/COPYING.GPLv3 -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion 2023-04-28 05:57:47,916 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks 2023-04-28 05:57:47,916 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/tasks 2023-04-28 05:57:47,916 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/tasks/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/tasks 2023-04-28 05:57:47,917 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,917 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_api_clients.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,917 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/create_array.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,917 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_network_interface_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,917 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_volumes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,917 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_protection_policies.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,918 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_availability_zones.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,918 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/remove_array.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,918 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_storage_classes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,918 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/make_tenant_admin.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,918 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_storage_services.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,919 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/create_availability_zone.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,919 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_interfaces.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,919 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_arrays.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,919 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/setup_infrastructure.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,919 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_roles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,920 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_tenant_spaces.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,920 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/create_tenant_space.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,920 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_snapshots.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,920 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_hosts.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,920 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_tenants.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,921 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/setup_protection_policies.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,921 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_users.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,921 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_hardware_types.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,921 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_all.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,921 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_storage_endpoints.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,922 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/list_placement_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,922 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/setup_workloads.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,922 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/simple/setup_storage_service_class.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/simple 2023-04-28 05:57:47,922 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/templates 2023-04-28 05:57:47,922 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/templates/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/templates 2023-04-28 05:57:47,923 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/vars 2023-04-28 05:57:47,923 root INFO copying build/lib/ansible_collections/purestorage/fusion/playbooks/vars/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/playbooks/vars 2023-04-28 05:57:47,923 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:47,923 root INFO copying build/lib/ansible_collections/purestorage/fusion/changelogs/99_update_protection_policy_retention_description.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:47,923 root INFO copying build/lib/ansible_collections/purestorage/fusion/changelogs/112_unify_hardware_types_key_in_fusion_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:47,923 root INFO copying build/lib/ansible_collections/purestorage/fusion/changelogs/109_unify_storage_classes_key_in_fusion_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:47,924 root INFO copying build/lib/ansible_collections/purestorage/fusion/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:47,924 root INFO copying build/lib/ansible_collections/purestorage/fusion/changelogs/101_improve_duration_parsing.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:47,924 root INFO copying build/lib/ansible_collections/purestorage/fusion/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion/changelogs 2023-04-28 05:57:47,924 root INFO copying build/lib/ansible_collections/purestorage/fusion/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/fusion 2023-04-28 05:57:47,924 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,925 root INFO copying build/lib/ansible_collections/purestorage/flasharray/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,925 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins 2023-04-28 05:57:47,925 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/doc_fragments 2023-04-28 05:57:47,925 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/doc_fragments/purestorage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/doc_fragments 2023-04-28 05:57:47,925 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,926 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_volume_tags.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,926 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,926 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_syslog_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,926 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_sso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,926 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_snmp_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,927 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_eula.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,927 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_dsrole.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,927 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,927 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,927 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,928 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_ra.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,928 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,928 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_phonehome.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,928 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_vg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,929 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_alert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,929 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_maintenance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,929 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_saml.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,929 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_ad.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,929 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,930 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_pod_replica.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,930 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_endpoint.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,930 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,930 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_smis.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,931 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_eradication.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,931 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_vnc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,931 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_default_protection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,931 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_pgsnap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,931 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,931 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_certs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,932 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_kmip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,932 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,932 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_hg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,932 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_fs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,933 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_console.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,933 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,933 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_pg.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,933 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,933 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_snap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,934 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_arrayname.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,934 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_offload.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,934 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,934 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_pod.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,935 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,935 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,935 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,935 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,936 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_messages.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,936 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_dirsnap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,936 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_connect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,936 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_ds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,936 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,937 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,937 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_timeout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,937 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_apiclient.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,937 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_snmp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,937 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/modules/purefa_pgsched.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/modules 2023-04-28 05:57:47,938 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/module_utils 2023-04-28 05:57:47,938 root INFO copying build/lib/ansible_collections/purestorage/flasharray/plugins/module_utils/purefa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/plugins/module_utils 2023-04-28 05:57:47,938 root INFO copying build/lib/ansible_collections/purestorage/flasharray/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,938 root INFO copying build/lib/ansible_collections/purestorage/flasharray/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,938 root INFO copying build/lib/ansible_collections/purestorage/flasharray/settings.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,939 root INFO copying build/lib/ansible_collections/purestorage/flasharray/README.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,939 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/meta 2023-04-28 05:57:47,939 root INFO copying build/lib/ansible_collections/purestorage/flasharray/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/meta 2023-04-28 05:57:47,939 root INFO copying build/lib/ansible_collections/purestorage/flasharray/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/meta 2023-04-28 05:57:47,939 root INFO copying build/lib/ansible_collections/purestorage/flasharray/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,940 root INFO copying build/lib/ansible_collections/purestorage/flasharray/COPYING.GPLv3 -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,940 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks 2023-04-28 05:57:47,940 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/tasks 2023-04-28 05:57:47,940 root INFO copying build/lib/ansible_collections/purestorage/flasharray/playbooks/tasks/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/tasks 2023-04-28 05:57:47,940 root INFO copying build/lib/ansible_collections/purestorage/flasharray/playbooks/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks 2023-04-28 05:57:47,941 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/templates 2023-04-28 05:57:47,941 root INFO copying build/lib/ansible_collections/purestorage/flasharray/playbooks/templates/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/templates 2023-04-28 05:57:47,941 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/vars 2023-04-28 05:57:47,941 root INFO copying build/lib/ansible_collections/purestorage/flasharray/playbooks/vars/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/vars 2023-04-28 05:57:47,941 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/files 2023-04-28 05:57:47,941 root INFO copying build/lib/ansible_collections/purestorage/flasharray/playbooks/files/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/files 2023-04-28 05:57:47,942 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/roles 2023-04-28 05:57:47,942 root INFO copying build/lib/ansible_collections/purestorage/flasharray/playbooks/roles/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/playbooks/roles 2023-04-28 05:57:47,942 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:47,942 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/210_add_rename_hgroup.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:47,943 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,943 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/152_fix_user.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,943 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/280_multihost_no_suffix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,943 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/206_add_naa_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,943 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/379_cap_compat.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,943 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/302_fix_pg_recover_and_target_update.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,944 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/234_add_vol_info_on_nochange.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,944 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/296_ad_tls.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,944 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/284_volfact_for_recover.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,944 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/305_fix_target_dempo.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,944 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/294_user_map_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,945 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/130_info_ds_update.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,945 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/111_add_filesystem_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,945 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/367_fix_vg.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,945 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/214_join_ou.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,945 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/347_dns_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,946 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/318_vol_defaults.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,946 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/271_vgroup_prio.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,946 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/201_increase_krb_count.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,946 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/293_add_chassis_inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,946 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/364_fc_targets.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,947 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/123_add_multi_vgroup_creation.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,947 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/131_add_v6_ds_update.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,947 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/115_add_gcp_offload.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,947 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/175_check_pgname.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,947 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/343_fix_ds.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,948 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/193_duplicate_initiators.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,948 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/168_dsrole_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,948 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/224_add_nguid_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,948 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/116_add_policies.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,948 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/156_snap_suffix_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,948 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/199_add_fc_port_enable.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,949 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/109_fa_files_support_purefa_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,949 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/v1.4.0_summary.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,949 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/360_fix_volume.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,949 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/365_pod_pgsched.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,949 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/268_fix_quotas_issues.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,950 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/249_allow_cert_reimport.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,950 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/133_purefa_info_v6_replication.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,950 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/229_snapsuffix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,950 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/163_add_maintenance_windows.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,950 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/196_fix_activedr_api_version.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,951 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/328_policy_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,951 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/200_add_DAR_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,951 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/374_offload_pgsnap.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,951 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/132_fc_replication.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,951 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/112_add_directory_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,952 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/134_ac_pg_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,952 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/170_pgsnap_stretch_pod_fail.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,952 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/137_pgsnap_regex.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,952 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/124_sdk_handshake.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,952 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/139_pgsnap_ac_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,953 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/121_add_multi_volume_creation.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,953 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/122_add_multi_host_creation.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,953 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/237_fix_network.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,953 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/213_add_kmip.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,953 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/205_policy_protocl.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,954 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/261_fix_bad_arrays.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,954 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/162_pgsnap_info_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,954 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/330_extend_vlan.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,954 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/363_overwrite_combo.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,954 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/257_fqcn.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,955 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/194_vg_qos.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,955 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/310_hg_vol_idempotency.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,955 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/145_fix_missing_move_variable.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,955 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/315_spf_details.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,955 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/348_add_default_prot.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,956 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/317_add_all_squash.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,956 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/188_add_dirsnap.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,956 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/235_eula.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,956 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/312_pg_alias.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,956 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/304_host_vlan.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,957 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/108_fix_eradicate_idempotency.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,957 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/113_add_exports_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,957 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/140_pod_case.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,957 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/342_add_vol_promotion.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,957 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/118_rename_host.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,958 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/349_add_alerts.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,958 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/243_sso_to_admin.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,958 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/125_dns_idempotency.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,958 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/259_fix_gateway_check.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,958 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/247_fix_smb_policy_rules.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,959 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/208_add_directory_quota_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,959 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/366_add_nvme_types.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,959 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/107_host_case_clarity.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,959 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/270_add_priority_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,959 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/187_add_ad.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,959 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/341_pg_400s.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,960 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/278_pgsnap_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,960 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/288_zero_params.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,960 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/203_add_eradication_timer.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,960 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/202_add_sso.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,960 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/149_volumes_demoted_pods_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,961 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/169_add_certs.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,961 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/351_fix_rest_check.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,961 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/220_capacity_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,961 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/242_multi_offload.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,961 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/227_missing_regex.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,962 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/246_python_precedence.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,962 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/135_no_cbs_ntp.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,962 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/231_syslog_settings.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,962 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/239_safe_mode.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,962 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/369_fix_host.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,963 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/354_fix_promotion.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,963 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/207_fix_disable_for_remote_assist.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,963 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/292_fix_ds_password.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,963 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/337_fix_non-prod_versions.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,963 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/110_add_apiclient_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,964 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/226_deprecate_protocol.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,964 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/345_user_map.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,964 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/320_completed_snaps.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,964 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/141_add_remote_snapshot.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,964 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/370_add_user_role.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,965 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/176_fix_promote_api_issue.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,965 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/375_fix_remote_hosts.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,965 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/153_syslog_update.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,965 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/126_fix_volume_move.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,965 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/294_dns_ntp_idempotency_absent.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,966 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/228_nguid_to_volfact.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,966 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/136_add_vol_get_send_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,966 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/334_fix_vg_qos.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,966 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/252_add_saml2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,966 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/272_volume_prio.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,967 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/238_add_dirsnap_rename.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,967 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/161_offline_offload_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,967 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/319_lockout.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,967 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/344_fix_smtp.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,967 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/265_fix_multiple_nfs_rules.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,968 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/307_multiple_dns.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,968 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/299_fix_pgsched_zero_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,968 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/336_add_servicelist.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,968 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/277_add_fs_repl.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,968 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/174_null_gateway.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,969 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/160_rename_pg.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,969 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/308_add_vm.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,969 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/182_allow_pgroup_with_create.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,969 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/279_pg_safemode.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,969 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/230_add_pg_deleted_vols.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,970 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/fragments/254_sam2_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs/fragments 2023-04-28 05:57:47,970 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:47,970 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:47,970 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/211_fix_clearing_host_inititators.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:47,970 root INFO copying build/lib/ansible_collections/purestorage/flasharray/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/changelogs 2023-04-28 05:57:47,971 root INFO copying build/lib/ansible_collections/purestorage/flasharray/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,971 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/roles 2023-04-28 05:57:47,971 root INFO copying build/lib/ansible_collections/purestorage/flasharray/roles/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray/roles 2023-04-28 05:57:47,971 root INFO copying build/lib/ansible_collections/purestorage/flasharray/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flasharray 2023-04-28 05:57:47,971 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,972 root INFO copying build/lib/ansible_collections/purestorage/flashblade/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,972 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins 2023-04-28 05:57:47,972 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/doc_fragments 2023-04-28 05:57:47,972 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/doc_fragments/purestorage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/doc_fragments 2023-04-28 05:57:47,972 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,973 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_bucket.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,973 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_s3acc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,973 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_fs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,973 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_alert.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,974 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_groupquota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,974 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_timeout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,974 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_phonehome.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,974 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_lag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,974 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_remote_cred.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,975 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_userquota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,975 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_ds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,975 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_lifecycle.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,975 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_virtualhost.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,975 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,976 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_userpolicy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,976 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_dns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,976 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_messages.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,976 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,976 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_eula.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,977 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_apiclient.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,977 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_fs_replica.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,977 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,977 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_banner.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,977 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_target.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,978 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_certs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,978 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_ra.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,978 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_snap.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,978 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_pingtrace.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,978 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_snmp_agent.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,979 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,979 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_s3user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,979 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_bucket_replica.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,979 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,979 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_bladename.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,980 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_keytabs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,980 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_certgrp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,980 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,980 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,980 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,981 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_snmp_mgr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,981 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_subnet.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,981 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_admin.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,981 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_connect.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,982 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,982 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_dsrole.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,982 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_ad.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,982 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/modules/purefb_tz.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/modules 2023-04-28 05:57:47,982 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/module_utils 2023-04-28 05:57:47,983 root INFO copying build/lib/ansible_collections/purestorage/flashblade/plugins/module_utils/purefb.py -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/plugins/module_utils 2023-04-28 05:57:47,983 root INFO copying build/lib/ansible_collections/purestorage/flashblade/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,983 root INFO copying build/lib/ansible_collections/purestorage/flashblade/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,983 root INFO copying build/lib/ansible_collections/purestorage/flashblade/settings.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,984 root INFO copying build/lib/ansible_collections/purestorage/flashblade/README.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,984 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/meta 2023-04-28 05:57:47,984 root INFO copying build/lib/ansible_collections/purestorage/flashblade/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/meta 2023-04-28 05:57:47,984 root INFO copying build/lib/ansible_collections/purestorage/flashblade/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,984 root INFO copying build/lib/ansible_collections/purestorage/flashblade/COPYING.GPLv3 -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:47,985 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks 2023-04-28 05:57:47,985 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/tasks 2023-04-28 05:57:47,985 root INFO copying build/lib/ansible_collections/purestorage/flashblade/playbooks/tasks/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/tasks 2023-04-28 05:57:47,985 root INFO copying build/lib/ansible_collections/purestorage/flashblade/playbooks/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks 2023-04-28 05:57:47,985 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/templates 2023-04-28 05:57:47,985 root INFO copying build/lib/ansible_collections/purestorage/flashblade/playbooks/templates/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/templates 2023-04-28 05:57:47,986 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/vars 2023-04-28 05:57:47,986 root INFO copying build/lib/ansible_collections/purestorage/flashblade/playbooks/vars/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/vars 2023-04-28 05:57:47,986 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/files 2023-04-28 05:57:47,986 root INFO copying build/lib/ansible_collections/purestorage/flashblade/playbooks/files/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/files 2023-04-28 05:57:47,986 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/roles 2023-04-28 05:57:47,986 root INFO copying build/lib/ansible_collections/purestorage/flashblade/playbooks/roles/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/playbooks/roles 2023-04-28 05:57:47,987 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:47,987 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,987 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/187_rename_nfs_policy.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,987 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/205_fix_multi_lifecycle.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,987 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/166_lag_mac_note.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,988 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/108_dns_search_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,988 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/127_add_eula.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,988 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/88_add_lifecycle.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,988 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/184_certificate_typos.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,988 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/218_object_account_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,989 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/140_more_32_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,989 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/179_fqcn.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,989 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/186_add_tz.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,989 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/80_support_reverse_replica_link.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,989 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/113_policy_cleanup.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,990 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/v1.3.0_summary.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,990 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/96_fix_update_connection.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,990 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/147_no_gateway.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,990 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/121_replication_perf.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,990 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/217_inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,991 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/183_v2_connections.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,991 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/188_bucket_type.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,991 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/216_extra_bucket_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,991 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/101_fix_policy_and_timezone_error.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,991 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/194_lists_for_service.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,992 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/128_add_32_to_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,992 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/161_add_lifecycle_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,992 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/136_add_s3user_policy.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,992 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/213_sec_update.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,992 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/129-virtualhost.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,992 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/139_add_keytabs.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,993 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/220_s3user_key_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,993 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/81_purefb_fs_new_options.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,993 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/115_multiprotocol.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,993 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/200_proxy.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,993 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/202_multiple_snap_rules.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,994 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/158_support_lags.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,994 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/109_update_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,994 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/111_dsrole_update_idempotency.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,994 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/97_fix_encrpyted_array_connection_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,994 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/123_lifecycle_rule_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,995 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/85_add_banner.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,995 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/135_add_user_policies.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,995 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/105_max_access_key.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,995 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/162_new_lifecycle.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,995 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/176_nfs_export_policies.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,996 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/211_change_booleans.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,996 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/163_admin_key.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,996 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/191_add_quota_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,996 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/212_object_account_quota.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,996 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/90_imported_keys.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,997 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/215_encrypt_sec_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,997 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/150_fix_joint_nfs_version_change.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,997 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/79_hide_connect_api.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,997 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/164_add_admin.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,997 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/154_add_snap_now.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,998 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/132_add_timeout.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,998 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/76_default_fs_size.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,998 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/175_throttle_support.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,998 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/77_filesystem_policies_info.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,998 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/84_add_cert.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,999 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/86_add_syslog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,999 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/185_nfs_export_rule.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,999 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/131-apiclient.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,999 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/152_s3acc_lowercase.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,999 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/107_add_remove_s3user_key.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:47,999 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/114_certificate_update.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,000 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/159_add_lag.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,000 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/153_add_quota.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,000 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/92_fix_ds_update.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,000 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/138_add_ad_module.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,000 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/174_access_policies.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,001 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/167_fix_logins.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,001 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/90_delete_conn_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,001 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/83_add_certgrp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,001 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/112_fix_check_mode.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,001 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/169_pypureclient_fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,002 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/fragments/78_update_filesystem_replica_link.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs/fragments 2023-04-28 05:57:48,002 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:48,002 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:48,002 root INFO copying build/lib/ansible_collections/purestorage/flashblade/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/changelogs 2023-04-28 05:57:48,003 root INFO copying build/lib/ansible_collections/purestorage/flashblade/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:48,003 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/roles 2023-04-28 05:57:48,003 root INFO copying build/lib/ansible_collections/purestorage/flashblade/roles/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade/roles 2023-04-28 05:57:48,003 root INFO copying build/lib/ansible_collections/purestorage/flashblade/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/purestorage/flashblade 2023-04-28 05:57:48,003 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc 2023-04-28 05:57:48,004 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:48,004 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins 2023-04-28 05:57:48,004 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/terminal 2023-04-28 05:57:48,004 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/terminal/sonic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/terminal 2023-04-28 05:57:48,005 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/terminal 2023-04-28 05:57:48,005 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,005 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,005 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vxlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,005 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,006 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_tacacs_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,006 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,006 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,006 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vrfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,006 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,007 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_neighbors_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,007 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_mclag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,007 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,007 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,007 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,008 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,008 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,008 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,008 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,008 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,009 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,009 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_as_paths.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,009 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,009 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,009 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_aaa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,010 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_ext_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,010 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,010 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_port_breakout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,010 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_api.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,011 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,011 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/modules 2023-04-28 05:57:48,011 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf 2023-04-28 05:57:48,011 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/sonic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf 2023-04-28 05:57:48,011 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf 2023-04-28 05:57:48,012 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/action 2023-04-28 05:57:48,012 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/action/sonic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/action 2023-04-28 05:57:48,012 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/action 2023-04-28 05:57:48,012 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi 2023-04-28 05:57:48,012 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/sonic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi 2023-04-28 05:57:48,012 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi 2023-04-28 05:57:48,013 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils 2023-04-28 05:57:48,013 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils 2023-04-28 05:57:48,013 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network 2023-04-28 05:57:48,013 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic 2023-04-28 05:57:48,013 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts 2023-04-28 05:57:48,014 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp 2023-04-28 05:57:48,014 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp 2023-04-28 05:57:48,014 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp 2023-04-28 05:57:48,014 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities 2023-04-28 05:57:48,014 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/bgp_ext_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities 2023-04-28 05:57:48,014 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities 2023-04-28 05:57:48,015 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans 2023-04-28 05:57:48,015 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans 2023-04-28 05:57:48,015 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans 2023-04-28 05:57:48,015 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users 2023-04-28 05:57:48,015 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users/users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users 2023-04-28 05:57:48,016 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes 2023-04-28 05:57:48,016 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes 2023-04-28 05:57:48,016 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes 2023-04-28 05:57:48,016 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors 2023-04-28 05:57:48,016 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors 2023-04-28 05:57:48,017 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/bgp_neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors 2023-04-28 05:57:48,017 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts 2023-04-28 05:57:48,017 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces 2023-04-28 05:57:48,017 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces 2023-04-28 05:57:48,017 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces 2023-04-28 05:57:48,018 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af 2023-04-28 05:57:48,018 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/bgp_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af 2023-04-28 05:57:48,018 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af 2023-04-28 05:57:48,018 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server 2023-04-28 05:57:48,018 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server/radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server 2023-04-28 05:57:48,019 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts 2023-04-28 05:57:48,019 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces 2023-04-28 05:57:48,019 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces 2023-04-28 05:57:48,019 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces 2023-04-28 05:57:48,019 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists 2023-04-28 05:57:48,019 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists 2023-04-28 05:57:48,020 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists 2023-04-28 05:57:48,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server 2023-04-28 05:57:48,020 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server/tacacs_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server 2023-04-28 05:57:48,020 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans 2023-04-28 05:57:48,021 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans 2023-04-28 05:57:48,021 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/vxlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans 2023-04-28 05:57:48,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag 2023-04-28 05:57:48,021 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag/mclag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag 2023-04-28 05:57:48,021 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces 2023-04-28 05:57:48,022 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces 2023-04-28 05:57:48,022 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces 2023-04-28 05:57:48,022 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces 2023-04-28 05:57:48,022 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces 2023-04-28 05:57:48,022 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system 2023-04-28 05:57:48,023 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system 2023-04-28 05:57:48,023 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system 2023-04-28 05:57:48,023 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths 2023-04-28 05:57:48,023 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/bgp_as_paths.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths 2023-04-28 05:57:48,023 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths 2023-04-28 05:57:48,024 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af 2023-04-28 05:57:48,024 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af 2023-04-28 05:57:48,024 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/bgp_neighbors_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af 2023-04-28 05:57:48,024 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs 2023-04-28 05:57:48,024 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs/vrfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs 2023-04-28 05:57:48,025 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa 2023-04-28 05:57:48,025 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa 2023-04-28 05:57:48,025 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/aaa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa 2023-04-28 05:57:48,025 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout 2023-04-28 05:57:48,025 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout/port_breakout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout 2023-04-28 05:57:48,026 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities 2023-04-28 05:57:48,026 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/bgp_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities 2023-04-28 05:57:48,026 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities 2023-04-28 05:57:48,026 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp 2023-04-28 05:57:48,026 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp 2023-04-28 05:57:48,026 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp 2023-04-28 05:57:48,027 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/sonic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic 2023-04-28 05:57:48,027 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:48,027 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/bgp_utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:48,027 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:48,028 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/interfaces_util.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:48,028 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils 2023-04-28 05:57:48,028 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic 2023-04-28 05:57:48,028 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config 2023-04-28 05:57:48,028 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp 2023-04-28 05:57:48,028 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp/bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp 2023-04-28 05:57:48,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities 2023-04-28 05:57:48,029 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/bgp_ext_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities 2023-04-28 05:57:48,029 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities 2023-04-28 05:57:48,029 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans 2023-04-28 05:57:48,029 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans 2023-04-28 05:57:48,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users 2023-04-28 05:57:48,030 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users/users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users 2023-04-28 05:57:48,030 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes 2023-04-28 05:57:48,030 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes 2023-04-28 05:57:48,031 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes 2023-04-28 05:57:48,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors 2023-04-28 05:57:48,031 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors/bgp_neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors 2023-04-28 05:57:48,031 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces 2023-04-28 05:57:48,031 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces 2023-04-28 05:57:48,032 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af 2023-04-28 05:57:48,032 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af/bgp_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af 2023-04-28 05:57:48,032 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server 2023-04-28 05:57:48,032 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server/radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server 2023-04-28 05:57:48,032 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config 2023-04-28 05:57:48,033 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces 2023-04-28 05:57:48,033 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces 2023-04-28 05:57:48,033 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists 2023-04-28 05:57:48,033 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists 2023-04-28 05:57:48,033 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists 2023-04-28 05:57:48,034 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server 2023-04-28 05:57:48,034 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server/tacacs_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server 2023-04-28 05:57:48,034 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans 2023-04-28 05:57:48,034 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans/vxlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans 2023-04-28 05:57:48,034 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag 2023-04-28 05:57:48,035 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag/mclag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag 2023-04-28 05:57:48,035 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces 2023-04-28 05:57:48,035 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces 2023-04-28 05:57:48,035 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces 2023-04-28 05:57:48,035 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces 2023-04-28 05:57:48,036 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system 2023-04-28 05:57:48,036 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system 2023-04-28 05:57:48,036 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system 2023-04-28 05:57:48,036 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths 2023-04-28 05:57:48,036 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths/bgp_as_paths.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths 2023-04-28 05:57:48,037 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af 2023-04-28 05:57:48,037 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af/bgp_neighbors_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af 2023-04-28 05:57:48,037 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs 2023-04-28 05:57:48,037 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs/vrfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs 2023-04-28 05:57:48,037 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa 2023-04-28 05:57:48,038 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa 2023-04-28 05:57:48,038 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/aaa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa 2023-04-28 05:57:48,038 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout 2023-04-28 05:57:48,038 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout/port_breakout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout 2023-04-28 05:57:48,038 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities 2023-04-28 05:57:48,039 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/bgp_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities 2023-04-28 05:57:48,039 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities 2023-04-28 05:57:48,039 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp 2023-04-28 05:57:48,039 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp/ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp 2023-04-28 05:57:48,039 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec 2023-04-28 05:57:48,040 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp 2023-04-28 05:57:48,040 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/bgp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp 2023-04-28 05:57:48,040 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp 2023-04-28 05:57:48,040 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities 2023-04-28 05:57:48,040 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/bgp_ext_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities 2023-04-28 05:57:48,041 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities 2023-04-28 05:57:48,041 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans 2023-04-28 05:57:48,041 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans 2023-04-28 05:57:48,041 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/vlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans 2023-04-28 05:57:48,041 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users 2023-04-28 05:57:48,042 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users/users.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users 2023-04-28 05:57:48,042 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes 2023-04-28 05:57:48,042 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/static_routes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes 2023-04-28 05:57:48,042 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes 2023-04-28 05:57:48,042 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors 2023-04-28 05:57:48,042 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors 2023-04-28 05:57:48,043 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/bgp_neighbors.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors 2023-04-28 05:57:48,043 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts 2023-04-28 05:57:48,043 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts 2023-04-28 05:57:48,043 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts 2023-04-28 05:57:48,043 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces 2023-04-28 05:57:48,044 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces 2023-04-28 05:57:48,044 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/l3_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces 2023-04-28 05:57:48,044 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af 2023-04-28 05:57:48,044 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/bgp_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af 2023-04-28 05:57:48,044 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af 2023-04-28 05:57:48,045 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server 2023-04-28 05:57:48,045 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server/radius_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server 2023-04-28 05:57:48,045 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec 2023-04-28 05:57:48,045 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces 2023-04-28 05:57:48,045 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces 2023-04-28 05:57:48,045 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/lag_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces 2023-04-28 05:57:48,046 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists 2023-04-28 05:57:48,046 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists 2023-04-28 05:57:48,046 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/prefix_lists.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists 2023-04-28 05:57:48,046 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server 2023-04-28 05:57:48,046 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server/tacacs_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server 2023-04-28 05:57:48,047 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans 2023-04-28 05:57:48,047 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans 2023-04-28 05:57:48,047 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/vxlans.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans 2023-04-28 05:57:48,047 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag 2023-04-28 05:57:48,047 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag/mclag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag 2023-04-28 05:57:48,048 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces 2023-04-28 05:57:48,048 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces 2023-04-28 05:57:48,048 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces 2023-04-28 05:57:48,048 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces 2023-04-28 05:57:48,048 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces/l2_interfaces.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces 2023-04-28 05:57:48,049 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system 2023-04-28 05:57:48,049 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/system.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system 2023-04-28 05:57:48,049 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system 2023-04-28 05:57:48,049 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths 2023-04-28 05:57:48,049 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/bgp_as_paths.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths 2023-04-28 05:57:48,049 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths 2023-04-28 05:57:48,050 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af 2023-04-28 05:57:48,050 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af 2023-04-28 05:57:48,050 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/bgp_neighbors_af.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af 2023-04-28 05:57:48,050 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs 2023-04-28 05:57:48,050 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs/vrfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs 2023-04-28 05:57:48,051 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa 2023-04-28 05:57:48,051 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa 2023-04-28 05:57:48,051 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/aaa.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa 2023-04-28 05:57:48,051 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout 2023-04-28 05:57:48,051 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout/port_breakout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout 2023-04-28 05:57:48,052 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities 2023-04-28 05:57:48,052 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/bgp_communities.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities 2023-04-28 05:57:48,052 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities 2023-04-28 05:57:48,052 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp 2023-04-28 05:57:48,052 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp/ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp 2023-04-28 05:57:48,052 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network 2023-04-28 05:57:48,053 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/rebuild.sh -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:48,053 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:48,053 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:48,054 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/meta 2023-04-28 05:57:48,054 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/meta 2023-04-28 05:57:48,054 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/meta 2023-04-28 05:57:48,054 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:48,054 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks 2023-04-28 05:57:48,055 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,055 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_interfaces_config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,055 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/src.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,055 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,055 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_vxlans_config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,056 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_system.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,056 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_aaa.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,056 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/hosts -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,056 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_bgp_communities.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,056 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/interface_naming.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,056 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_command.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,057 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_api.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,057 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_bgp.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,057 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_facts.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,057 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/patch.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples 2023-04-28 05:57:48,058 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric 2023-04-28 05:57:48,058 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/templates 2023-04-28 05:57:48,058 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/templates/clos_fabric_cfg.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/templates 2023-04-28 05:57:48,058 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/clos-fabric.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric 2023-04-28 05:57:48,058 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric 2023-04-28 05:57:48,058 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:48,059 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/all.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:48,059 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/spine.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:48,059 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/leaf.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars 2023-04-28 05:57:48,059 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:48,059 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:48,060 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:48,060 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:48,060 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments 2023-04-28 05:57:48,060 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,060 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/72-bgp_neighbors-add-attributes.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,061 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/81-add-bgp-peer-group-attributes.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,061 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/90-aaa-and-users-bugfix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,061 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/63-bgp_af-route_advertise_list.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,061 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/58-vxlan-primary-ip.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,061 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/105-vxlan-regression-test-fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,061 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/85-regression-test-fixes.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,062 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/53-oc-yang-compliance.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,062 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/100-prefix_lists-resource-module.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,062 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/103-standard-interface-naming-and-other-bugfixes.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,062 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/60-bgp-regression-test_fixes.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,062 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/99-ntp-resource-module.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,063 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/2.0.0.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,063 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/82-static_routes.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,063 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/67-bgp_neighbors-auth_pwd-and-neighbor_description.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,063 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/76-CLI-command-prompt-answer-fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,064 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/98-vlans-description.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,064 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/78-aaa-regression-fix.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,064 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/101-bgp-prefix_lists.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,064 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/102-playbook-example-updates.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,064 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/62-bgp-vxlan-primary-ip.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,064 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/88-port_breakout-and-execution-environment.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0 2023-04-28 05:57:48,065 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic/changelogs 2023-04-28 05:57:48,065 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:48,065 root INFO copying build/lib/ansible_collections/dellemc/enterprise_sonic/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/enterprise_sonic 2023-04-28 05:57:48,065 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,066 root INFO copying build/lib/ansible_collections/dellemc/powerflex/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,066 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins 2023-04-28 05:57:48,066 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/doc_fragments 2023-04-28 05:57:48,066 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/doc_fragments/powerflex.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/doc_fragments 2023-04-28 05:57:48,066 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,066 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/device.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,067 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/sds.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,067 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,067 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,068 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/replication_pair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,068 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,068 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/mdm_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,068 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/protection_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,069 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/sdc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,069 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/storagepool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,069 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/modules/replication_consistency_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/modules 2023-04-28 05:57:48,069 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/module_utils 2023-04-28 05:57:48,069 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/module_utils/storage 2023-04-28 05:57:48,070 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:48,070 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:48,070 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:48,070 root INFO copying build/lib/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/logging_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell 2023-04-28 05:57:48,070 root INFO copying build/lib/ansible_collections/dellemc/powerflex/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,071 root INFO copying build/lib/ansible_collections/dellemc/powerflex/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,071 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/meta 2023-04-28 05:57:48,071 root INFO copying build/lib/ansible_collections/dellemc/powerflex/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/meta 2023-04-28 05:57:48,071 root INFO copying build/lib/ansible_collections/dellemc/powerflex/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/meta 2023-04-28 05:57:48,071 root INFO copying build/lib/ansible_collections/dellemc/powerflex/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,072 root INFO copying build/lib/ansible_collections/dellemc/powerflex/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,072 root INFO copying build/lib/ansible_collections/dellemc/powerflex/MODULE-LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,072 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:48,072 root INFO copying build/lib/ansible_collections/dellemc/powerflex/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:48,072 root INFO copying build/lib/ansible_collections/dellemc/powerflex/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:48,073 root INFO copying build/lib/ansible_collections/dellemc/powerflex/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex/changelogs 2023-04-28 05:57:48,073 root INFO copying build/lib/ansible_collections/dellemc/powerflex/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,073 root INFO copying build/lib/ansible_collections/dellemc/powerflex/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,073 root INFO copying build/lib/ansible_collections/dellemc/powerflex/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/powerflex 2023-04-28 05:57:48,073 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,074 root INFO copying build/lib/ansible_collections/dellemc/openmanage/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,074 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins 2023-04-28 05:57:48,074 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins 2023-04-28 05:57:48,074 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,074 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments/idrac_auth_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,075 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments/oment_auth_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,075 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,075 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments/redfish_auth_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,075 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments/network_share_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,075 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments/ome_auth_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,076 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/doc_fragments/omem_auth_options.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/doc_fragments 2023-04-28 05:57:48,076 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,076 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,076 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/redfish_firmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,076 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,077 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_virtual_media.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,077 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,077 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,077 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,078 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_identity_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,078 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_console_preferences.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,078 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_active_directory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,078 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline_compliance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,078 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/dellemc_configure_idrac_eventing.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,079 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_mgmt_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,079 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_smart_fabric_uplink.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,079 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,079 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_groups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,080 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_template_network_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,080 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_timezone_ntp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,080 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,080 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,080 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_job_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,081 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/dellemc_idrac_lc_attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,081 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,081 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_os_deployment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,081 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_local_access_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,082 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_attributes.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,082 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/dellemc_get_firmware_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,082 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_smart_fabric.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,082 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_server_interface_profiles.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,082 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_configuration_compliance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,083 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_server_interface_profile_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,083 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_system_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,083 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,083 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_boot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,084 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_chassis_slots.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,084 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_network_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,084 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,084 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_logs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,084 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_firmware_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,085 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_bios.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,085 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/dellemc_get_system_inventory.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,085 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_diagnostics.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,085 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_time.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,085 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,086 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_jobs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,086 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,086 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_quick_deploy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,086 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_network_port_breakout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,086 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/dellemc_configure_idrac_services.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,087 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_firmware.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,087 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_network_vlan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,087 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_catalog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,087 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_power_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,088 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,088 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_alerts_syslog.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,088 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_template_identity_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,088 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_devices.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,088 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_redfish_storage_controller.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,089 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/dellemc_idrac_storage_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,089 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_network_vlan.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,089 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,089 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,090 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_security_settings.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,090 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,090 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/redfish_event_subscription.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,090 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_template_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,090 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/dellemc_system_lockdown_mode.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,091 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_configuration_compliance_baseline.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,091 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_discovery.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,091 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_certificates.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,091 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_domain_user_groups.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,092 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_alerts_smtp.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,092 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/redfish_powerstate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,092 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_proxy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,092 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_job_status_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,092 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_reset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,093 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/redfish_storage_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,093 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_device_location.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,093 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_powerstate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,093 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_webserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,093 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/modules/idrac_server_config_profile.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/modules 2023-04-28 05:57:48,094 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:48,094 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils/idrac_redfish.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:48,094 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:48,094 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils/redfish.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:48,095 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:48,095 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils/ome.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:48,095 root INFO copying build/lib/ansible_collections/dellemc/openmanage/plugins/module_utils/dellemc_idrac.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/plugins/module_utils 2023-04-28 05:57:48,095 root INFO copying build/lib/ansible_collections/dellemc/openmanage/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,095 root INFO copying build/lib/ansible_collections/dellemc/openmanage/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,096 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/meta 2023-04-28 05:57:48,096 root INFO copying build/lib/ansible_collections/dellemc/openmanage/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/meta 2023-04-28 05:57:48,096 root INFO copying build/lib/ansible_collections/dellemc/openmanage/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/meta 2023-04-28 05:57:48,096 root INFO copying build/lib/ansible_collections/dellemc/openmanage/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,096 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks 2023-04-28 05:57:48,097 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,097 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_smart_fabric.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,097 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_vlan.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,097 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_discovery.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,097 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_quick_deploy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,098 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_group_device_action.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,098 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_identity_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,098 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_devices.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,098 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profiles.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,098 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_power_settings.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,099 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_location.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,099 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:48,099 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_migrate_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:48,099 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:48,099 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_unassign_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:48,100 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_assign_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/profile 2023-04-28 05:57:48,100 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate 2023-04-28 05:57:48,100 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate/ome_powerstate.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate 2023-04-28 05:57:48,100 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate/ome_powerstate_with_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/powerstate 2023-04-28 05:57:48,100 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_port_breakout.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,101 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,101 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_mgmt_network.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,101 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_network_services.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,101 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_template_identity_pool.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,101 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_smart_fabric_uplink.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,102 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_diagnostics.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,102 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_active_directory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,102 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/user 2023-04-28 05:57:48,102 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/user/ome_user_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/user 2023-04-28 05:57:48,102 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/user/ome_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/user 2023-04-28 05:57:48,102 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_domain_user_groups.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,103 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:48,103 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_baseline.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:48,103 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:48,103 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_baseline_workflow.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/compliance 2023-04-28 05:57:48,103 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_job_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,104 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profile_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,104 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,104 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_proxy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,104 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_webserver.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,104 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_console_preferences.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,105 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_certificate.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,105 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_alerts_syslog.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,105 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_time_zone_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,105 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_webserver_port_changed_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,105 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_address_with_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,106 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_security_settings.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,106 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_time.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,106 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_address.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,106 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_settings.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,106 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_alerts_smtp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/application 2023-04-28 05:57:48,107 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_local_access_configuration.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,107 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_group.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,107 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,107 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,107 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,108 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_create_modify_lcd_display.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,108 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_network_vlan.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,108 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_lcd_display_string_deploy.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,108 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,108 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_with_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,109 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_info_with_filter.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/template 2023-04-28 05:57:48,109 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profile_workflow.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,109 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware 2023-04-28 05:57:48,109 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:48,109 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:48,110 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_compliance_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:48,110 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering 2023-04-28 05:57:48,110 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering/component_complaince_report_with_devices.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering 2023-04-28 05:57:48,110 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering/component_complaince_report_with_baseline.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering 2023-04-28 05:57:48,110 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_compliance_info_filters.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:48,111 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline 2023-04-28 05:57:48,111 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/ome_firmware.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware 2023-04-28 05:57:48,111 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/catalog 2023-04-28 05:57:48,111 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/catalog/ome_firmware_catalog.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/catalog 2023-04-28 05:57:48,111 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/firmware/ome_firmware_with_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome/firmware 2023-04-28 05:57:48,112 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_port_breakout_job_traking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,112 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_vlan_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,112 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/ome/ome_chassis_slots.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/ome 2023-04-28 05:57:48,112 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,112 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_redfish_storage_controller_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,112 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_bios.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,113 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/dellemc_idrac_storage_volume.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,113 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_server_config_profile.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,113 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_boot_virtual_media_workflow.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,113 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_redfish_storage_controller.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,114 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_logs.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,114 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_boot.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,114 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_job_status_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,114 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_attributes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,114 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_jobs.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,115 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,115 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_system_lockdown_mode.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,115 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_get_system_inventory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,115 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_configure_idrac_services.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,115 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/idrac_timezone_ntp.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,115 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/idrac_network.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,116 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_get_firmware_inventory.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,116 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_configure_idrac_eventing.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,116 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_idrac_lc_attributes.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated 2023-04-28 05:57:48,116 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_user.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,116 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_reset.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,117 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_syslog.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,117 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_virtual_media.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,117 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_firmware.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,117 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_firmware_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,117 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_reset_result_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,118 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_status_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,118 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_os_deployment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,118 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_system_info.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,118 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_certificates.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/idrac 2023-04-28 05:57:48,118 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish 2023-04-28 05:57:48,119 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/redfish_powerstate.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish 2023-04-28 05:57:48,119 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:48,119 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_create_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:48,119 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:48,119 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_delete_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:48,120 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_modify_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:48,120 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_initialize_job_tracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/storage 2023-04-28 05:57:48,120 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/redfish_event_subscription.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish 2023-04-28 05:57:48,120 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:48,120 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware_from_http_jobtracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:48,121 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware_from_local_jobtracking.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:48,121 root INFO copying build/lib/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/playbooks/redfish/firmware 2023-04-28 05:57:48,121 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:48,121 root INFO copying build/lib/ansible_collections/dellemc/openmanage/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:48,121 root INFO copying build/lib/ansible_collections/dellemc/openmanage/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:48,122 root INFO copying build/lib/ansible_collections/dellemc/openmanage/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage/changelogs 2023-04-28 05:57:48,122 root INFO copying build/lib/ansible_collections/dellemc/openmanage/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,122 root INFO copying build/lib/ansible_collections/dellemc/openmanage/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,122 root INFO copying build/lib/ansible_collections/dellemc/openmanage/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/openmanage 2023-04-28 05:57:48,122 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10 2023-04-28 05:57:48,123 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins 2023-04-28 05:57:48,123 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/terminal 2023-04-28 05:57:48,123 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/terminal/os10.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/terminal 2023-04-28 05:57:48,123 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/doc_fragments 2023-04-28 05:57:48,123 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/doc_fragments/os10.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/doc_fragments 2023-04-28 05:57:48,124 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,124 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/bgp_validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,124 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/os10_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,124 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/wiring_validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,124 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/base_xml_to_dict.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,124 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,125 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/show_system_network_summary.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,125 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/os10_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,125 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/mtu_validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,125 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/vlt_validate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,125 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/modules/os10_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/modules 2023-04-28 05:57:48,126 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/cliconf 2023-04-28 05:57:48,126 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/cliconf/os10.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/cliconf 2023-04-28 05:57:48,126 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/action 2023-04-28 05:57:48,126 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/action/os10.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/action 2023-04-28 05:57:48,126 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/action/textfsm_parser.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/action 2023-04-28 05:57:48,127 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/module_utils 2023-04-28 05:57:48,127 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:48,127 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/module_utils/network/os10.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:48,127 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:48,127 root INFO copying build/lib/ansible_collections/dellemc/os10/plugins/module_utils/network/base_network_show.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/plugins/module_utils/network 2023-04-28 05:57:48,128 root INFO copying build/lib/ansible_collections/dellemc/os10/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10 2023-04-28 05:57:48,128 root INFO copying build/lib/ansible_collections/dellemc/os10/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10 2023-04-28 05:57:48,128 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/meta 2023-04-28 05:57:48,128 root INFO copying build/lib/ansible_collections/dellemc/os10/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/meta 2023-04-28 05:57:48,129 root INFO copying build/lib/ansible_collections/dellemc/os10/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10 2023-04-28 05:57:48,129 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks 2023-04-28 05:57:48,129 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:48,130 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/vxlan_evpn_topology.png -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:48,130 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:48,130 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:48,130 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/prim-vtep2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:48,131 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/sec-vtep1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:48,131 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/spine1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:48,131 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/sec-vtep2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:48,131 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/spine2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:48,131 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/prim-vtep1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars 2023-04-28 05:57:48,132 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:48,132 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/vxlan_evpn/datacenter.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/vxlan_evpn 2023-04-28 05:57:48,132 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,132 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,132 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,132 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,133 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,133 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf3.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,133 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf4.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,133 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/spine1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,133 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/spine2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,134 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,134 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/datacenter.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,134 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:48,134 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars/all -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:48,134 root INFO copying build/lib/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars/spine.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:48,135 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:48,135 root INFO copying build/lib/ansible_collections/dellemc/os10/changelogs/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:48,135 root INFO copying build/lib/ansible_collections/dellemc/os10/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:48,135 root INFO copying build/lib/ansible_collections/dellemc/os10/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/changelogs 2023-04-28 05:57:48,135 root INFO copying build/lib/ansible_collections/dellemc/os10/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10 2023-04-28 05:57:48,136 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles 2023-04-28 05:57:48,136 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config 2023-04-28 05:57:48,136 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/tasks 2023-04-28 05:57:48,136 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/tasks 2023-04-28 05:57:48,136 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/defaults 2023-04-28 05:57:48,136 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/defaults 2023-04-28 05:57:48,137 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/handlers 2023-04-28 05:57:48,137 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/handlers 2023-04-28 05:57:48,137 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config 2023-04-28 05:57:48,137 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:48,137 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:48,138 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tests/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:48,138 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/tests 2023-04-28 05:57:48,138 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/templates 2023-04-28 05:57:48,138 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/templates/leaf1.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/templates 2023-04-28 05:57:48,138 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/vars 2023-04-28 05:57:48,139 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/vars 2023-04-28 05:57:48,139 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/meta 2023-04-28 05:57:48,139 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config/meta 2023-04-28 05:57:48,139 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_copy_config/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_copy_config 2023-04-28 05:57:48,139 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos 2023-04-28 05:57:48,140 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/tasks 2023-04-28 05:57:48,140 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/tasks 2023-04-28 05:57:48,140 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/defaults 2023-04-28 05:57:48,140 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/defaults 2023-04-28 05:57:48,140 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/handlers 2023-04-28 05:57:48,141 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/handlers 2023-04-28 05:57:48,141 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos 2023-04-28 05:57:48,141 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:48,141 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:48,141 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:48,141 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/tests 2023-04-28 05:57:48,142 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/templates 2023-04-28 05:57:48,142 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/templates/os10_qos.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/templates 2023-04-28 05:57:48,142 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/vars 2023-04-28 05:57:48,142 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/vars 2023-04-28 05:57:48,142 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/meta 2023-04-28 05:57:48,143 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos/meta 2023-04-28 05:57:48,143 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_qos/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_qos 2023-04-28 05:57:48,143 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation 2023-04-28 05:57:48,143 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:48,143 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/bgp_validation.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:48,144 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:48,144 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/wiring_validation.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:48,144 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/mtu_validation.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:48,144 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/vlt_validation.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tasks 2023-04-28 05:57:48,144 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation 2023-04-28 05:57:48,145 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:48,145 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:48,145 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:48,145 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site1-spine2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:48,146 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site1-spine1 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:48,146 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site2-spine2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:48,146 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site2-spine1 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars 2023-04-28 05:57:48,146 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:48,146 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests 2023-04-28 05:57:48,147 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/group_vars 2023-04-28 05:57:48,147 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/group_vars/all -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/tests/group_vars 2023-04-28 05:57:48,147 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/meta 2023-04-28 05:57:48,147 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation/meta 2023-04-28 05:57:48,147 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_network_validation/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_network_validation 2023-04-28 05:57:48,148 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp 2023-04-28 05:57:48,148 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/tasks 2023-04-28 05:57:48,148 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/tasks 2023-04-28 05:57:48,148 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/defaults 2023-04-28 05:57:48,148 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/defaults 2023-04-28 05:57:48,149 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/handlers 2023-04-28 05:57:48,149 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/handlers 2023-04-28 05:57:48,149 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp 2023-04-28 05:57:48,149 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:48,149 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:48,149 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:48,150 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/tests 2023-04-28 05:57:48,150 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/templates 2023-04-28 05:57:48,150 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/templates/os10_xstp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/templates 2023-04-28 05:57:48,150 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/vars 2023-04-28 05:57:48,150 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/vars 2023-04-28 05:57:48,151 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/meta 2023-04-28 05:57:48,151 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp/meta 2023-04-28 05:57:48,151 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_xstp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_xstp 2023-04-28 05:57:48,151 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor 2023-04-28 05:57:48,151 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tasks 2023-04-28 05:57:48,152 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tasks 2023-04-28 05:57:48,152 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/defaults 2023-04-28 05:57:48,152 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/defaults 2023-04-28 05:57:48,152 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/handlers 2023-04-28 05:57:48,152 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/handlers 2023-04-28 05:57:48,152 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor 2023-04-28 05:57:48,153 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:48,153 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:48,153 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:48,153 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests 2023-04-28 05:57:48,153 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/templates 2023-04-28 05:57:48,154 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/templates/os10_flow_monitor.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/templates 2023-04-28 05:57:48,154 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/vars 2023-04-28 05:57:48,154 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/vars 2023-04-28 05:57:48,154 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/meta 2023-04-28 05:57:48,154 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor/meta 2023-04-28 05:57:48,155 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_flow_monitor/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_flow_monitor 2023-04-28 05:57:48,155 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan 2023-04-28 05:57:48,155 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/tasks 2023-04-28 05:57:48,155 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/tasks 2023-04-28 05:57:48,155 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/defaults 2023-04-28 05:57:48,156 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/defaults 2023-04-28 05:57:48,156 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/handlers 2023-04-28 05:57:48,156 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/handlers 2023-04-28 05:57:48,156 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan 2023-04-28 05:57:48,156 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:48,156 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:48,157 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:48,157 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/tests 2023-04-28 05:57:48,157 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/templates 2023-04-28 05:57:48,157 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/templates/os10_vxlan.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/templates 2023-04-28 05:57:48,157 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/vars 2023-04-28 05:57:48,158 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/vars 2023-04-28 05:57:48,158 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/meta 2023-04-28 05:57:48,158 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan/meta 2023-04-28 05:57:48,158 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vxlan/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vxlan 2023-04-28 05:57:48,158 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf 2023-04-28 05:57:48,159 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/tasks 2023-04-28 05:57:48,159 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/tasks 2023-04-28 05:57:48,159 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/defaults 2023-04-28 05:57:48,159 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/defaults 2023-04-28 05:57:48,159 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/handlers 2023-04-28 05:57:48,160 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/handlers 2023-04-28 05:57:48,160 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf 2023-04-28 05:57:48,160 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:48,160 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:48,160 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:48,160 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/tests 2023-04-28 05:57:48,161 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/templates 2023-04-28 05:57:48,161 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/templates/os10_vrf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/templates 2023-04-28 05:57:48,161 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/vars 2023-04-28 05:57:48,161 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/vars 2023-04-28 05:57:48,161 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/meta 2023-04-28 05:57:48,162 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf/meta 2023-04-28 05:57:48,162 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrf/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrf 2023-04-28 05:57:48,162 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp 2023-04-28 05:57:48,162 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/tasks 2023-04-28 05:57:48,162 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/tasks 2023-04-28 05:57:48,163 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/defaults 2023-04-28 05:57:48,163 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/defaults 2023-04-28 05:57:48,163 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/handlers 2023-04-28 05:57:48,163 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/handlers 2023-04-28 05:57:48,163 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp 2023-04-28 05:57:48,164 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:48,164 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:48,164 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:48,164 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/tests 2023-04-28 05:57:48,164 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/templates 2023-04-28 05:57:48,164 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/templates/os10_ecmp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/templates 2023-04-28 05:57:48,165 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/vars 2023-04-28 05:57:48,165 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/vars 2023-04-28 05:57:48,165 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/meta 2023-04-28 05:57:48,165 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp/meta 2023-04-28 05:57:48,165 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ecmp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ecmp 2023-04-28 05:57:48,166 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp 2023-04-28 05:57:48,166 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/tasks 2023-04-28 05:57:48,166 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/tasks 2023-04-28 05:57:48,166 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/defaults 2023-04-28 05:57:48,166 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/defaults 2023-04-28 05:57:48,167 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/handlers 2023-04-28 05:57:48,167 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/handlers 2023-04-28 05:57:48,167 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp 2023-04-28 05:57:48,167 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:48,167 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:48,167 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:48,168 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/tests 2023-04-28 05:57:48,168 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/templates 2023-04-28 05:57:48,168 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/templates/os10_lldp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/templates 2023-04-28 05:57:48,168 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/vars 2023-04-28 05:57:48,168 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/vars 2023-04-28 05:57:48,169 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/meta 2023-04-28 05:57:48,169 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp/meta 2023-04-28 05:57:48,169 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lldp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lldp 2023-04-28 05:57:48,169 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade 2023-04-28 05:57:48,169 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tasks 2023-04-28 05:57:48,170 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tasks 2023-04-28 05:57:48,170 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/defaults 2023-04-28 05:57:48,170 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/defaults 2023-04-28 05:57:48,170 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/handlers 2023-04-28 05:57:48,170 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/handlers 2023-04-28 05:57:48,171 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade 2023-04-28 05:57:48,171 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:48,171 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:48,171 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:48,171 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests 2023-04-28 05:57:48,171 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/vars 2023-04-28 05:57:48,172 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/vars 2023-04-28 05:57:48,172 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/meta 2023-04-28 05:57:48,172 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade/meta 2023-04-28 05:57:48,172 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_image_upgrade/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_image_upgrade 2023-04-28 05:57:48,172 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl 2023-04-28 05:57:48,173 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/tasks 2023-04-28 05:57:48,173 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/tasks 2023-04-28 05:57:48,173 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/defaults 2023-04-28 05:57:48,173 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/defaults 2023-04-28 05:57:48,173 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/handlers 2023-04-28 05:57:48,174 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/handlers 2023-04-28 05:57:48,174 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl 2023-04-28 05:57:48,174 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:48,174 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:48,174 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:48,175 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/tests 2023-04-28 05:57:48,175 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/templates 2023-04-28 05:57:48,175 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/templates/os10_acl.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/templates 2023-04-28 05:57:48,175 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/vars 2023-04-28 05:57:48,175 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/vars 2023-04-28 05:57:48,175 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/meta 2023-04-28 05:57:48,176 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl/meta 2023-04-28 05:57:48,176 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_acl/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_acl 2023-04-28 05:57:48,176 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map 2023-04-28 05:57:48,176 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/tasks 2023-04-28 05:57:48,176 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/tasks 2023-04-28 05:57:48,177 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/defaults 2023-04-28 05:57:48,177 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/defaults 2023-04-28 05:57:48,177 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/handlers 2023-04-28 05:57:48,177 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/handlers 2023-04-28 05:57:48,177 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map 2023-04-28 05:57:48,178 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:48,178 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:48,178 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:48,178 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/tests 2023-04-28 05:57:48,178 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/templates 2023-04-28 05:57:48,179 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/templates/os10_route_map.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/templates 2023-04-28 05:57:48,179 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/vars 2023-04-28 05:57:48,179 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/vars 2023-04-28 05:57:48,179 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/meta 2023-04-28 05:57:48,179 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map/meta 2023-04-28 05:57:48,179 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_route_map/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_route_map 2023-04-28 05:57:48,180 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns 2023-04-28 05:57:48,180 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/tasks 2023-04-28 05:57:48,180 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/tasks 2023-04-28 05:57:48,180 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/defaults 2023-04-28 05:57:48,180 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/defaults 2023-04-28 05:57:48,181 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/handlers 2023-04-28 05:57:48,181 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/handlers 2023-04-28 05:57:48,181 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns 2023-04-28 05:57:48,181 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:48,181 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:48,182 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:48,182 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/tests 2023-04-28 05:57:48,182 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/templates 2023-04-28 05:57:48,182 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/templates/os10_dns.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/templates 2023-04-28 05:57:48,182 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/vars 2023-04-28 05:57:48,183 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/vars 2023-04-28 05:57:48,183 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/meta 2023-04-28 05:57:48,183 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns/meta 2023-04-28 05:57:48,183 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_dns/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_dns 2023-04-28 05:57:48,183 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink 2023-04-28 05:57:48,184 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/tasks 2023-04-28 05:57:48,184 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/tasks 2023-04-28 05:57:48,184 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/defaults 2023-04-28 05:57:48,184 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/defaults 2023-04-28 05:57:48,184 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/handlers 2023-04-28 05:57:48,184 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/handlers 2023-04-28 05:57:48,185 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink 2023-04-28 05:57:48,185 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:48,185 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:48,185 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:48,185 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/tests 2023-04-28 05:57:48,186 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/templates 2023-04-28 05:57:48,186 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/templates/os10_uplink.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/templates 2023-04-28 05:57:48,186 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/vars 2023-04-28 05:57:48,186 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/vars 2023-04-28 05:57:48,186 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/meta 2023-04-28 05:57:48,186 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink/meta 2023-04-28 05:57:48,187 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_uplink/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_uplink 2023-04-28 05:57:48,187 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp 2023-04-28 05:57:48,187 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/tasks 2023-04-28 05:57:48,187 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/tasks 2023-04-28 05:57:48,188 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/defaults 2023-04-28 05:57:48,188 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/defaults 2023-04-28 05:57:48,188 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/handlers 2023-04-28 05:57:48,188 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/handlers 2023-04-28 05:57:48,188 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp 2023-04-28 05:57:48,188 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:48,189 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:48,189 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:48,189 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/tests 2023-04-28 05:57:48,189 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/templates 2023-04-28 05:57:48,189 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/templates/os10_vrrp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/templates 2023-04-28 05:57:48,190 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/vars 2023-04-28 05:57:48,190 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/vars 2023-04-28 05:57:48,190 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/meta 2023-04-28 05:57:48,190 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp/meta 2023-04-28 05:57:48,190 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vrrp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vrrp 2023-04-28 05:57:48,191 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary 2023-04-28 05:57:48,191 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tasks 2023-04-28 05:57:48,191 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tasks 2023-04-28 05:57:48,191 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary 2023-04-28 05:57:48,191 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:48,191 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:48,192 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site1-spine2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:48,192 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site1-spine1 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:48,192 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site2-spine2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:48,192 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site2-spine1 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars 2023-04-28 05:57:48,192 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:48,193 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:48,193 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests 2023-04-28 05:57:48,193 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/meta 2023-04-28 05:57:48,193 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary/meta 2023-04-28 05:57:48,193 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_fabric_summary/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_fabric_summary 2023-04-28 05:57:48,194 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface 2023-04-28 05:57:48,194 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/tasks 2023-04-28 05:57:48,194 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/tasks 2023-04-28 05:57:48,194 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/defaults 2023-04-28 05:57:48,194 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/defaults 2023-04-28 05:57:48,195 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/handlers 2023-04-28 05:57:48,195 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/handlers 2023-04-28 05:57:48,195 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface 2023-04-28 05:57:48,195 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:48,195 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:48,195 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:48,196 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/tests 2023-04-28 05:57:48,196 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/templates 2023-04-28 05:57:48,196 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/templates/os10_interface.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/templates 2023-04-28 05:57:48,196 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/vars 2023-04-28 05:57:48,196 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/vars 2023-04-28 05:57:48,197 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/meta 2023-04-28 05:57:48,197 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface/meta 2023-04-28 05:57:48,197 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_interface/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_interface 2023-04-28 05:57:48,197 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp 2023-04-28 05:57:48,197 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/tasks 2023-04-28 05:57:48,198 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/tasks 2023-04-28 05:57:48,198 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/defaults 2023-04-28 05:57:48,198 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/defaults 2023-04-28 05:57:48,198 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/handlers 2023-04-28 05:57:48,198 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/handlers 2023-04-28 05:57:48,198 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp 2023-04-28 05:57:48,199 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:48,199 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:48,199 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:48,199 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/tests 2023-04-28 05:57:48,200 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/templates 2023-04-28 05:57:48,200 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/templates/os10_snmp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/templates 2023-04-28 05:57:48,200 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/vars 2023-04-28 05:57:48,200 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/vars 2023-04-28 05:57:48,200 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/meta 2023-04-28 05:57:48,200 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp/meta 2023-04-28 05:57:48,201 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_snmp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_snmp 2023-04-28 05:57:48,201 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard 2023-04-28 05:57:48,201 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/tasks 2023-04-28 05:57:48,201 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/tasks 2023-04-28 05:57:48,202 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/defaults 2023-04-28 05:57:48,202 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/defaults 2023-04-28 05:57:48,202 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/handlers 2023-04-28 05:57:48,202 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/handlers 2023-04-28 05:57:48,202 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard 2023-04-28 05:57:48,202 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:48,203 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:48,203 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:48,203 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/tests 2023-04-28 05:57:48,203 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/templates 2023-04-28 05:57:48,203 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/templates/os10_raguard.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/templates 2023-04-28 05:57:48,204 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/vars 2023-04-28 05:57:48,204 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/vars 2023-04-28 05:57:48,204 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/meta 2023-04-28 05:57:48,204 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard/meta 2023-04-28 05:57:48,204 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_raguard/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_raguard 2023-04-28 05:57:48,205 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users 2023-04-28 05:57:48,205 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/tasks 2023-04-28 05:57:48,205 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/tasks 2023-04-28 05:57:48,205 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/defaults 2023-04-28 05:57:48,205 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/defaults 2023-04-28 05:57:48,205 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/handlers 2023-04-28 05:57:48,206 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/handlers 2023-04-28 05:57:48,206 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users 2023-04-28 05:57:48,206 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:48,206 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:48,206 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:48,207 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/tests 2023-04-28 05:57:48,207 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/templates 2023-04-28 05:57:48,207 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/templates/os10_users.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/templates 2023-04-28 05:57:48,207 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/vars 2023-04-28 05:57:48,207 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/vars 2023-04-28 05:57:48,207 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/meta 2023-04-28 05:57:48,208 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users/meta 2023-04-28 05:57:48,208 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_users/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_users 2023-04-28 05:57:48,208 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system 2023-04-28 05:57:48,208 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/tasks 2023-04-28 05:57:48,208 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/tasks 2023-04-28 05:57:48,209 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/defaults 2023-04-28 05:57:48,209 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/defaults 2023-04-28 05:57:48,209 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/handlers 2023-04-28 05:57:48,209 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/handlers 2023-04-28 05:57:48,209 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system 2023-04-28 05:57:48,210 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:48,210 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:48,210 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:48,210 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/tests 2023-04-28 05:57:48,210 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/templates 2023-04-28 05:57:48,210 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/templates/os10_system.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/templates 2023-04-28 05:57:48,211 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/vars 2023-04-28 05:57:48,211 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/vars 2023-04-28 05:57:48,211 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/meta 2023-04-28 05:57:48,211 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system/meta 2023-04-28 05:57:48,211 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_system/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_system 2023-04-28 05:57:48,212 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt 2023-04-28 05:57:48,212 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/tasks 2023-04-28 05:57:48,212 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/tasks 2023-04-28 05:57:48,212 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/defaults 2023-04-28 05:57:48,212 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/defaults 2023-04-28 05:57:48,213 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/handlers 2023-04-28 05:57:48,213 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/handlers 2023-04-28 05:57:48,213 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt 2023-04-28 05:57:48,213 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:48,213 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:48,213 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:48,214 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/tests 2023-04-28 05:57:48,214 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/templates 2023-04-28 05:57:48,214 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/templates/os10_vlt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/templates 2023-04-28 05:57:48,214 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/vars 2023-04-28 05:57:48,214 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/vars 2023-04-28 05:57:48,215 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/meta 2023-04-28 05:57:48,215 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt/meta 2023-04-28 05:57:48,215 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlt/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlt 2023-04-28 05:57:48,215 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template 2023-04-28 05:57:48,215 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,216 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_port-channel_summary.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,216 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_spanning_tree_compatibility_mode.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,216 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_vlt_err_disabled_ports.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,216 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_vrf.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,216 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_lldp_neighbors.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,217 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,217 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_interface_brief.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,217 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_bgp_summary.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,217 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/show_vlan.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,217 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tasks/textfsm.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tasks 2023-04-28 05:57:48,218 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template 2023-04-28 05:57:48,218 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:48,218 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:48,218 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:48,218 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tests 2023-04-28 05:57:48,219 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tests/group_vars 2023-04-28 05:57:48,219 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/tests/group_vars/all -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/tests/group_vars 2023-04-28 05:57:48,219 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,219 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_vrf.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,219 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_spanning_tree_compatibility_mode.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,219 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_interface_brief.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,220 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_bgp_summary.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,220 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_vlt_err_disabled_ports.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,220 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_lldp_neighbors.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,220 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_port-channel_summary.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,220 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_vlan.template -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/templates 2023-04-28 05:57:48,221 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/meta 2023-04-28 05:57:48,221 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template/meta 2023-04-28 05:57:48,221 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_template/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_template 2023-04-28 05:57:48,221 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan 2023-04-28 05:57:48,221 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/tasks 2023-04-28 05:57:48,222 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/tasks 2023-04-28 05:57:48,222 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/defaults 2023-04-28 05:57:48,222 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/defaults 2023-04-28 05:57:48,222 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/handlers 2023-04-28 05:57:48,222 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/handlers 2023-04-28 05:57:48,223 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan 2023-04-28 05:57:48,223 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:48,223 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:48,223 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:48,223 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/tests 2023-04-28 05:57:48,224 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/templates 2023-04-28 05:57:48,224 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/templates/os10_vlan.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/templates 2023-04-28 05:57:48,224 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/vars 2023-04-28 05:57:48,224 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/vars 2023-04-28 05:57:48,224 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/meta 2023-04-28 05:57:48,224 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan/meta 2023-04-28 05:57:48,225 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_vlan/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_vlan 2023-04-28 05:57:48,225 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp 2023-04-28 05:57:48,225 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/tasks 2023-04-28 05:57:48,225 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/tasks 2023-04-28 05:57:48,225 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/defaults 2023-04-28 05:57:48,226 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/defaults 2023-04-28 05:57:48,226 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/handlers 2023-04-28 05:57:48,226 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/handlers 2023-04-28 05:57:48,226 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp 2023-04-28 05:57:48,226 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:48,227 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:48,227 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:48,227 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/tests 2023-04-28 05:57:48,227 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/templates 2023-04-28 05:57:48,227 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/templates/os10_bgp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/templates 2023-04-28 05:57:48,228 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/vars 2023-04-28 05:57:48,228 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/vars 2023-04-28 05:57:48,228 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/meta 2023-04-28 05:57:48,228 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp/meta 2023-04-28 05:57:48,228 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bgp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bgp 2023-04-28 05:57:48,229 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp 2023-04-28 05:57:48,229 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/tasks 2023-04-28 05:57:48,229 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/tasks 2023-04-28 05:57:48,229 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/defaults 2023-04-28 05:57:48,229 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/defaults 2023-04-28 05:57:48,230 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/handlers 2023-04-28 05:57:48,230 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/handlers 2023-04-28 05:57:48,230 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp 2023-04-28 05:57:48,230 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:48,230 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:48,230 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:48,231 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/tests 2023-04-28 05:57:48,231 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/templates 2023-04-28 05:57:48,231 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/templates/os10_ntp_vrf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/templates 2023-04-28 05:57:48,231 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/templates/os10_ntp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/templates 2023-04-28 05:57:48,231 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/vars 2023-04-28 05:57:48,232 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/vars 2023-04-28 05:57:48,232 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/meta 2023-04-28 05:57:48,232 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp/meta 2023-04-28 05:57:48,232 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_ntp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_ntp 2023-04-28 05:57:48,232 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list 2023-04-28 05:57:48,233 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/tasks 2023-04-28 05:57:48,233 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/tasks 2023-04-28 05:57:48,233 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/defaults 2023-04-28 05:57:48,233 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/defaults 2023-04-28 05:57:48,233 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/handlers 2023-04-28 05:57:48,234 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/handlers 2023-04-28 05:57:48,234 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list 2023-04-28 05:57:48,234 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:48,234 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:48,234 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:48,234 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/tests 2023-04-28 05:57:48,235 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/templates 2023-04-28 05:57:48,235 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/templates/os10_prefix_list.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/templates 2023-04-28 05:57:48,235 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/vars 2023-04-28 05:57:48,235 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/vars 2023-04-28 05:57:48,235 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta 2023-04-28 05:57:48,236 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta 2023-04-28 05:57:48,236 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta/.galaxy_install_info -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list/meta 2023-04-28 05:57:48,236 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_prefix_list/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_prefix_list 2023-04-28 05:57:48,236 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd 2023-04-28 05:57:48,236 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/tasks 2023-04-28 05:57:48,237 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/tasks 2023-04-28 05:57:48,237 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/defaults 2023-04-28 05:57:48,237 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/defaults 2023-04-28 05:57:48,237 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/handlers 2023-04-28 05:57:48,237 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/handlers 2023-04-28 05:57:48,237 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd 2023-04-28 05:57:48,238 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:48,238 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:48,238 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:48,238 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/tests/main.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/tests 2023-04-28 05:57:48,238 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/templates 2023-04-28 05:57:48,239 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/templates/os10_bfd.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/templates 2023-04-28 05:57:48,239 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/vars 2023-04-28 05:57:48,239 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/vars 2023-04-28 05:57:48,239 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/meta 2023-04-28 05:57:48,239 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd/meta 2023-04-28 05:57:48,239 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_bfd/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_bfd 2023-04-28 05:57:48,240 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag 2023-04-28 05:57:48,240 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/tasks 2023-04-28 05:57:48,240 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/tasks 2023-04-28 05:57:48,240 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/defaults 2023-04-28 05:57:48,240 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/defaults 2023-04-28 05:57:48,241 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/handlers 2023-04-28 05:57:48,241 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/handlers 2023-04-28 05:57:48,241 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag 2023-04-28 05:57:48,241 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:48,241 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:48,242 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:48,242 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/tests 2023-04-28 05:57:48,242 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/templates 2023-04-28 05:57:48,242 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/templates/os10_lag.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/templates 2023-04-28 05:57:48,242 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/vars 2023-04-28 05:57:48,243 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/vars 2023-04-28 05:57:48,243 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/meta 2023-04-28 05:57:48,243 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag/meta 2023-04-28 05:57:48,243 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_lag/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_lag 2023-04-28 05:57:48,243 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging 2023-04-28 05:57:48,244 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/tasks 2023-04-28 05:57:48,244 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/tasks 2023-04-28 05:57:48,244 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/defaults 2023-04-28 05:57:48,244 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/defaults 2023-04-28 05:57:48,244 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/handlers 2023-04-28 05:57:48,244 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/handlers 2023-04-28 05:57:48,245 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging 2023-04-28 05:57:48,245 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:48,245 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:48,245 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:48,245 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/tests 2023-04-28 05:57:48,246 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/templates 2023-04-28 05:57:48,246 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/templates/os10_logging.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/templates 2023-04-28 05:57:48,246 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/vars 2023-04-28 05:57:48,246 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/vars 2023-04-28 05:57:48,246 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/meta 2023-04-28 05:57:48,247 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging/meta 2023-04-28 05:57:48,247 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_logging/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_logging 2023-04-28 05:57:48,247 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa 2023-04-28 05:57:48,247 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/tasks 2023-04-28 05:57:48,247 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/tasks 2023-04-28 05:57:48,248 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/defaults 2023-04-28 05:57:48,248 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/defaults 2023-04-28 05:57:48,248 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/handlers 2023-04-28 05:57:48,248 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/handlers 2023-04-28 05:57:48,248 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa 2023-04-28 05:57:48,248 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:48,249 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tests/main.os10.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:48,249 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:48,249 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/tests 2023-04-28 05:57:48,249 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/templates 2023-04-28 05:57:48,249 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/templates/os10_aaa.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/templates 2023-04-28 05:57:48,250 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/vars 2023-04-28 05:57:48,250 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/vars 2023-04-28 05:57:48,250 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/meta 2023-04-28 05:57:48,250 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa/meta 2023-04-28 05:57:48,250 root INFO copying build/lib/ansible_collections/dellemc/os10/roles/os10_aaa/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os10/roles/os10_aaa 2023-04-28 05:57:48,251 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9 2023-04-28 05:57:48,251 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins 2023-04-28 05:57:48,251 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/terminal 2023-04-28 05:57:48,251 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/terminal 2023-04-28 05:57:48,251 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/terminal/os9.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/terminal 2023-04-28 05:57:48,251 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/doc_fragments 2023-04-28 05:57:48,252 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/doc_fragments 2023-04-28 05:57:48,252 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/doc_fragments/os9.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/doc_fragments 2023-04-28 05:57:48,252 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:48,252 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/modules/os9_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:48,252 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/modules/os9_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:48,253 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:48,253 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/modules/os9_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/modules 2023-04-28 05:57:48,253 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/cliconf 2023-04-28 05:57:48,253 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/cliconf 2023-04-28 05:57:48,253 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/cliconf/os9.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/cliconf 2023-04-28 05:57:48,254 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/action 2023-04-28 05:57:48,254 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/action 2023-04-28 05:57:48,254 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/action/os9.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/action 2023-04-28 05:57:48,255 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/module_utils 2023-04-28 05:57:48,255 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/module_utils 2023-04-28 05:57:48,255 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/module_utils/network 2023-04-28 05:57:48,255 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/module_utils/network 2023-04-28 05:57:48,255 root INFO copying build/lib/ansible_collections/dellemc/os9/plugins/module_utils/network/os9.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/plugins/module_utils/network 2023-04-28 05:57:48,255 root INFO copying build/lib/ansible_collections/dellemc/os9/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9 2023-04-28 05:57:48,256 root INFO copying build/lib/ansible_collections/dellemc/os9/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9 2023-04-28 05:57:48,256 root INFO copying build/lib/ansible_collections/dellemc/os9/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9 2023-04-28 05:57:48,256 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/meta 2023-04-28 05:57:48,256 root INFO copying build/lib/ansible_collections/dellemc/os9/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/meta 2023-04-28 05:57:48,257 root INFO copying build/lib/ansible_collections/dellemc/os9/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9 2023-04-28 05:57:48,257 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks 2023-04-28 05:57:48,257 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,257 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,257 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,258 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,258 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,258 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf3.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,258 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf4.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,258 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/spine1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,259 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/spine2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars 2023-04-28 05:57:48,259 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,259 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/datacenter.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp 2023-04-28 05:57:48,259 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:48,259 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars/all -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:48,259 root INFO copying build/lib/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars/spine.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars 2023-04-28 05:57:48,260 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:48,260 root INFO copying build/lib/ansible_collections/dellemc/os9/changelogs/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:48,260 root INFO copying build/lib/ansible_collections/dellemc/os9/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:48,260 root INFO copying build/lib/ansible_collections/dellemc/os9/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/changelogs 2023-04-28 05:57:48,260 root INFO copying build/lib/ansible_collections/dellemc/os9/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9 2023-04-28 05:57:48,261 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles 2023-04-28 05:57:48,261 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface 2023-04-28 05:57:48,261 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/tasks 2023-04-28 05:57:48,261 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/tasks 2023-04-28 05:57:48,261 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/defaults 2023-04-28 05:57:48,262 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/defaults 2023-04-28 05:57:48,262 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/handlers 2023-04-28 05:57:48,262 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/handlers 2023-04-28 05:57:48,262 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface 2023-04-28 05:57:48,262 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:48,262 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:48,263 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:48,263 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/tests 2023-04-28 05:57:48,263 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/templates 2023-04-28 05:57:48,263 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/templates/os9_interface.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/templates 2023-04-28 05:57:48,263 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/vars 2023-04-28 05:57:48,264 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/vars 2023-04-28 05:57:48,264 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/meta 2023-04-28 05:57:48,264 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface/meta 2023-04-28 05:57:48,264 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_interface/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_interface 2023-04-28 05:57:48,264 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow 2023-04-28 05:57:48,265 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/tasks 2023-04-28 05:57:48,265 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/tasks 2023-04-28 05:57:48,265 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/defaults 2023-04-28 05:57:48,265 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/defaults 2023-04-28 05:57:48,265 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/handlers 2023-04-28 05:57:48,265 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/handlers 2023-04-28 05:57:48,266 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow 2023-04-28 05:57:48,266 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:48,266 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:48,266 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:48,266 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/tests 2023-04-28 05:57:48,267 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/templates 2023-04-28 05:57:48,267 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/templates/os9_sflow.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/templates 2023-04-28 05:57:48,267 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/vars 2023-04-28 05:57:48,267 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/vars 2023-04-28 05:57:48,267 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/meta 2023-04-28 05:57:48,268 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow/meta 2023-04-28 05:57:48,268 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_sflow/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_sflow 2023-04-28 05:57:48,268 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp 2023-04-28 05:57:48,268 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/tasks 2023-04-28 05:57:48,268 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/tasks 2023-04-28 05:57:48,269 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/defaults 2023-04-28 05:57:48,269 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/defaults 2023-04-28 05:57:48,269 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/handlers 2023-04-28 05:57:48,269 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/handlers 2023-04-28 05:57:48,269 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp 2023-04-28 05:57:48,270 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:48,270 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:48,270 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:48,270 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/tests 2023-04-28 05:57:48,270 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/templates 2023-04-28 05:57:48,270 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/templates/os9_bgp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/templates 2023-04-28 05:57:48,271 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/vars 2023-04-28 05:57:48,271 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/vars 2023-04-28 05:57:48,271 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/meta 2023-04-28 05:57:48,271 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp/meta 2023-04-28 05:57:48,271 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_bgp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_bgp 2023-04-28 05:57:48,272 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp 2023-04-28 05:57:48,272 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/tasks 2023-04-28 05:57:48,272 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/tasks 2023-04-28 05:57:48,272 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/defaults 2023-04-28 05:57:48,272 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/defaults 2023-04-28 05:57:48,273 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/handlers 2023-04-28 05:57:48,273 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/handlers 2023-04-28 05:57:48,273 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp 2023-04-28 05:57:48,273 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:48,273 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:48,274 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:48,274 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/tests 2023-04-28 05:57:48,274 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/templates 2023-04-28 05:57:48,274 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/templates/os9_xstp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/templates 2023-04-28 05:57:48,274 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/vars 2023-04-28 05:57:48,274 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/vars 2023-04-28 05:57:48,275 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/meta 2023-04-28 05:57:48,275 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp/meta 2023-04-28 05:57:48,275 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_xstp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_xstp 2023-04-28 05:57:48,275 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag 2023-04-28 05:57:48,275 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/tasks 2023-04-28 05:57:48,276 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/tasks 2023-04-28 05:57:48,276 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/defaults 2023-04-28 05:57:48,276 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/defaults 2023-04-28 05:57:48,276 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/handlers 2023-04-28 05:57:48,276 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/handlers 2023-04-28 05:57:48,277 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag 2023-04-28 05:57:48,277 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:48,277 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:48,277 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:48,277 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/tests 2023-04-28 05:57:48,278 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/templates 2023-04-28 05:57:48,278 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/templates/os9_lag.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/templates 2023-04-28 05:57:48,278 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/vars 2023-04-28 05:57:48,278 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/vars 2023-04-28 05:57:48,278 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/meta 2023-04-28 05:57:48,278 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag/meta 2023-04-28 05:57:48,279 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lag/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lag 2023-04-28 05:57:48,279 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp 2023-04-28 05:57:48,279 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/tasks 2023-04-28 05:57:48,279 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/tasks 2023-04-28 05:57:48,279 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/defaults 2023-04-28 05:57:48,280 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/defaults 2023-04-28 05:57:48,280 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/handlers 2023-04-28 05:57:48,280 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/handlers 2023-04-28 05:57:48,280 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp 2023-04-28 05:57:48,280 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:48,281 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:48,281 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:48,281 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/tests 2023-04-28 05:57:48,281 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/templates 2023-04-28 05:57:48,281 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/templates/os9_vrrp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/templates 2023-04-28 05:57:48,282 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/vars 2023-04-28 05:57:48,282 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/vars 2023-04-28 05:57:48,282 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/meta 2023-04-28 05:57:48,282 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp/meta 2023-04-28 05:57:48,282 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrrp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrrp 2023-04-28 05:57:48,283 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users 2023-04-28 05:57:48,283 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/tasks 2023-04-28 05:57:48,283 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/tasks 2023-04-28 05:57:48,283 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/defaults 2023-04-28 05:57:48,283 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/defaults 2023-04-28 05:57:48,283 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/handlers 2023-04-28 05:57:48,284 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/handlers 2023-04-28 05:57:48,284 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users 2023-04-28 05:57:48,284 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:48,284 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:48,284 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:48,285 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/tests 2023-04-28 05:57:48,285 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/templates 2023-04-28 05:57:48,285 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/templates/os9_users.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/templates 2023-04-28 05:57:48,285 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/vars 2023-04-28 05:57:48,285 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/vars 2023-04-28 05:57:48,286 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/meta 2023-04-28 05:57:48,286 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users/meta 2023-04-28 05:57:48,286 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_users/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_users 2023-04-28 05:57:48,286 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns 2023-04-28 05:57:48,286 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/tasks 2023-04-28 05:57:48,287 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/tasks 2023-04-28 05:57:48,287 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/defaults 2023-04-28 05:57:48,287 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/defaults 2023-04-28 05:57:48,287 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/handlers 2023-04-28 05:57:48,287 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/handlers 2023-04-28 05:57:48,287 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns 2023-04-28 05:57:48,288 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:48,288 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:48,288 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:48,288 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/tests 2023-04-28 05:57:48,288 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/templates 2023-04-28 05:57:48,289 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/templates/os9_dns.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/templates 2023-04-28 05:57:48,289 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/vars 2023-04-28 05:57:48,289 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/vars 2023-04-28 05:57:48,289 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/meta 2023-04-28 05:57:48,289 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns/meta 2023-04-28 05:57:48,290 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dns/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dns 2023-04-28 05:57:48,290 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp 2023-04-28 05:57:48,290 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/tasks 2023-04-28 05:57:48,290 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/tasks 2023-04-28 05:57:48,290 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/defaults 2023-04-28 05:57:48,290 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/defaults 2023-04-28 05:57:48,291 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/handlers 2023-04-28 05:57:48,291 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/handlers 2023-04-28 05:57:48,291 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp 2023-04-28 05:57:48,291 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:48,291 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:48,292 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:48,292 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/tests 2023-04-28 05:57:48,292 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/templates 2023-04-28 05:57:48,292 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/templates/os9_ntp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/templates 2023-04-28 05:57:48,292 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/vars 2023-04-28 05:57:48,293 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/vars 2023-04-28 05:57:48,293 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/meta 2023-04-28 05:57:48,293 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp/meta 2023-04-28 05:57:48,293 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ntp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ntp 2023-04-28 05:57:48,293 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp 2023-04-28 05:57:48,294 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/tasks 2023-04-28 05:57:48,294 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/tasks 2023-04-28 05:57:48,294 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/defaults 2023-04-28 05:57:48,294 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/defaults 2023-04-28 05:57:48,294 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/handlers 2023-04-28 05:57:48,294 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/handlers 2023-04-28 05:57:48,295 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp 2023-04-28 05:57:48,295 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:48,295 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:48,295 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:48,295 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/tests 2023-04-28 05:57:48,296 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/templates 2023-04-28 05:57:48,296 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/templates/os9_ecmp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/templates 2023-04-28 05:57:48,296 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/vars 2023-04-28 05:57:48,296 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/vars 2023-04-28 05:57:48,296 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/meta 2023-04-28 05:57:48,296 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp/meta 2023-04-28 05:57:48,297 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_ecmp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_ecmp 2023-04-28 05:57:48,297 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging 2023-04-28 05:57:48,297 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/tasks 2023-04-28 05:57:48,297 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/tasks 2023-04-28 05:57:48,297 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/defaults 2023-04-28 05:57:48,298 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/defaults 2023-04-28 05:57:48,298 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/handlers 2023-04-28 05:57:48,298 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/handlers 2023-04-28 05:57:48,298 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging 2023-04-28 05:57:48,298 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:48,299 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:48,299 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:48,299 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/tests 2023-04-28 05:57:48,299 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/templates 2023-04-28 05:57:48,299 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/templates/os9_logging.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/templates 2023-04-28 05:57:48,300 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/vars 2023-04-28 05:57:48,300 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/vars 2023-04-28 05:57:48,300 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/meta 2023-04-28 05:57:48,300 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging/meta 2023-04-28 05:57:48,300 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_logging/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_logging 2023-04-28 05:57:48,301 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf 2023-04-28 05:57:48,301 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/tasks 2023-04-28 05:57:48,301 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/tasks 2023-04-28 05:57:48,301 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/defaults 2023-04-28 05:57:48,301 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/defaults 2023-04-28 05:57:48,301 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/handlers 2023-04-28 05:57:48,302 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/handlers 2023-04-28 05:57:48,302 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf 2023-04-28 05:57:48,302 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:48,302 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:48,302 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:48,303 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/tests 2023-04-28 05:57:48,303 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/templates 2023-04-28 05:57:48,303 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/templates/os9_vrf.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/templates 2023-04-28 05:57:48,303 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/vars 2023-04-28 05:57:48,303 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/vars 2023-04-28 05:57:48,304 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/meta 2023-04-28 05:57:48,304 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf/meta 2023-04-28 05:57:48,304 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vrf/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vrf 2023-04-28 05:57:48,304 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan 2023-04-28 05:57:48,304 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/tasks 2023-04-28 05:57:48,305 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/tasks 2023-04-28 05:57:48,305 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/defaults 2023-04-28 05:57:48,305 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/defaults 2023-04-28 05:57:48,305 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/handlers 2023-04-28 05:57:48,305 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/handlers 2023-04-28 05:57:48,305 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan 2023-04-28 05:57:48,306 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:48,306 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:48,306 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:48,306 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/tests 2023-04-28 05:57:48,306 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/templates 2023-04-28 05:57:48,307 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/templates/os9_vlan.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/templates 2023-04-28 05:57:48,307 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/vars 2023-04-28 05:57:48,307 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/vars 2023-04-28 05:57:48,307 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/meta 2023-04-28 05:57:48,307 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan/meta 2023-04-28 05:57:48,308 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlan/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlan 2023-04-28 05:57:48,308 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system 2023-04-28 05:57:48,308 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/tasks 2023-04-28 05:57:48,308 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/tasks 2023-04-28 05:57:48,308 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/defaults 2023-04-28 05:57:48,308 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/defaults 2023-04-28 05:57:48,309 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/handlers 2023-04-28 05:57:48,309 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/handlers 2023-04-28 05:57:48,309 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system 2023-04-28 05:57:48,309 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:48,309 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:48,310 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:48,310 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/tests 2023-04-28 05:57:48,310 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/templates 2023-04-28 05:57:48,310 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/templates/os9_system.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/templates 2023-04-28 05:57:48,310 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/vars 2023-04-28 05:57:48,311 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/vars 2023-04-28 05:57:48,311 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/meta 2023-04-28 05:57:48,311 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system/meta 2023-04-28 05:57:48,311 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_system/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_system 2023-04-28 05:57:48,311 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp 2023-04-28 05:57:48,312 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/tasks 2023-04-28 05:57:48,312 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/tasks 2023-04-28 05:57:48,312 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/defaults 2023-04-28 05:57:48,312 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/defaults 2023-04-28 05:57:48,312 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/handlers 2023-04-28 05:57:48,312 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/handlers 2023-04-28 05:57:48,313 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp 2023-04-28 05:57:48,313 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:48,313 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:48,313 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:48,313 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/tests 2023-04-28 05:57:48,314 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/templates 2023-04-28 05:57:48,314 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/templates/os9_snmp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/templates 2023-04-28 05:57:48,314 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/vars 2023-04-28 05:57:48,314 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/vars 2023-04-28 05:57:48,314 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/meta 2023-04-28 05:57:48,315 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp/meta 2023-04-28 05:57:48,315 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_snmp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_snmp 2023-04-28 05:57:48,315 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa 2023-04-28 05:57:48,315 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/tasks 2023-04-28 05:57:48,315 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/tasks 2023-04-28 05:57:48,316 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/defaults 2023-04-28 05:57:48,316 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/defaults 2023-04-28 05:57:48,316 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/handlers 2023-04-28 05:57:48,316 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/handlers 2023-04-28 05:57:48,316 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa 2023-04-28 05:57:48,317 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:48,317 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:48,317 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:48,317 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/tests 2023-04-28 05:57:48,317 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/templates 2023-04-28 05:57:48,318 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/templates/os9_aaa.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/templates 2023-04-28 05:57:48,318 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/vars 2023-04-28 05:57:48,318 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/vars 2023-04-28 05:57:48,318 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/meta 2023-04-28 05:57:48,318 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa/meta 2023-04-28 05:57:48,319 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_aaa/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_aaa 2023-04-28 05:57:48,319 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list 2023-04-28 05:57:48,319 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/tasks 2023-04-28 05:57:48,319 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/tasks 2023-04-28 05:57:48,319 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/defaults 2023-04-28 05:57:48,320 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/defaults 2023-04-28 05:57:48,320 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/handlers 2023-04-28 05:57:48,320 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/handlers 2023-04-28 05:57:48,320 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list 2023-04-28 05:57:48,320 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:48,321 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:48,321 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:48,321 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/tests 2023-04-28 05:57:48,321 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/templates 2023-04-28 05:57:48,321 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/templates/os9_prefix_list.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/templates 2023-04-28 05:57:48,321 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/vars 2023-04-28 05:57:48,322 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/vars 2023-04-28 05:57:48,322 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/meta 2023-04-28 05:57:48,322 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list/meta 2023-04-28 05:57:48,322 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_prefix_list/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_prefix_list 2023-04-28 05:57:48,322 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp 2023-04-28 05:57:48,323 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/tasks 2023-04-28 05:57:48,323 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/tasks 2023-04-28 05:57:48,323 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/defaults 2023-04-28 05:57:48,323 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/defaults 2023-04-28 05:57:48,323 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/handlers 2023-04-28 05:57:48,324 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/handlers 2023-04-28 05:57:48,324 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp 2023-04-28 05:57:48,324 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:48,324 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:48,324 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:48,325 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/tests 2023-04-28 05:57:48,325 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/templates 2023-04-28 05:57:48,325 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/templates/os9_lldp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/templates 2023-04-28 05:57:48,325 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/vars 2023-04-28 05:57:48,325 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/vars 2023-04-28 05:57:48,325 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/meta 2023-04-28 05:57:48,326 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp/meta 2023-04-28 05:57:48,326 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_lldp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_lldp 2023-04-28 05:57:48,326 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl 2023-04-28 05:57:48,326 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/tasks 2023-04-28 05:57:48,326 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/tasks 2023-04-28 05:57:48,327 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/defaults 2023-04-28 05:57:48,327 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/defaults 2023-04-28 05:57:48,327 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/handlers 2023-04-28 05:57:48,327 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/handlers 2023-04-28 05:57:48,327 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl 2023-04-28 05:57:48,328 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:48,328 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:48,328 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:48,328 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/tests 2023-04-28 05:57:48,328 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/templates 2023-04-28 05:57:48,329 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/templates/os9_acl.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/templates 2023-04-28 05:57:48,329 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/vars 2023-04-28 05:57:48,329 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/vars 2023-04-28 05:57:48,329 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/meta 2023-04-28 05:57:48,329 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl/meta 2023-04-28 05:57:48,329 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_acl/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_acl 2023-04-28 05:57:48,330 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config 2023-04-28 05:57:48,330 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/tasks 2023-04-28 05:57:48,330 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/tasks 2023-04-28 05:57:48,330 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/defaults 2023-04-28 05:57:48,330 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/defaults 2023-04-28 05:57:48,331 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/handlers 2023-04-28 05:57:48,331 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/handlers 2023-04-28 05:57:48,331 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config 2023-04-28 05:57:48,331 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:48,331 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:48,332 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:48,332 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/tests 2023-04-28 05:57:48,332 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/templates 2023-04-28 05:57:48,332 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/templates/os9_copy_config.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/templates 2023-04-28 05:57:48,332 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/vars 2023-04-28 05:57:48,333 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/vars 2023-04-28 05:57:48,333 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/meta 2023-04-28 05:57:48,333 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config/meta 2023-04-28 05:57:48,333 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_copy_config/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_copy_config 2023-04-28 05:57:48,333 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt 2023-04-28 05:57:48,334 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/tasks 2023-04-28 05:57:48,334 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/tasks 2023-04-28 05:57:48,334 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/defaults 2023-04-28 05:57:48,334 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/defaults 2023-04-28 05:57:48,334 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/handlers 2023-04-28 05:57:48,334 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/handlers 2023-04-28 05:57:48,335 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt 2023-04-28 05:57:48,335 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:48,335 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:48,335 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:48,335 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/tests 2023-04-28 05:57:48,336 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/templates 2023-04-28 05:57:48,336 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/templates/os9_vlt.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/templates 2023-04-28 05:57:48,336 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/vars 2023-04-28 05:57:48,336 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/vars 2023-04-28 05:57:48,336 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/meta 2023-04-28 05:57:48,336 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt/meta 2023-04-28 05:57:48,337 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_vlt/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_vlt 2023-04-28 05:57:48,337 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb 2023-04-28 05:57:48,337 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/tasks 2023-04-28 05:57:48,337 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/tasks 2023-04-28 05:57:48,338 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/defaults 2023-04-28 05:57:48,338 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/defaults 2023-04-28 05:57:48,338 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/handlers 2023-04-28 05:57:48,338 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/handlers 2023-04-28 05:57:48,338 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb 2023-04-28 05:57:48,338 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:48,339 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:48,339 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tests/main.os9.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:48,339 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/tests 2023-04-28 05:57:48,339 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/templates 2023-04-28 05:57:48,339 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/templates/os9_dcb.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/templates 2023-04-28 05:57:48,340 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/vars 2023-04-28 05:57:48,340 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/vars 2023-04-28 05:57:48,340 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/meta 2023-04-28 05:57:48,340 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb/meta 2023-04-28 05:57:48,340 root INFO copying build/lib/ansible_collections/dellemc/os9/roles/os9_dcb/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os9/roles/os9_dcb 2023-04-28 05:57:48,341 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,341 root INFO copying build/lib/ansible_collections/dellemc/unity/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,341 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins 2023-04-28 05:57:48,341 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/doc_fragments 2023-04-28 05:57:48,341 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/doc_fragments/unity.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/doc_fragments 2023-04-28 05:57:48,341 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,342 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/snapshotschedule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,342 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/smbshare.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,342 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/interface.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,342 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/filesystem.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,343 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,343 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,343 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,343 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/nfsserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,344 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/cifsserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,344 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/user_quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,344 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/nasserver.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,344 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/tree_quota.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,345 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/nfs.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,345 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/storagepool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,345 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/filesystem_snapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,345 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/consistencygroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,346 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/modules/host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/modules 2023-04-28 05:57:48,346 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/module_utils 2023-04-28 05:57:48,346 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/module_utils/storage 2023-04-28 05:57:48,346 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:48,346 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/utils.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:48,347 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:48,347 root INFO copying build/lib/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/logging_handler.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell 2023-04-28 05:57:48,347 root INFO copying build/lib/ansible_collections/dellemc/unity/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,347 root INFO copying build/lib/ansible_collections/dellemc/unity/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,348 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/meta 2023-04-28 05:57:48,348 root INFO copying build/lib/ansible_collections/dellemc/unity/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/meta 2023-04-28 05:57:48,348 root INFO copying build/lib/ansible_collections/dellemc/unity/meta/execution-environment.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/meta 2023-04-28 05:57:48,348 root INFO copying build/lib/ansible_collections/dellemc/unity/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,348 root INFO copying build/lib/ansible_collections/dellemc/unity/ansible.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,349 root INFO copying build/lib/ansible_collections/dellemc/unity/MODULE-LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,349 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:48,349 root INFO copying build/lib/ansible_collections/dellemc/unity/changelogs/.plugin-cache.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:48,349 root INFO copying build/lib/ansible_collections/dellemc/unity/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:48,349 root INFO copying build/lib/ansible_collections/dellemc/unity/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity/changelogs 2023-04-28 05:57:48,350 root INFO copying build/lib/ansible_collections/dellemc/unity/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,350 root INFO copying build/lib/ansible_collections/dellemc/unity/requirements.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,350 root INFO copying build/lib/ansible_collections/dellemc/unity/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/unity 2023-04-28 05:57:48,350 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6 2023-04-28 05:57:48,350 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins 2023-04-28 05:57:48,351 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/terminal 2023-04-28 05:57:48,351 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/terminal/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/terminal 2023-04-28 05:57:48,351 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/terminal/os6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/terminal 2023-04-28 05:57:48,351 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/doc_fragments 2023-04-28 05:57:48,351 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/doc_fragments 2023-04-28 05:57:48,351 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/doc_fragments/os6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/doc_fragments 2023-04-28 05:57:48,352 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:48,352 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/modules/os6_command.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:48,352 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:48,352 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/modules/os6_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:48,352 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/modules/os6_config.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/modules 2023-04-28 05:57:48,353 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/cliconf 2023-04-28 05:57:48,353 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/cliconf/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/cliconf 2023-04-28 05:57:48,353 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/cliconf/os6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/cliconf 2023-04-28 05:57:48,353 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/action 2023-04-28 05:57:48,353 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/action/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/action 2023-04-28 05:57:48,353 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/action/os6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/action 2023-04-28 05:57:48,354 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/module_utils 2023-04-28 05:57:48,354 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/module_utils/network 2023-04-28 05:57:48,354 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/module_utils/network/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/module_utils/network 2023-04-28 05:57:48,354 root INFO copying build/lib/ansible_collections/dellemc/os6/plugins/module_utils/network/os6.py -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/plugins/module_utils/network 2023-04-28 05:57:48,354 root INFO copying build/lib/ansible_collections/dellemc/os6/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6 2023-04-28 05:57:48,355 root INFO copying build/lib/ansible_collections/dellemc/os6/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6 2023-04-28 05:57:48,355 root INFO copying build/lib/ansible_collections/dellemc/os6/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6 2023-04-28 05:57:48,355 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/meta 2023-04-28 05:57:48,355 root INFO copying build/lib/ansible_collections/dellemc/os6/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/meta 2023-04-28 05:57:48,356 root INFO copying build/lib/ansible_collections/dellemc/os6/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6 2023-04-28 05:57:48,356 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks 2023-04-28 05:57:48,356 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:48,356 root INFO copying build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:48,356 root INFO copying build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/os6switch.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:48,357 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars 2023-04-28 05:57:48,357 root INFO copying build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars/switch1.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars 2023-04-28 05:57:48,357 root INFO copying build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars/switch2.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp/host_vars 2023-04-28 05:57:48,357 root INFO copying build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp 2023-04-28 05:57:48,357 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp/group_vars 2023-04-28 05:57:48,357 root INFO copying build/lib/ansible_collections/dellemc/os6/playbooks/ibgp/group_vars/all -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/playbooks/ibgp/group_vars 2023-04-28 05:57:48,358 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:48,358 root INFO copying build/lib/ansible_collections/dellemc/os6/changelogs/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:48,358 root INFO copying build/lib/ansible_collections/dellemc/os6/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:48,358 root INFO copying build/lib/ansible_collections/dellemc/os6/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/changelogs 2023-04-28 05:57:48,358 root INFO copying build/lib/ansible_collections/dellemc/os6/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6 2023-04-28 05:57:48,359 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles 2023-04-28 05:57:48,359 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl 2023-04-28 05:57:48,359 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/tasks 2023-04-28 05:57:48,359 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/tasks 2023-04-28 05:57:48,359 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/defaults 2023-04-28 05:57:48,359 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/defaults 2023-04-28 05:57:48,360 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/handlers 2023-04-28 05:57:48,360 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/handlers 2023-04-28 05:57:48,360 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl 2023-04-28 05:57:48,360 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:48,360 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:48,361 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:48,361 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/tests 2023-04-28 05:57:48,361 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/templates 2023-04-28 05:57:48,361 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/templates/os6_acl.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/templates 2023-04-28 05:57:48,361 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/vars 2023-04-28 05:57:48,362 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/vars 2023-04-28 05:57:48,362 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/meta 2023-04-28 05:57:48,362 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl/meta 2023-04-28 05:57:48,362 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_acl/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_acl 2023-04-28 05:57:48,362 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp 2023-04-28 05:57:48,363 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/tasks 2023-04-28 05:57:48,363 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/tasks 2023-04-28 05:57:48,363 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/defaults 2023-04-28 05:57:48,363 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/defaults 2023-04-28 05:57:48,363 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/handlers 2023-04-28 05:57:48,363 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/handlers 2023-04-28 05:57:48,364 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp 2023-04-28 05:57:48,364 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:48,364 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:48,364 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:48,364 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/tests 2023-04-28 05:57:48,365 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/templates 2023-04-28 05:57:48,365 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/templates/os6_bgp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/templates 2023-04-28 05:57:48,365 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/vars 2023-04-28 05:57:48,365 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/vars 2023-04-28 05:57:48,365 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/meta 2023-04-28 05:57:48,366 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp/meta 2023-04-28 05:57:48,366 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_bgp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_bgp 2023-04-28 05:57:48,366 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp 2023-04-28 05:57:48,366 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/tasks 2023-04-28 05:57:48,366 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/tasks 2023-04-28 05:57:48,367 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/defaults 2023-04-28 05:57:48,367 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/defaults 2023-04-28 05:57:48,367 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/handlers 2023-04-28 05:57:48,367 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/handlers 2023-04-28 05:57:48,367 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp 2023-04-28 05:57:48,368 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:48,368 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:48,368 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:48,368 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/tests 2023-04-28 05:57:48,368 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/templates 2023-04-28 05:57:48,368 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/templates/os6_lldp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/templates 2023-04-28 05:57:48,369 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/vars 2023-04-28 05:57:48,369 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/vars 2023-04-28 05:57:48,369 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/meta 2023-04-28 05:57:48,369 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp/meta 2023-04-28 05:57:48,369 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lldp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lldp 2023-04-28 05:57:48,370 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system 2023-04-28 05:57:48,370 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/tasks 2023-04-28 05:57:48,370 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/tasks 2023-04-28 05:57:48,370 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/defaults 2023-04-28 05:57:48,370 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/defaults 2023-04-28 05:57:48,371 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/handlers 2023-04-28 05:57:48,371 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/handlers 2023-04-28 05:57:48,371 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system 2023-04-28 05:57:48,371 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:48,371 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:48,371 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:48,372 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/tests 2023-04-28 05:57:48,372 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/templates 2023-04-28 05:57:48,372 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/templates/os6_system.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/templates 2023-04-28 05:57:48,372 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/vars 2023-04-28 05:57:48,372 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/vars 2023-04-28 05:57:48,373 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/meta 2023-04-28 05:57:48,373 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system/meta 2023-04-28 05:57:48,373 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_system/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_system 2023-04-28 05:57:48,373 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users 2023-04-28 05:57:48,373 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/tasks 2023-04-28 05:57:48,374 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/tasks 2023-04-28 05:57:48,374 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/defaults 2023-04-28 05:57:48,374 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/defaults 2023-04-28 05:57:48,374 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/handlers 2023-04-28 05:57:48,374 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/handlers 2023-04-28 05:57:48,374 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users 2023-04-28 05:57:48,375 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:48,375 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:48,375 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:48,375 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/tests 2023-04-28 05:57:48,375 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/templates 2023-04-28 05:57:48,376 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/templates/os6_users.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/templates 2023-04-28 05:57:48,376 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/vars 2023-04-28 05:57:48,376 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/vars 2023-04-28 05:57:48,376 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/meta 2023-04-28 05:57:48,376 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users/meta 2023-04-28 05:57:48,377 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_users/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_users 2023-04-28 05:57:48,377 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp 2023-04-28 05:57:48,377 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/tasks 2023-04-28 05:57:48,377 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/tasks 2023-04-28 05:57:48,377 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/defaults 2023-04-28 05:57:48,378 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/defaults 2023-04-28 05:57:48,378 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/handlers 2023-04-28 05:57:48,378 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/handlers 2023-04-28 05:57:48,378 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp 2023-04-28 05:57:48,378 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:48,378 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:48,379 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:48,379 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/tests 2023-04-28 05:57:48,379 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/templates 2023-04-28 05:57:48,380 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/templates/os6_vrrp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/templates 2023-04-28 05:57:48,380 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/vars 2023-04-28 05:57:48,380 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/vars 2023-04-28 05:57:48,380 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/meta 2023-04-28 05:57:48,380 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp/meta 2023-04-28 05:57:48,381 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vrrp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vrrp 2023-04-28 05:57:48,381 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp 2023-04-28 05:57:48,381 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/tasks 2023-04-28 05:57:48,381 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/tasks 2023-04-28 05:57:48,381 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/defaults 2023-04-28 05:57:48,381 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/defaults 2023-04-28 05:57:48,382 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/handlers 2023-04-28 05:57:48,382 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/handlers 2023-04-28 05:57:48,382 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp 2023-04-28 05:57:48,382 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:48,382 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:48,383 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:48,383 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/tests 2023-04-28 05:57:48,383 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/templates 2023-04-28 05:57:48,383 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/templates/os6_snmp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/templates 2023-04-28 05:57:48,383 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/vars 2023-04-28 05:57:48,384 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/vars 2023-04-28 05:57:48,384 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/meta 2023-04-28 05:57:48,384 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp/meta 2023-04-28 05:57:48,384 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_snmp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_snmp 2023-04-28 05:57:48,384 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp 2023-04-28 05:57:48,385 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/tasks 2023-04-28 05:57:48,385 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/tasks 2023-04-28 05:57:48,385 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/defaults 2023-04-28 05:57:48,385 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/defaults 2023-04-28 05:57:48,385 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/handlers 2023-04-28 05:57:48,385 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/handlers 2023-04-28 05:57:48,386 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp 2023-04-28 05:57:48,386 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:48,386 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:48,386 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:48,386 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/tests 2023-04-28 05:57:48,387 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/templates 2023-04-28 05:57:48,387 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/templates/os6_ntp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/templates 2023-04-28 05:57:48,387 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/vars 2023-04-28 05:57:48,387 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/vars 2023-04-28 05:57:48,387 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/meta 2023-04-28 05:57:48,387 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp/meta 2023-04-28 05:57:48,388 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_ntp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_ntp 2023-04-28 05:57:48,388 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag 2023-04-28 05:57:48,388 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/tasks 2023-04-28 05:57:48,388 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/tasks 2023-04-28 05:57:48,388 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/defaults 2023-04-28 05:57:48,389 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/defaults 2023-04-28 05:57:48,389 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/handlers 2023-04-28 05:57:48,389 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/handlers 2023-04-28 05:57:48,389 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag 2023-04-28 05:57:48,389 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:48,390 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:48,390 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:48,390 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/tests 2023-04-28 05:57:48,390 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/templates 2023-04-28 05:57:48,390 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/templates/os6_lag.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/templates 2023-04-28 05:57:48,391 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/vars 2023-04-28 05:57:48,391 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/vars 2023-04-28 05:57:48,391 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/meta 2023-04-28 05:57:48,391 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag/meta 2023-04-28 05:57:48,391 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_lag/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_lag 2023-04-28 05:57:48,392 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa 2023-04-28 05:57:48,392 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/tasks 2023-04-28 05:57:48,392 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/tasks 2023-04-28 05:57:48,392 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/defaults 2023-04-28 05:57:48,392 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/defaults 2023-04-28 05:57:48,392 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/handlers 2023-04-28 05:57:48,393 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/handlers 2023-04-28 05:57:48,393 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa 2023-04-28 05:57:48,393 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:48,393 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:48,393 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:48,394 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/tests 2023-04-28 05:57:48,394 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/templates 2023-04-28 05:57:48,394 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/templates/os6_aaa.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/templates 2023-04-28 05:57:48,394 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/vars 2023-04-28 05:57:48,394 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/vars 2023-04-28 05:57:48,395 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/meta 2023-04-28 05:57:48,395 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa/meta 2023-04-28 05:57:48,395 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_aaa/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_aaa 2023-04-28 05:57:48,395 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan 2023-04-28 05:57:48,395 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/tasks 2023-04-28 05:57:48,395 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/tasks 2023-04-28 05:57:48,396 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/defaults 2023-04-28 05:57:48,396 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/defaults 2023-04-28 05:57:48,396 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/handlers 2023-04-28 05:57:48,396 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/handlers 2023-04-28 05:57:48,396 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan 2023-04-28 05:57:48,397 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:48,397 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:48,397 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:48,397 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/tests 2023-04-28 05:57:48,397 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/templates 2023-04-28 05:57:48,398 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/templates/os6_vlan.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/templates 2023-04-28 05:57:48,398 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/vars 2023-04-28 05:57:48,398 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/vars 2023-04-28 05:57:48,398 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/meta 2023-04-28 05:57:48,398 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan/meta 2023-04-28 05:57:48,398 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_vlan/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_vlan 2023-04-28 05:57:48,399 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface 2023-04-28 05:57:48,399 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/tasks 2023-04-28 05:57:48,399 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/tasks 2023-04-28 05:57:48,399 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/defaults 2023-04-28 05:57:48,399 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/defaults 2023-04-28 05:57:48,400 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/handlers 2023-04-28 05:57:48,400 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/handlers 2023-04-28 05:57:48,400 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface 2023-04-28 05:57:48,400 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:48,400 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:48,401 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:48,401 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/tests 2023-04-28 05:57:48,401 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/templates 2023-04-28 05:57:48,401 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/templates/os6_interface.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/templates 2023-04-28 05:57:48,401 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/vars 2023-04-28 05:57:48,402 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/vars 2023-04-28 05:57:48,402 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/meta 2023-04-28 05:57:48,402 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface/meta 2023-04-28 05:57:48,402 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_interface/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_interface 2023-04-28 05:57:48,402 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging 2023-04-28 05:57:48,403 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/tasks 2023-04-28 05:57:48,403 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/tasks 2023-04-28 05:57:48,403 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/defaults 2023-04-28 05:57:48,403 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/defaults 2023-04-28 05:57:48,403 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/handlers 2023-04-28 05:57:48,403 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/handlers 2023-04-28 05:57:48,404 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging 2023-04-28 05:57:48,404 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:48,404 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:48,404 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:48,404 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/tests 2023-04-28 05:57:48,405 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/templates 2023-04-28 05:57:48,405 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/templates/os6_logging.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/templates 2023-04-28 05:57:48,405 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/vars 2023-04-28 05:57:48,405 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/vars 2023-04-28 05:57:48,405 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/meta 2023-04-28 05:57:48,405 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging/meta 2023-04-28 05:57:48,406 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_logging/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_logging 2023-04-28 05:57:48,406 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp 2023-04-28 05:57:48,406 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/tasks 2023-04-28 05:57:48,406 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/tasks 2023-04-28 05:57:48,407 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/defaults 2023-04-28 05:57:48,407 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/defaults 2023-04-28 05:57:48,407 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/handlers 2023-04-28 05:57:48,407 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/handlers 2023-04-28 05:57:48,407 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp 2023-04-28 05:57:48,407 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:48,408 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tests/test.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:48,408 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tests/inventory.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:48,408 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/tests 2023-04-28 05:57:48,408 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/templates 2023-04-28 05:57:48,408 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/templates/os6_xstp.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/templates 2023-04-28 05:57:48,409 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/vars 2023-04-28 05:57:48,409 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/vars 2023-04-28 05:57:48,409 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/meta 2023-04-28 05:57:48,409 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp/meta 2023-04-28 05:57:48,409 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_xstp/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_xstp 2023-04-28 05:57:48,410 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos 2023-04-28 05:57:48,410 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/tasks 2023-04-28 05:57:48,410 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tasks/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/tasks 2023-04-28 05:57:48,410 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/defaults 2023-04-28 05:57:48,410 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/defaults/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/defaults 2023-04-28 05:57:48,410 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/handlers 2023-04-28 05:57:48,411 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/handlers/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/handlers 2023-04-28 05:57:48,411 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos 2023-04-28 05:57:48,411 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:48,411 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tests/inventory -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:48,411 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tests/test.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:48,412 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/tests/main.os6.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/tests 2023-04-28 05:57:48,412 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/templates 2023-04-28 05:57:48,412 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/templates/os6_qos.j2 -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/templates 2023-04-28 05:57:48,412 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/vars 2023-04-28 05:57:48,412 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/vars/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/vars 2023-04-28 05:57:48,413 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/meta 2023-04-28 05:57:48,413 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/meta/main.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos/meta 2023-04-28 05:57:48,413 root INFO copying build/lib/ansible_collections/dellemc/os6/roles/os6_qos/LICENSE -> build/bdist.linux-x86_64/wheel/ansible_collections/dellemc/os6/roles/os6_qos 2023-04-28 05:57:48,413 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io 2023-04-28 05:57:48,413 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:48,414 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:48,414 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins 2023-04-28 05:57:48,414 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/doc_fragments 2023-04-28 05:57:48,414 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/doc_fragments 2023-04-28 05:57:48,414 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/plugins/doc_fragments/exoscale.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/doc_fragments 2023-04-28 05:57:48,415 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:48,415 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/plugins/modules/exo_dns_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:48,415 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:48,415 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/plugins/modules/exo_dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/modules 2023-04-28 05:57:48,415 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/module_utils 2023-04-28 05:57:48,415 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/plugins/module_utils/exoscale.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/plugins/module_utils 2023-04-28 05:57:48,416 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:48,416 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:48,416 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/meta 2023-04-28 05:57:48,416 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/meta 2023-04-28 05:57:48,416 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:48,417 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:48,417 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:48,417 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/changelogs/fragments 2023-04-28 05:57:48,417 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/changelogs/fragments 2023-04-28 05:57:48,417 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:48,418 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale/changelogs 2023-04-28 05:57:48,418 root INFO copying build/lib/ansible_collections/ngine_io/exoscale/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/exoscale 2023-04-28 05:57:48,418 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,418 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,418 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins 2023-04-28 05:57:48,418 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:48,419 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:48,419 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/cloudstack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:48,419 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/cloudstack_environment.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments 2023-04-28 05:57:48,419 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/inventory 2023-04-28 05:57:48,419 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/inventory 2023-04-28 05:57:48,420 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/inventory/instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/inventory 2023-04-28 05:57:48,420 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,420 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_role.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,420 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_configuration.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,420 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_template.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,421 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_affinitygroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,421 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_account.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,421 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,421 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_ip_address.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,421 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_image_store.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,422 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_project.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,422 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_connection.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,422 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_host.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,422 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_loadbalancer_rule_member.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,422 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vlan_ip_range.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,423 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,423 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,423 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,423 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_iso.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,424 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_resourcelimit.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,424 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vmsnapshot.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,424 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_staticnat.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,424 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_customer_gateway.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,424 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_disk_offering.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,425 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_storage_pool.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,425 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_service_offering.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,425 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_offering.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,425 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,425 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_loadbalancer_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,426 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instancegroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,426 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_pod.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,426 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_cluster.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,426 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_nic.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,426 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,427 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_traffic_type.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,427 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,427 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_zone_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,427 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_securitygroup_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,428 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_securitygroup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,428 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_router.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,428 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,428 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_nic_secondaryip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,428 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_sshkeypair.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,429 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_physical_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,429 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_zone.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,429 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_acl.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,429 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_region.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,429 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,430 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,430 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_portforward.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,430 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_acl_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,430 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_snapshot_policy.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,430 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpc_offering.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,431 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_role_permission.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,431 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpc.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,431 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_password_reset.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/modules 2023-04-28 05:57:48,431 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/module_utils 2023-04-28 05:57:48,431 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/plugins/module_utils/cloudstack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/plugins/module_utils 2023-04-28 05:57:48,432 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,432 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,432 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,432 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,433 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/meta 2023-04-28 05:57:48,433 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/meta 2023-04-28 05:57:48,433 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,433 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:48,433 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:48,434 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/changelogs/fragments 2023-04-28 05:57:48,434 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/changelogs/fragments 2023-04-28 05:57:48,434 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:48,434 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/changelogs 2023-04-28 05:57:48,434 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,435 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/scripts 2023-04-28 05:57:48,435 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/scripts/inventory 2023-04-28 05:57:48,435 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/scripts/inventory/cloudstack.ini -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/scripts/inventory 2023-04-28 05:57:48,435 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/scripts/inventory/cloudstack.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack/scripts/inventory 2023-04-28 05:57:48,435 root INFO copying build/lib/ansible_collections/ngine_io/cloudstack/requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/cloudstack 2023-04-28 05:57:48,435 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,436 root INFO copying build/lib/ansible_collections/ngine_io/vultr/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,436 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins 2023-04-28 05:57:48,436 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/doc_fragments 2023-04-28 05:57:48,436 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/doc_fragments/vultr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/doc_fragments 2023-04-28 05:57:48,436 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/doc_fragments 2023-04-28 05:57:48,437 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/inventory 2023-04-28 05:57:48,437 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/inventory/vultr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/inventory 2023-04-28 05:57:48,437 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/inventory 2023-04-28 05:57:48,437 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,437 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_plan_baremetal_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,437 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_os_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,438 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_record.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,438 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_rule.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,438 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_domain_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,438 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_block_storage.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,438 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_block_storage_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,439 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,439 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_startup_script.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,439 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_account_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,439 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_user_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,439 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,440 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_user.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,440 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_server_baremetal.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,440 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_ssh_key_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,440 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,440 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_startup_script_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,441 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,441 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_group_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,441 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_ssh_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,441 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_plan_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,441 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_domain.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,442 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,442 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_region_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,442 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/modules/vultr_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/modules 2023-04-28 05:57:48,442 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/module_utils 2023-04-28 05:57:48,442 root INFO copying build/lib/ansible_collections/ngine_io/vultr/plugins/module_utils/vultr.py -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/plugins/module_utils 2023-04-28 05:57:48,443 root INFO copying build/lib/ansible_collections/ngine_io/vultr/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,443 root INFO copying build/lib/ansible_collections/ngine_io/vultr/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,443 root INFO copying build/lib/ansible_collections/ngine_io/vultr/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,443 root INFO copying build/lib/ansible_collections/ngine_io/vultr/codecov.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,444 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/meta 2023-04-28 05:57:48,444 root INFO copying build/lib/ansible_collections/ngine_io/vultr/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/meta 2023-04-28 05:57:48,444 root INFO copying build/lib/ansible_collections/ngine_io/vultr/CONTRIBUTING.md -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,444 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:48,444 root INFO copying build/lib/ansible_collections/ngine_io/vultr/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:48,445 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/changelogs/fragments 2023-04-28 05:57:48,445 root INFO copying build/lib/ansible_collections/ngine_io/vultr/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/changelogs/fragments 2023-04-28 05:57:48,445 root INFO copying build/lib/ansible_collections/ngine_io/vultr/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:48,445 root INFO copying build/lib/ansible_collections/ngine_io/vultr/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr/changelogs 2023-04-28 05:57:48,445 root INFO copying build/lib/ansible_collections/ngine_io/vultr/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/ngine_io/vultr 2023-04-28 05:57:48,445 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers 2023-04-28 05:57:48,446 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,446 root INFO copying build/lib/ansible_collections/containers/podman/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,446 root INFO copying build/lib/ansible_collections/containers/podman/test-requirements.txt -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,446 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins 2023-04-28 05:57:48,446 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:48,447 root INFO copying build/lib/ansible_collections/containers/podman/plugins/connection/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:48,447 root INFO copying build/lib/ansible_collections/containers/podman/plugins/connection/podman.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:48,447 root INFO copying build/lib/ansible_collections/containers/podman/plugins/connection/buildah.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/connection 2023-04-28 05:57:48,447 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,447 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,448 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_tag.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,448 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_import.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,448 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_pod_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,448 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_container.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,448 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_play.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,449 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_image.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,449 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_login.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,449 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_save.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,449 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_logout.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,449 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,450 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,450 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_volume_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,450 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_load.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,450 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_container_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,450 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_pod.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,451 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,451 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_secret.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,451 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,451 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_generate_systemd.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,451 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_login_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,452 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_export.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,452 root INFO copying build/lib/ansible_collections/containers/podman/plugins/modules/podman_containers.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/modules 2023-04-28 05:57:48,452 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/module_utils 2023-04-28 05:57:48,452 root INFO copying build/lib/ansible_collections/containers/podman/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/module_utils 2023-04-28 05:57:48,452 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:48,453 root INFO copying build/lib/ansible_collections/containers/podman/plugins/module_utils/podman/common.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:48,453 root INFO copying build/lib/ansible_collections/containers/podman/plugins/module_utils/podman/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:48,453 root INFO copying build/lib/ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:48,453 root INFO copying build/lib/ansible_collections/containers/podman/plugins/module_utils/podman/podman_pod_lib.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/module_utils/podman 2023-04-28 05:57:48,454 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/become 2023-04-28 05:57:48,454 root INFO copying build/lib/ansible_collections/containers/podman/plugins/become/podman_unshare.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/plugins/become 2023-04-28 05:57:48,454 root INFO copying build/lib/ansible_collections/containers/podman/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,454 root INFO copying build/lib/ansible_collections/containers/podman/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,454 root INFO copying build/lib/ansible_collections/containers/podman/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,455 root INFO copying build/lib/ansible_collections/containers/podman/setup.cfg -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,455 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/meta 2023-04-28 05:57:48,455 root INFO copying build/lib/ansible_collections/containers/podman/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/meta 2023-04-28 05:57:48,455 root INFO copying build/lib/ansible_collections/containers/podman/SECURITY.md -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,455 root INFO copying build/lib/ansible_collections/containers/podman/CODE-OF-CONDUCT.md -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,456 root INFO copying build/lib/ansible_collections/containers/podman/ansible-collection-containers-podman.spec -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,456 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/changelogs 2023-04-28 05:57:48,456 root INFO copying build/lib/ansible_collections/containers/podman/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/changelogs 2023-04-28 05:57:48,456 root INFO copying build/lib/ansible_collections/containers/podman/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman/changelogs 2023-04-28 05:57:48,456 root INFO copying build/lib/ansible_collections/containers/podman/galaxy.yml.in -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,457 root INFO copying build/lib/ansible_collections/containers/podman/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,457 root INFO copying build/lib/ansible_collections/containers/podman/setup.py -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,457 root INFO copying build/lib/ansible_collections/containers/podman/Makefile -> build/bdist.linux-x86_64/wheel/ansible_collections/containers/podman 2023-04-28 05:57:48,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner 2023-04-28 05:57:48,457 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud 2023-04-28 05:57:48,457 root INFO copying build/lib/ansible_collections/hetzner/hcloud/CHANGELOG.rst -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud 2023-04-28 05:57:48,458 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins 2023-04-28 05:57:48,458 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/doc_fragments 2023-04-28 05:57:48,458 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/doc_fragments/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/doc_fragments 2023-04-28 05:57:48,458 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/doc_fragments/hcloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/doc_fragments 2023-04-28 05:57:48,458 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/inventory 2023-04-28 05:57:48,459 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/inventory/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/inventory 2023-04-28 05:57:48,459 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/inventory/hcloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/inventory 2023-04-28 05:57:48,459 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,459 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_image_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,459 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,460 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,460 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_certificate_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,460 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_location_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,460 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,460 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,461 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_service.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,461 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,461 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_datacenter_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,461 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_primary_ip.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,461 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,462 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,462 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_certificate.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,462 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,462 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,462 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_rdns.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,463 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,463 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,463 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_route.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,463 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_type_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,464 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,464 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_network.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,464 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_target.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,464 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,464 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_datacenter_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,465 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_placement_group.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,465 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,465 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,465 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,465 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_subnetwork.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,466 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_network_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,466 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_image_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,466 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_firewall.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,466 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_location_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,466 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_type_facts.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,467 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key_info.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,467 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/modules 2023-04-28 05:57:48,467 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/module_utils 2023-04-28 05:57:48,467 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/module_utils/__init__.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/module_utils 2023-04-28 05:57:48,467 root INFO copying build/lib/ansible_collections/hetzner/hcloud/plugins/module_utils/hcloud.py -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/plugins/module_utils 2023-04-28 05:57:48,468 root INFO copying build/lib/ansible_collections/hetzner/hcloud/README.md -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud 2023-04-28 05:57:48,468 root INFO copying build/lib/ansible_collections/hetzner/hcloud/FILES.json -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud 2023-04-28 05:57:48,468 root INFO copying build/lib/ansible_collections/hetzner/hcloud/COPYING -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud 2023-04-28 05:57:48,468 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/meta 2023-04-28 05:57:48,468 root INFO copying build/lib/ansible_collections/hetzner/hcloud/meta/runtime.yml -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/meta 2023-04-28 05:57:48,469 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:48,469 root INFO copying build/lib/ansible_collections/hetzner/hcloud/changelogs/.gitignore -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:48,469 root INFO creating build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/changelogs/fragments 2023-04-28 05:57:48,469 root INFO copying build/lib/ansible_collections/hetzner/hcloud/changelogs/fragments/.keep -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/changelogs/fragments 2023-04-28 05:57:48,469 root INFO copying build/lib/ansible_collections/hetzner/hcloud/changelogs/config.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:48,470 root INFO copying build/lib/ansible_collections/hetzner/hcloud/changelogs/changelog.yaml -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud/changelogs 2023-04-28 05:57:48,470 root INFO copying build/lib/ansible_collections/hetzner/hcloud/MANIFEST.json -> build/bdist.linux-x86_64/wheel/ansible_collections/hetzner/hcloud 2023-04-28 05:57:48,471 root INFO running install_egg_info 2023-04-28 05:57:48,475 root INFO Copying ansible.egg-info to build/bdist.linux-x86_64/wheel/ansible-7.5.0-py3.11.egg-info 2023-04-28 05:57:48,479 root INFO running install_scripts 2023-04-28 05:57:48,483 wheel INFO creating build/bdist.linux-x86_64/wheel/ansible-7.5.0.dist-info/WHEEL 2023-04-28 05:57:48,483 wheel INFO creating '/home/buildozer/aports/community/ansible/src/ansible-7.5.0/dist/.tmp-btdpi16j/ansible-7.5.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it 2023-04-28 05:57:48,484 wheel INFO adding 'ansible_collections/ansible_community.py' 2023-04-28 05:57:48,484 wheel INFO adding 'ansible_collections/ansible_release.py' 2023-04-28 05:57:48,484 wheel INFO adding 'ansible_collections/amazon/aws/CHANGELOG.rst' 2023-04-28 05:57:48,485 wheel INFO adding 'ansible_collections/amazon/aws/CONTRIBUTING.md' 2023-04-28 05:57:48,485 wheel INFO adding 'ansible_collections/amazon/aws/COPYING' 2023-04-28 05:57:48,486 wheel INFO adding 'ansible_collections/amazon/aws/FILES.json' 2023-04-28 05:57:48,488 wheel INFO adding 'ansible_collections/amazon/aws/MANIFEST.json' 2023-04-28 05:57:48,488 wheel INFO adding 'ansible_collections/amazon/aws/PSF-license.txt' 2023-04-28 05:57:48,488 wheel INFO adding 'ansible_collections/amazon/aws/README.md' 2023-04-28 05:57:48,488 wheel INFO adding 'ansible_collections/amazon/aws/bindep.txt' 2023-04-28 05:57:48,489 wheel INFO adding 'ansible_collections/amazon/aws/requirements.txt' 2023-04-28 05:57:48,489 wheel INFO adding 'ansible_collections/amazon/aws/test-requirements.txt' 2023-04-28 05:57:48,489 wheel INFO adding 'ansible_collections/amazon/aws/tox.ini' 2023-04-28 05:57:48,490 wheel INFO adding 'ansible_collections/amazon/aws/changelogs/changelog.yaml' 2023-04-28 05:57:48,490 wheel INFO adding 'ansible_collections/amazon/aws/changelogs/config.yaml' 2023-04-28 05:57:48,490 wheel INFO adding 'ansible_collections/amazon/aws/changelogs/fragments/.keep' 2023-04-28 05:57:48,491 wheel INFO adding 'ansible_collections/amazon/aws/meta/runtime.yml' 2023-04-28 05:57:48,491 wheel INFO adding 'ansible_collections/amazon/aws/plugins/action/s3_object.py' 2023-04-28 05:57:48,491 wheel INFO adding 'ansible_collections/amazon/aws/plugins/callback/aws_resource_actions.py' 2023-04-28 05:57:48,492 wheel INFO adding 'ansible_collections/amazon/aws/plugins/doc_fragments/aws.py' 2023-04-28 05:57:48,492 wheel INFO adding 'ansible_collections/amazon/aws/plugins/doc_fragments/aws_credentials.py' 2023-04-28 05:57:48,492 wheel INFO adding 'ansible_collections/amazon/aws/plugins/doc_fragments/aws_region.py' 2023-04-28 05:57:48,492 wheel INFO adding 'ansible_collections/amazon/aws/plugins/doc_fragments/boto3.py' 2023-04-28 05:57:48,492 wheel INFO adding 'ansible_collections/amazon/aws/plugins/doc_fragments/ec2.py' 2023-04-28 05:57:48,493 wheel INFO adding 'ansible_collections/amazon/aws/plugins/doc_fragments/tags.py' 2023-04-28 05:57:48,493 wheel INFO adding 'ansible_collections/amazon/aws/plugins/inventory/aws_ec2.py' 2023-04-28 05:57:48,493 wheel INFO adding 'ansible_collections/amazon/aws/plugins/inventory/aws_rds.py' 2023-04-28 05:57:48,494 wheel INFO adding 'ansible_collections/amazon/aws/plugins/lookup/aws_account_attribute.py' 2023-04-28 05:57:48,494 wheel INFO adding 'ansible_collections/amazon/aws/plugins/lookup/aws_secret.py' 2023-04-28 05:57:48,494 wheel INFO adding 'ansible_collections/amazon/aws/plugins/lookup/aws_service_ip_ranges.py' 2023-04-28 05:57:48,495 wheel INFO adding 'ansible_collections/amazon/aws/plugins/lookup/aws_ssm.py' 2023-04-28 05:57:48,495 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/_version.py' 2023-04-28 05:57:48,495 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/acm.py' 2023-04-28 05:57:48,496 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/arn.py' 2023-04-28 05:57:48,496 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/batch.py' 2023-04-28 05:57:48,496 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/botocore.py' 2023-04-28 05:57:48,496 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/cloud.py' 2023-04-28 05:57:48,497 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/cloudfront_facts.py' 2023-04-28 05:57:48,497 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/core.py' 2023-04-28 05:57:48,497 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/direct_connect.py' 2023-04-28 05:57:48,497 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/ec2.py' 2023-04-28 05:57:48,498 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/elb_utils.py' 2023-04-28 05:57:48,498 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/elbv2.py' 2023-04-28 05:57:48,498 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/iam.py' 2023-04-28 05:57:48,499 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/modules.py' 2023-04-28 05:57:48,499 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/policy.py' 2023-04-28 05:57:48,499 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/rds.py' 2023-04-28 05:57:48,500 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/retries.py' 2023-04-28 05:57:48,500 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/route53.py' 2023-04-28 05:57:48,500 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/s3.py' 2023-04-28 05:57:48,500 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/tagging.py' 2023-04-28 05:57:48,500 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/tower.py' 2023-04-28 05:57:48,501 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/transformation.py' 2023-04-28 05:57:48,501 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/urls.py' 2023-04-28 05:57:48,501 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/version.py' 2023-04-28 05:57:48,501 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/waf.py' 2023-04-28 05:57:48,502 wheel INFO adding 'ansible_collections/amazon/aws/plugins/module_utils/waiters.py' 2023-04-28 05:57:48,502 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/autoscaling_group.py' 2023-04-28 05:57:48,503 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/autoscaling_group_info.py' 2023-04-28 05:57:48,503 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/aws_az_info.py' 2023-04-28 05:57:48,504 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/aws_caller_info.py' 2023-04-28 05:57:48,504 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudformation.py' 2023-04-28 05:57:48,505 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudformation_info.py' 2023-04-28 05:57:48,505 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudtrail.py' 2023-04-28 05:57:48,505 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudtrail_info.py' 2023-04-28 05:57:48,506 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudwatch_metric_alarm.py' 2023-04-28 05:57:48,506 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudwatch_metric_alarm_info.py' 2023-04-28 05:57:48,506 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudwatchevent_rule.py' 2023-04-28 05:57:48,507 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group.py' 2023-04-28 05:57:48,507 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group_info.py' 2023-04-28 05:57:48,507 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/cloudwatchlogs_log_group_metric_filter.py' 2023-04-28 05:57:48,508 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_ami.py' 2023-04-28 05:57:48,508 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_ami_info.py' 2023-04-28 05:57:48,508 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_eip.py' 2023-04-28 05:57:48,509 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_eip_info.py' 2023-04-28 05:57:48,509 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_eni.py' 2023-04-28 05:57:48,509 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_eni_info.py' 2023-04-28 05:57:48,510 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_instance.py' 2023-04-28 05:57:48,510 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_instance_info.py' 2023-04-28 05:57:48,511 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_key.py' 2023-04-28 05:57:48,511 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_metadata_facts.py' 2023-04-28 05:57:48,512 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_security_group.py' 2023-04-28 05:57:48,512 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_security_group_info.py' 2023-04-28 05:57:48,512 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_snapshot.py' 2023-04-28 05:57:48,513 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_snapshot_info.py' 2023-04-28 05:57:48,513 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_spot_instance.py' 2023-04-28 05:57:48,513 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_spot_instance_info.py' 2023-04-28 05:57:48,514 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_tag.py' 2023-04-28 05:57:48,514 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_tag_info.py' 2023-04-28 05:57:48,514 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vol.py' 2023-04-28 05:57:48,514 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vol_info.py' 2023-04-28 05:57:48,515 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_dhcp_option.py' 2023-04-28 05:57:48,515 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_dhcp_option_info.py' 2023-04-28 05:57:48,515 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint.py' 2023-04-28 05:57:48,516 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint_info.py' 2023-04-28 05:57:48,516 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_endpoint_service_info.py' 2023-04-28 05:57:48,516 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_igw.py' 2023-04-28 05:57:48,516 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_igw_info.py' 2023-04-28 05:57:48,517 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_nat_gateway.py' 2023-04-28 05:57:48,517 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_nat_gateway_info.py' 2023-04-28 05:57:48,517 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_net.py' 2023-04-28 05:57:48,518 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_net_info.py' 2023-04-28 05:57:48,518 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_route_table.py' 2023-04-28 05:57:48,518 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_route_table_info.py' 2023-04-28 05:57:48,519 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_subnet.py' 2023-04-28 05:57:48,519 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/ec2_vpc_subnet_info.py' 2023-04-28 05:57:48,519 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/elb_application_lb.py' 2023-04-28 05:57:48,520 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/elb_application_lb_info.py' 2023-04-28 05:57:48,520 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/elb_classic_lb.py' 2023-04-28 05:57:48,521 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/iam_policy.py' 2023-04-28 05:57:48,521 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/iam_policy_info.py' 2023-04-28 05:57:48,521 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/iam_user.py' 2023-04-28 05:57:48,522 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/iam_user_info.py' 2023-04-28 05:57:48,522 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/kms_key.py' 2023-04-28 05:57:48,522 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/kms_key_info.py' 2023-04-28 05:57:48,523 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/lambda.py' 2023-04-28 05:57:48,523 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/lambda_alias.py' 2023-04-28 05:57:48,523 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/lambda_event.py' 2023-04-28 05:57:48,524 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/lambda_execute.py' 2023-04-28 05:57:48,524 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/lambda_info.py' 2023-04-28 05:57:48,524 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/lambda_policy.py' 2023-04-28 05:57:48,525 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_cluster.py' 2023-04-28 05:57:48,525 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_cluster_info.py' 2023-04-28 05:57:48,525 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_cluster_snapshot.py' 2023-04-28 05:57:48,526 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_instance.py' 2023-04-28 05:57:48,526 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_instance_info.py' 2023-04-28 05:57:48,527 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_instance_snapshot.py' 2023-04-28 05:57:48,527 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_option_group.py' 2023-04-28 05:57:48,527 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_option_group_info.py' 2023-04-28 05:57:48,528 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_param_group.py' 2023-04-28 05:57:48,528 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_snapshot_info.py' 2023-04-28 05:57:48,528 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/rds_subnet_group.py' 2023-04-28 05:57:48,529 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/route53.py' 2023-04-28 05:57:48,529 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/route53_health_check.py' 2023-04-28 05:57:48,529 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/route53_info.py' 2023-04-28 05:57:48,530 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/route53_zone.py' 2023-04-28 05:57:48,530 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/s3_bucket.py' 2023-04-28 05:57:48,531 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/s3_object.py' 2023-04-28 05:57:48,531 wheel INFO adding 'ansible_collections/amazon/aws/plugins/modules/s3_object_info.py' 2023-04-28 05:57:48,532 wheel INFO adding 'ansible_collections/ansible/netcommon/CHANGELOG.rst' 2023-04-28 05:57:48,532 wheel INFO adding 'ansible_collections/ansible/netcommon/FILES.json' 2023-04-28 05:57:48,533 wheel INFO adding 'ansible_collections/ansible/netcommon/LICENSE' 2023-04-28 05:57:48,533 wheel INFO adding 'ansible_collections/ansible/netcommon/MANIFEST.json' 2023-04-28 05:57:48,533 wheel INFO adding 'ansible_collections/ansible/netcommon/README.md' 2023-04-28 05:57:48,534 wheel INFO adding 'ansible_collections/ansible/netcommon/bindep.txt' 2023-04-28 05:57:48,534 wheel INFO adding 'ansible_collections/ansible/netcommon/pyproject.toml' 2023-04-28 05:57:48,534 wheel INFO adding 'ansible_collections/ansible/netcommon/requirements.txt' 2023-04-28 05:57:48,534 wheel INFO adding 'ansible_collections/ansible/netcommon/test-requirements.txt' 2023-04-28 05:57:48,534 wheel INFO adding 'ansible_collections/ansible/netcommon/tox.ini' 2023-04-28 05:57:48,535 wheel INFO adding 'ansible_collections/ansible/netcommon/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:48,535 wheel INFO adding 'ansible_collections/ansible/netcommon/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:48,535 wheel INFO adding 'ansible_collections/ansible/netcommon/changelogs/CHANGELOG.rst' 2023-04-28 05:57:48,536 wheel INFO adding 'ansible_collections/ansible/netcommon/changelogs/changelog.yaml' 2023-04-28 05:57:48,536 wheel INFO adding 'ansible_collections/ansible/netcommon/changelogs/config.yaml' 2023-04-28 05:57:48,536 wheel INFO adding 'ansible_collections/ansible/netcommon/changelogs/fragments/.keep' 2023-04-28 05:57:48,537 wheel INFO adding 'ansible_collections/ansible/netcommon/meta/runtime.yml' 2023-04-28 05:57:48,537 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/cli_command.py' 2023-04-28 05:57:48,537 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/cli_config.py' 2023-04-28 05:57:48,537 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/grpc.py' 2023-04-28 05:57:48,538 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/net_get.py' 2023-04-28 05:57:48,538 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/net_ping.py' 2023-04-28 05:57:48,538 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/net_put.py' 2023-04-28 05:57:48,538 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/netconf.py' 2023-04-28 05:57:48,539 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/network.py' 2023-04-28 05:57:48,539 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/network_resource.py' 2023-04-28 05:57:48,539 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/action/telnet.py' 2023-04-28 05:57:48,539 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/become/enable.py' 2023-04-28 05:57:48,540 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/cache/memory.py' 2023-04-28 05:57:48,540 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/connection/grpc.py' 2023-04-28 05:57:48,540 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/connection/httpapi.py' 2023-04-28 05:57:48,540 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/connection/libssh.py' 2023-04-28 05:57:48,541 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/connection/netconf.py' 2023-04-28 05:57:48,541 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/connection/network_cli.py' 2023-04-28 05:57:48,542 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/connection/persistent.py' 2023-04-28 05:57:48,542 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/doc_fragments/connection_persistent.py' 2023-04-28 05:57:48,542 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/doc_fragments/network_agnostic.py' 2023-04-28 05:57:48,542 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/filter/network.py' 2023-04-28 05:57:48,543 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/httpapi/restconf.py' 2023-04-28 05:57:48,543 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/cli_parserbase.py' 2023-04-28 05:57:48,543 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/cli_parsertemplate.py' 2023-04-28 05:57:48,544 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/config.py' 2023-04-28 05:57:48,544 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/netconf.py' 2023-04-28 05:57:48,544 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network.py' 2023-04-28 05:57:48,544 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/network_template.py' 2023-04-28 05:57:48,545 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/parsing.py' 2023-04-28 05:57:48,545 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/resource_module.py' 2023-04-28 05:57:48,545 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/utils.py' 2023-04-28 05:57:48,546 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg/base.py' 2023-04-28 05:57:48,546 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts/facts.py' 2023-04-28 05:57:48,546 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/network_template.py' 2023-04-28 05:57:48,546 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/resource_module.py' 2023-04-28 05:57:48,547 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/resource_module_base.py' 2023-04-28 05:57:48,547 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc/grpc.py' 2023-04-28 05:57:48,547 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf/netconf.py' 2023-04-28 05:57:48,547 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf/restconf.py' 2023-04-28 05:57:48,548 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/module_utils/utils/data.py' 2023-04-28 05:57:48,548 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/cli_command.py' 2023-04-28 05:57:48,548 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/cli_config.py' 2023-04-28 05:57:48,549 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/grpc_config.py' 2023-04-28 05:57:48,549 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/grpc_get.py' 2023-04-28 05:57:48,549 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/net_get.py' 2023-04-28 05:57:48,549 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/net_ping.py' 2023-04-28 05:57:48,550 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/net_put.py' 2023-04-28 05:57:48,550 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/netconf_config.py' 2023-04-28 05:57:48,550 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/netconf_get.py' 2023-04-28 05:57:48,551 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/netconf_rpc.py' 2023-04-28 05:57:48,551 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/network_resource.py' 2023-04-28 05:57:48,551 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/restconf_config.py' 2023-04-28 05:57:48,551 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/restconf_get.py' 2023-04-28 05:57:48,551 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/modules/telnet.py' 2023-04-28 05:57:48,552 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/netconf/default.py' 2023-04-28 05:57:48,552 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/plugin_utils/cliconf_base.py' 2023-04-28 05:57:48,552 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/plugin_utils/connection_base.py' 2023-04-28 05:57:48,553 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/plugin_utils/httpapi_base.py' 2023-04-28 05:57:48,553 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/plugin_utils/netconf_base.py' 2023-04-28 05:57:48,553 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/plugin_utils/terminal_base.py' 2023-04-28 05:57:48,553 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/plugin_utils/version.py' 2023-04-28 05:57:48,554 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/content_templates_parser.py' 2023-04-28 05:57:48,554 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/native_parser.py' 2023-04-28 05:57:48,554 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/ntc_templates_parser.py' 2023-04-28 05:57:48,554 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/pyats_parser.py' 2023-04-28 05:57:48,555 wheel INFO adding 'ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc/base.py' 2023-04-28 05:57:48,555 wheel INFO adding 'ansible_collections/ansible/posix/CHANGELOG.rst' 2023-04-28 05:57:48,555 wheel INFO adding 'ansible_collections/ansible/posix/COPYING' 2023-04-28 05:57:48,556 wheel INFO adding 'ansible_collections/ansible/posix/FILES.json' 2023-04-28 05:57:48,556 wheel INFO adding 'ansible_collections/ansible/posix/MANIFEST.json' 2023-04-28 05:57:48,557 wheel INFO adding 'ansible_collections/ansible/posix/PSF-license.txt' 2023-04-28 05:57:48,557 wheel INFO adding 'ansible_collections/ansible/posix/README.md' 2023-04-28 05:57:48,557 wheel INFO adding 'ansible_collections/ansible/posix/bindep.txt' 2023-04-28 05:57:48,557 wheel INFO adding 'ansible_collections/ansible/posix/codecov.yml' 2023-04-28 05:57:48,557 wheel INFO adding 'ansible_collections/ansible/posix/requirements.txt' 2023-04-28 05:57:48,558 wheel INFO adding 'ansible_collections/ansible/posix/shippable.yml' 2023-04-28 05:57:48,558 wheel INFO adding 'ansible_collections/ansible/posix/test-requirements.txt' 2023-04-28 05:57:48,558 wheel INFO adding 'ansible_collections/ansible/posix/changelogs/changelog.yaml' 2023-04-28 05:57:48,558 wheel INFO adding 'ansible_collections/ansible/posix/changelogs/config.yaml' 2023-04-28 05:57:48,559 wheel INFO adding 'ansible_collections/ansible/posix/changelogs/fragments/.keep' 2023-04-28 05:57:48,559 wheel INFO adding 'ansible_collections/ansible/posix/hacking/cgroup_perf_recap_graph.py' 2023-04-28 05:57:48,559 wheel INFO adding 'ansible_collections/ansible/posix/meta/runtime.yml' 2023-04-28 05:57:48,559 wheel INFO adding 'ansible_collections/ansible/posix/plugins/action/__init__.py' 2023-04-28 05:57:48,560 wheel INFO adding 'ansible_collections/ansible/posix/plugins/action/patch.py' 2023-04-28 05:57:48,560 wheel INFO adding 'ansible_collections/ansible/posix/plugins/action/synchronize.py' 2023-04-28 05:57:48,560 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/__init__.py' 2023-04-28 05:57:48,560 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/cgroup_perf_recap.py' 2023-04-28 05:57:48,561 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/debug.py' 2023-04-28 05:57:48,561 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/json.py' 2023-04-28 05:57:48,561 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/jsonl.py' 2023-04-28 05:57:48,561 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/profile_roles.py' 2023-04-28 05:57:48,562 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/profile_tasks.py' 2023-04-28 05:57:48,562 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/skippy.py' 2023-04-28 05:57:48,562 wheel INFO adding 'ansible_collections/ansible/posix/plugins/callback/timer.py' 2023-04-28 05:57:48,562 wheel INFO adding 'ansible_collections/ansible/posix/plugins/module_utils/__init__.py' 2023-04-28 05:57:48,563 wheel INFO adding 'ansible_collections/ansible/posix/plugins/module_utils/_version.py' 2023-04-28 05:57:48,563 wheel INFO adding 'ansible_collections/ansible/posix/plugins/module_utils/firewalld.py' 2023-04-28 05:57:48,563 wheel INFO adding 'ansible_collections/ansible/posix/plugins/module_utils/mount.py' 2023-04-28 05:57:48,563 wheel INFO adding 'ansible_collections/ansible/posix/plugins/module_utils/version.py' 2023-04-28 05:57:48,564 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/__init__.py' 2023-04-28 05:57:48,564 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/acl.py' 2023-04-28 05:57:48,564 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/at.py' 2023-04-28 05:57:48,564 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/authorized_key.py' 2023-04-28 05:57:48,565 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/firewalld.py' 2023-04-28 05:57:48,565 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/firewalld_info.py' 2023-04-28 05:57:48,566 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/mount.py' 2023-04-28 05:57:48,566 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/patch.py' 2023-04-28 05:57:48,566 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/rhel_facts.py' 2023-04-28 05:57:48,567 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/rhel_rpm_ostree.py' 2023-04-28 05:57:48,567 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/rpm_ostree_upgrade.py' 2023-04-28 05:57:48,567 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/seboolean.py' 2023-04-28 05:57:48,567 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/selinux.py' 2023-04-28 05:57:48,568 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/synchronize.py' 2023-04-28 05:57:48,568 wheel INFO adding 'ansible_collections/ansible/posix/plugins/modules/sysctl.py' 2023-04-28 05:57:48,568 wheel INFO adding 'ansible_collections/ansible/posix/plugins/shell/__init__.py' 2023-04-28 05:57:48,569 wheel INFO adding 'ansible_collections/ansible/posix/plugins/shell/csh.py' 2023-04-28 05:57:48,569 wheel INFO adding 'ansible_collections/ansible/posix/plugins/shell/fish.py' 2023-04-28 05:57:48,569 wheel INFO adding 'ansible_collections/ansible/utils/CHANGELOG.rst' 2023-04-28 05:57:48,570 wheel INFO adding 'ansible_collections/ansible/utils/FILES.json' 2023-04-28 05:57:48,570 wheel INFO adding 'ansible_collections/ansible/utils/LICENSE' 2023-04-28 05:57:48,571 wheel INFO adding 'ansible_collections/ansible/utils/MANIFEST.json' 2023-04-28 05:57:48,571 wheel INFO adding 'ansible_collections/ansible/utils/README.md' 2023-04-28 05:57:48,571 wheel INFO adding 'ansible_collections/ansible/utils/bindep.txt' 2023-04-28 05:57:48,571 wheel INFO adding 'ansible_collections/ansible/utils/pyproject.toml' 2023-04-28 05:57:48,572 wheel INFO adding 'ansible_collections/ansible/utils/requirements.txt' 2023-04-28 05:57:48,572 wheel INFO adding 'ansible_collections/ansible/utils/test-requirements.txt' 2023-04-28 05:57:48,572 wheel INFO adding 'ansible_collections/ansible/utils/tox.ini' 2023-04-28 05:57:48,572 wheel INFO adding 'ansible_collections/ansible/utils/changelogs/changelog.yaml' 2023-04-28 05:57:48,573 wheel INFO adding 'ansible_collections/ansible/utils/changelogs/cli_parse_fix.yaml' 2023-04-28 05:57:48,573 wheel INFO adding 'ansible_collections/ansible/utils/changelogs/config.yaml' 2023-04-28 05:57:48,573 wheel INFO adding 'ansible_collections/ansible/utils/changelogs/fragments/.keep' 2023-04-28 05:57:48,573 wheel INFO adding 'ansible_collections/ansible/utils/meta/runtime.yml' 2023-04-28 05:57:48,574 wheel INFO adding 'ansible_collections/ansible/utils/plugins/action/cli_parse.py' 2023-04-28 05:57:48,574 wheel INFO adding 'ansible_collections/ansible/utils/plugins/action/fact_diff.py' 2023-04-28 05:57:48,574 wheel INFO adding 'ansible_collections/ansible/utils/plugins/action/update_fact.py' 2023-04-28 05:57:48,574 wheel INFO adding 'ansible_collections/ansible/utils/plugins/action/validate.py' 2023-04-28 05:57:48,575 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/cidr_merge.py' 2023-04-28 05:57:48,575 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/consolidate.py' 2023-04-28 05:57:48,576 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/from_xml.py' 2023-04-28 05:57:48,576 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/get_path.py' 2023-04-28 05:57:48,576 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/hwaddr.py' 2023-04-28 05:57:48,576 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/index_of.py' 2023-04-28 05:57:48,577 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/ip4_hex.py' 2023-04-28 05:57:48,577 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/ipaddr.py' 2023-04-28 05:57:48,577 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/ipmath.py' 2023-04-28 05:57:48,577 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/ipsubnet.py' 2023-04-28 05:57:48,578 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/ipv4.py' 2023-04-28 05:57:48,578 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/ipv6.py' 2023-04-28 05:57:48,578 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/ipwrap.py' 2023-04-28 05:57:48,578 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/keep_keys.py' 2023-04-28 05:57:48,579 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/macaddr.py' 2023-04-28 05:57:48,579 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/network_in_network.py' 2023-04-28 05:57:48,579 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/network_in_usable.py' 2023-04-28 05:57:48,579 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/next_nth_usable.py' 2023-04-28 05:57:48,580 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/nthhost.py' 2023-04-28 05:57:48,580 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/param_list_compare.py' 2023-04-28 05:57:48,580 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/previous_nth_usable.py' 2023-04-28 05:57:48,580 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/reduce_on_network.py' 2023-04-28 05:57:48,580 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/remove_keys.py' 2023-04-28 05:57:48,581 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/replace_keys.py' 2023-04-28 05:57:48,581 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/slaac.py' 2023-04-28 05:57:48,581 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/to_paths.py' 2023-04-28 05:57:48,581 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/to_xml.py' 2023-04-28 05:57:48,582 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/usable_range.py' 2023-04-28 05:57:48,582 wheel INFO adding 'ansible_collections/ansible/utils/plugins/filter/validate.py' 2023-04-28 05:57:48,582 wheel INFO adding 'ansible_collections/ansible/utils/plugins/lookup/get_path.py' 2023-04-28 05:57:48,583 wheel INFO adding 'ansible_collections/ansible/utils/plugins/lookup/index_of.py' 2023-04-28 05:57:48,583 wheel INFO adding 'ansible_collections/ansible/utils/plugins/lookup/to_paths.py' 2023-04-28 05:57:48,583 wheel INFO adding 'ansible_collections/ansible/utils/plugins/lookup/validate.py' 2023-04-28 05:57:48,583 wheel INFO adding 'ansible_collections/ansible/utils/plugins/module_utils/common/argspec_validate.py' 2023-04-28 05:57:48,584 wheel INFO adding 'ansible_collections/ansible/utils/plugins/module_utils/common/get_path.py' 2023-04-28 05:57:48,584 wheel INFO adding 'ansible_collections/ansible/utils/plugins/module_utils/common/to_paths.py' 2023-04-28 05:57:48,584 wheel INFO adding 'ansible_collections/ansible/utils/plugins/module_utils/common/utils.py' 2023-04-28 05:57:48,584 wheel INFO adding 'ansible_collections/ansible/utils/plugins/modules/cli_parse.py' 2023-04-28 05:57:48,585 wheel INFO adding 'ansible_collections/ansible/utils/plugins/modules/fact_diff.py' 2023-04-28 05:57:48,585 wheel INFO adding 'ansible_collections/ansible/utils/plugins/modules/update_fact.py' 2023-04-28 05:57:48,585 wheel INFO adding 'ansible_collections/ansible/utils/plugins/modules/validate.py' 2023-04-28 05:57:48,585 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/connection_base.py' 2023-04-28 05:57:48,586 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/consolidate.py' 2023-04-28 05:57:48,586 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/from_xml.py' 2023-04-28 05:57:48,586 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/index_of.py' 2023-04-28 05:57:48,586 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/keep_keys.py' 2023-04-28 05:57:48,587 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/remove_keys.py' 2023-04-28 05:57:48,587 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/replace_keys.py' 2023-04-28 05:57:48,587 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/to_xml.py' 2023-04-28 05:57:48,587 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/base/cli_parser.py' 2023-04-28 05:57:48,587 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/base/fact_diff.py' 2023-04-28 05:57:48,588 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/base/ipaddr_utils.py' 2023-04-28 05:57:48,588 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/base/ipaddress_utils.py' 2023-04-28 05:57:48,588 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/base/utils.py' 2023-04-28 05:57:48,588 wheel INFO adding 'ansible_collections/ansible/utils/plugins/plugin_utils/base/validate.py' 2023-04-28 05:57:48,589 wheel INFO adding 'ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/json_parser.py' 2023-04-28 05:57:48,589 wheel INFO adding 'ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/textfsm_parser.py' 2023-04-28 05:57:48,589 wheel INFO adding 'ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/ttp_parser.py' 2023-04-28 05:57:48,589 wheel INFO adding 'ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/xml_parser.py' 2023-04-28 05:57:48,590 wheel INFO adding 'ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff/native.py' 2023-04-28 05:57:48,590 wheel INFO adding 'ansible_collections/ansible/utils/plugins/sub_plugins/validate/config.py' 2023-04-28 05:57:48,590 wheel INFO adding 'ansible_collections/ansible/utils/plugins/sub_plugins/validate/jsonschema.py' 2023-04-28 05:57:48,591 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/in_any_network.py' 2023-04-28 05:57:48,591 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/in_network.py' 2023-04-28 05:57:48,591 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/in_one_network.py' 2023-04-28 05:57:48,591 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ip.py' 2023-04-28 05:57:48,591 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ip_address.py' 2023-04-28 05:57:48,592 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv4.py' 2023-04-28 05:57:48,592 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv4_address.py' 2023-04-28 05:57:48,592 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv4_hostmask.py' 2023-04-28 05:57:48,592 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv4_netmask.py' 2023-04-28 05:57:48,593 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv6.py' 2023-04-28 05:57:48,593 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv6_address.py' 2023-04-28 05:57:48,593 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv6_ipv4_mapped.py' 2023-04-28 05:57:48,593 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv6_sixtofour.py' 2023-04-28 05:57:48,593 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/ipv6_teredo.py' 2023-04-28 05:57:48,594 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/loopback.py' 2023-04-28 05:57:48,594 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/mac.py' 2023-04-28 05:57:48,594 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/multicast.py' 2023-04-28 05:57:48,594 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/private.py' 2023-04-28 05:57:48,595 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/public.py' 2023-04-28 05:57:48,595 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/reserved.py' 2023-04-28 05:57:48,595 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/resolvable.py' 2023-04-28 05:57:48,595 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/subnet_of.py' 2023-04-28 05:57:48,595 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/supernet_of.py' 2023-04-28 05:57:48,596 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/unspecified.py' 2023-04-28 05:57:48,596 wheel INFO adding 'ansible_collections/ansible/utils/plugins/test/validate.py' 2023-04-28 05:57:48,596 wheel INFO adding 'ansible_collections/ansible/windows/CHANGELOG.rst' 2023-04-28 05:57:48,597 wheel INFO adding 'ansible_collections/ansible/windows/COPYING' 2023-04-28 05:57:48,597 wheel INFO adding 'ansible_collections/ansible/windows/FILES.json' 2023-04-28 05:57:48,598 wheel INFO adding 'ansible_collections/ansible/windows/MANIFEST.json' 2023-04-28 05:57:48,598 wheel INFO adding 'ansible_collections/ansible/windows/README.md' 2023-04-28 05:57:48,599 wheel INFO adding 'ansible_collections/ansible/windows/changelogs/changelog.yaml' 2023-04-28 05:57:48,599 wheel INFO adding 'ansible_collections/ansible/windows/changelogs/config.yaml' 2023-04-28 05:57:48,599 wheel INFO adding 'ansible_collections/ansible/windows/changelogs/fragments/.keep' 2023-04-28 05:57:48,599 wheel INFO adding 'ansible_collections/ansible/windows/meta/runtime.yml' 2023-04-28 05:57:48,600 wheel INFO adding 'ansible_collections/ansible/windows/plugins/action/__init__.py' 2023-04-28 05:57:48,600 wheel INFO adding 'ansible_collections/ansible/windows/plugins/action/win_copy.py' 2023-04-28 05:57:48,600 wheel INFO adding 'ansible_collections/ansible/windows/plugins/action/win_reboot.py' 2023-04-28 05:57:48,601 wheel INFO adding 'ansible_collections/ansible/windows/plugins/action/win_template.py' 2023-04-28 05:57:48,601 wheel INFO adding 'ansible_collections/ansible/windows/plugins/action/win_updates.py' 2023-04-28 05:57:48,602 wheel INFO adding 'ansible_collections/ansible/windows/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:48,602 wheel INFO adding 'ansible_collections/ansible/windows/plugins/doc_fragments/web_request.py' 2023-04-28 05:57:48,602 wheel INFO adding 'ansible_collections/ansible/windows/plugins/filter/__init__.py' 2023-04-28 05:57:48,602 wheel INFO adding 'ansible_collections/ansible/windows/plugins/filter/quote.py' 2023-04-28 05:57:48,603 wheel INFO adding 'ansible_collections/ansible/windows/plugins/filter/quote.yml' 2023-04-28 05:57:48,603 wheel INFO adding 'ansible_collections/ansible/windows/plugins/module_utils/Process.cs' 2023-04-28 05:57:48,603 wheel INFO adding 'ansible_collections/ansible/windows/plugins/module_utils/Process.psm1' 2023-04-28 05:57:48,604 wheel INFO adding 'ansible_collections/ansible/windows/plugins/module_utils/SCManager.cs' 2023-04-28 05:57:48,604 wheel INFO adding 'ansible_collections/ansible/windows/plugins/module_utils/WebRequest.psm1' 2023-04-28 05:57:48,605 wheel INFO adding 'ansible_collections/ansible/windows/plugins/module_utils/__init__.py' 2023-04-28 05:57:48,605 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/__init__.py' 2023-04-28 05:57:48,605 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/async_status.ps1' 2023-04-28 05:57:48,605 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/async_status.yml' 2023-04-28 05:57:48,606 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/setup.ps1' 2023-04-28 05:57:48,606 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/setup.yml' 2023-04-28 05:57:48,606 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/slurp.ps1' 2023-04-28 05:57:48,607 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/slurp.yml' 2023-04-28 05:57:48,607 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_acl.ps1' 2023-04-28 05:57:48,607 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_acl.py' 2023-04-28 05:57:48,607 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_acl_inheritance.ps1' 2023-04-28 05:57:48,607 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_acl_inheritance.py' 2023-04-28 05:57:48,608 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_certificate_store.ps1' 2023-04-28 05:57:48,608 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_certificate_store.py' 2023-04-28 05:57:48,608 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_command.ps1' 2023-04-28 05:57:48,609 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_command.py' 2023-04-28 05:57:48,609 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_copy.ps1' 2023-04-28 05:57:48,609 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_copy.py' 2023-04-28 05:57:48,609 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_dns_client.ps1' 2023-04-28 05:57:48,610 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_dns_client.py' 2023-04-28 05:57:48,610 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_domain.ps1' 2023-04-28 05:57:48,610 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_domain.py' 2023-04-28 05:57:48,610 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_domain_controller.ps1' 2023-04-28 05:57:48,611 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_domain_controller.py' 2023-04-28 05:57:48,611 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_domain_membership.ps1' 2023-04-28 05:57:48,611 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_domain_membership.py' 2023-04-28 05:57:48,612 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_dsc.ps1' 2023-04-28 05:57:48,612 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_dsc.py' 2023-04-28 05:57:48,612 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_environment.ps1' 2023-04-28 05:57:48,612 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_environment.py' 2023-04-28 05:57:48,613 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_feature.ps1' 2023-04-28 05:57:48,613 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_feature.py' 2023-04-28 05:57:48,613 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_file.ps1' 2023-04-28 05:57:48,613 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_file.py' 2023-04-28 05:57:48,614 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_find.ps1' 2023-04-28 05:57:48,614 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_find.py' 2023-04-28 05:57:48,614 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_get_url.ps1' 2023-04-28 05:57:48,614 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_get_url.py' 2023-04-28 05:57:48,615 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_group.ps1' 2023-04-28 05:57:48,615 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_group.py' 2023-04-28 05:57:48,615 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_group_membership.ps1' 2023-04-28 05:57:48,615 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_group_membership.py' 2023-04-28 05:57:48,616 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_hostname.ps1' 2023-04-28 05:57:48,616 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_hostname.py' 2023-04-28 05:57:48,616 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_optional_feature.ps1' 2023-04-28 05:57:48,616 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_optional_feature.py' 2023-04-28 05:57:48,617 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_owner.ps1' 2023-04-28 05:57:48,617 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_owner.py' 2023-04-28 05:57:48,617 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_package.ps1' 2023-04-28 05:57:48,618 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_package.py' 2023-04-28 05:57:48,618 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_path.ps1' 2023-04-28 05:57:48,618 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_path.py' 2023-04-28 05:57:48,618 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_ping.ps1' 2023-04-28 05:57:48,619 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_ping.py' 2023-04-28 05:57:48,619 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_powershell.ps1' 2023-04-28 05:57:48,619 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_powershell.py' 2023-04-28 05:57:48,620 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_reboot.py' 2023-04-28 05:57:48,620 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_reg_stat.ps1' 2023-04-28 05:57:48,620 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_reg_stat.py' 2023-04-28 05:57:48,620 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_regedit.ps1' 2023-04-28 05:57:48,621 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_regedit.py' 2023-04-28 05:57:48,621 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_service.ps1' 2023-04-28 05:57:48,621 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_service.py' 2023-04-28 05:57:48,622 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_service_info.ps1' 2023-04-28 05:57:48,622 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_service_info.py' 2023-04-28 05:57:48,622 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_share.ps1' 2023-04-28 05:57:48,622 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_share.py' 2023-04-28 05:57:48,623 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_shell.ps1' 2023-04-28 05:57:48,623 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_shell.py' 2023-04-28 05:57:48,623 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_stat.ps1' 2023-04-28 05:57:48,624 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_stat.py' 2023-04-28 05:57:48,624 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_tempfile.ps1' 2023-04-28 05:57:48,624 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_tempfile.py' 2023-04-28 05:57:48,624 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_template.py' 2023-04-28 05:57:48,625 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_updates.ps1' 2023-04-28 05:57:48,625 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_updates.py' 2023-04-28 05:57:48,625 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_uri.ps1' 2023-04-28 05:57:48,626 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_uri.py' 2023-04-28 05:57:48,626 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_user.ps1' 2023-04-28 05:57:48,626 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_user.py' 2023-04-28 05:57:48,626 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_user_right.ps1' 2023-04-28 05:57:48,627 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_user_right.py' 2023-04-28 05:57:48,627 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_wait_for.ps1' 2023-04-28 05:57:48,627 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_wait_for.py' 2023-04-28 05:57:48,628 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_whoami.ps1' 2023-04-28 05:57:48,628 wheel INFO adding 'ansible_collections/ansible/windows/plugins/modules/win_whoami.py' 2023-04-28 05:57:48,628 wheel INFO adding 'ansible_collections/ansible/windows/plugins/plugin_utils/__init__.py' 2023-04-28 05:57:48,628 wheel INFO adding 'ansible_collections/ansible/windows/plugins/plugin_utils/_quote.py' 2023-04-28 05:57:48,629 wheel INFO adding 'ansible_collections/ansible/windows/plugins/plugin_utils/_reboot.py' 2023-04-28 05:57:48,629 wheel INFO adding 'ansible_collections/arista/eos/CHANGELOG.rst' 2023-04-28 05:57:48,630 wheel INFO adding 'ansible_collections/arista/eos/FILES.json' 2023-04-28 05:57:48,632 wheel INFO adding 'ansible_collections/arista/eos/LICENSE' 2023-04-28 05:57:48,632 wheel INFO adding 'ansible_collections/arista/eos/MANIFEST.json' 2023-04-28 05:57:48,632 wheel INFO adding 'ansible_collections/arista/eos/README.md' 2023-04-28 05:57:48,633 wheel INFO adding 'ansible_collections/arista/eos/bindep.txt' 2023-04-28 05:57:48,633 wheel INFO adding 'ansible_collections/arista/eos/ignore-2.9.txt' 2023-04-28 05:57:48,633 wheel INFO adding 'ansible_collections/arista/eos/pyproject.toml' 2023-04-28 05:57:48,633 wheel INFO adding 'ansible_collections/arista/eos/requirements.txt' 2023-04-28 05:57:48,634 wheel INFO adding 'ansible_collections/arista/eos/test-requirements.txt' 2023-04-28 05:57:48,634 wheel INFO adding 'ansible_collections/arista/eos/tox.ini' 2023-04-28 05:57:48,634 wheel INFO adding 'ansible_collections/arista/eos/changelogs/changelog.yaml' 2023-04-28 05:57:48,634 wheel INFO adding 'ansible_collections/arista/eos/changelogs/config.yaml' 2023-04-28 05:57:48,635 wheel INFO adding 'ansible_collections/arista/eos/changelogs/fragments/.keep' 2023-04-28 05:57:48,635 wheel INFO adding 'ansible_collections/arista/eos/meta/runtime.yml' 2023-04-28 05:57:48,635 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/__init__.py' 2023-04-28 05:57:48,635 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/acl_interfaces.py' 2023-04-28 05:57:48,636 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/acls.py' 2023-04-28 05:57:48,636 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/banner.py' 2023-04-28 05:57:48,636 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/bgp.py' 2023-04-28 05:57:48,636 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/bgp_address_family.py' 2023-04-28 05:57:48,637 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/bgp_global.py' 2023-04-28 05:57:48,637 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/command.py' 2023-04-28 05:57:48,637 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/config.py' 2023-04-28 05:57:48,637 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/eapi.py' 2023-04-28 05:57:48,637 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/eos.py' 2023-04-28 05:57:48,638 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/facts.py' 2023-04-28 05:57:48,638 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/hostname.py' 2023-04-28 05:57:48,638 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/interface.py' 2023-04-28 05:57:48,638 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/interfaces.py' 2023-04-28 05:57:48,638 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/l2_interface.py' 2023-04-28 05:57:48,639 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/l2_interfaces.py' 2023-04-28 05:57:48,639 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/l3_interface.py' 2023-04-28 05:57:48,639 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/l3_interfaces.py' 2023-04-28 05:57:48,639 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/lacp.py' 2023-04-28 05:57:48,640 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/lacp_interfaces.py' 2023-04-28 05:57:48,640 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/lag_interfaces.py' 2023-04-28 05:57:48,640 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/linkagg.py' 2023-04-28 05:57:48,640 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/lldp.py' 2023-04-28 05:57:48,640 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/lldp_global.py' 2023-04-28 05:57:48,641 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/lldp_interfaces.py' 2023-04-28 05:57:48,641 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/logging.py' 2023-04-28 05:57:48,641 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/logging_global.py' 2023-04-28 05:57:48,641 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/ntp_global.py' 2023-04-28 05:57:48,641 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/ospf_interfaces.py' 2023-04-28 05:57:48,642 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/ospfv2.py' 2023-04-28 05:57:48,642 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/ospfv3.py' 2023-04-28 05:57:48,642 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/prefix_lists.py' 2023-04-28 05:57:48,642 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/route_maps.py' 2023-04-28 05:57:48,643 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/snmp_server.py' 2023-04-28 05:57:48,643 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/static_route.py' 2023-04-28 05:57:48,643 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/static_routes.py' 2023-04-28 05:57:48,643 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/system.py' 2023-04-28 05:57:48,643 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/user.py' 2023-04-28 05:57:48,644 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/vlan.py' 2023-04-28 05:57:48,644 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/vlans.py' 2023-04-28 05:57:48,644 wheel INFO adding 'ansible_collections/arista/eos/plugins/action/vrf.py' 2023-04-28 05:57:48,644 wheel INFO adding 'ansible_collections/arista/eos/plugins/cliconf/__init__.py' 2023-04-28 05:57:48,645 wheel INFO adding 'ansible_collections/arista/eos/plugins/cliconf/eos.py' 2023-04-28 05:57:48,645 wheel INFO adding 'ansible_collections/arista/eos/plugins/filter/__init__.py' 2023-04-28 05:57:48,645 wheel INFO adding 'ansible_collections/arista/eos/plugins/httpapi/__init__.py' 2023-04-28 05:57:48,645 wheel INFO adding 'ansible_collections/arista/eos/plugins/httpapi/eos.py' 2023-04-28 05:57:48,646 wheel INFO adding 'ansible_collections/arista/eos/plugins/inventory/__init__.py' 2023-04-28 05:57:48,646 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/__init__.py' 2023-04-28 05:57:48,646 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:48,646 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/__init__.py' 2023-04-28 05:57:48,647 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/eos.py' 2023-04-28 05:57:48,647 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/__init__.py' 2023-04-28 05:57:48,647 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/__init__.py' 2023-04-28 05:57:48,647 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:48,648 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/__init__.py' 2023-04-28 05:57:48,648 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/acls.py' 2023-04-28 05:57:48,648 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/__init__.py' 2023-04-28 05:57:48,649 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:48,649 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/__init__.py' 2023-04-28 05:57:48,649 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/bgp_global.py' 2023-04-28 05:57:48,650 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/__init__.py' 2023-04-28 05:57:48,650 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/facts.py' 2023-04-28 05:57:48,650 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/__init__.py' 2023-04-28 05:57:48,650 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/hostname.py' 2023-04-28 05:57:48,651 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/__init__.py' 2023-04-28 05:57:48,651 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/interfaces.py' 2023-04-28 05:57:48,651 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/__init__.py' 2023-04-28 05:57:48,651 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:48,651 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/__init__.py' 2023-04-28 05:57:48,652 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:48,652 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/__init__.py' 2023-04-28 05:57:48,652 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/lacp.py' 2023-04-28 05:57:48,652 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/__init__.py' 2023-04-28 05:57:48,653 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:48,653 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/__init__.py' 2023-04-28 05:57:48,653 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:48,653 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/__init__.py' 2023-04-28 05:57:48,654 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/lldp_global.py' 2023-04-28 05:57:48,654 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/__init__.py' 2023-04-28 05:57:48,654 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:48,654 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/__init__.py' 2023-04-28 05:57:48,655 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/logging_global.py' 2023-04-28 05:57:48,655 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/__init__.py' 2023-04-28 05:57:48,655 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/ntp_global.py' 2023-04-28 05:57:48,655 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/__init__.py' 2023-04-28 05:57:48,656 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:48,656 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/__init__.py' 2023-04-28 05:57:48,656 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/ospfv2.py' 2023-04-28 05:57:48,656 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/__init__.py' 2023-04-28 05:57:48,657 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/ospfv3.py' 2023-04-28 05:57:48,657 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/__init__.py' 2023-04-28 05:57:48,657 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/prefix_lists.py' 2023-04-28 05:57:48,658 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/__init__.py' 2023-04-28 05:57:48,658 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/route_maps.py' 2023-04-28 05:57:48,658 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/__init__.py' 2023-04-28 05:57:48,658 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/snmp_server.py' 2023-04-28 05:57:48,659 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/__init__.py' 2023-04-28 05:57:48,659 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/static_routes.py' 2023-04-28 05:57:48,659 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/__init__.py' 2023-04-28 05:57:48,659 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/vlans.py' 2023-04-28 05:57:48,660 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/__init__.py' 2023-04-28 05:57:48,660 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/__init__.py' 2023-04-28 05:57:48,660 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:48,661 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/__init__.py' 2023-04-28 05:57:48,661 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/acls.py' 2023-04-28 05:57:48,661 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/__init__.py' 2023-04-28 05:57:48,661 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:48,662 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/__init__.py' 2023-04-28 05:57:48,662 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/bgp_global.py' 2023-04-28 05:57:48,662 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/__init__.py' 2023-04-28 05:57:48,662 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/hostname.py' 2023-04-28 05:57:48,663 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/__init__.py' 2023-04-28 05:57:48,663 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/interfaces.py' 2023-04-28 05:57:48,663 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/__init__.py' 2023-04-28 05:57:48,664 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:48,664 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/__init__.py' 2023-04-28 05:57:48,664 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:48,664 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/__init__.py' 2023-04-28 05:57:48,665 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/lacp.py' 2023-04-28 05:57:48,665 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/__init__.py' 2023-04-28 05:57:48,665 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:48,665 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/__init__.py' 2023-04-28 05:57:48,666 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:48,666 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/__init__.py' 2023-04-28 05:57:48,666 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/lldp_global.py' 2023-04-28 05:57:48,667 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/__init__.py' 2023-04-28 05:57:48,667 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:48,667 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/__init__.py' 2023-04-28 05:57:48,667 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/logging_global.py' 2023-04-28 05:57:48,668 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/__init__.py' 2023-04-28 05:57:48,668 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/ntp_global.py' 2023-04-28 05:57:48,668 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/__init__.py' 2023-04-28 05:57:48,668 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:48,669 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/__init__.py' 2023-04-28 05:57:48,669 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/ospfv2.py' 2023-04-28 05:57:48,669 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/__init__.py' 2023-04-28 05:57:48,670 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/ospfv3.py' 2023-04-28 05:57:48,670 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/__init__.py' 2023-04-28 05:57:48,670 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/prefix_lists.py' 2023-04-28 05:57:48,670 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/__init__.py' 2023-04-28 05:57:48,671 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/route_maps.py' 2023-04-28 05:57:48,671 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/__init__.py' 2023-04-28 05:57:48,671 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/snmp_server.py' 2023-04-28 05:57:48,671 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/__init__.py' 2023-04-28 05:57:48,672 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/static_routes.py' 2023-04-28 05:57:48,672 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/__init__.py' 2023-04-28 05:57:48,672 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/vlans.py' 2023-04-28 05:57:48,673 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/__init__.py' 2023-04-28 05:57:48,673 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/facts.py' 2023-04-28 05:57:48,673 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/__init__.py' 2023-04-28 05:57:48,673 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:48,674 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/__init__.py' 2023-04-28 05:57:48,674 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/acls.py' 2023-04-28 05:57:48,674 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/__init__.py' 2023-04-28 05:57:48,674 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:48,675 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/__init__.py' 2023-04-28 05:57:48,675 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/bgp_global.py' 2023-04-28 05:57:48,675 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/__init__.py' 2023-04-28 05:57:48,675 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/hostname.py' 2023-04-28 05:57:48,676 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/__init__.py' 2023-04-28 05:57:48,676 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/interfaces.py' 2023-04-28 05:57:48,676 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/__init__.py' 2023-04-28 05:57:48,676 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:48,677 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/__init__.py' 2023-04-28 05:57:48,677 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:48,677 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/__init__.py' 2023-04-28 05:57:48,677 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/lacp.py' 2023-04-28 05:57:48,677 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/__init__.py' 2023-04-28 05:57:48,678 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:48,678 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/__init__.py' 2023-04-28 05:57:48,678 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:48,678 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/__init__.py' 2023-04-28 05:57:48,679 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/base.py' 2023-04-28 05:57:48,679 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/__init__.py' 2023-04-28 05:57:48,679 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/lldp_global.py' 2023-04-28 05:57:48,679 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/__init__.py' 2023-04-28 05:57:48,680 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:48,680 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/__init__.py' 2023-04-28 05:57:48,680 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/logging_global.py' 2023-04-28 05:57:48,680 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/__init__.py' 2023-04-28 05:57:48,681 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/ntp_global.py' 2023-04-28 05:57:48,681 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/__init__.py' 2023-04-28 05:57:48,681 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:48,681 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/__init__.py' 2023-04-28 05:57:48,682 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/ospfv2.py' 2023-04-28 05:57:48,682 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/__init__.py' 2023-04-28 05:57:48,682 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/ospfv3.py' 2023-04-28 05:57:48,683 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/__init__.py' 2023-04-28 05:57:48,683 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/prefix_lists.py' 2023-04-28 05:57:48,683 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/__init__.py' 2023-04-28 05:57:48,683 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/route_maps.py' 2023-04-28 05:57:48,684 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/__init__.py' 2023-04-28 05:57:48,684 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/snmp_server.py' 2023-04-28 05:57:48,684 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/__init__.py' 2023-04-28 05:57:48,684 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/static_routes.py' 2023-04-28 05:57:48,685 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/__init__.py' 2023-04-28 05:57:48,685 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/vlans.py' 2023-04-28 05:57:48,685 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/__init__.py' 2023-04-28 05:57:48,685 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/module.py' 2023-04-28 05:57:48,685 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/providers.py' 2023-04-28 05:57:48,686 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/__init__.py' 2023-04-28 05:57:48,686 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/__init__.py' 2023-04-28 05:57:48,686 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/__init__.py' 2023-04-28 05:57:48,686 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/address_family.py' 2023-04-28 05:57:48,687 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/neighbors.py' 2023-04-28 05:57:48,687 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/process.py' 2023-04-28 05:57:48,687 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/__init__.py' 2023-04-28 05:57:48,687 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/bgp_address_family.py' 2023-04-28 05:57:48,688 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/bgp_global.py' 2023-04-28 05:57:48,689 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/hostname.py' 2023-04-28 05:57:48,689 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/logging_global.py' 2023-04-28 05:57:48,689 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ntp_global.py' 2023-04-28 05:57:48,690 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ospf_interfaces.py' 2023-04-28 05:57:48,690 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/ospfv3.py' 2023-04-28 05:57:48,690 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/prefix_lists.py' 2023-04-28 05:57:48,691 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/route_maps.py' 2023-04-28 05:57:48,691 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/snmp_server.py' 2023-04-28 05:57:48,692 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/__init__.py' 2023-04-28 05:57:48,692 wheel INFO adding 'ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/utils.py' 2023-04-28 05:57:48,692 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/__init__.py' 2023-04-28 05:57:48,693 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_acl_interfaces.py' 2023-04-28 05:57:48,693 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_acls.py' 2023-04-28 05:57:48,693 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_banner.py' 2023-04-28 05:57:48,693 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_bgp.py' 2023-04-28 05:57:48,694 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_bgp_address_family.py' 2023-04-28 05:57:48,694 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_bgp_global.py' 2023-04-28 05:57:48,695 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_command.py' 2023-04-28 05:57:48,695 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_config.py' 2023-04-28 05:57:48,696 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_eapi.py' 2023-04-28 05:57:48,696 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_facts.py' 2023-04-28 05:57:48,696 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_hostname.py' 2023-04-28 05:57:48,697 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_interfaces.py' 2023-04-28 05:57:48,697 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_l2_interfaces.py' 2023-04-28 05:57:48,697 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_l3_interfaces.py' 2023-04-28 05:57:48,697 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_lacp.py' 2023-04-28 05:57:48,698 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_lacp_interfaces.py' 2023-04-28 05:57:48,698 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_lag_interfaces.py' 2023-04-28 05:57:48,698 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_lldp.py' 2023-04-28 05:57:48,698 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_lldp_global.py' 2023-04-28 05:57:48,699 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_lldp_interfaces.py' 2023-04-28 05:57:48,699 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_logging.py' 2023-04-28 05:57:48,699 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_logging_global.py' 2023-04-28 05:57:48,700 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_ntp_global.py' 2023-04-28 05:57:48,700 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_ospf_interfaces.py' 2023-04-28 05:57:48,701 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_ospfv2.py' 2023-04-28 05:57:48,701 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_ospfv3.py' 2023-04-28 05:57:48,702 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_prefix_lists.py' 2023-04-28 05:57:48,702 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_route_maps.py' 2023-04-28 05:57:48,703 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_snmp_server.py' 2023-04-28 05:57:48,703 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_static_routes.py' 2023-04-28 05:57:48,703 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_system.py' 2023-04-28 05:57:48,704 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_user.py' 2023-04-28 05:57:48,704 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_vlans.py' 2023-04-28 05:57:48,704 wheel INFO adding 'ansible_collections/arista/eos/plugins/modules/eos_vrf.py' 2023-04-28 05:57:48,705 wheel INFO adding 'ansible_collections/arista/eos/plugins/terminal/__init__.py' 2023-04-28 05:57:48,705 wheel INFO adding 'ansible_collections/arista/eos/plugins/terminal/eos.py' 2023-04-28 05:57:48,705 wheel INFO adding 'ansible_collections/awx/awx/COPYING' 2023-04-28 05:57:48,706 wheel INFO adding 'ansible_collections/awx/awx/FILES.json' 2023-04-28 05:57:48,706 wheel INFO adding 'ansible_collections/awx/awx/MANIFEST.json' 2023-04-28 05:57:48,706 wheel INFO adding 'ansible_collections/awx/awx/README.md' 2023-04-28 05:57:48,707 wheel INFO adding 'ansible_collections/awx/awx/TESTING.md' 2023-04-28 05:57:48,707 wheel INFO adding 'ansible_collections/awx/awx/bindep.txt' 2023-04-28 05:57:48,707 wheel INFO adding 'ansible_collections/awx/awx/requirements.txt' 2023-04-28 05:57:48,708 wheel INFO adding 'ansible_collections/awx/awx/images/completeness_test_output.png' 2023-04-28 05:57:48,710 wheel INFO adding 'ansible_collections/awx/awx/meta/runtime.yml' 2023-04-28 05:57:48,711 wheel INFO adding 'ansible_collections/awx/awx/plugins/doc_fragments/auth.py' 2023-04-28 05:57:48,711 wheel INFO adding 'ansible_collections/awx/awx/plugins/doc_fragments/auth_legacy.py' 2023-04-28 05:57:48,711 wheel INFO adding 'ansible_collections/awx/awx/plugins/doc_fragments/auth_plugin.py' 2023-04-28 05:57:48,711 wheel INFO adding 'ansible_collections/awx/awx/plugins/inventory/controller.py' 2023-04-28 05:57:48,712 wheel INFO adding 'ansible_collections/awx/awx/plugins/lookup/controller_api.py' 2023-04-28 05:57:48,712 wheel INFO adding 'ansible_collections/awx/awx/plugins/lookup/schedule_rrule.py' 2023-04-28 05:57:48,712 wheel INFO adding 'ansible_collections/awx/awx/plugins/lookup/schedule_rruleset.py' 2023-04-28 05:57:48,712 wheel INFO adding 'ansible_collections/awx/awx/plugins/module_utils/awxkit.py' 2023-04-28 05:57:48,713 wheel INFO adding 'ansible_collections/awx/awx/plugins/module_utils/controller_api.py' 2023-04-28 05:57:48,713 wheel INFO adding 'ansible_collections/awx/awx/plugins/module_utils/tower_legacy.py' 2023-04-28 05:57:48,714 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/__init__.py' 2023-04-28 05:57:48,714 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/ad_hoc_command.py' 2023-04-28 05:57:48,714 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/ad_hoc_command_cancel.py' 2023-04-28 05:57:48,714 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/ad_hoc_command_wait.py' 2023-04-28 05:57:48,714 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/application.py' 2023-04-28 05:57:48,715 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/bulk_host_create.py' 2023-04-28 05:57:48,715 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/bulk_job_launch.py' 2023-04-28 05:57:48,715 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/controller_meta.py' 2023-04-28 05:57:48,715 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/credential.py' 2023-04-28 05:57:48,716 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/credential_input_source.py' 2023-04-28 05:57:48,716 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/credential_type.py' 2023-04-28 05:57:48,716 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/execution_environment.py' 2023-04-28 05:57:48,716 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/export.py' 2023-04-28 05:57:48,717 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/group.py' 2023-04-28 05:57:48,717 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/host.py' 2023-04-28 05:57:48,717 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/import.py' 2023-04-28 05:57:48,717 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/instance.py' 2023-04-28 05:57:48,718 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/instance_group.py' 2023-04-28 05:57:48,718 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/inventory.py' 2023-04-28 05:57:48,718 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/inventory_source.py' 2023-04-28 05:57:48,718 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/inventory_source_update.py' 2023-04-28 05:57:48,719 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/job_cancel.py' 2023-04-28 05:57:48,719 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/job_launch.py' 2023-04-28 05:57:48,719 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/job_list.py' 2023-04-28 05:57:48,719 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/job_template.py' 2023-04-28 05:57:48,720 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/job_wait.py' 2023-04-28 05:57:48,720 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/label.py' 2023-04-28 05:57:48,720 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/license.py' 2023-04-28 05:57:48,720 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/notification_template.py' 2023-04-28 05:57:48,721 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/organization.py' 2023-04-28 05:57:48,721 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/project.py' 2023-04-28 05:57:48,721 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/project_update.py' 2023-04-28 05:57:48,721 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/role.py' 2023-04-28 05:57:48,722 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/schedule.py' 2023-04-28 05:57:48,722 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/settings.py' 2023-04-28 05:57:48,722 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/subscriptions.py' 2023-04-28 05:57:48,723 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/team.py' 2023-04-28 05:57:48,723 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/token.py' 2023-04-28 05:57:48,723 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/user.py' 2023-04-28 05:57:48,723 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/workflow_approval.py' 2023-04-28 05:57:48,724 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/workflow_job_template.py' 2023-04-28 05:57:48,724 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/workflow_job_template_node.py' 2023-04-28 05:57:48,724 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/workflow_launch.py' 2023-04-28 05:57:48,725 wheel INFO adding 'ansible_collections/awx/awx/plugins/modules/workflow_node_wait.py' 2023-04-28 05:57:48,725 wheel INFO adding 'ansible_collections/awx/awx/test/awx/conftest.py' 2023-04-28 05:57:48,725 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_ad_hoc_wait.py' 2023-04-28 05:57:48,725 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_application.py' 2023-04-28 05:57:48,726 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_bulk.py' 2023-04-28 05:57:48,726 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_completeness.py' 2023-04-28 05:57:48,726 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_credential.py' 2023-04-28 05:57:48,726 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_credential_input_source.py' 2023-04-28 05:57:48,727 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_credential_type.py' 2023-04-28 05:57:48,727 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_group.py' 2023-04-28 05:57:48,727 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_instance_group.py' 2023-04-28 05:57:48,727 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_inventory.py' 2023-04-28 05:57:48,728 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_inventory_source.py' 2023-04-28 05:57:48,728 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_job.py' 2023-04-28 05:57:48,728 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_job_template.py' 2023-04-28 05:57:48,728 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_label.py' 2023-04-28 05:57:48,729 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_module_utils.py' 2023-04-28 05:57:48,729 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_notification_template.py' 2023-04-28 05:57:48,729 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_organization.py' 2023-04-28 05:57:48,729 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_project.py' 2023-04-28 05:57:48,729 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_role.py' 2023-04-28 05:57:48,730 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_schedule.py' 2023-04-28 05:57:48,730 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_settings.py' 2023-04-28 05:57:48,730 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_team.py' 2023-04-28 05:57:48,730 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_token.py' 2023-04-28 05:57:48,731 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_user.py' 2023-04-28 05:57:48,731 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_workflow_job_template.py' 2023-04-28 05:57:48,731 wheel INFO adding 'ansible_collections/awx/awx/test/awx/test_workflow_job_template_node.py' 2023-04-28 05:57:48,732 wheel INFO adding 'ansible_collections/azure/azcollection/CHANGELOG.md' 2023-04-28 05:57:48,732 wheel INFO adding 'ansible_collections/azure/azcollection/CONTRIBUTING.md' 2023-04-28 05:57:48,732 wheel INFO adding 'ansible_collections/azure/azcollection/CredScanSuppressions.json' 2023-04-28 05:57:48,733 wheel INFO adding 'ansible_collections/azure/azcollection/FILES.json' 2023-04-28 05:57:48,734 wheel INFO adding 'ansible_collections/azure/azcollection/LICENSE' 2023-04-28 05:57:48,734 wheel INFO adding 'ansible_collections/azure/azcollection/MANIFEST.json' 2023-04-28 05:57:48,735 wheel INFO adding 'ansible_collections/azure/azcollection/README.md' 2023-04-28 05:57:48,735 wheel INFO adding 'ansible_collections/azure/azcollection/ansible.cfg' 2023-04-28 05:57:48,735 wheel INFO adding 'ansible_collections/azure/azcollection/azure-pipelines.yml' 2023-04-28 05:57:48,735 wheel INFO adding 'ansible_collections/azure/azcollection/pr-pipelines.yml' 2023-04-28 05:57:48,736 wheel INFO adding 'ansible_collections/azure/azcollection/release-pipelines.yml' 2023-04-28 05:57:48,736 wheel INFO adding 'ansible_collections/azure/azcollection/requirements-azure.txt' 2023-04-28 05:57:48,736 wheel INFO adding 'ansible_collections/azure/azcollection/sanity-requirements-azure.txt' 2023-04-28 05:57:48,736 wheel INFO adding 'ansible_collections/azure/azcollection/shippable.yml' 2023-04-28 05:57:48,736 wheel INFO adding 'ansible_collections/azure/azcollection/meta/execution-environment.yml' 2023-04-28 05:57:48,737 wheel INFO adding 'ansible_collections/azure/azcollection/meta/runtime.yml' 2023-04-28 05:57:48,737 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/doc_fragments/azure.py' 2023-04-28 05:57:48,737 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/doc_fragments/azure_rm.py' 2023-04-28 05:57:48,738 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/doc_fragments/azure_tags.py' 2023-04-28 05:57:48,738 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/inventory/azure_rm.py' 2023-04-28 05:57:48,738 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/lookup/azure_keyvault_secret.py' 2023-04-28 05:57:48,739 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common.py' 2023-04-28 05:57:48,739 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common_ext.py' 2023-04-28 05:57:48,740 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/module_utils/azure_rm_common_rest.py' 2023-04-28 05:57:48,740 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_account_info.py' 2023-04-28 05:57:48,741 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adapplication.py' 2023-04-28 05:57:48,741 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adapplication_info.py' 2023-04-28 05:57:48,741 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adgroup.py' 2023-04-28 05:57:48,742 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adgroup_info.py' 2023-04-28 05:57:48,742 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adpassword.py' 2023-04-28 05:57:48,742 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adpassword_info.py' 2023-04-28 05:57:48,742 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adserviceprincipal.py' 2023-04-28 05:57:48,743 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_adserviceprincipal_info.py' 2023-04-28 05:57:48,743 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aduser.py' 2023-04-28 05:57:48,743 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aduser_info.py' 2023-04-28 05:57:48,744 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aks.py' 2023-04-28 05:57:48,744 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aks_info.py' 2023-04-28 05:57:48,744 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpool.py' 2023-04-28 05:57:48,745 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpool_info.py' 2023-04-28 05:57:48,745 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksagentpoolversion_info.py' 2023-04-28 05:57:48,745 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksupgrade_info.py' 2023-04-28 05:57:48,745 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_aksversion_info.py' 2023-04-28 05:57:48,746 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagement.py' 2023-04-28 05:57:48,746 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagement_info.py' 2023-04-28 05:57:48,746 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagementservice.py' 2023-04-28 05:57:48,747 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_apimanagementservice_info.py' 2023-04-28 05:57:48,747 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_appgateway.py' 2023-04-28 05:57:48,748 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_appgateway_info.py' 2023-04-28 05:57:48,748 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_applicationsecuritygroup.py' 2023-04-28 05:57:48,748 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_applicationsecuritygroup_info.py' 2023-04-28 05:57:48,749 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_appserviceplan.py' 2023-04-28 05:57:48,749 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_appserviceplan_info.py' 2023-04-28 05:57:48,749 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationaccount.py' 2023-04-28 05:57:48,749 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationaccount_info.py' 2023-04-28 05:57:48,750 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationrunbook.py' 2023-04-28 05:57:48,750 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_automationrunbook_info.py' 2023-04-28 05:57:48,750 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_autoscale.py' 2023-04-28 05:57:48,751 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_autoscale_info.py' 2023-04-28 05:57:48,751 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_availabilityset.py' 2023-04-28 05:57:48,751 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_availabilityset_info.py' 2023-04-28 05:57:48,752 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_azurefirewall.py' 2023-04-28 05:57:48,752 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_azurefirewall_info.py' 2023-04-28 05:57:48,752 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_backupazurevm.py' 2023-04-28 05:57:48,753 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_backupazurevm_info.py' 2023-04-28 05:57:48,753 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_backuppolicy.py' 2023-04-28 05:57:48,753 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_backuppolicy_info.py' 2023-04-28 05:57:48,753 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_bastionhost.py' 2023-04-28 05:57:48,754 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_bastionhost_info.py' 2023-04-28 05:57:48,754 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_batchaccount.py' 2023-04-28 05:57:48,755 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnendpoint.py' 2023-04-28 05:57:48,755 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnendpoint_info.py' 2023-04-28 05:57:48,755 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnprofile.py' 2023-04-28 05:57:48,756 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cdnprofile_info.py' 2023-04-28 05:57:48,756 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cognitivesearch.py' 2023-04-28 05:57:48,756 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cognitivesearch_info.py' 2023-04-28 05:57:48,757 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerinstance.py' 2023-04-28 05:57:48,757 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerinstance_info.py' 2023-04-28 05:57:48,757 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistry.py' 2023-04-28 05:57:48,758 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistry_info.py' 2023-04-28 05:57:48,758 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistryreplication.py' 2023-04-28 05:57:48,758 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistryreplication_info.py' 2023-04-28 05:57:48,758 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrytag.py' 2023-04-28 05:57:48,759 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrytag_info.py' 2023-04-28 05:57:48,759 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrywebhook.py' 2023-04-28 05:57:48,759 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_containerregistrywebhook_info.py' 2023-04-28 05:57:48,759 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cosmosdbaccount.py' 2023-04-28 05:57:48,760 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_cosmosdbaccount_info.py' 2023-04-28 05:57:48,760 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_datafactory.py' 2023-04-28 05:57:48,760 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_datafactory_info.py' 2023-04-28 05:57:48,761 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_datalakestore.py' 2023-04-28 05:57:48,761 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_datalakestore_info.py' 2023-04-28 05:57:48,761 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_ddosprotectionplan.py' 2023-04-28 05:57:48,762 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_ddosprotectionplan_info.py' 2023-04-28 05:57:48,762 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_deployment.py' 2023-04-28 05:57:48,762 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_deployment_info.py' 2023-04-28 05:57:48,763 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlab.py' 2023-04-28 05:57:48,763 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlab_info.py' 2023-04-28 05:57:48,763 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabarmtemplate_info.py' 2023-04-28 05:57:48,764 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifact_info.py' 2023-04-28 05:57:48,764 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifactsource.py' 2023-04-28 05:57:48,764 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabartifactsource_info.py' 2023-04-28 05:57:48,764 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabcustomimage.py' 2023-04-28 05:57:48,765 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabcustomimage_info.py' 2023-04-28 05:57:48,765 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabenvironment.py' 2023-04-28 05:57:48,765 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabenvironment_info.py' 2023-04-28 05:57:48,766 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabpolicy.py' 2023-04-28 05:57:48,766 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabpolicy_info.py' 2023-04-28 05:57:48,766 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabschedule.py' 2023-04-28 05:57:48,766 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabschedule_info.py' 2023-04-28 05:57:48,767 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualmachine.py' 2023-04-28 05:57:48,767 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualmachine_info.py' 2023-04-28 05:57:48,767 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualnetwork.py' 2023-04-28 05:57:48,768 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_devtestlabvirtualnetwork_info.py' 2023-04-28 05:57:48,768 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_diskencryptionset.py' 2023-04-28 05:57:48,768 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_diskencryptionset_info.py' 2023-04-28 05:57:48,768 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnsrecordset.py' 2023-04-28 05:57:48,769 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnsrecordset_info.py' 2023-04-28 05:57:48,770 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnszone.py' 2023-04-28 05:57:48,771 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_dnszone_info.py' 2023-04-28 05:57:48,771 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_eventhub.py' 2023-04-28 05:57:48,771 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_eventhub_info.py' 2023-04-28 05:57:48,771 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_expressroute.py' 2023-04-28 05:57:48,772 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_expressroute_info.py' 2023-04-28 05:57:48,772 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_firewallpolicy.py' 2023-04-28 05:57:48,772 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_firewallpolicy_info.py' 2023-04-28 05:57:48,773 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_functionapp.py' 2023-04-28 05:57:48,773 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_functionapp_info.py' 2023-04-28 05:57:48,773 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_gallery.py' 2023-04-28 05:57:48,773 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_gallery_info.py' 2023-04-28 05:57:48,774 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimage.py' 2023-04-28 05:57:48,774 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimage_info.py' 2023-04-28 05:57:48,774 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimageversion.py' 2023-04-28 05:57:48,775 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_galleryimageversion_info.py' 2023-04-28 05:57:48,775 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_hdinsightcluster.py' 2023-04-28 05:57:48,775 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_hdinsightcluster_info.py' 2023-04-28 05:57:48,776 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_hostgroup.py' 2023-04-28 05:57:48,776 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_hostgroup_info.py' 2023-04-28 05:57:48,776 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_image.py' 2023-04-28 05:57:48,776 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_image_info.py' 2023-04-28 05:57:48,777 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevice.py' 2023-04-28 05:57:48,777 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevice_info.py' 2023-04-28 05:57:48,777 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_iotdevicemodule.py' 2023-04-28 05:57:48,778 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothub.py' 2023-04-28 05:57:48,778 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothub_info.py' 2023-04-28 05:57:48,779 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_iothubconsumergroup.py' 2023-04-28 05:57:48,779 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_ipgroup.py' 2023-04-28 05:57:48,779 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_ipgroup_info.py' 2023-04-28 05:57:48,779 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvault.py' 2023-04-28 05:57:48,780 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvault_info.py' 2023-04-28 05:57:48,780 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultkey.py' 2023-04-28 05:57:48,780 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultkey_info.py' 2023-04-28 05:57:48,781 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultsecret.py' 2023-04-28 05:57:48,781 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_keyvaultsecret_info.py' 2023-04-28 05:57:48,781 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_loadbalancer.py' 2023-04-28 05:57:48,782 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_loadbalancer_info.py' 2023-04-28 05:57:48,782 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_lock.py' 2023-04-28 05:57:48,782 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_lock_info.py' 2023-04-28 05:57:48,782 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_loganalyticsworkspace.py' 2023-04-28 05:57:48,783 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_loganalyticsworkspace_info.py' 2023-04-28 05:57:48,783 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_manageddisk.py' 2023-04-28 05:57:48,783 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_manageddisk_info.py' 2023-04-28 05:57:48,784 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_managementgroup.py' 2023-04-28 05:57:48,784 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_managementgroup_info.py' 2023-04-28 05:57:48,784 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbconfiguration.py' 2023-04-28 05:57:48,785 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbconfiguration_info.py' 2023-04-28 05:57:48,785 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbdatabase.py' 2023-04-28 05:57:48,785 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbdatabase_info.py' 2023-04-28 05:57:48,785 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbfirewallrule.py' 2023-04-28 05:57:48,786 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbfirewallrule_info.py' 2023-04-28 05:57:48,786 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbserver.py' 2023-04-28 05:57:48,786 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mariadbserver_info.py' 2023-04-28 05:57:48,787 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitordiagnosticsetting.py' 2023-04-28 05:57:48,787 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitordiagnosticsetting_info.py' 2023-04-28 05:57:48,787 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_monitorlogprofile.py' 2023-04-28 05:57:48,788 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_multiplemanageddisks.py' 2023-04-28 05:57:48,788 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlconfiguration.py' 2023-04-28 05:57:48,788 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlconfiguration_info.py' 2023-04-28 05:57:48,788 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqldatabase.py' 2023-04-28 05:57:48,789 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqldatabase_info.py' 2023-04-28 05:57:48,789 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlfirewallrule.py' 2023-04-28 05:57:48,789 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlfirewallrule_info.py' 2023-04-28 05:57:48,789 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlserver.py' 2023-04-28 05:57:48,790 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_mysqlserver_info.py' 2023-04-28 05:57:48,790 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_natgateway.py' 2023-04-28 05:57:48,790 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_natgateway_info.py' 2023-04-28 05:57:48,791 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_networkinterface.py' 2023-04-28 05:57:48,791 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_networkinterface_info.py' 2023-04-28 05:57:48,792 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_notificationhub.py' 2023-04-28 05:57:48,792 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_notificationhub_info.py' 2023-04-28 05:57:48,792 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_openshiftmanagedcluster.py' 2023-04-28 05:57:48,793 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_openshiftmanagedcluster_info.py' 2023-04-28 05:57:48,793 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlconfiguration.py' 2023-04-28 05:57:48,793 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlconfiguration_info.py' 2023-04-28 05:57:48,793 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqldatabase.py' 2023-04-28 05:57:48,794 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqldatabase_info.py' 2023-04-28 05:57:48,794 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlfirewallrule.py' 2023-04-28 05:57:48,794 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlfirewallrule_info.py' 2023-04-28 05:57:48,794 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlserver.py' 2023-04-28 05:57:48,795 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_postgresqlserver_info.py' 2023-04-28 05:57:48,795 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednsrecordset.py' 2023-04-28 05:57:48,795 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednsrecordset_info.py' 2023-04-28 05:57:48,796 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszone.py' 2023-04-28 05:57:48,796 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszone_info.py' 2023-04-28 05:57:48,796 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszonelink.py' 2023-04-28 05:57:48,796 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatednszonelink_info.py' 2023-04-28 05:57:48,797 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpoint.py' 2023-04-28 05:57:48,797 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpoint_info.py' 2023-04-28 05:57:48,797 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointconnection.py' 2023-04-28 05:57:48,797 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointconnection_info.py' 2023-04-28 05:57:48,798 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointdnszonegroup.py' 2023-04-28 05:57:48,798 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privateendpointdnszonegroup_info.py' 2023-04-28 05:57:48,798 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatelinkservice.py' 2023-04-28 05:57:48,799 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_privatelinkservice_info.py' 2023-04-28 05:57:48,799 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_proximityplacementgroup.py' 2023-04-28 05:57:48,799 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_proximityplacementgroup_info.py' 2023-04-28 05:57:48,800 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_publicipaddress.py' 2023-04-28 05:57:48,800 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_publicipaddress_info.py' 2023-04-28 05:57:48,800 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_recoveryservicesvault.py' 2023-04-28 05:57:48,800 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_recoveryservicesvault_info.py' 2023-04-28 05:57:48,801 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscache.py' 2023-04-28 05:57:48,801 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscache_info.py' 2023-04-28 05:57:48,801 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_rediscachefirewallrule.py' 2023-04-28 05:57:48,802 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationassignment.py' 2023-04-28 05:57:48,802 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationassignment_info.py' 2023-04-28 05:57:48,802 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationdefinition.py' 2023-04-28 05:57:48,802 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_registrationdefinition_info.py' 2023-04-28 05:57:48,803 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_resource.py' 2023-04-28 05:57:48,803 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_resource_info.py' 2023-04-28 05:57:48,803 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_resourcegroup.py' 2023-04-28 05:57:48,804 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_resourcegroup_info.py' 2023-04-28 05:57:48,804 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_roleassignment.py' 2023-04-28 05:57:48,804 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_roleassignment_info.py' 2023-04-28 05:57:48,804 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_roledefinition.py' 2023-04-28 05:57:48,805 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_roledefinition_info.py' 2023-04-28 05:57:48,805 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_route.py' 2023-04-28 05:57:48,805 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_route_info.py' 2023-04-28 05:57:48,806 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_routetable.py' 2023-04-28 05:57:48,806 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_routetable_info.py' 2023-04-28 05:57:48,806 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_securitygroup.py' 2023-04-28 05:57:48,807 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_securitygroup_info.py' 2023-04-28 05:57:48,807 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebus.py' 2023-04-28 05:57:48,807 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebus_info.py' 2023-04-28 05:57:48,807 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebusqueue.py' 2023-04-28 05:57:48,808 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebussaspolicy.py' 2023-04-28 05:57:48,808 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebustopic.py' 2023-04-28 05:57:48,808 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_servicebustopicsubscription.py' 2023-04-28 05:57:48,809 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_snapshot.py' 2023-04-28 05:57:48,809 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqldatabase.py' 2023-04-28 05:57:48,809 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqldatabase_info.py' 2023-04-28 05:57:48,810 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlelasticpool.py' 2023-04-28 05:57:48,810 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlelasticpool_info.py' 2023-04-28 05:57:48,810 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlfirewallrule.py' 2023-04-28 05:57:48,810 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlfirewallrule_info.py' 2023-04-28 05:57:48,811 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlmanagedinstance.py' 2023-04-28 05:57:48,811 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlmanagedinstance_info.py' 2023-04-28 05:57:48,811 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlserver.py' 2023-04-28 05:57:48,812 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_sqlserver_info.py' 2023-04-28 05:57:48,812 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageaccount.py' 2023-04-28 05:57:48,813 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageaccount_info.py' 2023-04-28 05:57:48,813 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageblob.py' 2023-04-28 05:57:48,813 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageshare.py' 2023-04-28 05:57:48,814 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_storageshare_info.py' 2023-04-28 05:57:48,814 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_subnet.py' 2023-04-28 05:57:48,814 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_subnet_info.py' 2023-04-28 05:57:48,815 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_subscription_info.py' 2023-04-28 05:57:48,815 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanager.py' 2023-04-28 05:57:48,815 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerendpoint.py' 2023-04-28 05:57:48,816 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerendpoint_info.py' 2023-04-28 05:57:48,816 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerprofile.py' 2023-04-28 05:57:48,816 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_trafficmanagerprofile_info.py' 2023-04-28 05:57:48,817 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhub.py' 2023-04-28 05:57:48,817 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhub_info.py' 2023-04-28 05:57:48,817 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhubconnection.py' 2023-04-28 05:57:48,818 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualhubconnection_info.py' 2023-04-28 05:57:48,818 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachine.py' 2023-04-28 05:57:48,819 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachine_info.py' 2023-04-28 05:57:48,819 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineextension.py' 2023-04-28 05:57:48,820 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineextension_info.py' 2023-04-28 05:57:48,820 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachineimage_info.py' 2023-04-28 05:57:48,820 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescaleset.py' 2023-04-28 05:57:48,821 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescaleset_info.py' 2023-04-28 05:57:48,821 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetextension.py' 2023-04-28 05:57:48,821 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetextension_info.py' 2023-04-28 05:57:48,822 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetinstance.py' 2023-04-28 05:57:48,822 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinescalesetinstance_info.py' 2023-04-28 05:57:48,822 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualmachinesize_info.py' 2023-04-28 05:57:48,823 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork.py' 2023-04-28 05:57:48,823 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetwork_info.py' 2023-04-28 05:57:48,823 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkgateway.py' 2023-04-28 05:57:48,823 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkpeering.py' 2023-04-28 05:57:48,824 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualnetworkpeering_info.py' 2023-04-28 05:57:48,824 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualwan.py' 2023-04-28 05:57:48,824 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_virtualwan_info.py' 2023-04-28 05:57:48,825 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_vmbackuppolicy.py' 2023-04-28 05:57:48,825 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_vmbackuppolicy_info.py' 2023-04-28 05:57:48,825 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsite.py' 2023-04-28 05:57:48,826 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsite_info.py' 2023-04-28 05:57:48,826 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_vpnsitelink_info.py' 2023-04-28 05:57:48,826 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_webapp.py' 2023-04-28 05:57:48,827 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_webapp_info.py' 2023-04-28 05:57:48,827 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappaccessrestriction.py' 2023-04-28 05:57:48,827 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappaccessrestriction_info.py' 2023-04-28 05:57:48,828 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappslot.py' 2023-04-28 05:57:48,828 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappvnetconnection.py' 2023-04-28 05:57:48,828 wheel INFO adding 'ansible_collections/azure/azcollection/plugins/modules/azure_rm_webappvnetconnection_info.py' 2023-04-28 05:57:48,829 wheel INFO adding 'ansible_collections/check_point/mgmt/CHANGELOG.rst' 2023-04-28 05:57:48,829 wheel INFO adding 'ansible_collections/check_point/mgmt/FILES.json' 2023-04-28 05:57:48,830 wheel INFO adding 'ansible_collections/check_point/mgmt/MANIFEST.json' 2023-04-28 05:57:48,830 wheel INFO adding 'ansible_collections/check_point/mgmt/README.md' 2023-04-28 05:57:48,830 wheel INFO adding 'ansible_collections/check_point/mgmt/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:48,831 wheel INFO adding 'ansible_collections/check_point/mgmt/changelogs/changelog.yaml' 2023-04-28 05:57:48,831 wheel INFO adding 'ansible_collections/check_point/mgmt/changelogs/config.yaml' 2023-04-28 05:57:48,831 wheel INFO adding 'ansible_collections/check_point/mgmt/meta/execution-environment.yml' 2023-04-28 05:57:48,832 wheel INFO adding 'ansible_collections/check_point/mgmt/meta/runtime.yml' 2023-04-28 05:57:48,832 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/action/cp_mgmt_access_rules.py' 2023-04-28 05:57:48,832 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_commands.py' 2023-04-28 05:57:48,832 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_facts.py' 2023-04-28 05:57:48,833 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_objects.py' 2023-04-28 05:57:48,833 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/doc_fragments/checkpoint_objects_action_module.py' 2023-04-28 05:57:48,833 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/httpapi/checkpoint.py' 2023-04-28 05:57:48,833 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/module_utils/checkpoint.py' 2023-04-28 05:57:48,834 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_layer.py' 2023-04-28 05:57:48,834 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_layer_facts.py' 2023-04-28 05:57:48,835 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_role.py' 2023-04-28 05:57:48,835 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_role_facts.py' 2023-04-28 05:57:48,835 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rule.py' 2023-04-28 05:57:48,835 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rule_facts.py' 2023-04-28 05:57:48,836 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_rules.py' 2023-04-28 05:57:48,836 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_access_section.py' 2023-04-28 05:57:48,836 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_api_key.py' 2023-04-28 05:57:48,836 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_data_center_object.py' 2023-04-28 05:57:48,837 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_domain.py' 2023-04-28 05:57:48,837 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_nat_rule.py' 2023-04-28 05:57:48,837 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_add_rules_batch.py' 2023-04-28 05:57:48,837 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_address_range.py' 2023-04-28 05:57:48,838 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_address_range_facts.py' 2023-04-28 05:57:48,838 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_administrator.py' 2023-04-28 05:57:48,838 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_administrator_facts.py' 2023-04-28 05:57:48,838 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site.py' 2023-04-28 05:57:48,839 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_category.py' 2023-04-28 05:57:48,839 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_category_facts.py' 2023-04-28 05:57:48,839 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_facts.py' 2023-04-28 05:57:48,839 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_group.py' 2023-04-28 05:57:48,840 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_application_site_group_facts.py' 2023-04-28 05:57:48,840 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_approve_session.py' 2023-04-28 05:57:48,840 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_assign_global_assignment.py' 2023-04-28 05:57:48,840 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_check_network_feed.py' 2023-04-28 05:57:48,840 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_check_threat_ioc_feed.py' 2023-04-28 05:57:48,841 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_cluster_members_facts.py' 2023-04-28 05:57:48,841 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_connect_cloud_services.py' 2023-04-28 05:57:48,841 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_data_center_object_facts.py' 2023-04-28 05:57:48,841 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_api_key.py' 2023-04-28 05:57:48,842 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_data_center_object.py' 2023-04-28 05:57:48,842 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_domain.py' 2023-04-28 05:57:48,842 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_nat_rule.py' 2023-04-28 05:57:48,842 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_delete_rules_batch.py' 2023-04-28 05:57:48,843 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_discard.py' 2023-04-28 05:57:48,843 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_disconnect_cloud_services.py' 2023-04-28 05:57:48,843 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dns_domain.py' 2023-04-28 05:57:48,843 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dns_domain_facts.py' 2023-04-28 05:57:48,843 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_facts.py' 2023-04-28 05:57:48,844 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_permissions_profile.py' 2023-04-28 05:57:48,844 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_domain_permissions_profile_facts.py' 2023-04-28 05:57:48,844 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dynamic_object.py' 2023-04-28 05:57:48,845 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_dynamic_object_facts.py' 2023-04-28 05:57:48,845 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_exception_group.py' 2023-04-28 05:57:48,845 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_exception_group_facts.py' 2023-04-28 05:57:48,845 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_get_platform.py' 2023-04-28 05:57:48,846 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_global_assignment.py' 2023-04-28 05:57:48,846 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_global_assignment_facts.py' 2023-04-28 05:57:48,846 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group.py' 2023-04-28 05:57:48,846 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_facts.py' 2023-04-28 05:57:48,846 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_with_exclusion.py' 2023-04-28 05:57:48,847 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_group_with_exclusion_facts.py' 2023-04-28 05:57:48,847 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_host.py' 2023-04-28 05:57:48,847 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_host_facts.py' 2023-04-28 05:57:48,847 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_https_section.py' 2023-04-28 05:57:48,848 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_identity_tag.py' 2023-04-28 05:57:48,848 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_identity_tag_facts.py' 2023-04-28 05:57:48,848 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_administrator_group.py' 2023-04-28 05:57:48,848 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_administrator_group_facts.py' 2023-04-28 05:57:48,849 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_idp_to_domain_assignment_facts.py' 2023-04-28 05:57:48,849 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_database.py' 2023-04-28 05:57:48,849 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_lsm_policy.py' 2023-04-28 05:57:48,849 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_lsm_settings.py' 2023-04-28 05:57:48,850 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_policy.py' 2023-04-28 05:57:48,850 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_install_software_package.py' 2023-04-28 05:57:48,850 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_interoperable_device.py' 2023-04-28 05:57:48,850 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_interoperable_device_facts.py' 2023-04-28 05:57:48,851 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster.py' 2023-04-28 05:57:48,851 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster_facts.py' 2023-04-28 05:57:48,851 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_cluster_profile_facts.py' 2023-04-28 05:57:48,851 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway.py' 2023-04-28 05:57:48,852 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway_facts.py' 2023-04-28 05:57:48,852 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_gateway_profile_facts.py' 2023-04-28 05:57:48,852 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_lsm_run_script.py' 2023-04-28 05:57:48,852 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_md_permissions_profile.py' 2023-04-28 05:57:48,853 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_md_permissions_profile_facts.py' 2023-04-28 05:57:48,853 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_mds.py' 2023-04-28 05:57:48,853 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_mds_facts.py' 2023-04-28 05:57:48,853 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_multicast_address_range.py' 2023-04-28 05:57:48,854 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_multicast_address_range_facts.py' 2023-04-28 05:57:48,854 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_nat_rule_facts.py' 2023-04-28 05:57:48,854 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_nat_section.py' 2023-04-28 05:57:48,854 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network.py' 2023-04-28 05:57:48,854 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_facts.py' 2023-04-28 05:57:48,855 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_feed.py' 2023-04-28 05:57:48,855 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_network_feed_facts.py' 2023-04-28 05:57:48,855 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_objects_facts.py' 2023-04-28 05:57:48,855 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_package.py' 2023-04-28 05:57:48,856 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_package_facts.py' 2023-04-28 05:57:48,856 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_provisioning_profile_facts.py' 2023-04-28 05:57:48,856 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_publish.py' 2023-04-28 05:57:48,856 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_put_file.py' 2023-04-28 05:57:48,857 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_reject_session.py' 2023-04-28 05:57:48,857 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_repository_script.py' 2023-04-28 05:57:48,857 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_repository_script_facts.py' 2023-04-28 05:57:48,857 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_reset_sic.py' 2023-04-28 05:57:48,858 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_run_ips_update.py' 2023-04-28 05:57:48,858 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_run_script.py' 2023-04-28 05:57:48,858 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_security_zone.py' 2023-04-28 05:57:48,858 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_security_zone_facts.py' 2023-04-28 05:57:48,858 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_dce_rpc.py' 2023-04-28 05:57:48,859 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_dce_rpc_facts.py' 2023-04-28 05:57:48,859 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_group.py' 2023-04-28 05:57:48,859 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_group_facts.py' 2023-04-28 05:57:48,859 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp.py' 2023-04-28 05:57:48,860 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp6.py' 2023-04-28 05:57:48,860 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp6_facts.py' 2023-04-28 05:57:48,860 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_icmp_facts.py' 2023-04-28 05:57:48,860 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_other.py' 2023-04-28 05:57:48,861 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_other_facts.py' 2023-04-28 05:57:48,861 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_rpc.py' 2023-04-28 05:57:48,861 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_rpc_facts.py' 2023-04-28 05:57:48,861 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_sctp.py' 2023-04-28 05:57:48,862 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_sctp_facts.py' 2023-04-28 05:57:48,862 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_tcp.py' 2023-04-28 05:57:48,862 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_tcp_facts.py' 2023-04-28 05:57:48,862 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_udp.py' 2023-04-28 05:57:48,863 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_service_udp_facts.py' 2023-04-28 05:57:48,863 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_session_facts.py' 2023-04-28 05:57:48,863 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_domain.py' 2023-04-28 05:57:48,864 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_global_properties.py' 2023-04-28 05:57:48,864 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_idp_default_assignment.py' 2023-04-28 05:57:48,865 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_idp_to_domain_assignment.py' 2023-04-28 05:57:48,865 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_nat_rule.py' 2023-04-28 05:57:48,865 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_session.py' 2023-04-28 05:57:48,865 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_set_threat_advanced_settings.py' 2023-04-28 05:57:48,866 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_access_section.py' 2023-04-28 05:57:48,866 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_cloud_services.py' 2023-04-28 05:57:48,866 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_global_properties.py' 2023-04-28 05:57:48,866 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_https_section.py' 2023-04-28 05:57:48,866 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_idp_default_assignment.py' 2023-04-28 05:57:48,867 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_logs.py' 2023-04-28 05:57:48,867 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_nat_section.py' 2023-04-28 05:57:48,867 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_servers_and_processes.py' 2023-04-28 05:57:48,867 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_software_package_details.py' 2023-04-28 05:57:48,868 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_task.py' 2023-04-28 05:57:48,868 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_tasks.py' 2023-04-28 05:57:48,868 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_show_threat_advanced_settings.py' 2023-04-28 05:57:48,868 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_cluster.py' 2023-04-28 05:57:48,869 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_cluster_facts.py' 2023-04-28 05:57:48,878 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_gateway.py' 2023-04-28 05:57:48,878 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_simple_gateway_facts.py' 2023-04-28 05:57:48,878 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_smtp_server.py' 2023-04-28 05:57:48,878 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_smtp_server_facts.py' 2023-04-28 05:57:48,879 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_submit_session.py' 2023-04-28 05:57:48,879 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_tag.py' 2023-04-28 05:57:48,880 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_tag_facts.py' 2023-04-28 05:57:48,880 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_test_sic_status.py' 2023-04-28 05:57:48,880 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_exception.py' 2023-04-28 05:57:48,880 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_exception_facts.py' 2023-04-28 05:57:48,881 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_indicator.py' 2023-04-28 05:57:48,881 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_indicator_facts.py' 2023-04-28 05:57:48,881 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_layer.py' 2023-04-28 05:57:48,881 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_layer_facts.py' 2023-04-28 05:57:48,882 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_profile.py' 2023-04-28 05:57:48,882 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_profile_facts.py' 2023-04-28 05:57:48,882 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_protection_override.py' 2023-04-28 05:57:48,882 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_rule.py' 2023-04-28 05:57:48,883 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_threat_rule_facts.py' 2023-04-28 05:57:48,883 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_time.py' 2023-04-28 05:57:48,883 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_time_facts.py' 2023-04-28 05:57:48,883 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_trusted_client.py' 2023-04-28 05:57:48,884 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_trusted_client_facts.py' 2023-04-28 05:57:48,884 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_uninstall_software_package.py' 2023-04-28 05:57:48,884 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_update_provisioned_satellites.py' 2023-04-28 05:57:48,884 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_verify_policy.py' 2023-04-28 05:57:48,885 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_verify_software_package.py' 2023-04-28 05:57:48,885 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_meshed.py' 2023-04-28 05:57:48,885 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_meshed_facts.py' 2023-04-28 05:57:48,885 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_star.py' 2023-04-28 05:57:48,886 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_vpn_community_star_facts.py' 2023-04-28 05:57:48,886 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_wildcard.py' 2023-04-28 05:57:48,886 wheel INFO adding 'ansible_collections/check_point/mgmt/plugins/modules/cp_mgmt_wildcard_facts.py' 2023-04-28 05:57:48,886 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/FILES.json' 2023-04-28 05:57:48,887 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/LICENSE' 2023-04-28 05:57:48,887 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/MANIFEST.json' 2023-04-28 05:57:48,887 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/README.md' 2023-04-28 05:57:48,888 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/requirements.txt' 2023-04-28 05:57:48,888 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:48,888 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/changelogs/changelog.yaml' 2023-04-28 05:57:48,888 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/changelogs/config.yaml' 2023-04-28 05:57:48,889 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/meta/runtime.yml' 2023-04-28 05:57:48,889 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/README.md' 2023-04-28 05:57:48,889 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/module_utils/Common.psm1' 2023-04-28 05:57:48,889 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/module_utils/Config.psm1' 2023-04-28 05:57:48,890 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/module_utils/Features.psm1' 2023-04-28 05:57:48,890 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/module_utils/Packages.psm1' 2023-04-28 05:57:48,890 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/module_utils/Sources.psm1' 2023-04-28 05:57:48,891 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey.ps1' 2023-04-28 05:57:48,891 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey.py' 2023-04-28 05:57:48,891 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_config.ps1' 2023-04-28 05:57:48,892 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_config.py' 2023-04-28 05:57:48,892 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_facts.ps1' 2023-04-28 05:57:48,892 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_facts.py' 2023-04-28 05:57:48,892 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_feature.ps1' 2023-04-28 05:57:48,893 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_feature.py' 2023-04-28 05:57:48,893 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_source.ps1' 2023-04-28 05:57:48,893 wheel INFO adding 'ansible_collections/chocolatey/chocolatey/plugins/modules/win_chocolatey_source.py' 2023-04-28 05:57:48,893 wheel INFO adding 'ansible_collections/cisco/aci/CHANGELOG.rst' 2023-04-28 05:57:48,894 wheel INFO adding 'ansible_collections/cisco/aci/FILES.json' 2023-04-28 05:57:48,895 wheel INFO adding 'ansible_collections/cisco/aci/LICENSE' 2023-04-28 05:57:48,895 wheel INFO adding 'ansible_collections/cisco/aci/MANIFEST.json' 2023-04-28 05:57:48,896 wheel INFO adding 'ansible_collections/cisco/aci/README.md' 2023-04-28 05:57:48,896 wheel INFO adding 'ansible_collections/cisco/aci/requirements.txt' 2023-04-28 05:57:48,896 wheel INFO adding 'ansible_collections/cisco/aci/changelogs/.gitignore' 2023-04-28 05:57:48,896 wheel INFO adding 'ansible_collections/cisco/aci/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:48,897 wheel INFO adding 'ansible_collections/cisco/aci/changelogs/changelog.yaml' 2023-04-28 05:57:48,897 wheel INFO adding 'ansible_collections/cisco/aci/changelogs/config.yaml' 2023-04-28 05:57:48,897 wheel INFO adding 'ansible_collections/cisco/aci/meta/runtime.yml' 2023-04-28 05:57:48,898 wheel INFO adding 'ansible_collections/cisco/aci/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:48,898 wheel INFO adding 'ansible_collections/cisco/aci/plugins/doc_fragments/aci.py' 2023-04-28 05:57:48,898 wheel INFO adding 'ansible_collections/cisco/aci/plugins/doc_fragments/annotation.py' 2023-04-28 05:57:48,898 wheel INFO adding 'ansible_collections/cisco/aci/plugins/doc_fragments/owner.py' 2023-04-28 05:57:48,899 wheel INFO adding 'ansible_collections/cisco/aci/plugins/lookup/__init__.py' 2023-04-28 05:57:48,899 wheel INFO adding 'ansible_collections/cisco/aci/plugins/lookup/interface_range.py' 2023-04-28 05:57:48,899 wheel INFO adding 'ansible_collections/cisco/aci/plugins/module_utils/__init__.py' 2023-04-28 05:57:48,899 wheel INFO adding 'ansible_collections/cisco/aci/plugins/module_utils/aci.py' 2023-04-28 05:57:48,900 wheel INFO adding 'ansible_collections/cisco/aci/plugins/module_utils/constants.py' 2023-04-28 05:57:48,900 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/__init__.py' 2023-04-28 05:57:48,901 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_custom_privilege.py' 2023-04-28 05:57:48,901 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_domain.py' 2023-04-28 05:57:48,901 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_role.py' 2023-04-28 05:57:48,901 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_ssh_auth.py' 2023-04-28 05:57:48,902 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_user.py' 2023-04-28 05:57:48,902 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_certificate.py' 2023-04-28 05:57:48,902 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_domain.py' 2023-04-28 05:57:48,903 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aaa_user_role.py' 2023-04-28 05:57:48,903 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_access_port_block_to_access_port.py' 2023-04-28 05:57:48,903 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_access_port_to_interface_policy_leaf_profile.py' 2023-04-28 05:57:48,903 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_access_span_dst_group.py' 2023-04-28 05:57:48,904 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_access_span_filter_group.py' 2023-04-28 05:57:48,904 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_access_span_filter_group_entry.py' 2023-04-28 05:57:48,904 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_access_sub_port_block_to_access_port.py' 2023-04-28 05:57:48,905 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aep.py' 2023-04-28 05:57:48,905 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aep_to_domain.py' 2023-04-28 05:57:48,905 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_aep_to_epg.py' 2023-04-28 05:57:48,905 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_ap.py' 2023-04-28 05:57:48,906 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_bd.py' 2023-04-28 05:57:48,906 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_bd_dhcp_label.py' 2023-04-28 05:57:48,906 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_bd_subnet.py' 2023-04-28 05:57:48,907 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_bd_to_l3out.py' 2023-04-28 05:57:48,907 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_bgp_rr_asn.py' 2023-04-28 05:57:48,907 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_bgp_rr_node.py' 2023-04-28 05:57:48,907 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_bulk_static_binding_to_epg.py' 2023-04-28 05:57:48,908 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_ap.py' 2023-04-28 05:57:48,908 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_aws_provider.py' 2023-04-28 05:57:48,908 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_bgp_asn.py' 2023-04-28 05:57:48,908 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_cidr.py' 2023-04-28 05:57:48,909 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_ctx_profile.py' 2023-04-28 05:57:48,909 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_epg.py' 2023-04-28 05:57:48,909 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_epg_selector.py' 2023-04-28 05:57:48,910 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_external_epg.py' 2023-04-28 05:57:48,910 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_external_epg_selector.py' 2023-04-28 05:57:48,910 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_provider.py' 2023-04-28 05:57:48,910 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_region.py' 2023-04-28 05:57:48,911 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_subnet.py' 2023-04-28 05:57:48,911 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_vpn_gateway.py' 2023-04-28 05:57:48,911 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_cloud_zone.py' 2023-04-28 05:57:48,911 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_config_export_policy.py' 2023-04-28 05:57:48,912 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_config_rollback.py' 2023-04-28 05:57:48,912 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_config_snapshot.py' 2023-04-28 05:57:48,912 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_contract.py' 2023-04-28 05:57:48,912 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_contract_export.py' 2023-04-28 05:57:48,913 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_contract_subject.py' 2023-04-28 05:57:48,913 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_contract_subject_to_filter.py' 2023-04-28 05:57:48,913 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_contract_subject_to_service_graph.py' 2023-04-28 05:57:48,914 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_dhcp_relay.py' 2023-04-28 05:57:48,914 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_dhcp_relay_provider.py' 2023-04-28 05:57:48,914 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_dns_domain.py' 2023-04-28 05:57:48,914 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_dns_profile.py' 2023-04-28 05:57:48,915 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_dns_provider.py' 2023-04-28 05:57:48,915 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_domain.py' 2023-04-28 05:57:48,915 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_domain_to_encap_pool.py' 2023-04-28 05:57:48,915 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_domain_to_vlan_pool.py' 2023-04-28 05:57:48,916 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_encap_pool.py' 2023-04-28 05:57:48,916 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_encap_pool_range.py' 2023-04-28 05:57:48,916 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_epg.py' 2023-04-28 05:57:48,917 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_epg_monitoring_policy.py' 2023-04-28 05:57:48,917 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract.py' 2023-04-28 05:57:48,917 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract_interface.py' 2023-04-28 05:57:48,917 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_epg_to_contract_master.py' 2023-04-28 05:57:48,918 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_epg_to_domain.py' 2023-04-28 05:57:48,918 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_esg.py' 2023-04-28 05:57:48,918 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_esg_contract_master.py' 2023-04-28 05:57:48,919 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_esg_epg_selector.py' 2023-04-28 05:57:48,919 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_esg_ip_subnet_selector.py' 2023-04-28 05:57:48,919 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_esg_tag_selector.py' 2023-04-28 05:57:48,919 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_leaf_profile.py' 2023-04-28 05:57:48,920 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_leaf_switch_assoc.py' 2023-04-28 05:57:48,920 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_node.py' 2023-04-28 05:57:48,920 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_pod_policy_group.py' 2023-04-28 05:57:48,920 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_scheduler.py' 2023-04-28 05:57:48,921 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_spine_profile.py' 2023-04-28 05:57:48,921 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_spine_switch_assoc.py' 2023-04-28 05:57:48,921 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_switch_block.py' 2023-04-28 05:57:48,921 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_fabric_switch_policy_group.py' 2023-04-28 05:57:48,922 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_filter.py' 2023-04-28 05:57:48,922 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_filter_entry.py' 2023-04-28 05:57:48,922 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_firmware_group.py' 2023-04-28 05:57:48,923 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_firmware_group_node.py' 2023-04-28 05:57:48,923 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_firmware_policy.py' 2023-04-28 05:57:48,923 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_firmware_source.py' 2023-04-28 05:57:48,923 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_igmp_interface_policy.py' 2023-04-28 05:57:48,924 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_blacklist.py' 2023-04-28 05:57:48,924 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_config.py' 2023-04-28 05:57:48,924 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_description.py' 2023-04-28 05:57:48,924 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_cdp.py' 2023-04-28 05:57:48,925 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_fc.py' 2023-04-28 05:57:48,925 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_l2.py' 2023-04-28 05:57:48,925 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_breakout_port_group.py' 2023-04-28 05:57:48,926 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_policy_group.py' 2023-04-28 05:57:48,926 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_profile.py' 2023-04-28 05:57:48,926 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_leaf_profile_fex_policy_group.py' 2023-04-28 05:57:48,926 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_link_level.py' 2023-04-28 05:57:48,927 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_lldp.py' 2023-04-28 05:57:48,927 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_mcp.py' 2023-04-28 05:57:48,927 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_ospf.py' 2023-04-28 05:57:48,927 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_port_channel.py' 2023-04-28 05:57:48,928 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_port_security.py' 2023-04-28 05:57:48,928 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_policy_spanning_tree.py' 2023-04-28 05:57:48,928 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_interface_selector_to_switch_policy_leaf_profile.py' 2023-04-28 05:57:48,929 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l2out.py' 2023-04-28 05:57:48,929 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l2out_extepg.py' 2023-04-28 05:57:48,929 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l2out_extepg_to_contract.py' 2023-04-28 05:57:48,929 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_interface_path.py' 2023-04-28 05:57:48,930 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_interface_profile.py' 2023-04-28 05:57:48,930 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l2out_logical_node_profile.py' 2023-04-28 05:57:48,930 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out.py' 2023-04-28 05:57:48,930 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_bgp_peer.py' 2023-04-28 05:57:48,931 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_extepg.py' 2023-04-28 05:57:48,931 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_extepg_to_contract.py' 2023-04-28 05:57:48,931 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_extsubnet.py' 2023-04-28 05:57:48,932 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_interface.py' 2023-04-28 05:57:48,932 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_interface_secondary_ip.py' 2023-04-28 05:57:48,932 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_profile.py' 2023-04-28 05:57:48,932 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_profile_ospf_policy.py' 2023-04-28 05:57:48,933 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_interface_vpc_member.py' 2023-04-28 05:57:48,933 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_node.py' 2023-04-28 05:57:48,933 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_logical_node_profile.py' 2023-04-28 05:57:48,933 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_route_tag_policy.py' 2023-04-28 05:57:48,934 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_static_routes.py' 2023-04-28 05:57:48,934 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_l3out_static_routes_nexthop.py' 2023-04-28 05:57:48,934 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_maintenance_group.py' 2023-04-28 05:57:48,934 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_maintenance_group_node.py' 2023-04-28 05:57:48,935 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_maintenance_policy.py' 2023-04-28 05:57:48,935 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_node_mgmt_epg.py' 2023-04-28 05:57:48,935 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_ntp_policy.py' 2023-04-28 05:57:48,936 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_ntp_server.py' 2023-04-28 05:57:48,936 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_rest.py' 2023-04-28 05:57:48,936 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_snmp_client.py' 2023-04-28 05:57:48,936 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_snmp_client_group.py' 2023-04-28 05:57:48,937 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_snmp_community_policy.py' 2023-04-28 05:57:48,937 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_snmp_policy.py' 2023-04-28 05:57:48,937 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_snmp_user.py' 2023-04-28 05:57:48,937 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_static_binding_to_epg.py' 2023-04-28 05:57:48,938 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_static_node_mgmt_address.py' 2023-04-28 05:57:48,938 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_switch_leaf_selector.py' 2023-04-28 05:57:48,938 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_switch_policy_leaf_profile.py' 2023-04-28 05:57:48,939 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_switch_policy_vpc_protection_group.py' 2023-04-28 05:57:48,939 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_syslog_group.py' 2023-04-28 05:57:48,939 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_syslog_remote_dest.py' 2023-04-28 05:57:48,939 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_syslog_source.py' 2023-04-28 05:57:48,940 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_system.py' 2023-04-28 05:57:48,940 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_taboo_contract.py' 2023-04-28 05:57:48,940 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tag.py' 2023-04-28 05:57:48,940 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tenant.py' 2023-04-28 05:57:48,941 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tenant_action_rule_profile.py' 2023-04-28 05:57:48,941 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tenant_ep_retention_policy.py' 2023-04-28 05:57:48,941 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_dst_group.py' 2023-04-28 05:57:48,941 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group.py' 2023-04-28 05:57:48,942 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group_src.py' 2023-04-28 05:57:48,942 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_tenant_span_src_group_to_dst_group.py' 2023-04-28 05:57:48,942 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vlan_pool.py' 2023-04-28 05:57:48,943 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vlan_pool_encap_block.py' 2023-04-28 05:57:48,943 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vmm_controller.py' 2023-04-28 05:57:48,943 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vmm_credential.py' 2023-04-28 05:57:48,943 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vmm_uplink.py' 2023-04-28 05:57:48,944 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vmm_uplink_container.py' 2023-04-28 05:57:48,944 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vmm_vswitch_policy.py' 2023-04-28 05:57:48,944 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vrf.py' 2023-04-28 05:57:48,944 wheel INFO adding 'ansible_collections/cisco/aci/plugins/modules/aci_vzany_to_contract.py' 2023-04-28 05:57:48,945 wheel INFO adding 'ansible_collections/cisco/asa/CHANGELOG.rst' 2023-04-28 05:57:48,945 wheel INFO adding 'ansible_collections/cisco/asa/FILES.json' 2023-04-28 05:57:48,946 wheel INFO adding 'ansible_collections/cisco/asa/LICENSE' 2023-04-28 05:57:48,946 wheel INFO adding 'ansible_collections/cisco/asa/MANIFEST.json' 2023-04-28 05:57:48,946 wheel INFO adding 'ansible_collections/cisco/asa/README.md' 2023-04-28 05:57:48,947 wheel INFO adding 'ansible_collections/cisco/asa/bindep.txt' 2023-04-28 05:57:48,947 wheel INFO adding 'ansible_collections/cisco/asa/pyproject.toml' 2023-04-28 05:57:48,947 wheel INFO adding 'ansible_collections/cisco/asa/requirements.txt' 2023-04-28 05:57:48,947 wheel INFO adding 'ansible_collections/cisco/asa/test-requirements.txt' 2023-04-28 05:57:48,947 wheel INFO adding 'ansible_collections/cisco/asa/tox.ini' 2023-04-28 05:57:48,948 wheel INFO adding 'ansible_collections/cisco/asa/changelogs/changelog.yaml' 2023-04-28 05:57:48,948 wheel INFO adding 'ansible_collections/cisco/asa/changelogs/config.yaml' 2023-04-28 05:57:48,948 wheel INFO adding 'ansible_collections/cisco/asa/changelogs/fragments/.keep' 2023-04-28 05:57:48,948 wheel INFO adding 'ansible_collections/cisco/asa/meta/runtime.yml' 2023-04-28 05:57:48,949 wheel INFO adding 'ansible_collections/cisco/asa/plugins/action/__init__.py' 2023-04-28 05:57:48,949 wheel INFO adding 'ansible_collections/cisco/asa/plugins/action/asa.py' 2023-04-28 05:57:48,949 wheel INFO adding 'ansible_collections/cisco/asa/plugins/cliconf/__init__.py' 2023-04-28 05:57:48,949 wheel INFO adding 'ansible_collections/cisco/asa/plugins/cliconf/asa.py' 2023-04-28 05:57:48,950 wheel INFO adding 'ansible_collections/cisco/asa/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:48,950 wheel INFO adding 'ansible_collections/cisco/asa/plugins/doc_fragments/asa.py' 2023-04-28 05:57:48,950 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/__init__.py' 2023-04-28 05:57:48,950 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/__init__.py' 2023-04-28 05:57:48,951 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/asa.py' 2023-04-28 05:57:48,951 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/__init__.py' 2023-04-28 05:57:48,951 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/__init__.py' 2023-04-28 05:57:48,951 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/acls.py' 2023-04-28 05:57:48,952 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/__init__.py' 2023-04-28 05:57:48,952 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/facts.py' 2023-04-28 05:57:48,952 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/__init__.py' 2023-04-28 05:57:48,952 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/ogs.py' 2023-04-28 05:57:48,953 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/__init__.py' 2023-04-28 05:57:48,953 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/__init__.py' 2023-04-28 05:57:48,953 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/acls.py' 2023-04-28 05:57:48,953 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/__init__.py' 2023-04-28 05:57:48,954 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/ogs.py' 2023-04-28 05:57:48,954 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/__init__.py' 2023-04-28 05:57:48,954 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/facts.py' 2023-04-28 05:57:48,955 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/__init__.py' 2023-04-28 05:57:48,955 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/acls.py' 2023-04-28 05:57:48,955 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/__init__.py' 2023-04-28 05:57:48,955 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/base.py' 2023-04-28 05:57:48,956 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/__init__.py' 2023-04-28 05:57:48,956 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/ogs.py' 2023-04-28 05:57:48,956 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/__init__.py' 2023-04-28 05:57:48,956 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/module.py' 2023-04-28 05:57:48,957 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/providers.py' 2023-04-28 05:57:48,957 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/acls.py' 2023-04-28 05:57:48,957 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/ogs.py' 2023-04-28 05:57:48,958 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/__init__.py' 2023-04-28 05:57:48,958 wheel INFO adding 'ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/utils.py' 2023-04-28 05:57:48,958 wheel INFO adding 'ansible_collections/cisco/asa/plugins/modules/__init__.py' 2023-04-28 05:57:48,958 wheel INFO adding 'ansible_collections/cisco/asa/plugins/modules/asa_acls.py' 2023-04-28 05:57:48,959 wheel INFO adding 'ansible_collections/cisco/asa/plugins/modules/asa_command.py' 2023-04-28 05:57:48,959 wheel INFO adding 'ansible_collections/cisco/asa/plugins/modules/asa_config.py' 2023-04-28 05:57:48,959 wheel INFO adding 'ansible_collections/cisco/asa/plugins/modules/asa_facts.py' 2023-04-28 05:57:48,960 wheel INFO adding 'ansible_collections/cisco/asa/plugins/modules/asa_ogs.py' 2023-04-28 05:57:48,960 wheel INFO adding 'ansible_collections/cisco/asa/plugins/terminal/__init__.py' 2023-04-28 05:57:48,960 wheel INFO adding 'ansible_collections/cisco/asa/plugins/terminal/asa.py' 2023-04-28 05:57:48,961 wheel INFO adding 'ansible_collections/cisco/dnac/FILES.json' 2023-04-28 05:57:48,962 wheel INFO adding 'ansible_collections/cisco/dnac/LICENSE' 2023-04-28 05:57:48,962 wheel INFO adding 'ansible_collections/cisco/dnac/MANIFEST.json' 2023-04-28 05:57:48,963 wheel INFO adding 'ansible_collections/cisco/dnac/Makefile' 2023-04-28 05:57:48,963 wheel INFO adding 'ansible_collections/cisco/dnac/README.md' 2023-04-28 05:57:48,963 wheel INFO adding 'ansible_collections/cisco/dnac/requirements.txt' 2023-04-28 05:57:48,964 wheel INFO adding 'ansible_collections/cisco/dnac/changelogs/changelog.yaml' 2023-04-28 05:57:48,964 wheel INFO adding 'ansible_collections/cisco/dnac/meta/runtime.yml' 2023-04-28 05:57:48,964 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/application_set_info.yml' 2023-04-28 05:57:48,964 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/application_sets.yml' 2023-04-28 05:57:48,965 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/applications.yml' 2023-04-28 05:57:48,965 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/authentication_import.yml' 2023-04-28 05:57:48,965 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/command_runner_run_command.yml' 2023-04-28 05:57:48,965 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/configuration_template_version_create.yml' 2023-04-28 05:57:48,966 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/credentials.template' 2023-04-28 05:57:48,966 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/credentials.yml' 2023-04-28 05:57:48,966 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/device_details.yml' 2023-04-28 05:57:48,966 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/discovery.yml' 2023-04-28 05:57:48,966 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/download_device_cmd_runner_output.yml' 2023-04-28 05:57:48,967 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/global_credentials.yml' 2023-04-28 05:57:48,967 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/global_credentials_info.yml' 2023-04-28 05:57:48,967 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/global_pool.yml' 2023-04-28 05:57:48,967 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/hosts' 2023-04-28 05:57:48,967 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/image_details.yml' 2023-04-28 05:57:48,968 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/import_image_file.yml' 2023-04-28 05:57:48,968 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/network_device_custom_prompt_info.yml' 2023-04-28 05:57:48,968 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/network_device_info.yml' 2023-04-28 05:57:48,968 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/network_device_update_role.yml' 2023-04-28 05:57:48,969 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/pnp_device.yml' 2023-04-28 05:57:48,969 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/reports_executions_info.yml' 2023-04-28 05:57:48,969 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/reserve_ip_subpool.yml' 2023-04-28 05:57:48,969 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/sda_fabric.yml' 2023-04-28 05:57:48,969 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/sda_fabric_site.yml' 2023-04-28 05:57:48,970 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/sda_virtual_network_v2.yml' 2023-04-28 05:57:48,970 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/tag.yml' 2023-04-28 05:57:48,970 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/template.yml' 2023-04-28 05:57:48,970 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/template_pnp_intent.yml' 2023-04-28 05:57:48,970 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/test_swim_module.yml' 2023-04-28 05:57:48,971 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/wireless_enterprise_ssid.yml' 2023-04-28 05:57:48,971 wheel INFO adding 'ansible_collections/cisco/dnac/playbooks/files/test.template' 2023-04-28 05:57:48,971 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/README.md' 2023-04-28 05:57:48,971 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/__init__.py' 2023-04-28 05:57:48,972 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/accesspoint_configuration_details_by_task_id_info.py' 2023-04-28 05:57:48,972 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/app_policy_default_info.py' 2023-04-28 05:57:48,973 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/app_policy_info.py' 2023-04-28 05:57:48,973 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/app_policy_intent_create.py' 2023-04-28 05:57:48,973 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile.py' 2023-04-28 05:57:48,973 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile_count_info.py' 2023-04-28 05:57:48,974 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/app_policy_queuing_profile_info.py' 2023-04-28 05:57:48,974 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/application_sets.py' 2023-04-28 05:57:48,974 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/application_sets_count_info.py' 2023-04-28 05:57:48,974 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/application_sets_info.py' 2023-04-28 05:57:48,975 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/applications.py' 2023-04-28 05:57:48,975 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/applications_count_info.py' 2023-04-28 05:57:48,975 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/applications_health_info.py' 2023-04-28 05:57:48,975 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/applications_info.py' 2023-04-28 05:57:48,976 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/assign_device_to_site.py' 2023-04-28 05:57:48,976 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/associate_site_to_network_profile.py' 2023-04-28 05:57:48,976 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/authentication_import_certificate.py' 2023-04-28 05:57:48,976 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/authentication_import_certificate_p12.py' 2023-04-28 05:57:48,976 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/authentication_policy_servers_info.py' 2023-04-28 05:57:48,977 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/buildings_planned_access_points_info.py' 2023-04-28 05:57:48,977 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/business_sda_hostonboarding_ssid_ippool.py' 2023-04-28 05:57:48,977 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/business_sda_hostonboarding_ssid_ippool_info.py' 2023-04-28 05:57:48,977 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/business_sda_virtual_network_summary_info.py' 2023-04-28 05:57:48,978 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/business_sda_wireless_controller_create.py' 2023-04-28 05:57:48,978 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/business_sda_wireless_controller_delete.py' 2023-04-28 05:57:48,978 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/cli_credential.py' 2023-04-28 05:57:48,978 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/client_detail_info.py' 2023-04-28 05:57:48,979 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/client_enrichment_details_info.py' 2023-04-28 05:57:48,979 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/client_health_info.py' 2023-04-28 05:57:48,979 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/client_proximity_info.py' 2023-04-28 05:57:48,979 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/command_runner_run_command.py' 2023-04-28 05:57:48,979 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/compliance_check_run.py' 2023-04-28 05:57:48,980 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/compliance_device_by_id_info.py' 2023-04-28 05:57:48,980 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/compliance_device_details_count_info.py' 2023-04-28 05:57:48,980 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/compliance_device_details_info.py' 2023-04-28 05:57:48,980 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/compliance_device_info.py' 2023-04-28 05:57:48,981 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/compliance_device_status_count_info.py' 2023-04-28 05:57:48,981 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template.py' 2023-04-28 05:57:48,981 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_clone.py' 2023-04-28 05:57:48,981 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_create.py' 2023-04-28 05:57:48,982 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy.py' 2023-04-28 05:57:48,982 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy_status_info.py' 2023-04-28 05:57:48,982 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_deploy_v2.py' 2023-04-28 05:57:48,982 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_export_project.py' 2023-04-28 05:57:48,983 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_export_template.py' 2023-04-28 05:57:48,983 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_import_project.py' 2023-04-28 05:57:48,983 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_import_template.py' 2023-04-28 05:57:48,983 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_info.py' 2023-04-28 05:57:48,983 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_project.py' 2023-04-28 05:57:48,984 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_project_info.py' 2023-04-28 05:57:48,984 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_version_create.py' 2023-04-28 05:57:48,984 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/configuration_template_version_info.py' 2023-04-28 05:57:48,984 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/credential_to_site_by_siteid_create_v2.py' 2023-04-28 05:57:48,985 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_configurations_export.py' 2023-04-28 05:57:48,985 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_credential_create.py' 2023-04-28 05:57:48,985 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_credential_delete.py' 2023-04-28 05:57:48,985 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_credential_info.py' 2023-04-28 05:57:48,986 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_credential_update.py' 2023-04-28 05:57:48,986 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_details_info.py' 2023-04-28 05:57:48,986 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_enrichment_details_info.py' 2023-04-28 05:57:48,986 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_family_identifiers_details_info.py' 2023-04-28 05:57:48,986 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_health_info.py' 2023-04-28 05:57:48,987 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_interface_by_ip_info.py' 2023-04-28 05:57:48,987 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_interface_count_info.py' 2023-04-28 05:57:48,987 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_interface_info.py' 2023-04-28 05:57:48,987 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_interface_isis_info.py' 2023-04-28 05:57:48,988 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_interface_ospf_info.py' 2023-04-28 05:57:48,988 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_reboot_apreboot_info.py' 2023-04-28 05:57:48,988 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_replacement.py' 2023-04-28 05:57:48,988 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_replacement_count_info.py' 2023-04-28 05:57:48,989 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_replacement_deploy.py' 2023-04-28 05:57:48,989 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/device_replacement_info.py' 2023-04-28 05:57:48,989 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/disassociate_site_to_network_profile.py' 2023-04-28 05:57:48,989 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/disasterrecovery_system_operationstatus_info.py' 2023-04-28 05:57:48,989 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/disasterrecovery_system_status_info.py' 2023-04-28 05:57:48,990 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery.py' 2023-04-28 05:57:48,990 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_count_info.py' 2023-04-28 05:57:48,990 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_device_count_info.py' 2023-04-28 05:57:48,991 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_device_info.py' 2023-04-28 05:57:48,991 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_device_range_info.py' 2023-04-28 05:57:48,991 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_info.py' 2023-04-28 05:57:48,991 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_job_info.py' 2023-04-28 05:57:48,991 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_range_delete.py' 2023-04-28 05:57:48,992 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_range_info.py' 2023-04-28 05:57:48,992 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/discovery_summary_info.py' 2023-04-28 05:57:48,992 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/dna_command_runner_keywords_info.py' 2023-04-28 05:57:48,992 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/dnac_packages_info.py' 2023-04-28 05:57:48,993 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/dnacaap_management_execution_status_info.py' 2023-04-28 05:57:48,993 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/endpoint_analytics_profiling_rules.py' 2023-04-28 05:57:48,993 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/endpoint_analytics_profiling_rules_info.py' 2023-04-28 05:57:48,993 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/eox_status_device_info.py' 2023-04-28 05:57:48,994 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/eox_status_summary_info.py' 2023-04-28 05:57:48,994 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_api_status_info.py' 2023-04-28 05:57:48,994 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_artifact_count_info.py' 2023-04-28 05:57:48,994 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_artifact_info.py' 2023-04-28 05:57:48,994 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_config_connector_types_info.py' 2023-04-28 05:57:48,995 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_count_info.py' 2023-04-28 05:57:48,995 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_email_config.py' 2023-04-28 05:57:48,995 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_email_config_create.py' 2023-04-28 05:57:48,995 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_email_config_info.py' 2023-04-28 05:57:48,996 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_email_config_update.py' 2023-04-28 05:57:48,996 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_info.py' 2023-04-28 05:57:48,996 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_info.py' 2023-04-28 05:57:48,996 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_parent_records_info.py' 2023-04-28 05:57:48,997 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_series_audit_logs_summary_info.py' 2023-04-28 05:57:48,997 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_series_count_info.py' 2023-04-28 05:57:48,997 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_series_info.py' 2023-04-28 05:57:48,997 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_snmp_config_info.py' 2023-04-28 05:57:48,998 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription.py' 2023-04-28 05:57:48,998 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_count_info.py' 2023-04-28 05:57:48,998 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_details_email_info.py' 2023-04-28 05:57:48,998 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_details_rest_info.py' 2023-04-28 05:57:48,999 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_details_syslog_info.py' 2023-04-28 05:57:48,999 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_email.py' 2023-04-28 05:57:48,999 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_email_info.py' 2023-04-28 05:57:48,999 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_info.py' 2023-04-28 05:57:48,999 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_rest.py' 2023-04-28 05:57:49,000 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_rest_info.py' 2023-04-28 05:57:49,000 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_syslog.py' 2023-04-28 05:57:49,000 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_subscription_syslog_info.py' 2023-04-28 05:57:49,000 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_syslog_config.py' 2023-04-28 05:57:49,001 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_syslog_config_info.py' 2023-04-28 05:57:49,001 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_webhook_create.py' 2023-04-28 05:57:49,001 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/event_webhook_update.py' 2023-04-28 05:57:49,001 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/execute_suggested_actions_commands.py' 2023-04-28 05:57:49,002 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/file_import.py' 2023-04-28 05:57:49,002 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/file_info.py' 2023-04-28 05:57:49,002 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/file_namespace_files_info.py' 2023-04-28 05:57:49,002 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/file_namespaces_info.py' 2023-04-28 05:57:49,002 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/global_credential_delete.py' 2023-04-28 05:57:49,003 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/global_credential_info.py' 2023-04-28 05:57:49,003 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/global_credential_update.py' 2023-04-28 05:57:49,003 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/global_credential_v2.py' 2023-04-28 05:57:49,003 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/global_credential_v2_info.py' 2023-04-28 05:57:49,004 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/global_pool.py' 2023-04-28 05:57:49,004 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/global_pool_info.py' 2023-04-28 05:57:49,005 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/golden_image_create.py' 2023-04-28 05:57:49,005 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/golden_tag_image_delete.py' 2023-04-28 05:57:49,005 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/golden_tag_image_details_info.py' 2023-04-28 05:57:49,005 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/http_read_credential.py' 2023-04-28 05:57:49,006 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/http_write_credential.py' 2023-04-28 05:57:49,006 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/integration_settings_instances_itsm.py' 2023-04-28 05:57:49,006 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/integration_settings_instances_itsm_info.py' 2023-04-28 05:57:49,006 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/interface_info.py' 2023-04-28 05:57:49,007 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/interface_network_device_detail_info.py' 2023-04-28 05:57:49,007 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/interface_network_device_info.py' 2023-04-28 05:57:49,007 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/interface_network_device_range_info.py' 2023-04-28 05:57:49,007 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/interface_operation_create.py' 2023-04-28 05:57:49,007 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/interface_update.py' 2023-04-28 05:57:49,008 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/issues_enrichment_details_info.py' 2023-04-28 05:57:49,008 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/issues_info.py' 2023-04-28 05:57:49,008 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/itsm_cmdb_sync_status_info.py' 2023-04-28 05:57:49,008 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/itsm_integration_events_failed_info.py' 2023-04-28 05:57:49,009 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/itsm_integration_events_retry.py' 2023-04-28 05:57:49,009 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/lan_automation_count_info.py' 2023-04-28 05:57:49,009 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/lan_automation_create.py' 2023-04-28 05:57:49,009 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/lan_automation_delete.py' 2023-04-28 05:57:49,009 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/lan_automation_log_by_serial_number_info.py' 2023-04-28 05:57:49,010 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/lan_automation_log_info.py' 2023-04-28 05:57:49,010 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/lan_automation_status_info.py' 2023-04-28 05:57:49,010 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_device_count_info.py' 2023-04-28 05:57:49,010 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_device_deregistration.py' 2023-04-28 05:57:49,011 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_device_license_details_info.py' 2023-04-28 05:57:49,011 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_device_license_summary_info.py' 2023-04-28 05:57:49,011 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_device_registration.py' 2023-04-28 05:57:49,011 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_smart_account_details_info.py' 2023-04-28 05:57:49,011 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_term_details_info.py' 2023-04-28 05:57:49,012 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_usage_details_info.py' 2023-04-28 05:57:49,012 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_virtual_account_change.py' 2023-04-28 05:57:49,012 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/license_virtual_account_details_info.py' 2023-04-28 05:57:49,012 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/netconf_credential.py' 2023-04-28 05:57:49,013 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_create.py' 2023-04-28 05:57:49,013 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device.py' 2023-04-28 05:57:49,013 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_by_ip_info.py' 2023-04-28 05:57:49,013 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_by_serial_number_info.py' 2023-04-28 05:57:49,014 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_chassis_details_info.py' 2023-04-28 05:57:49,014 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_config_count_info.py' 2023-04-28 05:57:49,014 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_config_info.py' 2023-04-28 05:57:49,014 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_count_info.py' 2023-04-28 05:57:49,015 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_custom_prompt.py' 2023-04-28 05:57:49,015 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_custom_prompt_info.py' 2023-04-28 05:57:49,015 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_equipment_info.py' 2023-04-28 05:57:49,015 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_export.py' 2023-04-28 05:57:49,015 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_functional_capability_info.py' 2023-04-28 05:57:49,016 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_global_polling_interval_info.py' 2023-04-28 05:57:49,016 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_info.py' 2023-04-28 05:57:49,016 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_interface_neighbor_info.py' 2023-04-28 05:57:49,016 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_interface_poe_info.py' 2023-04-28 05:57:49,017 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_inventory_insight_link_mismatch_info.py' 2023-04-28 05:57:49,017 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_lexicographically_sorted_info.py' 2023-04-28 05:57:49,017 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_linecard_details_info.py' 2023-04-28 05:57:49,017 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_meraki_organization_info.py' 2023-04-28 05:57:49,018 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_module_count_info.py' 2023-04-28 05:57:49,018 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_module_info.py' 2023-04-28 05:57:49,018 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_poe_info.py' 2023-04-28 05:57:49,018 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_polling_interval_info.py' 2023-04-28 05:57:49,018 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_range_info.py' 2023-04-28 05:57:49,019 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_register_for_wsa_info.py' 2023-04-28 05:57:49,019 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_stack_details_info.py' 2023-04-28 05:57:49,019 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_summary_info.py' 2023-04-28 05:57:49,019 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_supervisor_card_details_info.py' 2023-04-28 05:57:49,020 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_sync.py' 2023-04-28 05:57:49,020 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_update_role.py' 2023-04-28 05:57:49,020 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_user_defined_field.py' 2023-04-28 05:57:49,020 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_user_defined_field_info.py' 2023-04-28 05:57:49,021 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_vlan_info.py' 2023-04-28 05:57:49,021 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_wireless_lan_info.py' 2023-04-28 05:57:49,021 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_device_with_snmp_v3_des_info.py' 2023-04-28 05:57:49,021 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_info.py' 2023-04-28 05:57:49,021 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_update.py' 2023-04-28 05:57:49,022 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_v2.py' 2023-04-28 05:57:49,022 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/network_v2_info.py' 2023-04-28 05:57:49,022 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/nfv_profile.py' 2023-04-28 05:57:49,022 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/nfv_profile_info.py' 2023-04-28 05:57:49,023 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/nfv_provision.py' 2023-04-28 05:57:49,023 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/nfv_provision_detail_info.py' 2023-04-28 05:57:49,023 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/nfv_provision_details.py' 2023-04-28 05:57:49,023 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/path_trace.py' 2023-04-28 05:57:49,024 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/path_trace_info.py' 2023-04-28 05:57:49,024 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/planned_access_points_info.py' 2023-04-28 05:57:49,024 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/platform_nodes_configuration_summary_info.py' 2023-04-28 05:57:49,024 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/platform_release_summary_info.py' 2023-04-28 05:57:49,025 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device.py' 2023-04-28 05:57:49,025 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_authorize.py' 2023-04-28 05:57:49,025 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_claim.py' 2023-04-28 05:57:49,025 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_claim_to_site.py' 2023-04-28 05:57:49,026 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_config_preview.py' 2023-04-28 05:57:49,026 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_count_info.py' 2023-04-28 05:57:49,026 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_history_info.py' 2023-04-28 05:57:49,026 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_import.py' 2023-04-28 05:57:49,026 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_info.py' 2023-04-28 05:57:49,027 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_reset.py' 2023-04-28 05:57:49,027 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_device_unclaim.py' 2023-04-28 05:57:49,027 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_global_settings.py' 2023-04-28 05:57:49,027 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_global_settings_info.py' 2023-04-28 05:57:49,028 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_server_profile_update.py' 2023-04-28 05:57:49,028 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_smart_account_domains_info.py' 2023-04-28 05:57:49,028 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_add.py' 2023-04-28 05:57:49,028 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_deregister.py' 2023-04-28 05:57:49,028 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_devices_sync.py' 2023-04-28 05:57:49,029 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_virtual_account_sync_result_info.py' 2023-04-28 05:57:49,029 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_virtual_accounts_info.py' 2023-04-28 05:57:49,029 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_workflow.py' 2023-04-28 05:57:49,029 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_workflow_count_info.py' 2023-04-28 05:57:49,030 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/pnp_workflow_info.py' 2023-04-28 05:57:49,030 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/profiling_rules_count_info.py' 2023-04-28 05:57:49,030 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/profiling_rules_in_bulk_create.py' 2023-04-28 05:57:49,030 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/projects_details_info.py' 2023-04-28 05:57:49,031 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/qos_device_interface.py' 2023-04-28 05:57:49,031 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/qos_device_interface_info.py' 2023-04-28 05:57:49,031 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/qos_device_interface_info_count_info.py' 2023-04-28 05:57:49,031 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reports.py' 2023-04-28 05:57:49,032 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reports_executions_info.py' 2023-04-28 05:57:49,032 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reports_info.py' 2023-04-28 05:57:49,032 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reports_view_group_info.py' 2023-04-28 05:57:49,032 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reports_view_group_view_info.py' 2023-04-28 05:57:49,033 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool.py' 2023-04-28 05:57:49,033 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_create.py' 2023-04-28 05:57:49,033 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_delete.py' 2023-04-28 05:57:49,033 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_info.py' 2023-04-28 05:57:49,034 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/reserve_ip_subpool_update.py' 2023-04-28 05:57:49,034 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/role_permissions_info.py' 2023-04-28 05:57:49,034 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/roles_info.py' 2023-04-28 05:57:49,034 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_count_info.py' 2023-04-28 05:57:49,034 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_device_info.py' 2023-04-28 05:57:49,035 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_device_role_info.py' 2023-04-28 05:57:49,035 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric.py' 2023-04-28 05:57:49,035 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_authentication_profile.py' 2023-04-28 05:57:49,035 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_authentication_profile_info.py' 2023-04-28 05:57:49,036 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_border_device.py' 2023-04-28 05:57:49,036 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_border_device_info.py' 2023-04-28 05:57:49,036 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_control_plane_device.py' 2023-04-28 05:57:49,036 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_control_plane_device_info.py' 2023-04-28 05:57:49,037 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_edge_device.py' 2023-04-28 05:57:49,037 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_edge_device_info.py' 2023-04-28 05:57:49,037 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_info.py' 2023-04-28 05:57:49,037 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_site.py' 2023-04-28 05:57:49,038 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_fabric_site_info.py' 2023-04-28 05:57:49,038 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_multicast.py' 2023-04-28 05:57:49,038 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_multicast_info.py' 2023-04-28 05:57:49,038 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_access_point.py' 2023-04-28 05:57:49,039 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_access_point_info.py' 2023-04-28 05:57:49,039 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_user_device.py' 2023-04-28 05:57:49,039 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_port_assignment_for_user_device_info.py' 2023-04-28 05:57:49,039 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_provision_device.py' 2023-04-28 05:57:49,040 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_provision_device_info.py' 2023-04-28 05:57:49,040 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_virtual_network.py' 2023-04-28 05:57:49,040 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_info.py' 2023-04-28 05:57:49,040 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_ip_pool.py' 2023-04-28 05:57:49,041 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_ip_pool_info.py' 2023-04-28 05:57:49,041 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_v2.py' 2023-04-28 05:57:49,041 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sda_virtual_network_v2_info.py' 2023-04-28 05:57:49,041 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/security_advisories_devices_info.py' 2023-04-28 05:57:49,041 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/security_advisories_ids_per_device_info.py' 2023-04-28 05:57:49,042 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/security_advisories_info.py' 2023-04-28 05:57:49,042 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/security_advisories_per_device_info.py' 2023-04-28 05:57:49,042 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/security_advisories_summary_info.py' 2023-04-28 05:57:49,042 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sensor.py' 2023-04-28 05:57:49,043 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sensor_info.py' 2023-04-28 05:57:49,043 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sensor_test_run.py' 2023-04-28 05:57:49,043 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sensor_test_template_duplicate.py' 2023-04-28 05:57:49,043 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sensor_test_template_edit.py' 2023-04-28 05:57:49,044 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/service_provider_create.py' 2023-04-28 05:57:49,044 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/service_provider_info.py' 2023-04-28 05:57:49,044 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/service_provider_profile_delete.py' 2023-04-28 05:57:49,044 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/service_provider_update.py' 2023-04-28 05:57:49,044 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/service_provider_v2.py' 2023-04-28 05:57:49,045 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/service_provider_v2_info.py' 2023-04-28 05:57:49,045 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_assign_credential.py' 2023-04-28 05:57:49,045 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_assign_device.py' 2023-04-28 05:57:49,045 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_count_info.py' 2023-04-28 05:57:49,046 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_create.py' 2023-04-28 05:57:49,046 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_delete.py' 2023-04-28 05:57:49,046 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_design_floormap.py' 2023-04-28 05:57:49,046 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_design_floormap_info.py' 2023-04-28 05:57:49,047 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_health_info.py' 2023-04-28 05:57:49,047 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_info.py' 2023-04-28 05:57:49,047 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_membership_info.py' 2023-04-28 05:57:49,047 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/site_update.py' 2023-04-28 05:57:49,047 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/snmp_properties.py' 2023-04-28 05:57:49,048 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/snmp_properties_info.py' 2023-04-28 05:57:49,048 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/snmpv2_read_community_credential.py' 2023-04-28 05:57:49,048 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/snmpv2_write_community_credential.py' 2023-04-28 05:57:49,048 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/snmpv3_credential.py' 2023-04-28 05:57:49,049 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/sp_profile_delete_v2.py' 2023-04-28 05:57:49,049 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/swim_image_details_info.py' 2023-04-28 05:57:49,049 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/swim_import_local.py' 2023-04-28 05:57:49,049 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/swim_import_via_url.py' 2023-04-28 05:57:49,050 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/swim_trigger_activation.py' 2023-04-28 05:57:49,050 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/swim_trigger_distribution.py' 2023-04-28 05:57:49,050 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/syslog_config_create.py' 2023-04-28 05:57:49,050 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/syslog_config_update.py' 2023-04-28 05:57:49,051 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/system_health_count_info.py' 2023-04-28 05:57:49,051 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/system_health_info.py' 2023-04-28 05:57:49,051 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/system_performance_historical_info.py' 2023-04-28 05:57:49,051 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/system_performance_info.py' 2023-04-28 05:57:49,051 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag.py' 2023-04-28 05:57:49,052 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag_count_info.py' 2023-04-28 05:57:49,052 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag_info.py' 2023-04-28 05:57:49,052 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag_member.py' 2023-04-28 05:57:49,052 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag_member_count_info.py' 2023-04-28 05:57:49,053 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag_member_info.py' 2023-04-28 05:57:49,053 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag_member_type_info.py' 2023-04-28 05:57:49,053 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/tag_membership.py' 2023-04-28 05:57:49,053 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/task_count_info.py' 2023-04-28 05:57:49,054 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/task_info.py' 2023-04-28 05:57:49,054 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/task_operation_info.py' 2023-04-28 05:57:49,054 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/task_tree_info.py' 2023-04-28 05:57:49,054 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/template_preview.py' 2023-04-28 05:57:49,055 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/templates_details_info.py' 2023-04-28 05:57:49,055 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/threat_detail.py' 2023-04-28 05:57:49,055 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/threat_detail_count.py' 2023-04-28 05:57:49,055 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/threat_summary.py' 2023-04-28 05:57:49,055 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/topology_layer_2_info.py' 2023-04-28 05:57:49,056 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/topology_layer_3_info.py' 2023-04-28 05:57:49,056 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/topology_network_health_info.py' 2023-04-28 05:57:49,056 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/topology_physical_info.py' 2023-04-28 05:57:49,056 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/topology_site_info.py' 2023-04-28 05:57:49,057 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/topology_vlan_details_info.py' 2023-04-28 05:57:49,057 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/transit_peer_network.py' 2023-04-28 05:57:49,057 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/transit_peer_network_info.py' 2023-04-28 05:57:49,057 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/user.py' 2023-04-28 05:57:49,058 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/user_enrichment_details_info.py' 2023-04-28 05:57:49,058 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/user_info.py' 2023-04-28 05:57:49,058 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/users_external_servers_info.py' 2023-04-28 05:57:49,058 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_accespoint_configuration.py' 2023-04-28 05:57:49,059 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_accesspoint_configuration_summary_info.py' 2023-04-28 05:57:49,059 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_dynamic_interface.py' 2023-04-28 05:57:49,059 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_dynamic_interface_info.py' 2023-04-28 05:57:49,059 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_enterprise_ssid.py' 2023-04-28 05:57:49,060 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_enterprise_ssid_info.py' 2023-04-28 05:57:49,060 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_profile.py' 2023-04-28 05:57:49,060 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_profile_info.py' 2023-04-28 05:57:49,060 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_provision_access_point.py' 2023-04-28 05:57:49,061 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_provision_device_create.py' 2023-04-28 05:57:49,061 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_provision_device_update.py' 2023-04-28 05:57:49,061 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_provision_ssid_create_provision.py' 2023-04-28 05:57:49,061 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_provision_ssid_delete_reprovision.py' 2023-04-28 05:57:49,061 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_psk_override.py' 2023-04-28 05:57:49,062 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_rf_profile.py' 2023-04-28 05:57:49,062 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_rf_profile_info.py' 2023-04-28 05:57:49,062 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/action/wireless_sensor_test_results_info.py' 2023-04-28 05:57:49,062 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:49,063 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/doc_fragments/intent_params.py' 2023-04-28 05:57:49,063 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/doc_fragments/module.py' 2023-04-28 05:57:49,063 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/doc_fragments/module_info.py' 2023-04-28 05:57:49,063 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/module_utils/__init__.py' 2023-04-28 05:57:49,064 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/module_utils/dnac.py' 2023-04-28 05:57:49,064 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/module_utils/exceptions.py' 2023-04-28 05:57:49,065 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/__init__.py' 2023-04-28 05:57:49,065 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/accesspoint_configuration_details_by_task_id_info.py' 2023-04-28 05:57:49,065 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/app_policy_default_info.py' 2023-04-28 05:57:49,065 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/app_policy_info.py' 2023-04-28 05:57:49,066 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/app_policy_intent_create.py' 2023-04-28 05:57:49,066 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile.py' 2023-04-28 05:57:49,066 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile_count_info.py' 2023-04-28 05:57:49,066 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/app_policy_queuing_profile_info.py' 2023-04-28 05:57:49,067 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/application_sets.py' 2023-04-28 05:57:49,067 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/application_sets_count_info.py' 2023-04-28 05:57:49,067 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/application_sets_info.py' 2023-04-28 05:57:49,067 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/applications.py' 2023-04-28 05:57:49,068 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/applications_count_info.py' 2023-04-28 05:57:49,068 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/applications_health_info.py' 2023-04-28 05:57:49,068 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/applications_info.py' 2023-04-28 05:57:49,068 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/assign_device_to_site.py' 2023-04-28 05:57:49,068 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/associate_site_to_network_profile.py' 2023-04-28 05:57:49,069 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/authentication_import_certificate.py' 2023-04-28 05:57:49,069 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/authentication_import_certificate_p12.py' 2023-04-28 05:57:49,069 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/authentication_policy_servers_info.py' 2023-04-28 05:57:49,069 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/buildings_planned_access_points_info.py' 2023-04-28 05:57:49,070 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/business_sda_hostonboarding_ssid_ippool.py' 2023-04-28 05:57:49,070 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/business_sda_hostonboarding_ssid_ippool_info.py' 2023-04-28 05:57:49,070 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/business_sda_virtual_network_summary_info.py' 2023-04-28 05:57:49,070 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/business_sda_wireless_controller_create.py' 2023-04-28 05:57:49,070 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/business_sda_wireless_controller_delete.py' 2023-04-28 05:57:49,071 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/cli_credential.py' 2023-04-28 05:57:49,071 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/client_detail_info.py' 2023-04-28 05:57:49,071 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/client_enrichment_details_info.py' 2023-04-28 05:57:49,071 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/client_health_info.py' 2023-04-28 05:57:49,072 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/client_proximity_info.py' 2023-04-28 05:57:49,072 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/command_runner_run_command.py' 2023-04-28 05:57:49,072 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/compliance_check_run.py' 2023-04-28 05:57:49,072 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/compliance_device_by_id_info.py' 2023-04-28 05:57:49,072 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/compliance_device_details_count_info.py' 2023-04-28 05:57:49,073 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/compliance_device_details_info.py' 2023-04-28 05:57:49,073 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/compliance_device_info.py' 2023-04-28 05:57:49,073 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/compliance_device_status_count_info.py' 2023-04-28 05:57:49,073 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template.py' 2023-04-28 05:57:49,074 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_clone.py' 2023-04-28 05:57:49,074 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_create.py' 2023-04-28 05:57:49,074 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy.py' 2023-04-28 05:57:49,075 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy_status_info.py' 2023-04-28 05:57:49,075 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_deploy_v2.py' 2023-04-28 05:57:49,075 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_export_project.py' 2023-04-28 05:57:49,075 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_export_template.py' 2023-04-28 05:57:49,075 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_import_project.py' 2023-04-28 05:57:49,076 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_import_template.py' 2023-04-28 05:57:49,076 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_info.py' 2023-04-28 05:57:49,076 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_project.py' 2023-04-28 05:57:49,077 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_project_info.py' 2023-04-28 05:57:49,077 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_version_create.py' 2023-04-28 05:57:49,077 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/configuration_template_version_info.py' 2023-04-28 05:57:49,077 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/credential_to_site_by_siteid_create_v2.py' 2023-04-28 05:57:49,078 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_configurations_export.py' 2023-04-28 05:57:49,078 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_credential_create.py' 2023-04-28 05:57:49,078 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_credential_delete.py' 2023-04-28 05:57:49,078 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_credential_info.py' 2023-04-28 05:57:49,079 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_credential_update.py' 2023-04-28 05:57:49,079 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_details_info.py' 2023-04-28 05:57:49,079 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_enrichment_details_info.py' 2023-04-28 05:57:49,079 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_family_identifiers_details_info.py' 2023-04-28 05:57:49,079 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_health_info.py' 2023-04-28 05:57:49,080 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_interface_by_ip_info.py' 2023-04-28 05:57:49,080 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_interface_count_info.py' 2023-04-28 05:57:49,080 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_interface_info.py' 2023-04-28 05:57:49,080 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_interface_isis_info.py' 2023-04-28 05:57:49,081 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_interface_ospf_info.py' 2023-04-28 05:57:49,081 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_reboot_apreboot.py' 2023-04-28 05:57:49,081 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_reboot_apreboot_info.py' 2023-04-28 05:57:49,081 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_replacement.py' 2023-04-28 05:57:49,081 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_replacement_count_info.py' 2023-04-28 05:57:49,082 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_replacement_deploy.py' 2023-04-28 05:57:49,082 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/device_replacement_info.py' 2023-04-28 05:57:49,082 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/disassociate_site_to_network_profile.py' 2023-04-28 05:57:49,082 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/disasterrecovery_system_operationstatus_info.py' 2023-04-28 05:57:49,083 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/disasterrecovery_system_status_info.py' 2023-04-28 05:57:49,083 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery.py' 2023-04-28 05:57:49,083 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_count_info.py' 2023-04-28 05:57:49,083 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_device_count_info.py' 2023-04-28 05:57:49,083 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_device_info.py' 2023-04-28 05:57:49,084 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_device_range_info.py' 2023-04-28 05:57:49,084 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_info.py' 2023-04-28 05:57:49,084 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_job_info.py' 2023-04-28 05:57:49,084 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_range_delete.py' 2023-04-28 05:57:49,085 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_range_info.py' 2023-04-28 05:57:49,085 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/discovery_summary_info.py' 2023-04-28 05:57:49,085 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/dna_command_runner_keywords_info.py' 2023-04-28 05:57:49,085 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/dnac_packages_info.py' 2023-04-28 05:57:49,085 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/dnacaap_management_execution_status_info.py' 2023-04-28 05:57:49,086 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/endpoint_analytics_profiling_rules.py' 2023-04-28 05:57:49,086 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/endpoint_analytics_profiling_rules_info.py' 2023-04-28 05:57:49,086 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/eox_status_device_info.py' 2023-04-28 05:57:49,086 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/eox_status_summary_info.py' 2023-04-28 05:57:49,087 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_api_status_info.py' 2023-04-28 05:57:49,087 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_artifact_count_info.py' 2023-04-28 05:57:49,087 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_artifact_info.py' 2023-04-28 05:57:49,087 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_config_connector_types_info.py' 2023-04-28 05:57:49,088 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_count_info.py' 2023-04-28 05:57:49,088 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_email_config.py' 2023-04-28 05:57:49,088 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_email_config_create.py' 2023-04-28 05:57:49,088 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_email_config_info.py' 2023-04-28 05:57:49,088 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_email_config_update.py' 2023-04-28 05:57:49,089 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_info.py' 2023-04-28 05:57:49,089 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_info.py' 2023-04-28 05:57:49,089 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_parent_records_info.py' 2023-04-28 05:57:49,089 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_series_audit_logs_summary_info.py' 2023-04-28 05:57:49,090 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_series_count_info.py' 2023-04-28 05:57:49,090 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_series_info.py' 2023-04-28 05:57:49,090 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_snmp_config_info.py' 2023-04-28 05:57:49,090 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription.py' 2023-04-28 05:57:49,091 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_count_info.py' 2023-04-28 05:57:49,091 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_email_info.py' 2023-04-28 05:57:49,091 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_rest_info.py' 2023-04-28 05:57:49,091 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_details_syslog_info.py' 2023-04-28 05:57:49,091 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_email.py' 2023-04-28 05:57:49,092 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_email_info.py' 2023-04-28 05:57:49,092 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_info.py' 2023-04-28 05:57:49,092 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_rest.py' 2023-04-28 05:57:49,092 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_rest_info.py' 2023-04-28 05:57:49,093 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_syslog.py' 2023-04-28 05:57:49,093 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_subscription_syslog_info.py' 2023-04-28 05:57:49,093 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_syslog_config.py' 2023-04-28 05:57:49,093 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_syslog_config_info.py' 2023-04-28 05:57:49,094 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_webhook_create.py' 2023-04-28 05:57:49,094 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/event_webhook_update.py' 2023-04-28 05:57:49,094 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/execute_suggested_actions_commands.py' 2023-04-28 05:57:49,094 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/file_import.py' 2023-04-28 05:57:49,094 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/file_info.py' 2023-04-28 05:57:49,095 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/file_namespace_files_info.py' 2023-04-28 05:57:49,095 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/file_namespaces_info.py' 2023-04-28 05:57:49,095 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/global_credential_delete.py' 2023-04-28 05:57:49,095 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/global_credential_info.py' 2023-04-28 05:57:49,096 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/global_credential_update.py' 2023-04-28 05:57:49,096 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/global_credential_v2.py' 2023-04-28 05:57:49,096 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/global_credential_v2_info.py' 2023-04-28 05:57:49,096 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/global_pool.py' 2023-04-28 05:57:49,096 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/global_pool_info.py' 2023-04-28 05:57:49,097 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/golden_image_create.py' 2023-04-28 05:57:49,097 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/golden_tag_image_delete.py' 2023-04-28 05:57:49,097 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/golden_tag_image_details_info.py' 2023-04-28 05:57:49,097 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/http_read_credential.py' 2023-04-28 05:57:49,098 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/http_write_credential.py' 2023-04-28 05:57:49,098 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/integration_settings_instances_itsm.py' 2023-04-28 05:57:49,098 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/integration_settings_instances_itsm_info.py' 2023-04-28 05:57:49,098 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/interface_info.py' 2023-04-28 05:57:49,098 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/interface_network_device_detail_info.py' 2023-04-28 05:57:49,099 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/interface_network_device_info.py' 2023-04-28 05:57:49,099 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/interface_network_device_range_info.py' 2023-04-28 05:57:49,099 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/interface_operation_create.py' 2023-04-28 05:57:49,099 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/interface_update.py' 2023-04-28 05:57:49,100 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/issues_enrichment_details_info.py' 2023-04-28 05:57:49,100 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/issues_info.py' 2023-04-28 05:57:49,100 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/itsm_cmdb_sync_status_info.py' 2023-04-28 05:57:49,100 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/itsm_integration_events_failed_info.py' 2023-04-28 05:57:49,100 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/itsm_integration_events_retry.py' 2023-04-28 05:57:49,101 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/lan_automation_count_info.py' 2023-04-28 05:57:49,101 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/lan_automation_create.py' 2023-04-28 05:57:49,101 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/lan_automation_delete.py' 2023-04-28 05:57:49,101 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/lan_automation_log_by_serial_number_info.py' 2023-04-28 05:57:49,102 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/lan_automation_log_info.py' 2023-04-28 05:57:49,102 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/lan_automation_status_info.py' 2023-04-28 05:57:49,102 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_device_count_info.py' 2023-04-28 05:57:49,102 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_device_deregistration.py' 2023-04-28 05:57:49,102 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_device_license_details_info.py' 2023-04-28 05:57:49,103 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_device_license_summary_info.py' 2023-04-28 05:57:49,103 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_device_registration.py' 2023-04-28 05:57:49,103 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_smart_account_details_info.py' 2023-04-28 05:57:49,103 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_term_details_info.py' 2023-04-28 05:57:49,104 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_usage_details_info.py' 2023-04-28 05:57:49,104 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_virtual_account_change.py' 2023-04-28 05:57:49,104 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/license_virtual_account_details_info.py' 2023-04-28 05:57:49,104 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/netconf_credential.py' 2023-04-28 05:57:49,105 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_create.py' 2023-04-28 05:57:49,105 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device.py' 2023-04-28 05:57:49,105 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_by_ip_info.py' 2023-04-28 05:57:49,105 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_by_serial_number_info.py' 2023-04-28 05:57:49,105 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_chassis_details_info.py' 2023-04-28 05:57:49,106 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_config_count_info.py' 2023-04-28 05:57:49,106 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_config_info.py' 2023-04-28 05:57:49,106 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_count_info.py' 2023-04-28 05:57:49,106 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_custom_prompt.py' 2023-04-28 05:57:49,107 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_custom_prompt_info.py' 2023-04-28 05:57:49,107 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_equipment_info.py' 2023-04-28 05:57:49,107 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_export.py' 2023-04-28 05:57:49,107 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_functional_capability_info.py' 2023-04-28 05:57:49,108 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_global_polling_interval_info.py' 2023-04-28 05:57:49,108 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_info.py' 2023-04-28 05:57:49,108 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_interface_neighbor_info.py' 2023-04-28 05:57:49,108 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_interface_poe_info.py' 2023-04-28 05:57:49,108 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_inventory_insight_link_mismatch_info.py' 2023-04-28 05:57:49,109 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_lexicographically_sorted_info.py' 2023-04-28 05:57:49,109 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_linecard_details_info.py' 2023-04-28 05:57:49,109 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_meraki_organization_info.py' 2023-04-28 05:57:49,109 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_module_count_info.py' 2023-04-28 05:57:49,110 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_module_info.py' 2023-04-28 05:57:49,110 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_poe_info.py' 2023-04-28 05:57:49,110 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_polling_interval_info.py' 2023-04-28 05:57:49,110 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_range_info.py' 2023-04-28 05:57:49,110 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_register_for_wsa_info.py' 2023-04-28 05:57:49,111 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_stack_details_info.py' 2023-04-28 05:57:49,111 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_summary_info.py' 2023-04-28 05:57:49,111 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_supervisor_card_details_info.py' 2023-04-28 05:57:49,111 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_sync.py' 2023-04-28 05:57:49,112 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_update_role.py' 2023-04-28 05:57:49,112 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_user_defined_field.py' 2023-04-28 05:57:49,112 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_user_defined_field_info.py' 2023-04-28 05:57:49,112 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_vlan_info.py' 2023-04-28 05:57:49,112 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_wireless_lan_info.py' 2023-04-28 05:57:49,113 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_device_with_snmp_v3_des_info.py' 2023-04-28 05:57:49,113 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_info.py' 2023-04-28 05:57:49,113 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_update.py' 2023-04-28 05:57:49,113 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_v2.py' 2023-04-28 05:57:49,114 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/network_v2_info.py' 2023-04-28 05:57:49,114 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/nfv_profile.py' 2023-04-28 05:57:49,114 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/nfv_profile_info.py' 2023-04-28 05:57:49,114 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/nfv_provision.py' 2023-04-28 05:57:49,115 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/nfv_provision_detail_info.py' 2023-04-28 05:57:49,115 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/nfv_provision_details.py' 2023-04-28 05:57:49,115 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/path_trace.py' 2023-04-28 05:57:49,115 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/path_trace_info.py' 2023-04-28 05:57:49,116 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/planned_access_points_info.py' 2023-04-28 05:57:49,116 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/platform_nodes_configuration_summary_info.py' 2023-04-28 05:57:49,116 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/platform_release_summary_info.py' 2023-04-28 05:57:49,117 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device.py' 2023-04-28 05:57:49,117 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_authorize.py' 2023-04-28 05:57:49,117 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_claim.py' 2023-04-28 05:57:49,117 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_claim_to_site.py' 2023-04-28 05:57:49,118 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_config_preview.py' 2023-04-28 05:57:49,118 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_count_info.py' 2023-04-28 05:57:49,118 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_history_info.py' 2023-04-28 05:57:49,118 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_import.py' 2023-04-28 05:57:49,119 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_info.py' 2023-04-28 05:57:49,119 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_reset.py' 2023-04-28 05:57:49,119 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_device_unclaim.py' 2023-04-28 05:57:49,120 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_global_settings.py' 2023-04-28 05:57:49,120 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_global_settings_info.py' 2023-04-28 05:57:49,120 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_intent.py' 2023-04-28 05:57:49,121 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_server_profile_update.py' 2023-04-28 05:57:49,121 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_smart_account_domains_info.py' 2023-04-28 05:57:49,121 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_add.py' 2023-04-28 05:57:49,121 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_deregister.py' 2023-04-28 05:57:49,121 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_devices_sync.py' 2023-04-28 05:57:49,122 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_account_sync_result_info.py' 2023-04-28 05:57:49,122 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_virtual_accounts_info.py' 2023-04-28 05:57:49,122 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_workflow.py' 2023-04-28 05:57:49,122 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_workflow_count_info.py' 2023-04-28 05:57:49,123 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/pnp_workflow_info.py' 2023-04-28 05:57:49,123 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/profiling_rules_count_info.py' 2023-04-28 05:57:49,123 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/profiling_rules_in_bulk_create.py' 2023-04-28 05:57:49,123 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/projects_details_info.py' 2023-04-28 05:57:49,124 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/qos_device_interface.py' 2023-04-28 05:57:49,124 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/qos_device_interface_info.py' 2023-04-28 05:57:49,124 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/qos_device_interface_info_count_info.py' 2023-04-28 05:57:49,124 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reports.py' 2023-04-28 05:57:49,124 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reports_executions_info.py' 2023-04-28 05:57:49,125 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reports_info.py' 2023-04-28 05:57:49,125 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reports_view_group_info.py' 2023-04-28 05:57:49,125 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reports_view_group_view_info.py' 2023-04-28 05:57:49,125 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool.py' 2023-04-28 05:57:49,126 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_create.py' 2023-04-28 05:57:49,126 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_delete.py' 2023-04-28 05:57:49,126 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_info.py' 2023-04-28 05:57:49,126 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/reserve_ip_subpool_update.py' 2023-04-28 05:57:49,127 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/role_permissions_info.py' 2023-04-28 05:57:49,127 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/roles_info.py' 2023-04-28 05:57:49,127 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_count_info.py' 2023-04-28 05:57:49,127 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_device_info.py' 2023-04-28 05:57:49,127 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_device_role_info.py' 2023-04-28 05:57:49,128 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric.py' 2023-04-28 05:57:49,128 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_authentication_profile.py' 2023-04-28 05:57:49,128 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_authentication_profile_info.py' 2023-04-28 05:57:49,128 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_border_device.py' 2023-04-28 05:57:49,129 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_border_device_info.py' 2023-04-28 05:57:49,129 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_control_plane_device.py' 2023-04-28 05:57:49,129 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_control_plane_device_info.py' 2023-04-28 05:57:49,130 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_edge_device.py' 2023-04-28 05:57:49,130 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_edge_device_info.py' 2023-04-28 05:57:49,130 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_info.py' 2023-04-28 05:57:49,130 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_site.py' 2023-04-28 05:57:49,131 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_fabric_site_info.py' 2023-04-28 05:57:49,131 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_multicast.py' 2023-04-28 05:57:49,131 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_multicast_info.py' 2023-04-28 05:57:49,131 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_access_point.py' 2023-04-28 05:57:49,131 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_access_point_info.py' 2023-04-28 05:57:49,132 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_user_device.py' 2023-04-28 05:57:49,132 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_port_assignment_for_user_device_info.py' 2023-04-28 05:57:49,132 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_provision_device.py' 2023-04-28 05:57:49,132 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_provision_device_info.py' 2023-04-28 05:57:49,133 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network.py' 2023-04-28 05:57:49,133 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_info.py' 2023-04-28 05:57:49,133 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_ip_pool.py' 2023-04-28 05:57:49,133 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_ip_pool_info.py' 2023-04-28 05:57:49,133 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_v2.py' 2023-04-28 05:57:49,134 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sda_virtual_network_v2_info.py' 2023-04-28 05:57:49,134 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/security_advisories_devices_info.py' 2023-04-28 05:57:49,134 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/security_advisories_ids_per_device_info.py' 2023-04-28 05:57:49,134 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/security_advisories_info.py' 2023-04-28 05:57:49,135 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/security_advisories_per_device_info.py' 2023-04-28 05:57:49,135 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/security_advisories_summary_info.py' 2023-04-28 05:57:49,135 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sensor.py' 2023-04-28 05:57:49,135 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sensor_info.py' 2023-04-28 05:57:49,135 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sensor_test_run.py' 2023-04-28 05:57:49,136 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sensor_test_template_duplicate.py' 2023-04-28 05:57:49,136 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sensor_test_template_edit.py' 2023-04-28 05:57:49,136 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/service_provider_create.py' 2023-04-28 05:57:49,136 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/service_provider_info.py' 2023-04-28 05:57:49,137 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/service_provider_profile_delete.py' 2023-04-28 05:57:49,137 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/service_provider_update.py' 2023-04-28 05:57:49,137 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/service_provider_v2.py' 2023-04-28 05:57:49,137 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/service_provider_v2_info.py' 2023-04-28 05:57:49,138 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_assign_credential.py' 2023-04-28 05:57:49,138 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_assign_device.py' 2023-04-28 05:57:49,138 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_count_info.py' 2023-04-28 05:57:49,138 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_create.py' 2023-04-28 05:57:49,138 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_delete.py' 2023-04-28 05:57:49,139 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_design_floormap.py' 2023-04-28 05:57:49,139 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_design_floormap_info.py' 2023-04-28 05:57:49,139 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_health_info.py' 2023-04-28 05:57:49,139 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_info.py' 2023-04-28 05:57:49,140 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_intent.py' 2023-04-28 05:57:49,140 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_membership_info.py' 2023-04-28 05:57:49,140 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/site_update.py' 2023-04-28 05:57:49,140 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/snmp_properties.py' 2023-04-28 05:57:49,141 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/snmp_properties_info.py' 2023-04-28 05:57:49,141 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/snmpv2_read_community_credential.py' 2023-04-28 05:57:49,141 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/snmpv2_write_community_credential.py' 2023-04-28 05:57:49,141 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/snmpv3_credential.py' 2023-04-28 05:57:49,141 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/sp_profile_delete_v2.py' 2023-04-28 05:57:49,142 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/swim_image_details_info.py' 2023-04-28 05:57:49,142 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/swim_import_local.py' 2023-04-28 05:57:49,142 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/swim_import_via_url.py' 2023-04-28 05:57:49,142 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/swim_intent.py' 2023-04-28 05:57:49,143 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/swim_trigger_activation.py' 2023-04-28 05:57:49,143 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/swim_trigger_distribution.py' 2023-04-28 05:57:49,143 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/syslog_config_create.py' 2023-04-28 05:57:49,143 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/syslog_config_update.py' 2023-04-28 05:57:49,144 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/system_health_count_info.py' 2023-04-28 05:57:49,144 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/system_health_info.py' 2023-04-28 05:57:49,144 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/system_performance_historical_info.py' 2023-04-28 05:57:49,144 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/system_performance_info.py' 2023-04-28 05:57:49,145 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag.py' 2023-04-28 05:57:49,145 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag_count_info.py' 2023-04-28 05:57:49,145 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag_info.py' 2023-04-28 05:57:49,145 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag_member.py' 2023-04-28 05:57:49,145 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag_member_count_info.py' 2023-04-28 05:57:49,146 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag_member_info.py' 2023-04-28 05:57:49,146 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag_member_type_info.py' 2023-04-28 05:57:49,146 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/tag_membership.py' 2023-04-28 05:57:49,146 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/task_count_info.py' 2023-04-28 05:57:49,147 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/task_info.py' 2023-04-28 05:57:49,147 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/task_operation_info.py' 2023-04-28 05:57:49,147 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/task_tree_info.py' 2023-04-28 05:57:49,147 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/template_intent.py' 2023-04-28 05:57:49,148 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/template_preview.py' 2023-04-28 05:57:49,148 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/templates_details_info.py' 2023-04-28 05:57:49,148 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/threat_detail.py' 2023-04-28 05:57:49,148 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/threat_detail_count.py' 2023-04-28 05:57:49,149 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/threat_summary.py' 2023-04-28 05:57:49,149 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/topology_layer_2_info.py' 2023-04-28 05:57:49,149 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/topology_layer_3_info.py' 2023-04-28 05:57:49,149 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/topology_network_health_info.py' 2023-04-28 05:57:49,150 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/topology_physical_info.py' 2023-04-28 05:57:49,150 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/topology_site_info.py' 2023-04-28 05:57:49,150 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/topology_vlan_details_info.py' 2023-04-28 05:57:49,150 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/transit_peer_network.py' 2023-04-28 05:57:49,150 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/transit_peer_network_info.py' 2023-04-28 05:57:49,151 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/user.py' 2023-04-28 05:57:49,151 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/user_enrichment_details_info.py' 2023-04-28 05:57:49,151 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/user_info.py' 2023-04-28 05:57:49,151 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/users_external_servers_info.py' 2023-04-28 05:57:49,152 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_accespoint_configuration.py' 2023-04-28 05:57:49,152 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_accesspoint_configuration_summary_info.py' 2023-04-28 05:57:49,152 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_dynamic_interface.py' 2023-04-28 05:57:49,152 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_dynamic_interface_info.py' 2023-04-28 05:57:49,153 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_enterprise_ssid.py' 2023-04-28 05:57:49,153 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_enterprise_ssid_info.py' 2023-04-28 05:57:49,153 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_profile.py' 2023-04-28 05:57:49,153 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_profile_info.py' 2023-04-28 05:57:49,153 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_provision_access_point.py' 2023-04-28 05:57:49,154 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_provision_device_create.py' 2023-04-28 05:57:49,154 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_provision_device_update.py' 2023-04-28 05:57:49,154 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_provision_ssid_create_provision.py' 2023-04-28 05:57:49,154 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_provision_ssid_delete_reprovision.py' 2023-04-28 05:57:49,155 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_psk_override.py' 2023-04-28 05:57:49,155 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_rf_profile.py' 2023-04-28 05:57:49,155 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_rf_profile_info.py' 2023-04-28 05:57:49,155 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/modules/wireless_sensor_test_results_info.py' 2023-04-28 05:57:49,156 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/plugin_utils/__init__.py' 2023-04-28 05:57:49,156 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/plugin_utils/dnac.py' 2023-04-28 05:57:49,156 wheel INFO adding 'ansible_collections/cisco/dnac/plugins/plugin_utils/exceptions.py' 2023-04-28 05:57:49,156 wheel INFO adding 'ansible_collections/cisco/intersight/Development.md' 2023-04-28 05:57:49,157 wheel INFO adding 'ansible_collections/cisco/intersight/FILES.json' 2023-04-28 05:57:49,157 wheel INFO adding 'ansible_collections/cisco/intersight/LICENSE.txt' 2023-04-28 05:57:49,157 wheel INFO adding 'ansible_collections/cisco/intersight/MANIFEST.json' 2023-04-28 05:57:49,157 wheel INFO adding 'ansible_collections/cisco/intersight/README.md' 2023-04-28 05:57:49,158 wheel INFO adding 'ansible_collections/cisco/intersight/requirements.txt' 2023-04-28 05:57:49,158 wheel INFO adding 'ansible_collections/cisco/intersight/meta/execution-environment.yml' 2023-04-28 05:57:49,158 wheel INFO adding 'ansible_collections/cisco/intersight/meta/runtime.yml' 2023-04-28 05:57:49,161 wheel INFO adding 'ansible_collections/cisco/intersight/misc/CL2020 EMEAR DEVWKS-1542 Intersight Ansible Lab Guide.pdf' 2023-04-28 05:57:49,165 wheel INFO adding 'ansible_collections/cisco/intersight/misc/README.md' 2023-04-28 05:57:49,165 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/claim_device.yml' 2023-04-28 05:57:49,166 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/cos_server_policies_and_profiles.yml' 2023-04-28 05:57:49,166 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/deploy_server_profiles.yml' 2023-04-28 05:57:49,166 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/derive_profiles.yml' 2023-04-28 05:57:49,166 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/devnet_inventory' 2023-04-28 05:57:49,166 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/example_hx_host_vars' 2023-04-28 05:57:49,167 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/example_imm_inventory' 2023-04-28 05:57:49,167 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/example_inventory' 2023-04-28 05:57:49,167 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/firmware_direct_download.yml' 2023-04-28 05:57:49,167 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/hcl_status.yml' 2023-04-28 05:57:49,168 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/hyperflex_cluster_profiles.yml' 2023-04-28 05:57:49,168 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/hyperflex_edge_cluster_profiles.yml' 2023-04-28 05:57:49,168 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_boot_order_policy.yml' 2023-04-28 05:57:49,168 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_domain_profile.yml' 2023-04-28 05:57:49,169 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_eth_network.yml' 2023-04-28 05:57:49,169 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_imc_access_policy.yml' 2023-04-28 05:57:49,169 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_lan_connectivity_policy.yml' 2023-04-28 05:57:49,169 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_local_user_policy.yml' 2023-04-28 05:57:49,169 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_ntp_policy.yml' 2023-04-28 05:57:49,170 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_port_policy.yml' 2023-04-28 05:57:49,170 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_server_profile.yml' 2023-04-28 05:57:49,170 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_server_profile_template.yml' 2023-04-28 05:57:49,170 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_virtual_media_policy.yml' 2023-04-28 05:57:49,171 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/intersight_vm_hosts.yml' 2023-04-28 05:57:49,171 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/only_new_server_profiles.yml' 2023-04-28 05:57:49,171 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/os_install.yml' 2023-04-28 05:57:49,171 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/ova_workflow.yml' 2023-04-28 05:57:49,171 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/profile_inventory' 2023-04-28 05:57:49,172 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/profile_with_buckets.yml' 2023-04-28 05:57:49,172 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/pxe_boot.yml' 2023-04-28 05:57:49,172 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/server_actions.yml' 2023-04-28 05:57:49,172 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/server_firmware.yml' 2023-04-28 05:57:49,172 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/servers_to_file.yml' 2023-04-28 05:57:49,173 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/update_all_inventory.yml' 2023-04-28 05:57:49,173 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/update_hx_edge_inventory.yml' 2023-04-28 05:57:49,173 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/update_hx_inventory.yml' 2023-04-28 05:57:49,173 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/update_standalone_inventory.yml' 2023-04-28 05:57:49,174 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/vault_intersight_server_profile.yml' 2023-04-28 05:57:49,174 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/vlans_to_file.yml' 2023-04-28 05:57:49,174 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/auto_support/tasks/main.yml' 2023-04-28 05:57:49,175 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_network/tasks/main.yml' 2023-04-28 05:57:49,175 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/defaults/main.yml' 2023-04-28 05:57:49,175 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_profile/tasks/main.yml' 2023-04-28 05:57:49,175 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/cluster_storage/tasks/main.yml' 2023-04-28 05:57:49,176 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/deploy/tasks/main.yml' 2023-04-28 05:57:49,176 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_network/tasks/main.yml' 2023-04-28 05:57:49,176 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/defaults/main.yml' 2023-04-28 05:57:49,176 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_profile/tasks/main.yml' 2023-04-28 05:57:49,177 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_cluster_storage/tasks/main.yml' 2023-04-28 05:57:49,177 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/edge_software_version/tasks/main.yml' 2023-04-28 05:57:49,177 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/fc/tasks/main.yml' 2023-04-28 05:57:49,178 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/intersight_org/tasks/main.yml' 2023-04-28 05:57:49,178 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/iscsi/tasks/main.yml' 2023-04-28 05:57:49,178 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/local_credential/tasks/main.yml' 2023-04-28 05:57:49,178 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_config/tasks/main.yml' 2023-04-28 05:57:49,179 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/node_profiles/tasks/main.yml' 2023-04-28 05:57:49,179 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/proxy/tasks/main.yml' 2023-04-28 05:57:49,179 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/software_version/tasks/main.yml' 2023-04-28 05:57:49,179 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/sys_config/tasks/main.yml' 2023-04-28 05:57:49,180 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/hyperflex_policies/vcenter/tasks/main.yml' 2023-04-28 05:57:49,180 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/policies/server_policies/tasks/main.yml' 2023-04-28 05:57:49,180 wheel INFO adding 'ansible_collections/cisco/intersight/playbooks/roles/servers/actions/tasks/main.yml' 2023-04-28 05:57:49,181 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/README.md' 2023-04-28 05:57:49,181 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/doc_fragments/intersight.py' 2023-04-28 05:57:49,181 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/module_utils/intersight.py' 2023-04-28 05:57:49,182 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_boot_order_policy.py' 2023-04-28 05:57:49,182 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_imc_access_policy.py' 2023-04-28 05:57:49,182 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_info.py' 2023-04-28 05:57:49,182 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_local_user_policy.py' 2023-04-28 05:57:49,183 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_ntp_policy.py' 2023-04-28 05:57:49,183 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_rest_api.py' 2023-04-28 05:57:49,183 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_server_profile.py' 2023-04-28 05:57:49,183 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_target_claim.py' 2023-04-28 05:57:49,184 wheel INFO adding 'ansible_collections/cisco/intersight/plugins/modules/intersight_virtual_media_policy.py' 2023-04-28 05:57:49,184 wheel INFO adding 'ansible_collections/cisco/ios/CHANGELOG.rst' 2023-04-28 05:57:49,185 wheel INFO adding 'ansible_collections/cisco/ios/FILES.json' 2023-04-28 05:57:49,187 wheel INFO adding 'ansible_collections/cisco/ios/LICENSE' 2023-04-28 05:57:49,187 wheel INFO adding 'ansible_collections/cisco/ios/MANIFEST.json' 2023-04-28 05:57:49,187 wheel INFO adding 'ansible_collections/cisco/ios/README.md' 2023-04-28 05:57:49,187 wheel INFO adding 'ansible_collections/cisco/ios/bindep.txt' 2023-04-28 05:57:49,188 wheel INFO adding 'ansible_collections/cisco/ios/codecov.yml' 2023-04-28 05:57:49,188 wheel INFO adding 'ansible_collections/cisco/ios/pyproject.toml' 2023-04-28 05:57:49,188 wheel INFO adding 'ansible_collections/cisco/ios/requirements.txt' 2023-04-28 05:57:49,188 wheel INFO adding 'ansible_collections/cisco/ios/test-requirements.txt' 2023-04-28 05:57:49,188 wheel INFO adding 'ansible_collections/cisco/ios/tox.ini' 2023-04-28 05:57:49,189 wheel INFO adding 'ansible_collections/cisco/ios/changelogs/changelog.yaml' 2023-04-28 05:57:49,189 wheel INFO adding 'ansible_collections/cisco/ios/changelogs/config.yaml' 2023-04-28 05:57:49,189 wheel INFO adding 'ansible_collections/cisco/ios/changelogs/fragments/.keep' 2023-04-28 05:57:49,190 wheel INFO adding 'ansible_collections/cisco/ios/meta/runtime.yml' 2023-04-28 05:57:49,190 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/__init__.py' 2023-04-28 05:57:49,190 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/acl_interfaces.py' 2023-04-28 05:57:49,190 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/acls.py' 2023-04-28 05:57:49,191 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/banner.py' 2023-04-28 05:57:49,191 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/bgp.py' 2023-04-28 05:57:49,191 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/bgp_address_family.py' 2023-04-28 05:57:49,191 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/bgp_global.py' 2023-04-28 05:57:49,192 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/command.py' 2023-04-28 05:57:49,192 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/config.py' 2023-04-28 05:57:49,192 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/facts.py' 2023-04-28 05:57:49,192 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/hostname.py' 2023-04-28 05:57:49,192 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/interfaces.py' 2023-04-28 05:57:49,193 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/ios.py' 2023-04-28 05:57:49,193 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/l2_interfaces.py' 2023-04-28 05:57:49,193 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/l3_interfaces.py' 2023-04-28 05:57:49,193 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/lacp.py' 2023-04-28 05:57:49,193 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/lacp_interfaces.py' 2023-04-28 05:57:49,194 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/lag_interfaces.py' 2023-04-28 05:57:49,194 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/linkagg.py' 2023-04-28 05:57:49,194 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/lldp.py' 2023-04-28 05:57:49,194 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/lldp_global.py' 2023-04-28 05:57:49,195 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/lldp_interfaces.py' 2023-04-28 05:57:49,195 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/logging.py' 2023-04-28 05:57:49,195 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/logging_global.py' 2023-04-28 05:57:49,195 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/ntp.py' 2023-04-28 05:57:49,195 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/ntp_global.py' 2023-04-28 05:57:49,196 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/ospf_interfaces.py' 2023-04-28 05:57:49,196 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/ospfv2.py' 2023-04-28 05:57:49,196 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/ospfv3.py' 2023-04-28 05:57:49,196 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/ping.py' 2023-04-28 05:57:49,197 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/prefix_lists.py' 2023-04-28 05:57:49,197 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/route_maps.py' 2023-04-28 05:57:49,197 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/snmp_server.py' 2023-04-28 05:57:49,197 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/static_routes.py' 2023-04-28 05:57:49,197 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/system.py' 2023-04-28 05:57:49,198 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/user.py' 2023-04-28 05:57:49,198 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/vlans.py' 2023-04-28 05:57:49,198 wheel INFO adding 'ansible_collections/cisco/ios/plugins/action/vrf.py' 2023-04-28 05:57:49,198 wheel INFO adding 'ansible_collections/cisco/ios/plugins/cliconf/__init__.py' 2023-04-28 05:57:49,199 wheel INFO adding 'ansible_collections/cisco/ios/plugins/cliconf/ios.py' 2023-04-28 05:57:49,199 wheel INFO adding 'ansible_collections/cisco/ios/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:49,199 wheel INFO adding 'ansible_collections/cisco/ios/plugins/doc_fragments/ios.py' 2023-04-28 05:57:49,199 wheel INFO adding 'ansible_collections/cisco/ios/plugins/filter/__init__.py' 2023-04-28 05:57:49,200 wheel INFO adding 'ansible_collections/cisco/ios/plugins/inventory/__init__.py' 2023-04-28 05:57:49,200 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/__init__.py' 2023-04-28 05:57:49,200 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:49,200 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/__init__.py' 2023-04-28 05:57:49,201 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/ios.py' 2023-04-28 05:57:49,201 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/__init__.py' 2023-04-28 05:57:49,201 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/__init__.py' 2023-04-28 05:57:49,201 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,202 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/__init__.py' 2023-04-28 05:57:49,202 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/acls.py' 2023-04-28 05:57:49,202 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/__init__.py' 2023-04-28 05:57:49,203 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,203 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/__init__.py' 2023-04-28 05:57:49,203 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/bgp_global.py' 2023-04-28 05:57:49,204 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/__init__.py' 2023-04-28 05:57:49,204 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/facts.py' 2023-04-28 05:57:49,204 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/__init__.py' 2023-04-28 05:57:49,204 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/hostname.py' 2023-04-28 05:57:49,205 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/__init__.py' 2023-04-28 05:57:49,205 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/interfaces.py' 2023-04-28 05:57:49,205 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/__init__.py' 2023-04-28 05:57:49,205 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,206 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/__init__.py' 2023-04-28 05:57:49,206 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,206 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/__init__.py' 2023-04-28 05:57:49,206 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/lacp.py' 2023-04-28 05:57:49,207 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,207 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,207 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/__init__.py' 2023-04-28 05:57:49,207 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,208 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/__init__.py' 2023-04-28 05:57:49,208 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/lldp_global.py' 2023-04-28 05:57:49,208 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,208 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,208 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/__init__.py' 2023-04-28 05:57:49,209 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/logging_global.py' 2023-04-28 05:57:49,209 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/__init__.py' 2023-04-28 05:57:49,209 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/ntp_global.py' 2023-04-28 05:57:49,210 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,210 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,210 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/__init__.py' 2023-04-28 05:57:49,210 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/ospfv2.py' 2023-04-28 05:57:49,211 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/__init__.py' 2023-04-28 05:57:49,211 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/ospfv3.py' 2023-04-28 05:57:49,211 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/__init__.py' 2023-04-28 05:57:49,212 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/ping.py' 2023-04-28 05:57:49,212 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/__init__.py' 2023-04-28 05:57:49,212 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,212 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/__init__.py' 2023-04-28 05:57:49,213 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/route_maps.py' 2023-04-28 05:57:49,213 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/__init__.py' 2023-04-28 05:57:49,213 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/snmp_server.py' 2023-04-28 05:57:49,214 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/__init__.py' 2023-04-28 05:57:49,214 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/static_routes.py' 2023-04-28 05:57:49,214 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/__init__.py' 2023-04-28 05:57:49,214 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/vlans.py' 2023-04-28 05:57:49,215 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/__init__.py' 2023-04-28 05:57:49,215 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/__init__.py' 2023-04-28 05:57:49,215 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,215 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/__init__.py' 2023-04-28 05:57:49,216 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/acls.py' 2023-04-28 05:57:49,216 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/__init__.py' 2023-04-28 05:57:49,216 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,217 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/__init__.py' 2023-04-28 05:57:49,217 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/bgp_global.py' 2023-04-28 05:57:49,217 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/__init__.py' 2023-04-28 05:57:49,217 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/hostname.py' 2023-04-28 05:57:49,218 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/__init__.py' 2023-04-28 05:57:49,218 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/interfaces.py' 2023-04-28 05:57:49,218 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/__init__.py' 2023-04-28 05:57:49,218 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,219 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/__init__.py' 2023-04-28 05:57:49,219 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,219 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/__init__.py' 2023-04-28 05:57:49,219 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/lacp.py' 2023-04-28 05:57:49,220 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,220 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,220 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/__init__.py' 2023-04-28 05:57:49,220 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,221 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/__init__.py' 2023-04-28 05:57:49,221 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/lldp_global.py' 2023-04-28 05:57:49,221 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,221 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,222 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/__init__.py' 2023-04-28 05:57:49,222 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/logging_global.py' 2023-04-28 05:57:49,222 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/__init__.py' 2023-04-28 05:57:49,222 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/ntp_global.py' 2023-04-28 05:57:49,223 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,223 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,223 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/__init__.py' 2023-04-28 05:57:49,224 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/ospfv2.py' 2023-04-28 05:57:49,224 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/__init__.py' 2023-04-28 05:57:49,224 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/ospfv3.py' 2023-04-28 05:57:49,224 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/__init__.py' 2023-04-28 05:57:49,225 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/ping.py' 2023-04-28 05:57:49,225 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/__init__.py' 2023-04-28 05:57:49,225 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,225 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/__init__.py' 2023-04-28 05:57:49,226 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/route_maps.py' 2023-04-28 05:57:49,226 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/__init__.py' 2023-04-28 05:57:49,226 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/snmp_server.py' 2023-04-28 05:57:49,226 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/__init__.py' 2023-04-28 05:57:49,227 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/static_routes.py' 2023-04-28 05:57:49,227 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/__init__.py' 2023-04-28 05:57:49,227 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/vlans.py' 2023-04-28 05:57:49,228 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/__init__.py' 2023-04-28 05:57:49,228 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/facts.py' 2023-04-28 05:57:49,228 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/__init__.py' 2023-04-28 05:57:49,228 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,229 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/__init__.py' 2023-04-28 05:57:49,229 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/acls.py' 2023-04-28 05:57:49,229 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/__init__.py' 2023-04-28 05:57:49,229 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,230 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/__init__.py' 2023-04-28 05:57:49,230 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/bgp_global.py' 2023-04-28 05:57:49,230 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/__init__.py' 2023-04-28 05:57:49,230 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/hostname.py' 2023-04-28 05:57:49,231 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/__init__.py' 2023-04-28 05:57:49,231 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/interfaces.py' 2023-04-28 05:57:49,231 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/__init__.py' 2023-04-28 05:57:49,231 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,231 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/__init__.py' 2023-04-28 05:57:49,232 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,232 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/__init__.py' 2023-04-28 05:57:49,232 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/lacp.py' 2023-04-28 05:57:49,232 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,233 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,233 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/__init__.py' 2023-04-28 05:57:49,233 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,233 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/__init__.py' 2023-04-28 05:57:49,234 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/base.py' 2023-04-28 05:57:49,234 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/__init__.py' 2023-04-28 05:57:49,234 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/lldp_global.py' 2023-04-28 05:57:49,234 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,235 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,235 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/__init__.py' 2023-04-28 05:57:49,235 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/logging_global.py' 2023-04-28 05:57:49,235 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/__init__.py' 2023-04-28 05:57:49,236 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/ntp_global.py' 2023-04-28 05:57:49,236 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,236 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,236 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/__init__.py' 2023-04-28 05:57:49,237 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/ospfv2.py' 2023-04-28 05:57:49,237 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/__init__.py' 2023-04-28 05:57:49,237 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/ospfv3.py' 2023-04-28 05:57:49,237 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/__init__.py' 2023-04-28 05:57:49,238 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,238 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/__init__.py' 2023-04-28 05:57:49,238 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/route_maps.py' 2023-04-28 05:57:49,238 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/__init__.py' 2023-04-28 05:57:49,239 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/snmp_server.py' 2023-04-28 05:57:49,239 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/__init__.py' 2023-04-28 05:57:49,239 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/static_routes.py' 2023-04-28 05:57:49,240 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/__init__.py' 2023-04-28 05:57:49,240 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/vlans.py' 2023-04-28 05:57:49,240 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/__init__.py' 2023-04-28 05:57:49,241 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/module.py' 2023-04-28 05:57:49,241 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/providers.py' 2023-04-28 05:57:49,241 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/__init__.py' 2023-04-28 05:57:49,241 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/__init__.py' 2023-04-28 05:57:49,242 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/base.py' 2023-04-28 05:57:49,242 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/__init__.py' 2023-04-28 05:57:49,242 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/address_family.py' 2023-04-28 05:57:49,242 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/neighbors.py' 2023-04-28 05:57:49,243 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/process.py' 2023-04-28 05:57:49,243 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/__init__.py' 2023-04-28 05:57:49,243 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/acl_interfaces.py' 2023-04-28 05:57:49,243 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/acls.py' 2023-04-28 05:57:49,244 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/bgp_address_family.py' 2023-04-28 05:57:49,245 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/bgp_global.py' 2023-04-28 05:57:49,246 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/hostname.py' 2023-04-28 05:57:49,246 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/interfaces.py' 2023-04-28 05:57:49,246 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/l2_interfaces.py' 2023-04-28 05:57:49,246 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/l3_interfaces.py' 2023-04-28 05:57:49,247 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/lag_interfaces.py' 2023-04-28 05:57:49,247 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/logging_global.py' 2023-04-28 05:57:49,247 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ntp_global.py' 2023-04-28 05:57:49,248 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospf_interfaces.py' 2023-04-28 05:57:49,248 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospfv2.py' 2023-04-28 05:57:49,249 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ospfv3.py' 2023-04-28 05:57:49,250 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/ping.py' 2023-04-28 05:57:49,250 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/prefix_lists.py' 2023-04-28 05:57:49,250 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/route_maps.py' 2023-04-28 05:57:49,251 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/snmp_server.py' 2023-04-28 05:57:49,251 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/static_routes.py' 2023-04-28 05:57:49,252 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/__init__.py' 2023-04-28 05:57:49,252 wheel INFO adding 'ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/utils.py' 2023-04-28 05:57:49,252 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/__init__.py' 2023-04-28 05:57:49,253 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_acl_interfaces.py' 2023-04-28 05:57:49,253 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_acls.py' 2023-04-28 05:57:49,254 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_banner.py' 2023-04-28 05:57:49,254 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_bgp.py' 2023-04-28 05:57:49,255 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_bgp_address_family.py' 2023-04-28 05:57:49,256 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_bgp_global.py' 2023-04-28 05:57:49,256 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_command.py' 2023-04-28 05:57:49,257 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_config.py' 2023-04-28 05:57:49,257 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_facts.py' 2023-04-28 05:57:49,257 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_hostname.py' 2023-04-28 05:57:49,257 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_interfaces.py' 2023-04-28 05:57:49,258 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_l2_interfaces.py' 2023-04-28 05:57:49,258 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_l3_interfaces.py' 2023-04-28 05:57:49,259 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_lacp.py' 2023-04-28 05:57:49,259 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_lacp_interfaces.py' 2023-04-28 05:57:49,259 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_lag_interfaces.py' 2023-04-28 05:57:49,259 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_linkagg.py' 2023-04-28 05:57:49,260 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_lldp.py' 2023-04-28 05:57:49,260 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_lldp_global.py' 2023-04-28 05:57:49,260 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_lldp_interfaces.py' 2023-04-28 05:57:49,261 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_logging.py' 2023-04-28 05:57:49,261 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_logging_global.py' 2023-04-28 05:57:49,261 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_ntp.py' 2023-04-28 05:57:49,262 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_ntp_global.py' 2023-04-28 05:57:49,262 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_ospf_interfaces.py' 2023-04-28 05:57:49,263 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_ospfv2.py' 2023-04-28 05:57:49,263 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_ospfv3.py' 2023-04-28 05:57:49,264 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_ping.py' 2023-04-28 05:57:49,264 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_prefix_lists.py' 2023-04-28 05:57:49,265 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_route_maps.py' 2023-04-28 05:57:49,265 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_snmp_server.py' 2023-04-28 05:57:49,266 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_static_routes.py' 2023-04-28 05:57:49,266 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_system.py' 2023-04-28 05:57:49,267 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_user.py' 2023-04-28 05:57:49,267 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_vlans.py' 2023-04-28 05:57:49,267 wheel INFO adding 'ansible_collections/cisco/ios/plugins/modules/ios_vrf.py' 2023-04-28 05:57:49,268 wheel INFO adding 'ansible_collections/cisco/ios/plugins/terminal/__init__.py' 2023-04-28 05:57:49,268 wheel INFO adding 'ansible_collections/cisco/ios/plugins/terminal/ios.py' 2023-04-28 05:57:49,268 wheel INFO adding 'ansible_collections/cisco/iosxr/CHANGELOG.rst' 2023-04-28 05:57:49,269 wheel INFO adding 'ansible_collections/cisco/iosxr/FILES.json' 2023-04-28 05:57:49,271 wheel INFO adding 'ansible_collections/cisco/iosxr/LICENSE' 2023-04-28 05:57:49,271 wheel INFO adding 'ansible_collections/cisco/iosxr/MANIFEST.json' 2023-04-28 05:57:49,271 wheel INFO adding 'ansible_collections/cisco/iosxr/README.md' 2023-04-28 05:57:49,271 wheel INFO adding 'ansible_collections/cisco/iosxr/bindep.txt' 2023-04-28 05:57:49,272 wheel INFO adding 'ansible_collections/cisco/iosxr/pyproject.toml' 2023-04-28 05:57:49,272 wheel INFO adding 'ansible_collections/cisco/iosxr/requirements.txt' 2023-04-28 05:57:49,272 wheel INFO adding 'ansible_collections/cisco/iosxr/test-requirements.txt' 2023-04-28 05:57:49,272 wheel INFO adding 'ansible_collections/cisco/iosxr/tox.ini' 2023-04-28 05:57:49,273 wheel INFO adding 'ansible_collections/cisco/iosxr/changelogs/changelog.yaml' 2023-04-28 05:57:49,273 wheel INFO adding 'ansible_collections/cisco/iosxr/changelogs/config.yaml' 2023-04-28 05:57:49,273 wheel INFO adding 'ansible_collections/cisco/iosxr/changelogs/fragments/.keep' 2023-04-28 05:57:49,273 wheel INFO adding 'ansible_collections/cisco/iosxr/meta/runtime.yml' 2023-04-28 05:57:49,274 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/__init__.py' 2023-04-28 05:57:49,274 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/acl_interfaces.py' 2023-04-28 05:57:49,274 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/acls.py' 2023-04-28 05:57:49,274 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/banner.py' 2023-04-28 05:57:49,275 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/bgp.py' 2023-04-28 05:57:49,275 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/bgp_address_family.py' 2023-04-28 05:57:49,275 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/bgp_global.py' 2023-04-28 05:57:49,275 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,275 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/command.py' 2023-04-28 05:57:49,276 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/config.py' 2023-04-28 05:57:49,276 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/facts.py' 2023-04-28 05:57:49,276 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/hostname.py' 2023-04-28 05:57:49,276 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/interface.py' 2023-04-28 05:57:49,277 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/interfaces.py' 2023-04-28 05:57:49,277 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/iosxr.py' 2023-04-28 05:57:49,277 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/l2_interfaces.py' 2023-04-28 05:57:49,277 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/l3_interfaces.py' 2023-04-28 05:57:49,277 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/lacp.py' 2023-04-28 05:57:49,278 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/lacp_interfaces.py' 2023-04-28 05:57:49,278 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/lag_interfaces.py' 2023-04-28 05:57:49,278 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/lldp_global.py' 2023-04-28 05:57:49,278 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/lldp_interfaces.py' 2023-04-28 05:57:49,279 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/logging.py' 2023-04-28 05:57:49,279 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/logging_global.py' 2023-04-28 05:57:49,279 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/netconf.py' 2023-04-28 05:57:49,279 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/ntp_global.py' 2023-04-28 05:57:49,279 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/ospf_interfaces.py' 2023-04-28 05:57:49,280 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/ospfv2.py' 2023-04-28 05:57:49,280 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/ospfv3.py' 2023-04-28 05:57:49,280 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/prefix_lists.py' 2023-04-28 05:57:49,280 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/snmp_server.py' 2023-04-28 05:57:49,280 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/static_routes.py' 2023-04-28 05:57:49,281 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/system.py' 2023-04-28 05:57:49,281 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/action/user.py' 2023-04-28 05:57:49,281 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/cliconf/__init__.py' 2023-04-28 05:57:49,281 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/cliconf/iosxr.py' 2023-04-28 05:57:49,282 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:49,282 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/doc_fragments/iosxr.py' 2023-04-28 05:57:49,282 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/filter/__init__.py' 2023-04-28 05:57:49,282 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/inventory/__init__.py' 2023-04-28 05:57:49,283 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/__init__.py' 2023-04-28 05:57:49,283 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:49,283 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/__init__.py' 2023-04-28 05:57:49,283 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/iosxr.py' 2023-04-28 05:57:49,284 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/__init__.py' 2023-04-28 05:57:49,284 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/__init__.py' 2023-04-28 05:57:49,284 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,285 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/__init__.py' 2023-04-28 05:57:49,285 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/acls.py' 2023-04-28 05:57:49,285 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/__init__.py' 2023-04-28 05:57:49,286 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,286 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/__init__.py' 2023-04-28 05:57:49,286 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/bgp_global.py' 2023-04-28 05:57:49,287 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/__init__.py' 2023-04-28 05:57:49,287 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,287 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/__init__.py' 2023-04-28 05:57:49,288 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/facts.py' 2023-04-28 05:57:49,288 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/__init__.py' 2023-04-28 05:57:49,288 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/hostname.py' 2023-04-28 05:57:49,288 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/__init__.py' 2023-04-28 05:57:49,289 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/interfaces.py' 2023-04-28 05:57:49,289 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/__init__.py' 2023-04-28 05:57:49,289 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,289 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/__init__.py' 2023-04-28 05:57:49,289 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,290 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/__init__.py' 2023-04-28 05:57:49,290 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/lacp.py' 2023-04-28 05:57:49,290 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,290 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,291 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/__init__.py' 2023-04-28 05:57:49,291 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,291 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/__init__.py' 2023-04-28 05:57:49,291 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/lldp_global.py' 2023-04-28 05:57:49,292 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,292 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,292 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/__init__.py' 2023-04-28 05:57:49,292 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/logging_global.py' 2023-04-28 05:57:49,293 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/__init__.py' 2023-04-28 05:57:49,293 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/ntp_global.py' 2023-04-28 05:57:49,293 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,294 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,294 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/__init__.py' 2023-04-28 05:57:49,294 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/ospfv2.py' 2023-04-28 05:57:49,295 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/__init__.py' 2023-04-28 05:57:49,295 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/ospfv3.py' 2023-04-28 05:57:49,296 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/__init__.py' 2023-04-28 05:57:49,296 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/ping.py' 2023-04-28 05:57:49,296 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/__init__.py' 2023-04-28 05:57:49,296 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,297 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/__init__.py' 2023-04-28 05:57:49,297 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/snmp_server.py' 2023-04-28 05:57:49,297 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/__init__.py' 2023-04-28 05:57:49,298 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/static_routes.py' 2023-04-28 05:57:49,298 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/__init__.py' 2023-04-28 05:57:49,298 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/__init__.py' 2023-04-28 05:57:49,298 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,299 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/__init__.py' 2023-04-28 05:57:49,299 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/acls.py' 2023-04-28 05:57:49,299 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/__init__.py' 2023-04-28 05:57:49,299 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,300 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/__init__.py' 2023-04-28 05:57:49,300 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/bgp_global.py' 2023-04-28 05:57:49,300 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/__init__.py' 2023-04-28 05:57:49,301 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,301 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/__init__.py' 2023-04-28 05:57:49,301 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/hostname.py' 2023-04-28 05:57:49,301 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/__init__.py' 2023-04-28 05:57:49,302 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/interfaces.py' 2023-04-28 05:57:49,302 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/__init__.py' 2023-04-28 05:57:49,302 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,302 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/__init__.py' 2023-04-28 05:57:49,303 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,303 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/__init__.py' 2023-04-28 05:57:49,303 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/lacp.py' 2023-04-28 05:57:49,304 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,304 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,304 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/__init__.py' 2023-04-28 05:57:49,304 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,305 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/__init__.py' 2023-04-28 05:57:49,305 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/lldp_global.py' 2023-04-28 05:57:49,305 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,305 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,306 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/__init__.py' 2023-04-28 05:57:49,306 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/logging_global.py' 2023-04-28 05:57:49,306 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/__init__.py' 2023-04-28 05:57:49,306 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/ntp_global.py' 2023-04-28 05:57:49,307 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,307 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,307 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/__init__.py' 2023-04-28 05:57:49,307 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/ospfv2.py' 2023-04-28 05:57:49,308 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/__init__.py' 2023-04-28 05:57:49,308 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/ospfv3.py' 2023-04-28 05:57:49,308 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/__init__.py' 2023-04-28 05:57:49,308 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/ping.py' 2023-04-28 05:57:49,309 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/__init__.py' 2023-04-28 05:57:49,309 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,309 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/__init__.py' 2023-04-28 05:57:49,309 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/snmp_server.py' 2023-04-28 05:57:49,310 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/__init__.py' 2023-04-28 05:57:49,310 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/static_routes.py' 2023-04-28 05:57:49,310 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/__init__.py' 2023-04-28 05:57:49,311 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/facts.py' 2023-04-28 05:57:49,311 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/__init__.py' 2023-04-28 05:57:49,311 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,311 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/__init__.py' 2023-04-28 05:57:49,312 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/acls.py' 2023-04-28 05:57:49,312 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/__init__.py' 2023-04-28 05:57:49,312 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,312 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/__init__.py' 2023-04-28 05:57:49,313 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/bgp_global.py' 2023-04-28 05:57:49,313 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/__init__.py' 2023-04-28 05:57:49,313 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,313 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/__init__.py' 2023-04-28 05:57:49,314 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/hostname.py' 2023-04-28 05:57:49,314 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/__init__.py' 2023-04-28 05:57:49,314 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/interfaces.py' 2023-04-28 05:57:49,314 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/__init__.py' 2023-04-28 05:57:49,315 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,315 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/__init__.py' 2023-04-28 05:57:49,315 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,315 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/__init__.py' 2023-04-28 05:57:49,316 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/lacp.py' 2023-04-28 05:57:49,316 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,316 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,316 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/__init__.py' 2023-04-28 05:57:49,317 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,317 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/__init__.py' 2023-04-28 05:57:49,317 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/base.py' 2023-04-28 05:57:49,317 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/__init__.py' 2023-04-28 05:57:49,318 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/lldp_global.py' 2023-04-28 05:57:49,318 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,318 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,318 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/__init__.py' 2023-04-28 05:57:49,319 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/logging_global.py' 2023-04-28 05:57:49,319 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/__init__.py' 2023-04-28 05:57:49,319 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/ntp_global.py' 2023-04-28 05:57:49,319 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,320 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,320 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/__init__.py' 2023-04-28 05:57:49,320 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/ospfv2.py' 2023-04-28 05:57:49,320 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/__init__.py' 2023-04-28 05:57:49,321 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/ospfv3.py' 2023-04-28 05:57:49,321 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/__init__.py' 2023-04-28 05:57:49,321 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,321 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/__init__.py' 2023-04-28 05:57:49,321 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/snmp_server.py' 2023-04-28 05:57:49,322 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/__init__.py' 2023-04-28 05:57:49,322 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/static_routes.py' 2023-04-28 05:57:49,322 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/__init__.py' 2023-04-28 05:57:49,322 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/module.py' 2023-04-28 05:57:49,323 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/providers.py' 2023-04-28 05:57:49,323 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/__init__.py' 2023-04-28 05:57:49,323 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/__init__.py' 2023-04-28 05:57:49,323 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/__init__.py' 2023-04-28 05:57:49,324 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/address_family.py' 2023-04-28 05:57:49,324 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/neighbors.py' 2023-04-28 05:57:49,324 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/process.py' 2023-04-28 05:57:49,324 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/__init__.py' 2023-04-28 05:57:49,325 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/acl_interfaces.py' 2023-04-28 05:57:49,325 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_address_family.py' 2023-04-28 05:57:49,326 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_global.py' 2023-04-28 05:57:49,326 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,327 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/hostname.py' 2023-04-28 05:57:49,327 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/logging_global.py' 2023-04-28 05:57:49,328 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ntp_global.py' 2023-04-28 05:57:49,328 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospf_interfaces.py' 2023-04-28 05:57:49,329 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospfv2.py' 2023-04-28 05:57:49,330 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ospfv3.py' 2023-04-28 05:57:49,330 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/ping.py' 2023-04-28 05:57:49,330 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/prefix_lists.py' 2023-04-28 05:57:49,331 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/snmp_server.py' 2023-04-28 05:57:49,332 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/__init__.py' 2023-04-28 05:57:49,332 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/utils.py' 2023-04-28 05:57:49,332 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/__init__.py' 2023-04-28 05:57:49,332 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_acl_interfaces.py' 2023-04-28 05:57:49,333 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_acls.py' 2023-04-28 05:57:49,333 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_banner.py' 2023-04-28 05:57:49,334 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp.py' 2023-04-28 05:57:49,334 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_address_family.py' 2023-04-28 05:57:49,334 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_global.py' 2023-04-28 05:57:49,335 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_bgp_neighbor_address_family.py' 2023-04-28 05:57:49,335 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_command.py' 2023-04-28 05:57:49,336 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_config.py' 2023-04-28 05:57:49,336 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_facts.py' 2023-04-28 05:57:49,336 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_hostname.py' 2023-04-28 05:57:49,336 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_interfaces.py' 2023-04-28 05:57:49,337 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_l2_interfaces.py' 2023-04-28 05:57:49,337 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_l3_interfaces.py' 2023-04-28 05:57:49,337 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_lacp.py' 2023-04-28 05:57:49,338 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_lacp_interfaces.py' 2023-04-28 05:57:49,338 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_lag_interfaces.py' 2023-04-28 05:57:49,338 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_lldp_global.py' 2023-04-28 05:57:49,339 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_lldp_interfaces.py' 2023-04-28 05:57:49,339 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_logging.py' 2023-04-28 05:57:49,339 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_logging_global.py' 2023-04-28 05:57:49,340 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_netconf.py' 2023-04-28 05:57:49,340 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_ntp_global.py' 2023-04-28 05:57:49,341 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospf_interfaces.py' 2023-04-28 05:57:49,341 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospfv2.py' 2023-04-28 05:57:49,342 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_ospfv3.py' 2023-04-28 05:57:49,343 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_ping.py' 2023-04-28 05:57:49,343 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_prefix_lists.py' 2023-04-28 05:57:49,343 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_snmp_server.py' 2023-04-28 05:57:49,344 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_static_routes.py' 2023-04-28 05:57:49,344 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_system.py' 2023-04-28 05:57:49,345 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/modules/iosxr_user.py' 2023-04-28 05:57:49,345 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/netconf/__init__.py' 2023-04-28 05:57:49,345 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/netconf/iosxr.py' 2023-04-28 05:57:49,346 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/__init__.py' 2023-04-28 05:57:49,346 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/iosxr.py' 2023-04-28 05:57:49,346 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/__init__.py' 2023-04-28 05:57:49,347 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/ems_grpc_pb2.py' 2023-04-28 05:57:49,347 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/terminal/__init__.py' 2023-04-28 05:57:49,348 wheel INFO adding 'ansible_collections/cisco/iosxr/plugins/terminal/iosxr.py' 2023-04-28 05:57:49,348 wheel INFO adding 'ansible_collections/cisco/ise/FILES.json' 2023-04-28 05:57:49,349 wheel INFO adding 'ansible_collections/cisco/ise/LICENSE' 2023-04-28 05:57:49,350 wheel INFO adding 'ansible_collections/cisco/ise/MANIFEST.json' 2023-04-28 05:57:49,350 wheel INFO adding 'ansible_collections/cisco/ise/Makefile' 2023-04-28 05:57:49,350 wheel INFO adding 'ansible_collections/cisco/ise/README.md' 2023-04-28 05:57:49,350 wheel INFO adding 'ansible_collections/cisco/ise/hosts' 2023-04-28 05:57:49,351 wheel INFO adding 'ansible_collections/cisco/ise/requirements.txt' 2023-04-28 05:57:49,351 wheel INFO adding 'ansible_collections/cisco/ise/changelogs/changelog.yaml' 2023-04-28 05:57:49,351 wheel INFO adding 'ansible_collections/cisco/ise/meta/runtime.yml' 2023-04-28 05:57:49,352 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/aci_settings.yml' 2023-04-28 05:57:49,352 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/active_directory.yml' 2023-04-28 05:57:49,352 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/allowed_protocols.yml' 2023-04-28 05:57:49,352 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/anc_policy.yml' 2023-04-28 05:57:49,353 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/authorization_profile.yml' 2023-04-28 05:57:49,353 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/aws_deployment.yml' 2023-04-28 05:57:49,353 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/azure_deployment.yml' 2023-04-28 05:57:49,353 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/b.yml' 2023-04-28 05:57:49,354 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/backup_create.yml' 2023-04-28 05:57:49,354 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/backup_restore.yml' 2023-04-28 05:57:49,354 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/backup_schedule.yml' 2023-04-28 05:57:49,354 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/byod_portal.yml' 2023-04-28 05:57:49,354 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/certificate_management.yml' 2023-04-28 05:57:49,355 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/certificate_profile.yml' 2023-04-28 05:57:49,355 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/certificates.yml' 2023-04-28 05:57:49,355 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/credentials.template' 2023-04-28 05:57:49,355 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/credentials.yml' 2023-04-28 05:57:49,355 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/csr_export.yml' 2023-04-28 05:57:49,356 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/deployment_info.yml' 2023-04-28 05:57:49,356 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/device_administration_authentication_rules.yml' 2023-04-28 05:57:49,356 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/device_administration_authorization_exception_rules.yml' 2023-04-28 05:57:49,356 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/device_administration_authorization_global_exception_rules.yml' 2023-04-28 05:57:49,357 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/device_administration_authorization_rules.yml' 2023-04-28 05:57:49,357 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/device_administration_network_conditions.yml' 2023-04-28 05:57:49,357 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/device_administration_policy_set.yml' 2023-04-28 05:57:49,357 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/device_administration_time_date_conditions.yml' 2023-04-28 05:57:49,357 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/downloadable_acl.yml' 2023-04-28 05:57:49,358 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/egress_matrix_cell.yml' 2023-04-28 05:57:49,358 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/endpoint.yml' 2023-04-28 05:57:49,358 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/endpoint_certificate.yml' 2023-04-28 05:57:49,358 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/endpoint_group.yml' 2023-04-28 05:57:49,358 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/filter_policy.yml' 2023-04-28 05:57:49,359 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/hosts' 2023-04-28 05:57:49,359 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/identity_group.yml' 2023-04-28 05:57:49,359 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/internal_user.yml' 2023-04-28 05:57:49,359 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/my_device_portal.yml' 2023-04-28 05:57:49,359 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/native_supplicant_profile.yml' 2023-04-28 05:57:49,360 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_authentication_rules.yml' 2023-04-28 05:57:49,360 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_authorization_exception_rules.yml' 2023-04-28 05:57:49,360 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_authorization_global_exception_rules.yml' 2023-04-28 05:57:49,360 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_authorization_rules.yml' 2023-04-28 05:57:49,361 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_conditions.yml' 2023-04-28 05:57:49,361 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_dictionary.yml' 2023-04-28 05:57:49,361 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_dictionary_attribute.yml' 2023-04-28 05:57:49,361 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_network_condition.yml' 2023-04-28 05:57:49,361 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_policy_set.yml' 2023-04-28 05:57:49,362 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_access_time_date_conditions.yml' 2023-04-28 05:57:49,362 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_device.yml' 2023-04-28 05:57:49,362 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_device_group.yml' 2023-04-28 05:57:49,362 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/network_device_group_deparments.yml' 2023-04-28 05:57:49,363 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/personas_deployment.yml' 2023-04-28 05:57:49,363 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/playbookstest.yml' 2023-04-28 05:57:49,363 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/portal_global_setting.yml' 2023-04-28 05:57:49,363 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/portal_theme.yml' 2023-04-28 05:57:49,363 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/profiler-services.yml' 2023-04-28 05:57:49,364 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/radius_server_sequence.yml' 2023-04-28 05:57:49,364 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/sponsor_portal.yml' 2023-04-28 05:57:49,364 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/support_bundle.yml' 2023-04-28 05:57:49,365 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/system_certificate.yml' 2023-04-28 05:57:49,365 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/trustsec_nbarapp.yml' 2023-04-28 05:57:49,365 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/trustsec_sg_vn_mapping.yml' 2023-04-28 05:57:49,365 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/trustsec_vn.yml' 2023-04-28 05:57:49,366 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/trustsec_vn_vlan_mapping.yml' 2023-04-28 05:57:49,366 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/group_vars/ise_servers' 2023-04-28 05:57:49,366 wheel INFO adding 'ansible_collections/cisco/ise/playbooks/vars/device_administration_time_date_conditions.yml' 2023-04-28 05:57:49,367 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/aci_bindings_info.py' 2023-04-28 05:57:49,367 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/aci_settings.py' 2023-04-28 05:57:49,367 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/aci_settings_info.py' 2023-04-28 05:57:49,368 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/aci_test_connectivity.py' 2023-04-28 05:57:49,368 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory.py' 2023-04-28 05:57:49,368 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_add_groups.py' 2023-04-28 05:57:49,368 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_groups_by_domain_info.py' 2023-04-28 05:57:49,369 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_info.py' 2023-04-28 05:57:49,369 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_is_user_member_of_group_info.py' 2023-04-28 05:57:49,369 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_join_domain.py' 2023-04-28 05:57:49,369 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_join_domain_with_all_nodes.py' 2023-04-28 05:57:49,370 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_leave_domain.py' 2023-04-28 05:57:49,370 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_leave_domain_with_all_nodes.py' 2023-04-28 05:57:49,370 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_trusted_domains_info.py' 2023-04-28 05:57:49,370 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/active_directory_user_groups_info.py' 2023-04-28 05:57:49,370 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/admin_user_info.py' 2023-04-28 05:57:49,371 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/allowed_protocols.py' 2023-04-28 05:57:49,371 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/allowed_protocols_info.py' 2023-04-28 05:57:49,371 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_endpoint_apply.py' 2023-04-28 05:57:49,371 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_endpoint_bulk_monitor_status_info.py' 2023-04-28 05:57:49,372 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_endpoint_bulk_request.py' 2023-04-28 05:57:49,372 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_endpoint_clear.py' 2023-04-28 05:57:49,372 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_endpoint_info.py' 2023-04-28 05:57:49,372 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_policy.py' 2023-04-28 05:57:49,373 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_policy_bulk_monitor_status_info.py' 2023-04-28 05:57:49,373 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_policy_bulk_request.py' 2023-04-28 05:57:49,373 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/anc_policy_info.py' 2023-04-28 05:57:49,373 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/authorization_profile.py' 2023-04-28 05:57:49,374 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/authorization_profile_info.py' 2023-04-28 05:57:49,374 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/backup_cancel.py' 2023-04-28 05:57:49,374 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/backup_config.py' 2023-04-28 05:57:49,374 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/backup_last_status_info.py' 2023-04-28 05:57:49,374 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/backup_restore.py' 2023-04-28 05:57:49,375 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/backup_schedule_config.py' 2023-04-28 05:57:49,375 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/backup_schedule_config_update.py' 2023-04-28 05:57:49,375 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/bind_signed_certificate.py' 2023-04-28 05:57:49,375 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/byod_portal.py' 2023-04-28 05:57:49,376 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/byod_portal_info.py' 2023-04-28 05:57:49,376 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/certificate_profile.py' 2023-04-28 05:57:49,376 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/certificate_profile_info.py' 2023-04-28 05:57:49,376 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/certificate_template_info.py' 2023-04-28 05:57:49,377 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/csr_delete.py' 2023-04-28 05:57:49,377 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/csr_export_info.py' 2023-04-28 05:57:49,377 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/csr_generate.py' 2023-04-28 05:57:49,377 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/csr_generate_intermediate_ca.py' 2023-04-28 05:57:49,378 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/csr_info.py' 2023-04-28 05:57:49,378 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/deployment_info.py' 2023-04-28 05:57:49,378 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_authentication_reset_hitcount.py' 2023-04-28 05:57:49,378 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_authentication_rules.py' 2023-04-28 05:57:49,379 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_authentication_rules_info.py' 2023-04-28 05:57:49,379 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_authorization_reset_hitcount.py' 2023-04-28 05:57:49,379 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_authorization_rules.py' 2023-04-28 05:57:49,380 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_authorization_rules_info.py' 2023-04-28 05:57:49,380 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_command_set_info.py' 2023-04-28 05:57:49,380 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_conditions.py' 2023-04-28 05:57:49,380 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_authentication_rule_info.py' 2023-04-28 05:57:49,381 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_authorization_rule_info.py' 2023-04-28 05:57:49,381 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_conditions_for_policy_set_info.py' 2023-04-28 05:57:49,381 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_conditions_info.py' 2023-04-28 05:57:49,381 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_authentication_info.py' 2023-04-28 05:57:49,381 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_authorization_info.py' 2023-04-28 05:57:49,382 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_dictionary_attributes_policy_set_info.py' 2023-04-28 05:57:49,382 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules.py' 2023-04-28 05:57:49,382 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules_info.py' 2023-04-28 05:57:49,382 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_global_exception_rules_reset_hitcount.py' 2023-04-28 05:57:49,383 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_identity_stores_info.py' 2023-04-28 05:57:49,383 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules.py' 2023-04-28 05:57:49,383 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules_info.py' 2023-04-28 05:57:49,383 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_local_exception_rules_reset_hitcount.py' 2023-04-28 05:57:49,384 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_network_conditions.py' 2023-04-28 05:57:49,384 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_network_conditions_info.py' 2023-04-28 05:57:49,384 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_policy_set.py' 2023-04-28 05:57:49,384 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_policy_set_info.py' 2023-04-28 05:57:49,385 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_policy_set_reset_hitcount.py' 2023-04-28 05:57:49,385 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_profiles_info.py' 2023-04-28 05:57:49,385 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_service_names_info.py' 2023-04-28 05:57:49,385 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_time_date_conditions.py' 2023-04-28 05:57:49,386 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/device_administration_time_date_conditions_info.py' 2023-04-28 05:57:49,386 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/downloadable_acl.py' 2023-04-28 05:57:49,386 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/downloadable_acl_info.py' 2023-04-28 05:57:49,386 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/egress_matrix_cell.py' 2023-04-28 05:57:49,387 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_bulk_monitor_status_info.py' 2023-04-28 05:57:49,387 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_bulk_request.py' 2023-04-28 05:57:49,387 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_clear_all.py' 2023-04-28 05:57:49,387 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_clone.py' 2023-04-28 05:57:49,388 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_info.py' 2023-04-28 05:57:49,388 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/egress_matrix_cell_set_all_status.py' 2023-04-28 05:57:49,388 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint.py' 2023-04-28 05:57:49,388 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_bulk_monitor_status_info.py' 2023-04-28 05:57:49,388 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_bulk_request.py' 2023-04-28 05:57:49,389 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_certificate.py' 2023-04-28 05:57:49,389 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_deregister.py' 2023-04-28 05:57:49,389 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_get_rejected_endpoints_info.py' 2023-04-28 05:57:49,389 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_group.py' 2023-04-28 05:57:49,390 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_group_info.py' 2023-04-28 05:57:49,390 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_info.py' 2023-04-28 05:57:49,390 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_register.py' 2023-04-28 05:57:49,390 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/endpoint_release_rejected_endpoint.py' 2023-04-28 05:57:49,391 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/external_radius_server.py' 2023-04-28 05:57:49,391 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/external_radius_server_info.py' 2023-04-28 05:57:49,391 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/filter_policy.py' 2023-04-28 05:57:49,391 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/filter_policy_info.py' 2023-04-28 05:57:49,392 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_location_info.py' 2023-04-28 05:57:49,392 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_smtp_notification_settings.py' 2023-04-28 05:57:49,392 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_smtp_notification_settings_info.py' 2023-04-28 05:57:49,392 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_ssid.py' 2023-04-28 05:57:49,393 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_ssid_info.py' 2023-04-28 05:57:49,393 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_type.py' 2023-04-28 05:57:49,393 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_type_email.py' 2023-04-28 05:57:49,393 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_type_info.py' 2023-04-28 05:57:49,394 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_type_sms.py' 2023-04-28 05:57:49,394 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user.py' 2023-04-28 05:57:49,394 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_approve.py' 2023-04-28 05:57:49,394 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_bulk_monitor_status_info.py' 2023-04-28 05:57:49,395 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_bulk_request.py' 2023-04-28 05:57:49,395 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_change_sponsor_password.py' 2023-04-28 05:57:49,395 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_deny.py' 2023-04-28 05:57:49,395 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_email.py' 2023-04-28 05:57:49,395 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_info.py' 2023-04-28 05:57:49,396 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_reinstate.py' 2023-04-28 05:57:49,396 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_reset_password.py' 2023-04-28 05:57:49,396 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_sms.py' 2023-04-28 05:57:49,396 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/guest_user_suspend.py' 2023-04-28 05:57:49,397 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/hotpatch_info.py' 2023-04-28 05:57:49,397 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/hotpatch_install.py' 2023-04-28 05:57:49,397 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/hotpatch_rollback.py' 2023-04-28 05:57:49,397 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/hotspot_portal.py' 2023-04-28 05:57:49,398 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/hotspot_portal_info.py' 2023-04-28 05:57:49,398 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/id_store_sequence.py' 2023-04-28 05:57:49,398 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/id_store_sequence_info.py' 2023-04-28 05:57:49,398 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/identity_group.py' 2023-04-28 05:57:49,399 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/identity_group_info.py' 2023-04-28 05:57:49,399 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/internal_user.py' 2023-04-28 05:57:49,399 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/internal_user_info.py' 2023-04-28 05:57:49,399 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/ise_root_ca_regenerate.py' 2023-04-28 05:57:49,400 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_connection_type_info.py' 2023-04-28 05:57:49,400 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_eval_license_info.py' 2023-04-28 05:57:49,400 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_feature_to_tier_mapping_info.py' 2023-04-28 05:57:49,400 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_registration_create.py' 2023-04-28 05:57:49,400 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_registration_info.py' 2023-04-28 05:57:49,401 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_smart_state_create.py' 2023-04-28 05:57:49,401 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_smart_state_info.py' 2023-04-28 05:57:49,401 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_tier_state_create.py' 2023-04-28 05:57:49,401 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/licensing_tier_state_info.py' 2023-04-28 05:57:49,402 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_account_status_info.py' 2023-04-28 05:57:49,402 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_athentication_status_info.py' 2023-04-28 05:57:49,402 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_authentication_status_info.py' 2023-04-28 05:57:49,402 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_failure_reasons_info.py' 2023-04-28 05:57:49,402 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_active_count_info.py' 2023-04-28 05:57:49,403 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_active_list_info.py' 2023-04-28 05:57:49,403 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_auth_list_info.py' 2023-04-28 05:57:49,403 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_by_ip_info.py' 2023-04-28 05:57:49,403 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_by_mac_info.py' 2023-04-28 05:57:49,404 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_by_nas_ip_info.py' 2023-04-28 05:57:49,404 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_by_username_info.py' 2023-04-28 05:57:49,404 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_delete_all.py' 2023-04-28 05:57:49,404 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_disconnect_info.py' 2023-04-28 05:57:49,404 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_posture_count_info.py' 2023-04-28 05:57:49,405 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_profiler_count_info.py' 2023-04-28 05:57:49,405 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_session_reauthentication_info.py' 2023-04-28 05:57:49,405 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_sessions_by_session_id_info.py' 2023-04-28 05:57:49,405 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/mnt_version_info.py' 2023-04-28 05:57:49,406 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/my_device_portal.py' 2023-04-28 05:57:49,406 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/my_device_portal_info.py' 2023-04-28 05:57:49,406 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/native_supplicant_profile.py' 2023-04-28 05:57:49,406 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/native_supplicant_profile_info.py' 2023-04-28 05:57:49,407 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules.py' 2023-04-28 05:57:49,407 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules_info.py' 2023-04-28 05:57:49,407 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_authentication_rules_reset_hitcount.py' 2023-04-28 05:57:49,407 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules.py' 2023-04-28 05:57:49,408 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules_info.py' 2023-04-28 05:57:49,408 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_authorization_rules_reset_hitcount.py' 2023-04-28 05:57:49,408 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_conditions.py' 2023-04-28 05:57:49,408 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_authentication_rule_info.py' 2023-04-28 05:57:49,408 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_authorization_rule_info.py' 2023-04-28 05:57:49,409 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_conditions_for_policy_set_info.py' 2023-04-28 05:57:49,409 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_conditions_info.py' 2023-04-28 05:57:49,409 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_dictionary.py' 2023-04-28 05:57:49,409 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attribute.py' 2023-04-28 05:57:49,410 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attribute_info.py' 2023-04-28 05:57:49,410 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_authentication_info.py' 2023-04-28 05:57:49,410 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_authorization_info.py' 2023-04-28 05:57:49,410 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_dictionary_attributes_policy_set_info.py' 2023-04-28 05:57:49,411 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_dictionary_info.py' 2023-04-28 05:57:49,411 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules.py' 2023-04-28 05:57:49,411 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules_info.py' 2023-04-28 05:57:49,411 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_global_exception_rules_reset_hitcount.py' 2023-04-28 05:57:49,412 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_identity_stores_info.py' 2023-04-28 05:57:49,412 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules.py' 2023-04-28 05:57:49,412 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules_info.py' 2023-04-28 05:57:49,412 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_local_exception_rules_reset_hitcounts.py' 2023-04-28 05:57:49,413 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_network_condition.py' 2023-04-28 05:57:49,413 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_network_condition_info.py' 2023-04-28 05:57:49,413 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_policy_set.py' 2023-04-28 05:57:49,413 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_policy_set_info.py' 2023-04-28 05:57:49,413 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_policy_set_reset_hitcount.py' 2023-04-28 05:57:49,414 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_profiles_info.py' 2023-04-28 05:57:49,414 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_security_groups_info.py' 2023-04-28 05:57:49,414 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_service_name_info.py' 2023-04-28 05:57:49,414 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_time_date_conditions.py' 2023-04-28 05:57:49,415 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_access_time_date_conditions_info.py' 2023-04-28 05:57:49,415 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_device.py' 2023-04-28 05:57:49,415 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_device_bulk_monitor_status_info.py' 2023-04-28 05:57:49,415 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_device_bulk_request.py' 2023-04-28 05:57:49,416 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_device_group.py' 2023-04-28 05:57:49,416 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_device_group_info.py' 2023-04-28 05:57:49,416 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/network_device_info.py' 2023-04-28 05:57:49,416 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_deployment.py' 2023-04-28 05:57:49,417 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_deployment_info.py' 2023-04-28 05:57:49,417 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_deployment_sync.py' 2023-04-28 05:57:49,417 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_group.py' 2023-04-28 05:57:49,417 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_group_info.py' 2023-04-28 05:57:49,418 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_group_node_create.py' 2023-04-28 05:57:49,418 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_group_node_delete.py' 2023-04-28 05:57:49,418 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_group_node_info.py' 2023-04-28 05:57:49,418 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_info.py' 2023-04-28 05:57:49,418 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_primary_to_standalone.py' 2023-04-28 05:57:49,419 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_promotion.py' 2023-04-28 05:57:49,419 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_replication_status_info.py' 2023-04-28 05:57:49,419 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_secondary_to_primary.py' 2023-04-28 05:57:49,419 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_services_interfaces_info.py' 2023-04-28 05:57:49,420 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_services_profiler_probe_config.py' 2023-04-28 05:57:49,420 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_services_profiler_probe_config_info.py' 2023-04-28 05:57:49,420 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_services_sxp_interfaces.py' 2023-04-28 05:57:49,420 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_services_sxp_interfaces_info.py' 2023-04-28 05:57:49,421 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_standalone_to_primary.py' 2023-04-28 05:57:49,421 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/node_sync.py' 2023-04-28 05:57:49,421 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pan_ha.py' 2023-04-28 05:57:49,421 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pan_ha_info.py' 2023-04-28 05:57:49,422 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pan_ha_update.py' 2023-04-28 05:57:49,422 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/patch_info.py' 2023-04-28 05:57:49,422 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/patch_install.py' 2023-04-28 05:57:49,422 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/patch_rollback.py' 2023-04-28 05:57:49,423 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/personas_check_standalone.py' 2023-04-28 05:57:49,423 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/personas_export_certs.py' 2023-04-28 05:57:49,423 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/personas_promote_primary.py' 2023-04-28 05:57:49,423 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/personas_register_node.py' 2023-04-28 05:57:49,423 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/personas_update_roles_services.py' 2023-04-28 05:57:49,424 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/portal_global_setting.py' 2023-04-28 05:57:49,424 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/portal_global_setting_info.py' 2023-04-28 05:57:49,424 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/portal_info.py' 2023-04-28 05:57:49,424 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/portal_theme.py' 2023-04-28 05:57:49,425 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/portal_theme_info.py' 2023-04-28 05:57:49,425 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/profiler_profile_info.py' 2023-04-28 05:57:49,425 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/proxy_connection_settings.py' 2023-04-28 05:57:49,425 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/proxy_connection_settings_info.py' 2023-04-28 05:57:49,426 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/px_grid_node_approve.py' 2023-04-28 05:57:49,426 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/px_grid_node_delete.py' 2023-04-28 05:57:49,426 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/px_grid_node_info.py' 2023-04-28 05:57:49,426 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/px_grid_settings_auto_approve.py' 2023-04-28 05:57:49,427 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_access_secret.py' 2023-04-28 05:57:49,427 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_account_activate.py' 2023-04-28 05:57:49,427 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_account_create.py' 2023-04-28 05:57:49,427 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_authorization.py' 2023-04-28 05:57:49,427 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_bindings_info.py' 2023-04-28 05:57:49,428 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_egress_matrices_info.py' 2023-04-28 05:57:49,428 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_egress_policies_info.py' 2023-04-28 05:57:49,428 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_endpoint_by_mac_info.py' 2023-04-28 05:57:49,428 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_by_os_type_info.py' 2023-04-28 05:57:49,429 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_by_type_info.py' 2023-04-28 05:57:49,429 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_endpoints_info.py' 2023-04-28 05:57:49,429 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_failures_info.py' 2023-04-28 05:57:49,429 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_healths_info.py' 2023-04-28 05:57:49,429 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_node_approve.py' 2023-04-28 05:57:49,430 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_node_delete.py' 2023-04-28 05:57:49,430 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_node_info.py' 2023-04-28 05:57:49,430 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_performances_info.py' 2023-04-28 05:57:49,430 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_profiles_info.py' 2023-04-28 05:57:49,431 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_security_group_acls_info.py' 2023-04-28 05:57:49,431 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_security_groups_info.py' 2023-04-28 05:57:49,431 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_service_lookup.py' 2023-04-28 05:57:49,431 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_service_register.py' 2023-04-28 05:57:49,431 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_service_reregister.py' 2023-04-28 05:57:49,432 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_service_unregister.py' 2023-04-28 05:57:49,432 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_session_by_ip_info.py' 2023-04-28 05:57:49,432 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_session_by_mac_info.py' 2023-04-28 05:57:49,432 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_session_for_recovery_info.py' 2023-04-28 05:57:49,432 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_sessions_info.py' 2023-04-28 05:57:49,433 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_settings_auto_approve.py' 2023-04-28 05:57:49,433 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_user_group_by_username_info.py' 2023-04-28 05:57:49,433 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/pxgrid_user_groups_info.py' 2023-04-28 05:57:49,433 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/radius_server_sequence.py' 2023-04-28 05:57:49,434 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/radius_server_sequence_info.py' 2023-04-28 05:57:49,434 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/renew_certificate.py' 2023-04-28 05:57:49,434 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/repository.py' 2023-04-28 05:57:49,434 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/repository_files_info.py' 2023-04-28 05:57:49,435 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/repository_info.py' 2023-04-28 05:57:49,435 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/resource_version_info.py' 2023-04-28 05:57:49,435 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/rest_id_store.py' 2023-04-28 05:57:49,435 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/rest_id_store_info.py' 2023-04-28 05:57:49,436 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/self_registered_portal.py' 2023-04-28 05:57:49,436 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/self_registered_portal_info.py' 2023-04-28 05:57:49,436 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/selfsigned_certificate_generate.py' 2023-04-28 05:57:49,436 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/session_service_node_info.py' 2023-04-28 05:57:49,437 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_acl.py' 2023-04-28 05:57:49,437 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_acl_bulk_monitor_status_info.py' 2023-04-28 05:57:49,437 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_acl_bulk_request.py' 2023-04-28 05:57:49,437 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_acl_info.py' 2023-04-28 05:57:49,438 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping.py' 2023-04-28 05:57:49,438 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_bulk_monitor_status_info.py' 2023-04-28 05:57:49,438 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_bulk_request.py' 2023-04-28 05:57:49,438 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy.py' 2023-04-28 05:57:49,439 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy_all.py' 2023-04-28 05:57:49,439 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_deploy_status_info.py' 2023-04-28 05:57:49,439 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_group.py' 2023-04-28 05:57:49,439 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_group_bulk_monitor_status_info.py' 2023-04-28 05:57:49,439 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_group_bulk_request.py' 2023-04-28 05:57:49,440 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy.py' 2023-04-28 05:57:49,440 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy_all.py' 2023-04-28 05:57:49,440 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_group_deploy_status_info.py' 2023-04-28 05:57:49,440 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_group_info.py' 2023-04-28 05:57:49,441 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_mapping_info.py' 2023-04-28 05:57:49,441 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan.py' 2023-04-28 05:57:49,441 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_bulk_monitor_status_info.py' 2023-04-28 05:57:49,441 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_bulk_request.py' 2023-04-28 05:57:49,442 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sg_to_vn_to_vlan_info.py' 2023-04-28 05:57:49,442 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sgt.py' 2023-04-28 05:57:49,442 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sgt_bulk_monitor_status_info.py' 2023-04-28 05:57:49,442 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sgt_bulk_request.py' 2023-04-28 05:57:49,443 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sgt_info.py' 2023-04-28 05:57:49,443 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sms_provider_info.py' 2023-04-28 05:57:49,443 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sponsor_group.py' 2023-04-28 05:57:49,443 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sponsor_group_info.py' 2023-04-28 05:57:49,444 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sponsor_group_member_info.py' 2023-04-28 05:57:49,444 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sponsor_portal.py' 2023-04-28 05:57:49,444 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sponsor_portal_info.py' 2023-04-28 05:57:49,444 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sponsored_guest_portal.py' 2023-04-28 05:57:49,445 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sponsored_guest_portal_info.py' 2023-04-28 05:57:49,445 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/support_bundle.py' 2023-04-28 05:57:49,445 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/support_bundle_download.py' 2023-04-28 05:57:49,445 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/support_bundle_status_info.py' 2023-04-28 05:57:49,446 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_connections.py' 2023-04-28 05:57:49,446 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_connections_bulk_monitor_status_info.py' 2023-04-28 05:57:49,446 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_connections_bulk_request.py' 2023-04-28 05:57:49,446 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_connections_info.py' 2023-04-28 05:57:49,447 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_local_bindings.py' 2023-04-28 05:57:49,447 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_bulk_monitor_status_info.py' 2023-04-28 05:57:49,447 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_bulk_request.py' 2023-04-28 05:57:49,447 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_local_bindings_info.py' 2023-04-28 05:57:49,447 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_vpns.py' 2023-04-28 05:57:49,448 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_vpns_bulk_monitor_status_info.py' 2023-04-28 05:57:49,448 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_vpns_bulk_request.py' 2023-04-28 05:57:49,448 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/sxp_vpns_info.py' 2023-04-28 05:57:49,448 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/system_certificate.py' 2023-04-28 05:57:49,449 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/system_certificate_create.py' 2023-04-28 05:57:49,449 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/system_certificate_export_info.py' 2023-04-28 05:57:49,449 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/system_certificate_import.py' 2023-04-28 05:57:49,449 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/system_certificate_info.py' 2023-04-28 05:57:49,450 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/system_config_version_info.py' 2023-04-28 05:57:49,450 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_command_sets.py' 2023-04-28 05:57:49,450 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_command_sets_info.py' 2023-04-28 05:57:49,450 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_external_servers.py' 2023-04-28 05:57:49,451 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_external_servers_info.py' 2023-04-28 05:57:49,451 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_profile.py' 2023-04-28 05:57:49,451 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_profile_info.py' 2023-04-28 05:57:49,451 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_server_sequence.py' 2023-04-28 05:57:49,452 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tacacs_server_sequence_info.py' 2023-04-28 05:57:49,452 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/tasks_info.py' 2023-04-28 05:57:49,452 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/telemetry_info.py' 2023-04-28 05:57:49,452 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/threat_vulnerabilities_clear.py' 2023-04-28 05:57:49,453 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/transport_gateway_settings.py' 2023-04-28 05:57:49,453 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/transport_gateway_settings_info.py' 2023-04-28 05:57:49,453 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trusted_certificate.py' 2023-04-28 05:57:49,453 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trusted_certificate_export_info.py' 2023-04-28 05:57:49,454 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trusted_certificate_import.py' 2023-04-28 05:57:49,454 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trusted_certificate_info.py' 2023-04-28 05:57:49,454 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_nbar_app.py' 2023-04-28 05:57:49,454 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_nbar_app_info.py' 2023-04-28 05:57:49,455 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping.py' 2023-04-28 05:57:49,455 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_create.py' 2023-04-28 05:57:49,455 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_delete.py' 2023-04-28 05:57:49,455 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_bulk_update.py' 2023-04-28 05:57:49,455 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_sg_vn_mapping_info.py' 2023-04-28 05:57:49,456 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn.py' 2023-04-28 05:57:49,456 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_create.py' 2023-04-28 05:57:49,456 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_delete.py' 2023-04-28 05:57:49,456 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_bulk_update.py' 2023-04-28 05:57:49,457 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_info.py' 2023-04-28 05:57:49,457 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping.py' 2023-04-28 05:57:49,457 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_create.py' 2023-04-28 05:57:49,457 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_delete.py' 2023-04-28 05:57:49,458 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_bulk_update.py' 2023-04-28 05:57:49,458 wheel INFO adding 'ansible_collections/cisco/ise/plugins/action/trustsec_vn_vlan_mapping_info.py' 2023-04-28 05:57:49,458 wheel INFO adding 'ansible_collections/cisco/ise/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:49,458 wheel INFO adding 'ansible_collections/cisco/ise/plugins/doc_fragments/module.py' 2023-04-28 05:57:49,459 wheel INFO adding 'ansible_collections/cisco/ise/plugins/doc_fragments/module_info.py' 2023-04-28 05:57:49,459 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/__init__.py' 2023-04-28 05:57:49,460 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/aci_bindings_info.py' 2023-04-28 05:57:49,460 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/aci_settings.py' 2023-04-28 05:57:49,460 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/aci_settings_info.py' 2023-04-28 05:57:49,460 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/aci_test_connectivity.py' 2023-04-28 05:57:49,461 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory.py' 2023-04-28 05:57:49,461 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_add_groups.py' 2023-04-28 05:57:49,461 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_groups_by_domain_info.py' 2023-04-28 05:57:49,461 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_info.py' 2023-04-28 05:57:49,462 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_is_user_member_of_group_info.py' 2023-04-28 05:57:49,462 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_join_domain.py' 2023-04-28 05:57:49,462 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_join_domain_with_all_nodes.py' 2023-04-28 05:57:49,462 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_leave_domain.py' 2023-04-28 05:57:49,462 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_leave_domain_with_all_nodes.py' 2023-04-28 05:57:49,463 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_trusted_domains_info.py' 2023-04-28 05:57:49,463 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/active_directory_user_groups_info.py' 2023-04-28 05:57:49,463 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/admin_user_info.py' 2023-04-28 05:57:49,463 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/allowed_protocols.py' 2023-04-28 05:57:49,464 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/allowed_protocols_info.py' 2023-04-28 05:57:49,464 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_endpoint_apply.py' 2023-04-28 05:57:49,464 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_endpoint_bulk_monitor_status_info.py' 2023-04-28 05:57:49,464 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_endpoint_bulk_request.py' 2023-04-28 05:57:49,465 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_endpoint_clear.py' 2023-04-28 05:57:49,465 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_endpoint_info.py' 2023-04-28 05:57:49,465 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_policy.py' 2023-04-28 05:57:49,465 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_policy_bulk_monitor_status_info.py' 2023-04-28 05:57:49,466 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_policy_bulk_request.py' 2023-04-28 05:57:49,466 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/anc_policy_info.py' 2023-04-28 05:57:49,466 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/authorization_profile.py' 2023-04-28 05:57:49,466 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/authorization_profile_info.py' 2023-04-28 05:57:49,467 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/backup_cancel.py' 2023-04-28 05:57:49,467 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/backup_config.py' 2023-04-28 05:57:49,467 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/backup_last_status_info.py' 2023-04-28 05:57:49,467 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/backup_restore.py' 2023-04-28 05:57:49,467 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/backup_schedule_config.py' 2023-04-28 05:57:49,468 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/backup_schedule_config_update.py' 2023-04-28 05:57:49,468 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/bind_signed_certificate.py' 2023-04-28 05:57:49,468 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/byod_portal.py' 2023-04-28 05:57:49,468 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/byod_portal_info.py' 2023-04-28 05:57:49,469 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/certificate_profile.py' 2023-04-28 05:57:49,469 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/certificate_profile_info.py' 2023-04-28 05:57:49,469 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/certificate_template_info.py' 2023-04-28 05:57:49,469 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/csr_delete.py' 2023-04-28 05:57:49,470 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/csr_export_info.py' 2023-04-28 05:57:49,470 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/csr_generate.py' 2023-04-28 05:57:49,470 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/csr_generate_intermediate_ca.py' 2023-04-28 05:57:49,470 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/csr_info.py' 2023-04-28 05:57:49,471 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/deployment_info.py' 2023-04-28 05:57:49,471 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_reset_hitcount.py' 2023-04-28 05:57:49,471 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_rules.py' 2023-04-28 05:57:49,471 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_authentication_rules_info.py' 2023-04-28 05:57:49,472 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_reset_hitcount.py' 2023-04-28 05:57:49,472 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_rules.py' 2023-04-28 05:57:49,472 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_authorization_rules_info.py' 2023-04-28 05:57:49,472 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_command_set_info.py' 2023-04-28 05:57:49,473 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_conditions.py' 2023-04-28 05:57:49,473 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_authentication_rule_info.py' 2023-04-28 05:57:49,473 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_authorization_rule_info.py' 2023-04-28 05:57:49,473 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_for_policy_set_info.py' 2023-04-28 05:57:49,474 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_conditions_info.py' 2023-04-28 05:57:49,474 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_authentication_info.py' 2023-04-28 05:57:49,474 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_authorization_info.py' 2023-04-28 05:57:49,474 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_dictionary_attributes_policy_set_info.py' 2023-04-28 05:57:49,475 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules.py' 2023-04-28 05:57:49,475 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules_info.py' 2023-04-28 05:57:49,475 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_global_exception_rules_reset_hitcount.py' 2023-04-28 05:57:49,475 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_identity_stores_info.py' 2023-04-28 05:57:49,476 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules.py' 2023-04-28 05:57:49,476 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules_info.py' 2023-04-28 05:57:49,476 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_local_exception_rules_reset_hitcount.py' 2023-04-28 05:57:49,476 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_network_conditions.py' 2023-04-28 05:57:49,477 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_network_conditions_info.py' 2023-04-28 05:57:49,477 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set.py' 2023-04-28 05:57:49,477 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set_info.py' 2023-04-28 05:57:49,477 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_policy_set_reset_hitcount.py' 2023-04-28 05:57:49,478 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_profiles_info.py' 2023-04-28 05:57:49,478 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_service_names_info.py' 2023-04-28 05:57:49,478 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_time_date_conditions.py' 2023-04-28 05:57:49,478 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/device_administration_time_date_conditions_info.py' 2023-04-28 05:57:49,479 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/downloadable_acl.py' 2023-04-28 05:57:49,479 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/downloadable_acl_info.py' 2023-04-28 05:57:49,479 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell.py' 2023-04-28 05:57:49,479 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_bulk_monitor_status_info.py' 2023-04-28 05:57:49,479 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_bulk_request.py' 2023-04-28 05:57:49,480 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_clear_all.py' 2023-04-28 05:57:49,480 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_clone.py' 2023-04-28 05:57:49,480 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_info.py' 2023-04-28 05:57:49,480 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/egress_matrix_cell_set_all_status.py' 2023-04-28 05:57:49,481 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint.py' 2023-04-28 05:57:49,481 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_bulk_monitor_status_info.py' 2023-04-28 05:57:49,481 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_bulk_request.py' 2023-04-28 05:57:49,481 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_certificate.py' 2023-04-28 05:57:49,482 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_deregister.py' 2023-04-28 05:57:49,482 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_get_rejected_endpoints_info.py' 2023-04-28 05:57:49,482 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_group.py' 2023-04-28 05:57:49,482 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_group_info.py' 2023-04-28 05:57:49,482 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_info.py' 2023-04-28 05:57:49,483 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_register.py' 2023-04-28 05:57:49,483 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/endpoint_release_rejected_endpoint.py' 2023-04-28 05:57:49,483 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/external_radius_server.py' 2023-04-28 05:57:49,483 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/external_radius_server_info.py' 2023-04-28 05:57:49,484 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/filter_policy.py' 2023-04-28 05:57:49,484 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/filter_policy_info.py' 2023-04-28 05:57:49,484 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_location_info.py' 2023-04-28 05:57:49,484 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_smtp_notification_settings.py' 2023-04-28 05:57:49,485 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_smtp_notification_settings_info.py' 2023-04-28 05:57:49,485 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_ssid.py' 2023-04-28 05:57:49,485 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_ssid_info.py' 2023-04-28 05:57:49,485 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_type.py' 2023-04-28 05:57:49,485 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_type_email.py' 2023-04-28 05:57:49,486 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_type_info.py' 2023-04-28 05:57:49,486 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_type_sms.py' 2023-04-28 05:57:49,486 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user.py' 2023-04-28 05:57:49,486 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_approve.py' 2023-04-28 05:57:49,487 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_bulk_monitor_status_info.py' 2023-04-28 05:57:49,487 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_bulk_request.py' 2023-04-28 05:57:49,487 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_change_sponsor_password.py' 2023-04-28 05:57:49,487 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_deny.py' 2023-04-28 05:57:49,487 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_email.py' 2023-04-28 05:57:49,488 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_info.py' 2023-04-28 05:57:49,488 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_reinstate.py' 2023-04-28 05:57:49,488 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_reset_password.py' 2023-04-28 05:57:49,488 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_sms.py' 2023-04-28 05:57:49,489 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/guest_user_suspend.py' 2023-04-28 05:57:49,489 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/hotpatch_info.py' 2023-04-28 05:57:49,489 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/hotpatch_install.py' 2023-04-28 05:57:49,489 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/hotpatch_rollback.py' 2023-04-28 05:57:49,490 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/hotspot_portal.py' 2023-04-28 05:57:49,490 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/hotspot_portal_info.py' 2023-04-28 05:57:49,490 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/id_store_sequence.py' 2023-04-28 05:57:49,490 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/id_store_sequence_info.py' 2023-04-28 05:57:49,491 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/identity_group.py' 2023-04-28 05:57:49,491 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/identity_group_info.py' 2023-04-28 05:57:49,491 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/internal_user.py' 2023-04-28 05:57:49,491 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/internal_user_info.py' 2023-04-28 05:57:49,492 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/ise_root_ca_regenerate.py' 2023-04-28 05:57:49,492 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_connection_type_info.py' 2023-04-28 05:57:49,492 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_eval_license_info.py' 2023-04-28 05:57:49,492 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_feature_to_tier_mapping_info.py' 2023-04-28 05:57:49,492 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_registration_create.py' 2023-04-28 05:57:49,493 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_registration_info.py' 2023-04-28 05:57:49,493 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_smart_state_create.py' 2023-04-28 05:57:49,493 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_smart_state_info.py' 2023-04-28 05:57:49,493 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_tier_state_create.py' 2023-04-28 05:57:49,493 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/licensing_tier_state_info.py' 2023-04-28 05:57:49,494 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_account_status_info.py' 2023-04-28 05:57:49,494 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_athentication_status_info.py' 2023-04-28 05:57:49,494 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_authentication_status_info.py' 2023-04-28 05:57:49,494 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_failure_reasons_info.py' 2023-04-28 05:57:49,495 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_active_count_info.py' 2023-04-28 05:57:49,495 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_active_list_info.py' 2023-04-28 05:57:49,495 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_auth_list_info.py' 2023-04-28 05:57:49,495 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_by_ip_info.py' 2023-04-28 05:57:49,495 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_by_mac_info.py' 2023-04-28 05:57:49,496 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_by_nas_ip_info.py' 2023-04-28 05:57:49,496 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_by_username_info.py' 2023-04-28 05:57:49,496 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_delete_all.py' 2023-04-28 05:57:49,496 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_disconnect_info.py' 2023-04-28 05:57:49,496 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_posture_count_info.py' 2023-04-28 05:57:49,497 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_profiler_count_info.py' 2023-04-28 05:57:49,497 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_session_reauthentication_info.py' 2023-04-28 05:57:49,497 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_sessions_by_session_id_info.py' 2023-04-28 05:57:49,497 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/mnt_version_info.py' 2023-04-28 05:57:49,498 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/my_device_portal.py' 2023-04-28 05:57:49,498 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/my_device_portal_info.py' 2023-04-28 05:57:49,498 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/native_supplicant_profile.py' 2023-04-28 05:57:49,498 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/native_supplicant_profile_info.py' 2023-04-28 05:57:49,499 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules.py' 2023-04-28 05:57:49,499 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules_info.py' 2023-04-28 05:57:49,499 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_authentication_rules_reset_hitcount.py' 2023-04-28 05:57:49,499 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules.py' 2023-04-28 05:57:49,500 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules_info.py' 2023-04-28 05:57:49,500 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_authorization_rules_reset_hitcount.py' 2023-04-28 05:57:49,500 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_conditions.py' 2023-04-28 05:57:49,500 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_authentication_rule_info.py' 2023-04-28 05:57:49,501 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_authorization_rule_info.py' 2023-04-28 05:57:49,501 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_conditions_for_policy_set_info.py' 2023-04-28 05:57:49,501 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_conditions_info.py' 2023-04-28 05:57:49,501 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_dictionary.py' 2023-04-28 05:57:49,502 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attribute.py' 2023-04-28 05:57:49,502 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attribute_info.py' 2023-04-28 05:57:49,502 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_authentication_info.py' 2023-04-28 05:57:49,502 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_authorization_info.py' 2023-04-28 05:57:49,502 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_attributes_policy_set_info.py' 2023-04-28 05:57:49,503 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_dictionary_info.py' 2023-04-28 05:57:49,503 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules.py' 2023-04-28 05:57:49,503 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules_info.py' 2023-04-28 05:57:49,503 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_global_exception_rules_reset_hitcount.py' 2023-04-28 05:57:49,504 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_identity_stores_info.py' 2023-04-28 05:57:49,504 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules.py' 2023-04-28 05:57:49,505 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules_info.py' 2023-04-28 05:57:49,505 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_local_exception_rules_reset_hitcounts.py' 2023-04-28 05:57:49,505 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_network_condition.py' 2023-04-28 05:57:49,505 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_network_condition_info.py' 2023-04-28 05:57:49,506 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_policy_set.py' 2023-04-28 05:57:49,506 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_policy_set_info.py' 2023-04-28 05:57:49,506 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_policy_set_reset_hitcount.py' 2023-04-28 05:57:49,506 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_profiles_info.py' 2023-04-28 05:57:49,506 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_security_groups_info.py' 2023-04-28 05:57:49,507 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_service_name_info.py' 2023-04-28 05:57:49,507 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_time_date_conditions.py' 2023-04-28 05:57:49,507 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_access_time_date_conditions_info.py' 2023-04-28 05:57:49,507 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_device.py' 2023-04-28 05:57:49,508 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_device_bulk_monitor_status_info.py' 2023-04-28 05:57:49,508 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_device_bulk_request.py' 2023-04-28 05:57:49,508 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_device_group.py' 2023-04-28 05:57:49,508 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_device_group_info.py' 2023-04-28 05:57:49,509 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/network_device_info.py' 2023-04-28 05:57:49,509 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_deployment.py' 2023-04-28 05:57:49,509 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_deployment_info.py' 2023-04-28 05:57:49,509 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_deployment_sync.py' 2023-04-28 05:57:49,510 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_group.py' 2023-04-28 05:57:49,510 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_group_info.py' 2023-04-28 05:57:49,510 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_group_node_create.py' 2023-04-28 05:57:49,510 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_group_node_delete.py' 2023-04-28 05:57:49,510 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_group_node_info.py' 2023-04-28 05:57:49,511 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_info.py' 2023-04-28 05:57:49,511 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_primary_to_standalone.py' 2023-04-28 05:57:49,511 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_promotion.py' 2023-04-28 05:57:49,511 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_replication_status_info.py' 2023-04-28 05:57:49,512 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_secondary_to_primary.py' 2023-04-28 05:57:49,512 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_services_interfaces_info.py' 2023-04-28 05:57:49,512 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_services_profiler_probe_config.py' 2023-04-28 05:57:49,512 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_services_profiler_probe_config_info.py' 2023-04-28 05:57:49,512 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_services_sxp_interfaces.py' 2023-04-28 05:57:49,513 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_services_sxp_interfaces_info.py' 2023-04-28 05:57:49,513 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_standalone_to_primary.py' 2023-04-28 05:57:49,513 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/node_sync.py' 2023-04-28 05:57:49,513 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pan_ha.py' 2023-04-28 05:57:49,514 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pan_ha_info.py' 2023-04-28 05:57:49,514 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pan_ha_update.py' 2023-04-28 05:57:49,514 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/patch_info.py' 2023-04-28 05:57:49,514 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/patch_install.py' 2023-04-28 05:57:49,514 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/patch_rollback.py' 2023-04-28 05:57:49,515 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/personas_check_standalone.py' 2023-04-28 05:57:49,515 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/personas_export_certs.py' 2023-04-28 05:57:49,515 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/personas_promote_primary.py' 2023-04-28 05:57:49,515 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/personas_register_node.py' 2023-04-28 05:57:49,516 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/personas_update_roles_services.py' 2023-04-28 05:57:49,516 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/portal_global_setting.py' 2023-04-28 05:57:49,516 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/portal_global_setting_info.py' 2023-04-28 05:57:49,516 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/portal_info.py' 2023-04-28 05:57:49,516 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/portal_theme.py' 2023-04-28 05:57:49,517 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/portal_theme_info.py' 2023-04-28 05:57:49,517 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/profiler_profile_info.py' 2023-04-28 05:57:49,517 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/proxy_connection_settings.py' 2023-04-28 05:57:49,517 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/proxy_connection_settings_info.py' 2023-04-28 05:57:49,518 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/px_grid_node_approve.py' 2023-04-28 05:57:49,518 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/px_grid_node_delete.py' 2023-04-28 05:57:49,518 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/px_grid_node_info.py' 2023-04-28 05:57:49,518 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/px_grid_settings_auto_approve.py' 2023-04-28 05:57:49,518 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_access_secret.py' 2023-04-28 05:57:49,519 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_account_activate.py' 2023-04-28 05:57:49,519 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_account_create.py' 2023-04-28 05:57:49,519 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_authorization.py' 2023-04-28 05:57:49,519 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_bindings_info.py' 2023-04-28 05:57:49,519 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_egress_matrices_info.py' 2023-04-28 05:57:49,520 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_egress_policies_info.py' 2023-04-28 05:57:49,520 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoint_by_mac_info.py' 2023-04-28 05:57:49,520 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_by_os_type_info.py' 2023-04-28 05:57:49,520 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_by_type_info.py' 2023-04-28 05:57:49,521 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_endpoints_info.py' 2023-04-28 05:57:49,521 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_failures_info.py' 2023-04-28 05:57:49,521 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_healths_info.py' 2023-04-28 05:57:49,521 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_node_approve.py' 2023-04-28 05:57:49,521 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_node_delete.py' 2023-04-28 05:57:49,522 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_node_info.py' 2023-04-28 05:57:49,522 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_performances_info.py' 2023-04-28 05:57:49,522 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_profiles_info.py' 2023-04-28 05:57:49,522 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_security_group_acls_info.py' 2023-04-28 05:57:49,522 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_security_groups_info.py' 2023-04-28 05:57:49,523 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_service_lookup.py' 2023-04-28 05:57:49,523 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_service_register.py' 2023-04-28 05:57:49,523 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_service_reregister.py' 2023-04-28 05:57:49,523 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_service_unregister.py' 2023-04-28 05:57:49,523 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_session_by_ip_info.py' 2023-04-28 05:57:49,524 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_session_by_mac_info.py' 2023-04-28 05:57:49,524 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_session_for_recovery_info.py' 2023-04-28 05:57:49,524 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_sessions_info.py' 2023-04-28 05:57:49,524 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_settings_auto_approve.py' 2023-04-28 05:57:49,525 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_user_group_by_username_info.py' 2023-04-28 05:57:49,525 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/pxgrid_user_groups_info.py' 2023-04-28 05:57:49,525 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/radius_server_sequence.py' 2023-04-28 05:57:49,525 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/radius_server_sequence_info.py' 2023-04-28 05:57:49,525 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/renew_certificate.py' 2023-04-28 05:57:49,526 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/repository.py' 2023-04-28 05:57:49,526 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/repository_files_info.py' 2023-04-28 05:57:49,526 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/repository_info.py' 2023-04-28 05:57:49,526 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/resource_version_info.py' 2023-04-28 05:57:49,527 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/rest_id_store.py' 2023-04-28 05:57:49,527 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/rest_id_store_info.py' 2023-04-28 05:57:49,527 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/self_registered_portal.py' 2023-04-28 05:57:49,528 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/self_registered_portal_info.py' 2023-04-28 05:57:49,528 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/selfsigned_certificate_generate.py' 2023-04-28 05:57:49,528 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/session_service_node_info.py' 2023-04-28 05:57:49,528 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_acl.py' 2023-04-28 05:57:49,529 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_acl_bulk_monitor_status_info.py' 2023-04-28 05:57:49,529 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_acl_bulk_request.py' 2023-04-28 05:57:49,529 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_acl_info.py' 2023-04-28 05:57:49,529 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping.py' 2023-04-28 05:57:49,530 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_bulk_monitor_status_info.py' 2023-04-28 05:57:49,530 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_bulk_request.py' 2023-04-28 05:57:49,530 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy.py' 2023-04-28 05:57:49,530 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy_all.py' 2023-04-28 05:57:49,531 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_deploy_status_info.py' 2023-04-28 05:57:49,531 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_group.py' 2023-04-28 05:57:49,531 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_bulk_monitor_status_info.py' 2023-04-28 05:57:49,531 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_bulk_request.py' 2023-04-28 05:57:49,531 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy.py' 2023-04-28 05:57:49,532 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy_all.py' 2023-04-28 05:57:49,532 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_deploy_status_info.py' 2023-04-28 05:57:49,532 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_group_info.py' 2023-04-28 05:57:49,532 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_mapping_info.py' 2023-04-28 05:57:49,533 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan.py' 2023-04-28 05:57:49,533 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_bulk_monitor_status_info.py' 2023-04-28 05:57:49,533 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_bulk_request.py' 2023-04-28 05:57:49,533 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sg_to_vn_to_vlan_info.py' 2023-04-28 05:57:49,533 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sgt.py' 2023-04-28 05:57:49,534 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sgt_bulk_monitor_status_info.py' 2023-04-28 05:57:49,534 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sgt_bulk_request.py' 2023-04-28 05:57:49,534 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sgt_info.py' 2023-04-28 05:57:49,534 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sms_provider_info.py' 2023-04-28 05:57:49,535 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sponsor_group.py' 2023-04-28 05:57:49,535 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sponsor_group_info.py' 2023-04-28 05:57:49,535 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sponsor_group_member_info.py' 2023-04-28 05:57:49,535 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sponsor_portal.py' 2023-04-28 05:57:49,536 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sponsor_portal_info.py' 2023-04-28 05:57:49,536 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sponsored_guest_portal.py' 2023-04-28 05:57:49,536 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sponsored_guest_portal_info.py' 2023-04-28 05:57:49,537 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/support_bundle.py' 2023-04-28 05:57:49,537 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/support_bundle_download.py' 2023-04-28 05:57:49,537 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/support_bundle_status_info.py' 2023-04-28 05:57:49,537 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_connections.py' 2023-04-28 05:57:49,538 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_connections_bulk_monitor_status_info.py' 2023-04-28 05:57:49,538 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_connections_bulk_request.py' 2023-04-28 05:57:49,538 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_connections_info.py' 2023-04-28 05:57:49,538 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings.py' 2023-04-28 05:57:49,538 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_bulk_monitor_status_info.py' 2023-04-28 05:57:49,539 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_bulk_request.py' 2023-04-28 05:57:49,539 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_local_bindings_info.py' 2023-04-28 05:57:49,539 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_vpns.py' 2023-04-28 05:57:49,539 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_vpns_bulk_monitor_status_info.py' 2023-04-28 05:57:49,540 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_vpns_bulk_request.py' 2023-04-28 05:57:49,540 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/sxp_vpns_info.py' 2023-04-28 05:57:49,540 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/system_certificate.py' 2023-04-28 05:57:49,540 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/system_certificate_create.py' 2023-04-28 05:57:49,540 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/system_certificate_export_info.py' 2023-04-28 05:57:49,541 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/system_certificate_import.py' 2023-04-28 05:57:49,541 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/system_certificate_info.py' 2023-04-28 05:57:49,541 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/system_config_version_info.py' 2023-04-28 05:57:49,541 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_command_sets.py' 2023-04-28 05:57:49,542 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_command_sets_info.py' 2023-04-28 05:57:49,542 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_external_servers.py' 2023-04-28 05:57:49,542 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_external_servers_info.py' 2023-04-28 05:57:49,542 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_profile.py' 2023-04-28 05:57:49,543 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_profile_info.py' 2023-04-28 05:57:49,543 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_server_sequence.py' 2023-04-28 05:57:49,543 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tacacs_server_sequence_info.py' 2023-04-28 05:57:49,543 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/tasks_info.py' 2023-04-28 05:57:49,543 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/telemetry_info.py' 2023-04-28 05:57:49,544 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/threat_vulnerabilities_clear.py' 2023-04-28 05:57:49,544 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/transport_gateway_settings.py' 2023-04-28 05:57:49,544 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/transport_gateway_settings_info.py' 2023-04-28 05:57:49,544 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trusted_certificate.py' 2023-04-28 05:57:49,545 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trusted_certificate_export_info.py' 2023-04-28 05:57:49,545 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trusted_certificate_import.py' 2023-04-28 05:57:49,545 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trusted_certificate_info.py' 2023-04-28 05:57:49,545 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_nbar_app.py' 2023-04-28 05:57:49,546 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_nbar_app_info.py' 2023-04-28 05:57:49,546 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping.py' 2023-04-28 05:57:49,546 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_create.py' 2023-04-28 05:57:49,546 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_delete.py' 2023-04-28 05:57:49,546 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_bulk_update.py' 2023-04-28 05:57:49,547 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_sg_vn_mapping_info.py' 2023-04-28 05:57:49,547 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn.py' 2023-04-28 05:57:49,547 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_create.py' 2023-04-28 05:57:49,547 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_delete.py' 2023-04-28 05:57:49,548 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_bulk_update.py' 2023-04-28 05:57:49,548 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_info.py' 2023-04-28 05:57:49,548 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping.py' 2023-04-28 05:57:49,548 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_create.py' 2023-04-28 05:57:49,548 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_delete.py' 2023-04-28 05:57:49,549 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_bulk_update.py' 2023-04-28 05:57:49,549 wheel INFO adding 'ansible_collections/cisco/ise/plugins/modules/trustsec_vn_vlan_mapping_info.py' 2023-04-28 05:57:49,549 wheel INFO adding 'ansible_collections/cisco/ise/plugins/plugin_utils/__init__.py' 2023-04-28 05:57:49,549 wheel INFO adding 'ansible_collections/cisco/ise/plugins/plugin_utils/exceptions.py' 2023-04-28 05:57:49,550 wheel INFO adding 'ansible_collections/cisco/ise/plugins/plugin_utils/ise.py' 2023-04-28 05:57:49,550 wheel INFO adding 'ansible_collections/cisco/ise/plugins/plugin_utils/personas_utils.py' 2023-04-28 05:57:49,550 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/README.md' 2023-04-28 05:57:49,551 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/defaults/main.yml' 2023-04-28 05:57:49,551 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/tasks/main.yml' 2023-04-28 05:57:49,551 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/aws.yml' 2023-04-28 05:57:49,551 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/large_deployment.yml' 2023-04-28 05:57:49,551 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/medium_deployment.yml' 2023-04-28 05:57:49,552 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/single_node.yml' 2023-04-28 05:57:49,552 wheel INFO adding 'ansible_collections/cisco/ise/roles/aws_deployment/tasks/aws/small_deployment.yml' 2023-04-28 05:57:49,552 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/.travis.yml' 2023-04-28 05:57:49,552 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/README.md' 2023-04-28 05:57:49,553 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/defaults/main.yml' 2023-04-28 05:57:49,553 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/handlers/main.yml' 2023-04-28 05:57:49,553 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/meta/main.yml' 2023-04-28 05:57:49,553 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/tasks/large_deployment.yml' 2023-04-28 05:57:49,554 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/tasks/main.yml' 2023-04-28 05:57:49,554 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/tasks/medium_deployment.yml' 2023-04-28 05:57:49,554 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/tasks/small_deployment.yml' 2023-04-28 05:57:49,554 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/tests/inventory' 2023-04-28 05:57:49,555 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/tests/test.yml' 2023-04-28 05:57:49,555 wheel INFO adding 'ansible_collections/cisco/ise/roles/personas_deployment/vars/main.yml' 2023-04-28 05:57:49,555 wheel INFO adding 'ansible_collections/cisco/meraki/CHANGELOG.rst' 2023-04-28 05:57:49,555 wheel INFO adding 'ansible_collections/cisco/meraki/COPYING' 2023-04-28 05:57:49,556 wheel INFO adding 'ansible_collections/cisco/meraki/FILES.json' 2023-04-28 05:57:49,556 wheel INFO adding 'ansible_collections/cisco/meraki/MANIFEST.json' 2023-04-28 05:57:49,557 wheel INFO adding 'ansible_collections/cisco/meraki/README.md' 2023-04-28 05:57:49,557 wheel INFO adding 'ansible_collections/cisco/meraki/contributing.md' 2023-04-28 05:57:49,557 wheel INFO adding 'ansible_collections/cisco/meraki/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:49,557 wheel INFO adding 'ansible_collections/cisco/meraki/changelogs/changelog.yaml' 2023-04-28 05:57:49,558 wheel INFO adding 'ansible_collections/cisco/meraki/changelogs/config.yaml' 2023-04-28 05:57:49,558 wheel INFO adding 'ansible_collections/cisco/meraki/meta/execution-environment.yml' 2023-04-28 05:57:49,558 wheel INFO adding 'ansible_collections/cisco/meraki/meta/runtime.yml' 2023-04-28 05:57:49,558 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:49,559 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/doc_fragments/meraki.py' 2023-04-28 05:57:49,559 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/__init__.py' 2023-04-28 05:57:49,559 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/meraki.py' 2023-04-28 05:57:49,560 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/__init__.py' 2023-04-28 05:57:49,560 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_action_batch.py' 2023-04-28 05:57:49,560 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_admin.py' 2023-04-28 05:57:49,560 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_alert.py' 2023-04-28 05:57:49,561 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_config_template.py' 2023-04-28 05:57:49,561 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_device.py' 2023-04-28 05:57:49,561 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_firewalled_services.py' 2023-04-28 05:57:49,562 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_management_interface.py' 2023-04-28 05:57:49,562 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mr_l3_firewall.py' 2023-04-28 05:57:49,562 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mr_l7_firewall.py' 2023-04-28 05:57:49,563 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mr_radio.py' 2023-04-28 05:57:49,563 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mr_rf_profile.py' 2023-04-28 05:57:49,563 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mr_settings.py' 2023-04-28 05:57:49,564 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mr_ssid.py' 2023-04-28 05:57:49,564 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_access_list.py' 2023-04-28 05:57:49,564 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_access_policies.py' 2023-04-28 05:57:49,565 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_l3_interface.py' 2023-04-28 05:57:49,565 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_link_aggregation.py' 2023-04-28 05:57:49,565 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_ospf.py' 2023-04-28 05:57:49,565 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_stack.py' 2023-04-28 05:57:49,566 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_stack_l3_interface.py' 2023-04-28 05:57:49,566 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_storm_control.py' 2023-04-28 05:57:49,566 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_ms_switchport.py' 2023-04-28 05:57:49,567 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_content_filtering.py' 2023-04-28 05:57:49,567 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_intrusion_prevention.py' 2023-04-28 05:57:49,567 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l2_interface.py' 2023-04-28 05:57:49,567 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l3_firewall.py' 2023-04-28 05:57:49,568 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_l7_firewall.py' 2023-04-28 05:57:49,568 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_malware.py' 2023-04-28 05:57:49,568 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_nat.py' 2023-04-28 05:57:49,569 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_network_vlan_settings.py' 2023-04-28 05:57:49,569 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_site_to_site_firewall.py' 2023-04-28 05:57:49,569 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_site_to_site_vpn.py' 2023-04-28 05:57:49,570 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_static_route.py' 2023-04-28 05:57:49,570 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_third_party_vpn_peers.py' 2023-04-28 05:57:49,570 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_uplink_bandwidth.py' 2023-04-28 05:57:49,571 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_mx_vlan.py' 2023-04-28 05:57:49,571 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_network.py' 2023-04-28 05:57:49,571 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_network_settings.py' 2023-04-28 05:57:49,571 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_organization.py' 2023-04-28 05:57:49,572 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_snmp.py' 2023-04-28 05:57:49,572 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_syslog.py' 2023-04-28 05:57:49,572 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_webhook.py' 2023-04-28 05:57:49,573 wheel INFO adding 'ansible_collections/cisco/meraki/plugins/modules/meraki_webhook_payload_template.py' 2023-04-28 05:57:49,573 wheel INFO adding 'ansible_collections/cisco/meraki/scripts/sublime-build/build.py' 2023-04-28 05:57:49,573 wheel INFO adding 'ansible_collections/cisco/meraki/scripts/sublime-build/build.py.generic' 2023-04-28 05:57:49,573 wheel INFO adding 'ansible_collections/cisco/meraki/scripts/sublime-build/requirements.txt' 2023-04-28 05:57:49,574 wheel INFO adding 'ansible_collections/cisco/mso/CHANGELOG.rst' 2023-04-28 05:57:49,574 wheel INFO adding 'ansible_collections/cisco/mso/FILES.json' 2023-04-28 05:57:49,575 wheel INFO adding 'ansible_collections/cisco/mso/LICENSE' 2023-04-28 05:57:49,575 wheel INFO adding 'ansible_collections/cisco/mso/MANIFEST.json' 2023-04-28 05:57:49,575 wheel INFO adding 'ansible_collections/cisco/mso/README.md' 2023-04-28 05:57:49,576 wheel INFO adding 'ansible_collections/cisco/mso/codecov.yml' 2023-04-28 05:57:49,576 wheel INFO adding 'ansible_collections/cisco/mso/requirements.txt' 2023-04-28 05:57:49,576 wheel INFO adding 'ansible_collections/cisco/mso/changelogs/.gitignore' 2023-04-28 05:57:49,576 wheel INFO adding 'ansible_collections/cisco/mso/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:49,577 wheel INFO adding 'ansible_collections/cisco/mso/changelogs/changelog.yaml' 2023-04-28 05:57:49,577 wheel INFO adding 'ansible_collections/cisco/mso/changelogs/config.yaml' 2023-04-28 05:57:49,577 wheel INFO adding 'ansible_collections/cisco/mso/meta/runtime.yml' 2023-04-28 05:57:49,577 wheel INFO adding 'ansible_collections/cisco/mso/plugins/.DS_Store' 2023-04-28 05:57:49,578 wheel INFO adding 'ansible_collections/cisco/mso/plugins/doc_fragments/modules.py' 2023-04-28 05:57:49,578 wheel INFO adding 'ansible_collections/cisco/mso/plugins/httpapi/mso.py' 2023-04-28 05:57:49,578 wheel INFO adding 'ansible_collections/cisco/mso/plugins/module_utils/constants.py' 2023-04-28 05:57:49,579 wheel INFO adding 'ansible_collections/cisco/mso/plugins/module_utils/mso.py' 2023-04-28 05:57:49,579 wheel INFO adding 'ansible_collections/cisco/mso/plugins/module_utils/schema.py' 2023-04-28 05:57:49,580 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_backup.py' 2023-04-28 05:57:49,580 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_backup_schedule.py' 2023-04-28 05:57:49,580 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_dhcp_option_policy.py' 2023-04-28 05:57:49,580 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_dhcp_option_policy_option.py' 2023-04-28 05:57:49,581 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_dhcp_relay_policy.py' 2023-04-28 05:57:49,581 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_dhcp_relay_policy_provider.py' 2023-04-28 05:57:49,581 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_label.py' 2023-04-28 05:57:49,581 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_remote_location.py' 2023-04-28 05:57:49,582 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_rest.py' 2023-04-28 05:57:49,582 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_role.py' 2023-04-28 05:57:49,582 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema.py' 2023-04-28 05:57:49,582 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_clone.py' 2023-04-28 05:57:49,583 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site.py' 2023-04-28 05:57:49,583 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp.py' 2023-04-28 05:57:49,583 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg.py' 2023-04-28 05:57:49,583 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_bulk_staticport.py' 2023-04-28 05:57:49,584 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_domain.py' 2023-04-28 05:57:49,584 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_selector.py' 2023-04-28 05:57:49,584 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_staticleaf.py' 2023-04-28 05:57:49,584 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_staticport.py' 2023-04-28 05:57:49,585 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_anp_epg_subnet.py' 2023-04-28 05:57:49,585 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd.py' 2023-04-28 05:57:49,585 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd_l3out.py' 2023-04-28 05:57:49,586 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_bd_subnet.py' 2023-04-28 05:57:49,586 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_external_epg.py' 2023-04-28 05:57:49,586 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_external_epg_selector.py' 2023-04-28 05:57:49,586 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_l3out.py' 2023-04-28 05:57:49,587 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_service_graph.py' 2023-04-28 05:57:49,587 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf.py' 2023-04-28 05:57:49,587 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region.py' 2023-04-28 05:57:49,587 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_cidr.py' 2023-04-28 05:57:49,588 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_cidr_subnet.py' 2023-04-28 05:57:49,588 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_site_vrf_region_hub_network.py' 2023-04-28 05:57:49,588 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template.py' 2023-04-28 05:57:49,588 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp.py' 2023-04-28 05:57:49,589 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg.py' 2023-04-28 05:57:49,589 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_contract.py' 2023-04-28 05:57:49,589 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_selector.py' 2023-04-28 05:57:49,589 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_anp_epg_subnet.py' 2023-04-28 05:57:49,590 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd.py' 2023-04-28 05:57:49,590 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd_dhcp_policy.py' 2023-04-28 05:57:49,590 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_bd_subnet.py' 2023-04-28 05:57:49,591 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_clone.py' 2023-04-28 05:57:49,592 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_contract_filter.py' 2023-04-28 05:57:49,592 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_contract_service_graph.py' 2023-04-28 05:57:49,592 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_deploy.py' 2023-04-28 05:57:49,592 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_deploy_status.py' 2023-04-28 05:57:49,593 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg.py' 2023-04-28 05:57:49,593 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_contract.py' 2023-04-28 05:57:49,593 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_selector.py' 2023-04-28 05:57:49,593 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_external_epg_subnet.py' 2023-04-28 05:57:49,594 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_externalepg.py' 2023-04-28 05:57:49,594 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_filter_entry.py' 2023-04-28 05:57:49,594 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_l3out.py' 2023-04-28 05:57:49,595 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_migrate.py' 2023-04-28 05:57:49,595 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_service_graph.py' 2023-04-28 05:57:49,595 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_vrf.py' 2023-04-28 05:57:49,595 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_template_vrf_contract.py' 2023-04-28 05:57:49,596 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_schema_validate.py' 2023-04-28 05:57:49,596 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_service_node_type.py' 2023-04-28 05:57:49,596 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_site.py' 2023-04-28 05:57:49,596 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_tenant.py' 2023-04-28 05:57:49,597 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_tenant_site.py' 2023-04-28 05:57:49,597 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_user.py' 2023-04-28 05:57:49,597 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/mso_version.py' 2023-04-28 05:57:49,597 wheel INFO adding 'ansible_collections/cisco/mso/plugins/modules/ndo_schema_template_deploy.py' 2023-04-28 05:57:49,598 wheel INFO adding 'ansible_collections/cisco/nso/CHANGELOG.rst' 2023-04-28 05:57:49,598 wheel INFO adding 'ansible_collections/cisco/nso/FILES.json' 2023-04-28 05:57:49,598 wheel INFO adding 'ansible_collections/cisco/nso/LICENSE' 2023-04-28 05:57:49,599 wheel INFO adding 'ansible_collections/cisco/nso/MANIFEST.json' 2023-04-28 05:57:49,599 wheel INFO adding 'ansible_collections/cisco/nso/README.md' 2023-04-28 05:57:49,599 wheel INFO adding 'ansible_collections/cisco/nso/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:49,599 wheel INFO adding 'ansible_collections/cisco/nso/changelogs/changelog.yaml' 2023-04-28 05:57:49,599 wheel INFO adding 'ansible_collections/cisco/nso/changelogs/config.yaml' 2023-04-28 05:57:49,600 wheel INFO adding 'ansible_collections/cisco/nso/changelogs/fragments/1.0.1.yml' 2023-04-28 05:57:49,600 wheel INFO adding 'ansible_collections/cisco/nso/changelogs/fragments/1.0.2.yml' 2023-04-28 05:57:49,600 wheel INFO adding 'ansible_collections/cisco/nso/changelogs/fragments/1.0.3.yml' 2023-04-28 05:57:49,600 wheel INFO adding 'ansible_collections/cisco/nso/meta/runtime.yml' 2023-04-28 05:57:49,601 wheel INFO adding 'ansible_collections/cisco/nso/plugins/doc_fragments/nso.py' 2023-04-28 05:57:49,601 wheel INFO adding 'ansible_collections/cisco/nso/plugins/module_utils/__init__.py' 2023-04-28 05:57:49,601 wheel INFO adding 'ansible_collections/cisco/nso/plugins/module_utils/nso.py' 2023-04-28 05:57:49,602 wheel INFO adding 'ansible_collections/cisco/nso/plugins/modules/__init__.py' 2023-04-28 05:57:49,602 wheel INFO adding 'ansible_collections/cisco/nso/plugins/modules/nso_action.py' 2023-04-28 05:57:49,602 wheel INFO adding 'ansible_collections/cisco/nso/plugins/modules/nso_config.py' 2023-04-28 05:57:49,602 wheel INFO adding 'ansible_collections/cisco/nso/plugins/modules/nso_query.py' 2023-04-28 05:57:49,603 wheel INFO adding 'ansible_collections/cisco/nso/plugins/modules/nso_show.py' 2023-04-28 05:57:49,603 wheel INFO adding 'ansible_collections/cisco/nso/plugins/modules/nso_verify.py' 2023-04-28 05:57:49,603 wheel INFO adding 'ansible_collections/cisco/nxos/CHANGELOG.rst' 2023-04-28 05:57:49,605 wheel INFO adding 'ansible_collections/cisco/nxos/FILES.json' 2023-04-28 05:57:49,607 wheel INFO adding 'ansible_collections/cisco/nxos/LICENSE' 2023-04-28 05:57:49,607 wheel INFO adding 'ansible_collections/cisco/nxos/MANIFEST.json' 2023-04-28 05:57:49,608 wheel INFO adding 'ansible_collections/cisco/nxos/README.md' 2023-04-28 05:57:49,608 wheel INFO adding 'ansible_collections/cisco/nxos/bindep.txt' 2023-04-28 05:57:49,608 wheel INFO adding 'ansible_collections/cisco/nxos/codecov.yml' 2023-04-28 05:57:49,608 wheel INFO adding 'ansible_collections/cisco/nxos/pyproject.toml' 2023-04-28 05:57:49,609 wheel INFO adding 'ansible_collections/cisco/nxos/requirements.txt' 2023-04-28 05:57:49,609 wheel INFO adding 'ansible_collections/cisco/nxos/test-requirements.txt' 2023-04-28 05:57:49,609 wheel INFO adding 'ansible_collections/cisco/nxos/tox.ini' 2023-04-28 05:57:49,609 wheel INFO adding 'ansible_collections/cisco/nxos/changelogs/changelog.yaml' 2023-04-28 05:57:49,610 wheel INFO adding 'ansible_collections/cisco/nxos/changelogs/config.yaml' 2023-04-28 05:57:49,610 wheel INFO adding 'ansible_collections/cisco/nxos/changelogs/fragments/.keep' 2023-04-28 05:57:49,610 wheel INFO adding 'ansible_collections/cisco/nxos/meta/runtime.yml' 2023-04-28 05:57:49,611 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/__init__.py' 2023-04-28 05:57:49,611 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/aaa_server.py' 2023-04-28 05:57:49,611 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/aaa_server_host.py' 2023-04-28 05:57:49,611 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/acl.py' 2023-04-28 05:57:49,612 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/acl_interface.py' 2023-04-28 05:57:49,612 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/acl_interfaces.py' 2023-04-28 05:57:49,612 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/acls.py' 2023-04-28 05:57:49,612 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/banner.py' 2023-04-28 05:57:49,613 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bfd_global.py' 2023-04-28 05:57:49,613 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bfd_interfaces.py' 2023-04-28 05:57:49,613 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bgp.py' 2023-04-28 05:57:49,613 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bgp_address_family.py' 2023-04-28 05:57:49,614 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bgp_af.py' 2023-04-28 05:57:49,614 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bgp_global.py' 2023-04-28 05:57:49,614 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bgp_neighbor.py' 2023-04-28 05:57:49,614 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,615 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/bgp_neighbor_af.py' 2023-04-28 05:57:49,615 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/command.py' 2023-04-28 05:57:49,615 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/config.py' 2023-04-28 05:57:49,615 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/devicealias.py' 2023-04-28 05:57:49,616 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/evpn_global.py' 2023-04-28 05:57:49,616 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/evpn_vni.py' 2023-04-28 05:57:49,616 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/facts.py' 2023-04-28 05:57:49,616 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/feature.py' 2023-04-28 05:57:49,617 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/file_copy.py' 2023-04-28 05:57:49,617 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/gir.py' 2023-04-28 05:57:49,617 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/gir_profile_management.py' 2023-04-28 05:57:49,617 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/hostname.py' 2023-04-28 05:57:49,618 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/hsrp.py' 2023-04-28 05:57:49,618 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/hsrp_interfaces.py' 2023-04-28 05:57:49,618 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/igmp.py' 2023-04-28 05:57:49,618 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/igmp_interface.py' 2023-04-28 05:57:49,619 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/igmp_snooping.py' 2023-04-28 05:57:49,619 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/install_os.py' 2023-04-28 05:57:49,619 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/interface.py' 2023-04-28 05:57:49,619 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/interface_ospf.py' 2023-04-28 05:57:49,620 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/interfaces.py' 2023-04-28 05:57:49,620 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/l2_interface.py' 2023-04-28 05:57:49,620 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/l2_interfaces.py' 2023-04-28 05:57:49,620 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/l3_interface.py' 2023-04-28 05:57:49,621 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/l3_interfaces.py' 2023-04-28 05:57:49,621 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/lacp.py' 2023-04-28 05:57:49,621 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/lacp_interfaces.py' 2023-04-28 05:57:49,621 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/lag_interfaces.py' 2023-04-28 05:57:49,622 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/linkagg.py' 2023-04-28 05:57:49,622 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/lldp.py' 2023-04-28 05:57:49,622 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/lldp_global.py' 2023-04-28 05:57:49,622 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/lldp_interfaces.py' 2023-04-28 05:57:49,622 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/logging.py' 2023-04-28 05:57:49,623 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/logging_global.py' 2023-04-28 05:57:49,623 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ntp.py' 2023-04-28 05:57:49,623 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ntp_auth.py' 2023-04-28 05:57:49,623 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ntp_global.py' 2023-04-28 05:57:49,624 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ntp_options.py' 2023-04-28 05:57:49,624 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/nxapi.py' 2023-04-28 05:57:49,624 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/nxos.py' 2023-04-28 05:57:49,624 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ospf.py' 2023-04-28 05:57:49,625 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ospf_interfaces.py' 2023-04-28 05:57:49,625 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ospf_vrf.py' 2023-04-28 05:57:49,625 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ospfv2.py' 2023-04-28 05:57:49,625 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ospfv3.py' 2023-04-28 05:57:49,626 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/overlay_global.py' 2023-04-28 05:57:49,626 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/pim.py' 2023-04-28 05:57:49,626 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/pim_interface.py' 2023-04-28 05:57:49,626 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/pim_rp_address.py' 2023-04-28 05:57:49,627 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/ping.py' 2023-04-28 05:57:49,627 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/prefix_lists.py' 2023-04-28 05:57:49,627 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/reboot.py' 2023-04-28 05:57:49,627 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/rollback.py' 2023-04-28 05:57:49,628 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/route_maps.py' 2023-04-28 05:57:49,628 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/rpm.py' 2023-04-28 05:57:49,628 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/smu.py' 2023-04-28 05:57:49,628 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snapshot.py' 2023-04-28 05:57:49,629 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snmp_community.py' 2023-04-28 05:57:49,629 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snmp_contact.py' 2023-04-28 05:57:49,629 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snmp_host.py' 2023-04-28 05:57:49,630 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snmp_location.py' 2023-04-28 05:57:49,630 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snmp_server.py' 2023-04-28 05:57:49,630 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snmp_traps.py' 2023-04-28 05:57:49,630 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/snmp_user.py' 2023-04-28 05:57:49,631 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/static_route.py' 2023-04-28 05:57:49,631 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/static_routes.py' 2023-04-28 05:57:49,631 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/system.py' 2023-04-28 05:57:49,631 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/telemetry.py' 2023-04-28 05:57:49,632 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/udld.py' 2023-04-28 05:57:49,632 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/udld_interface.py' 2023-04-28 05:57:49,632 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/user.py' 2023-04-28 05:57:49,632 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vlan.py' 2023-04-28 05:57:49,633 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vlans.py' 2023-04-28 05:57:49,633 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vpc.py' 2023-04-28 05:57:49,633 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vpc_interface.py' 2023-04-28 05:57:49,633 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vrf.py' 2023-04-28 05:57:49,634 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vrf_af.py' 2023-04-28 05:57:49,634 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vrf_interface.py' 2023-04-28 05:57:49,634 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vrrp.py' 2023-04-28 05:57:49,634 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vsan.py' 2023-04-28 05:57:49,635 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vtp_domain.py' 2023-04-28 05:57:49,635 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vtp_password.py' 2023-04-28 05:57:49,635 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vtp_version.py' 2023-04-28 05:57:49,635 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vxlan_vtep.py' 2023-04-28 05:57:49,636 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/vxlan_vtep_vni.py' 2023-04-28 05:57:49,636 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/action/zone_zoneset.py' 2023-04-28 05:57:49,636 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/cliconf/__init__.py' 2023-04-28 05:57:49,636 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/cliconf/nxos.py' 2023-04-28 05:57:49,637 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:49,637 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/doc_fragments/nxos.py' 2023-04-28 05:57:49,637 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/filter/__init__.py' 2023-04-28 05:57:49,637 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/httpapi/__init__.py' 2023-04-28 05:57:49,638 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/httpapi/nxos.py' 2023-04-28 05:57:49,638 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/inventory/__init__.py' 2023-04-28 05:57:49,638 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/__init__.py' 2023-04-28 05:57:49,638 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:49,639 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/__init__.py' 2023-04-28 05:57:49,639 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/nxos.py' 2023-04-28 05:57:49,639 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/__init__.py' 2023-04-28 05:57:49,640 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/__init__.py' 2023-04-28 05:57:49,640 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,640 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/__init__.py' 2023-04-28 05:57:49,640 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/acls.py' 2023-04-28 05:57:49,641 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/__init__.py' 2023-04-28 05:57:49,641 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/bfd_interfaces.py' 2023-04-28 05:57:49,641 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/__init__.py' 2023-04-28 05:57:49,641 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,642 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/__init__.py' 2023-04-28 05:57:49,642 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/bgp_global.py' 2023-04-28 05:57:49,642 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/__init__.py' 2023-04-28 05:57:49,643 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,643 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/__init__.py' 2023-04-28 05:57:49,643 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/facts.py' 2023-04-28 05:57:49,643 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/__init__.py' 2023-04-28 05:57:49,644 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/hostname.py' 2023-04-28 05:57:49,644 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/__init__.py' 2023-04-28 05:57:49,644 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/hsrp_interfaces.py' 2023-04-28 05:57:49,644 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/__init__.py' 2023-04-28 05:57:49,645 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/interfaces.py' 2023-04-28 05:57:49,645 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/__init__.py' 2023-04-28 05:57:49,645 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,645 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/__init__.py' 2023-04-28 05:57:49,646 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,646 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/__init__.py' 2023-04-28 05:57:49,646 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/lacp.py' 2023-04-28 05:57:49,646 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,646 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,647 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/__init__.py' 2023-04-28 05:57:49,647 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,647 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/__init__.py' 2023-04-28 05:57:49,647 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/lldp_global.py' 2023-04-28 05:57:49,648 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,648 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,648 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/__init__.py' 2023-04-28 05:57:49,648 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/logging_global.py' 2023-04-28 05:57:49,649 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/__init__.py' 2023-04-28 05:57:49,649 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/ntp_global.py' 2023-04-28 05:57:49,649 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,649 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,650 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/__init__.py' 2023-04-28 05:57:49,650 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/ospfv2.py' 2023-04-28 05:57:49,650 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/__init__.py' 2023-04-28 05:57:49,651 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/ospfv3.py' 2023-04-28 05:57:49,651 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/__init__.py' 2023-04-28 05:57:49,651 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,652 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/__init__.py' 2023-04-28 05:57:49,652 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/route_maps.py' 2023-04-28 05:57:49,652 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/__init__.py' 2023-04-28 05:57:49,652 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/snmp_server.py' 2023-04-28 05:57:49,653 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/__init__.py' 2023-04-28 05:57:49,653 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/static_routes.py' 2023-04-28 05:57:49,653 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/__init__.py' 2023-04-28 05:57:49,654 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/telemetry.py' 2023-04-28 05:57:49,654 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/__init__.py' 2023-04-28 05:57:49,654 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/vlans.py' 2023-04-28 05:57:49,654 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/__init__.py' 2023-04-28 05:57:49,654 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/__init__.py' 2023-04-28 05:57:49,655 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/telemetry.py' 2023-04-28 05:57:49,655 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/__init__.py' 2023-04-28 05:57:49,655 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/__init__.py' 2023-04-28 05:57:49,655 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,656 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/__init__.py' 2023-04-28 05:57:49,656 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/acls.py' 2023-04-28 05:57:49,656 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/__init__.py' 2023-04-28 05:57:49,657 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/bfd_interfaces.py' 2023-04-28 05:57:49,657 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/__init__.py' 2023-04-28 05:57:49,657 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,658 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/__init__.py' 2023-04-28 05:57:49,658 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/bgp_global.py' 2023-04-28 05:57:49,658 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/__init__.py' 2023-04-28 05:57:49,658 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,659 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/__init__.py' 2023-04-28 05:57:49,659 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/hostname.py' 2023-04-28 05:57:49,659 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/__init__.py' 2023-04-28 05:57:49,659 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/hsrp_interfaces.py' 2023-04-28 05:57:49,660 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/__init__.py' 2023-04-28 05:57:49,660 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/interfaces.py' 2023-04-28 05:57:49,660 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/__init__.py' 2023-04-28 05:57:49,660 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,661 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/__init__.py' 2023-04-28 05:57:49,661 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,661 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/__init__.py' 2023-04-28 05:57:49,662 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/lacp.py' 2023-04-28 05:57:49,662 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,662 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,662 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/__init__.py' 2023-04-28 05:57:49,663 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,663 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/__init__.py' 2023-04-28 05:57:49,663 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/lldp_global.py' 2023-04-28 05:57:49,664 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,664 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,664 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/__init__.py' 2023-04-28 05:57:49,664 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/logging_global.py' 2023-04-28 05:57:49,665 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/__init__.py' 2023-04-28 05:57:49,665 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/ntp_global.py' 2023-04-28 05:57:49,665 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,665 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,666 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/__init__.py' 2023-04-28 05:57:49,666 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/ospfv2.py' 2023-04-28 05:57:49,666 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/__init__.py' 2023-04-28 05:57:49,666 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/ospfv3.py' 2023-04-28 05:57:49,667 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/__init__.py' 2023-04-28 05:57:49,667 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,667 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/__init__.py' 2023-04-28 05:57:49,667 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/route_maps.py' 2023-04-28 05:57:49,668 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/__init__.py' 2023-04-28 05:57:49,668 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/snmp_server.py' 2023-04-28 05:57:49,668 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/__init__.py' 2023-04-28 05:57:49,668 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/static_routes.py' 2023-04-28 05:57:49,669 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/__init__.py' 2023-04-28 05:57:49,669 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/telemetry.py' 2023-04-28 05:57:49,669 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/__init__.py' 2023-04-28 05:57:49,670 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/vlans.py' 2023-04-28 05:57:49,670 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/__init__.py' 2023-04-28 05:57:49,670 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/facts.py' 2023-04-28 05:57:49,671 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/__init__.py' 2023-04-28 05:57:49,671 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:49,671 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/__init__.py' 2023-04-28 05:57:49,671 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/acls.py' 2023-04-28 05:57:49,672 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/__init__.py' 2023-04-28 05:57:49,672 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/bfd_interfaces.py' 2023-04-28 05:57:49,672 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/__init__.py' 2023-04-28 05:57:49,672 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:49,673 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/__init__.py' 2023-04-28 05:57:49,673 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/bgp_global.py' 2023-04-28 05:57:49,673 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/__init__.py' 2023-04-28 05:57:49,673 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,674 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/__init__.py' 2023-04-28 05:57:49,674 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/hostname.py' 2023-04-28 05:57:49,674 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/__init__.py' 2023-04-28 05:57:49,674 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/hsrp_interfaces.py' 2023-04-28 05:57:49,674 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/__init__.py' 2023-04-28 05:57:49,675 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/interfaces.py' 2023-04-28 05:57:49,675 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/__init__.py' 2023-04-28 05:57:49,675 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:49,675 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/__init__.py' 2023-04-28 05:57:49,676 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:49,676 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/__init__.py' 2023-04-28 05:57:49,676 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/lacp.py' 2023-04-28 05:57:49,676 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/__init__.py' 2023-04-28 05:57:49,677 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:49,677 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/__init__.py' 2023-04-28 05:57:49,677 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:49,677 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/__init__.py' 2023-04-28 05:57:49,678 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/base.py' 2023-04-28 05:57:49,678 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/__init__.py' 2023-04-28 05:57:49,678 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/lldp_global.py' 2023-04-28 05:57:49,679 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/__init__.py' 2023-04-28 05:57:49,679 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:49,679 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/__init__.py' 2023-04-28 05:57:49,679 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/logging_global.py' 2023-04-28 05:57:49,680 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/__init__.py' 2023-04-28 05:57:49,680 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/ntp_global.py' 2023-04-28 05:57:49,680 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/__init__.py' 2023-04-28 05:57:49,680 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:49,681 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/__init__.py' 2023-04-28 05:57:49,681 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/ospfv2.py' 2023-04-28 05:57:49,681 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/__init__.py' 2023-04-28 05:57:49,681 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/ospfv3.py' 2023-04-28 05:57:49,681 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/__init__.py' 2023-04-28 05:57:49,682 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/prefix_lists.py' 2023-04-28 05:57:49,682 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/__init__.py' 2023-04-28 05:57:49,682 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/route_maps.py' 2023-04-28 05:57:49,682 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/__init__.py' 2023-04-28 05:57:49,683 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/snmp_server.py' 2023-04-28 05:57:49,683 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/__init__.py' 2023-04-28 05:57:49,683 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/static_routes.py' 2023-04-28 05:57:49,683 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/__init__.py' 2023-04-28 05:57:49,684 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/telemetry.py' 2023-04-28 05:57:49,684 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/__init__.py' 2023-04-28 05:57:49,684 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/vlans.py' 2023-04-28 05:57:49,685 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/__init__.py' 2023-04-28 05:57:49,685 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_address_family.py' 2023-04-28 05:57:49,685 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_global.py' 2023-04-28 05:57:49,686 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/bgp_neighbor_address_family.py' 2023-04-28 05:57:49,686 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/hostname.py' 2023-04-28 05:57:49,686 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/logging_global.py' 2023-04-28 05:57:49,687 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ntp_global.py' 2023-04-28 05:57:49,687 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospf_interfaces.py' 2023-04-28 05:57:49,687 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospfv2.py' 2023-04-28 05:57:49,688 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/ospfv3.py' 2023-04-28 05:57:49,688 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/prefix_lists.py' 2023-04-28 05:57:49,689 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/route_maps.py' 2023-04-28 05:57:49,689 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/snmp_server.py' 2023-04-28 05:57:49,690 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/__init__.py' 2023-04-28 05:57:49,690 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/utils.py' 2023-04-28 05:57:49,690 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/__init__.py' 2023-04-28 05:57:49,690 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/telemetry.py' 2023-04-28 05:57:49,691 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/__init__.py' 2023-04-28 05:57:49,691 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_aaa_server.py' 2023-04-28 05:57:49,691 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_aaa_server_host.py' 2023-04-28 05:57:49,692 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_acl_interfaces.py' 2023-04-28 05:57:49,692 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_acls.py' 2023-04-28 05:57:49,692 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_banner.py' 2023-04-28 05:57:49,692 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bfd_global.py' 2023-04-28 05:57:49,693 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bfd_interfaces.py' 2023-04-28 05:57:49,693 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bgp.py' 2023-04-28 05:57:49,693 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_address_family.py' 2023-04-28 05:57:49,694 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_af.py' 2023-04-28 05:57:49,694 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_global.py' 2023-04-28 05:57:49,695 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor.py' 2023-04-28 05:57:49,695 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor_address_family.py' 2023-04-28 05:57:49,696 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_bgp_neighbor_af.py' 2023-04-28 05:57:49,696 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_command.py' 2023-04-28 05:57:49,696 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_config.py' 2023-04-28 05:57:49,697 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_devicealias.py' 2023-04-28 05:57:49,697 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_evpn_global.py' 2023-04-28 05:57:49,697 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_evpn_vni.py' 2023-04-28 05:57:49,697 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_facts.py' 2023-04-28 05:57:49,698 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_feature.py' 2023-04-28 05:57:49,698 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_file_copy.py' 2023-04-28 05:57:49,698 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_gir.py' 2023-04-28 05:57:49,699 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_gir_profile_management.py' 2023-04-28 05:57:49,699 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_hostname.py' 2023-04-28 05:57:49,699 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_hsrp.py' 2023-04-28 05:57:49,699 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_hsrp_interfaces.py' 2023-04-28 05:57:49,700 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_igmp.py' 2023-04-28 05:57:49,700 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_igmp_interface.py' 2023-04-28 05:57:49,700 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_igmp_snooping.py' 2023-04-28 05:57:49,701 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_install_os.py' 2023-04-28 05:57:49,701 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_interfaces.py' 2023-04-28 05:57:49,701 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_l2_interfaces.py' 2023-04-28 05:57:49,701 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_l3_interfaces.py' 2023-04-28 05:57:49,702 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_lacp.py' 2023-04-28 05:57:49,702 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_lacp_interfaces.py' 2023-04-28 05:57:49,702 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_lag_interfaces.py' 2023-04-28 05:57:49,703 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_lldp_global.py' 2023-04-28 05:57:49,703 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_lldp_interfaces.py' 2023-04-28 05:57:49,703 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_logging.py' 2023-04-28 05:57:49,704 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_logging_global.py' 2023-04-28 05:57:49,704 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ntp.py' 2023-04-28 05:57:49,704 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_auth.py' 2023-04-28 05:57:49,704 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_global.py' 2023-04-28 05:57:49,705 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ntp_options.py' 2023-04-28 05:57:49,705 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_nxapi.py' 2023-04-28 05:57:49,705 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ospf_interfaces.py' 2023-04-28 05:57:49,706 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ospfv2.py' 2023-04-28 05:57:49,707 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ospfv3.py' 2023-04-28 05:57:49,707 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_overlay_global.py' 2023-04-28 05:57:49,707 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_pim.py' 2023-04-28 05:57:49,708 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_pim_interface.py' 2023-04-28 05:57:49,708 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_pim_rp_address.py' 2023-04-28 05:57:49,708 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_ping.py' 2023-04-28 05:57:49,708 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_prefix_lists.py' 2023-04-28 05:57:49,709 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_reboot.py' 2023-04-28 05:57:49,709 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_rollback.py' 2023-04-28 05:57:49,709 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_route_maps.py' 2023-04-28 05:57:49,710 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_rpm.py' 2023-04-28 05:57:49,710 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snapshot.py' 2023-04-28 05:57:49,710 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_community.py' 2023-04-28 05:57:49,711 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_contact.py' 2023-04-28 05:57:49,711 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_host.py' 2023-04-28 05:57:49,711 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_location.py' 2023-04-28 05:57:49,712 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_server.py' 2023-04-28 05:57:49,712 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_traps.py' 2023-04-28 05:57:49,712 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_snmp_user.py' 2023-04-28 05:57:49,713 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_static_routes.py' 2023-04-28 05:57:49,713 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_system.py' 2023-04-28 05:57:49,713 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_telemetry.py' 2023-04-28 05:57:49,713 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_udld.py' 2023-04-28 05:57:49,714 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_udld_interface.py' 2023-04-28 05:57:49,714 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_user.py' 2023-04-28 05:57:49,714 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vlans.py' 2023-04-28 05:57:49,715 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vpc.py' 2023-04-28 05:57:49,715 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vpc_interface.py' 2023-04-28 05:57:49,715 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vrf.py' 2023-04-28 05:57:49,715 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vrf_af.py' 2023-04-28 05:57:49,716 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vrf_interface.py' 2023-04-28 05:57:49,716 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vrrp.py' 2023-04-28 05:57:49,716 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vsan.py' 2023-04-28 05:57:49,717 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_domain.py' 2023-04-28 05:57:49,717 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_password.py' 2023-04-28 05:57:49,717 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vtp_version.py' 2023-04-28 05:57:49,717 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vxlan_vtep.py' 2023-04-28 05:57:49,718 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_vxlan_vtep_vni.py' 2023-04-28 05:57:49,718 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/nxos_zone_zoneset.py' 2023-04-28 05:57:49,718 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/storage/__init__.py' 2023-04-28 05:57:49,719 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/storage/nxos_devicealias.py' 2023-04-28 05:57:49,719 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/storage/nxos_vsan.py' 2023-04-28 05:57:49,719 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/modules/storage/nxos_zone_zoneset.py' 2023-04-28 05:57:49,720 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/netconf/__init__.py' 2023-04-28 05:57:49,720 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/netconf/nxos.py' 2023-04-28 05:57:49,720 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/terminal/__init__.py' 2023-04-28 05:57:49,720 wheel INFO adding 'ansible_collections/cisco/nxos/plugins/terminal/nxos.py' 2023-04-28 05:57:49,721 wheel INFO adding 'ansible_collections/cisco/ucs/Development.md' 2023-04-28 05:57:49,721 wheel INFO adding 'ansible_collections/cisco/ucs/FILES.json' 2023-04-28 05:57:49,721 wheel INFO adding 'ansible_collections/cisco/ucs/LICENSE.txt' 2023-04-28 05:57:49,722 wheel INFO adding 'ansible_collections/cisco/ucs/MANIFEST.json' 2023-04-28 05:57:49,722 wheel INFO adding 'ansible_collections/cisco/ucs/README.md' 2023-04-28 05:57:49,722 wheel INFO adding 'ansible_collections/cisco/ucs/requirements.txt' 2023-04-28 05:57:49,722 wheel INFO adding 'ansible_collections/cisco/ucs/meta/runtime.yml' 2023-04-28 05:57:49,723 wheel INFO adding 'ansible_collections/cisco/ucs/misc/Impact DNW07 UCS Ansible Collection Lab Guide.pdf' 2023-04-28 05:57:49,725 wheel INFO adding 'ansible_collections/cisco/ucs/misc/README.md' 2023-04-28 05:57:49,726 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/example_playbook.yml' 2023-04-28 05:57:49,726 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/fw_download_config_hfp.yml' 2023-04-28 05:57:49,726 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/inventory' 2023-04-28 05:57:49,726 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/sandbox_inventory' 2023-04-28 05:57:49,727 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/server_deploy.yml' 2023-04-28 05:57:49,727 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_disk_group_policy.yml' 2023-04-28 05:57:49,727 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_dns_server.yml' 2023-04-28 05:57:49,727 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_graphics_card_policy.yml' 2023-04-28 05:57:49,727 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_ip_pool.yml' 2023-04-28 05:57:49,728 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_lan_connectivity.yml' 2023-04-28 05:57:49,728 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_mac_pool.yml' 2023-04-28 05:57:49,728 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_managed_objects.yml' 2023-04-28 05:57:49,728 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_ntp_server.yml' 2023-04-28 05:57:49,729 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_org.yml' 2023-04-28 05:57:49,729 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_query.yml' 2023-04-28 05:57:49,729 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_san_connectivity.yml' 2023-04-28 05:57:49,729 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_scrub_policy.yml' 2023-04-28 05:57:49,729 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_serial_over_lan_policy.yml' 2023-04-28 05:57:49,730 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_server_maintenance.yml' 2023-04-28 05:57:49,730 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_service_profile_association.yml' 2023-04-28 05:57:49,730 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_service_profile_from_template.yml' 2023-04-28 05:57:49,730 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_service_profile_template.yml' 2023-04-28 05:57:49,730 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_sp_vnic_order.yml' 2023-04-28 05:57:49,731 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_storage_profile.yml' 2023-04-28 05:57:49,731 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_system_qos.yml' 2023-04-28 05:57:49,731 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_timezone.yml' 2023-04-28 05:57:49,731 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_uuid_pool.yml' 2023-04-28 05:57:49,732 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_vhba_template.yml' 2023-04-28 05:57:49,732 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_vlan_find.yml' 2023-04-28 05:57:49,732 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_vlan_to_group.yml' 2023-04-28 05:57:49,732 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_vlans.yml' 2023-04-28 05:57:49,732 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_vnic_template.yml' 2023-04-28 05:57:49,733 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_vsans.yml' 2023-04-28 05:57:49,733 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/ucs_wwn_pool.yml' 2023-04-28 05:57:49,733 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/roles/servers/defaults/tasks/main.yml' 2023-04-28 05:57:49,733 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/roles/servers/service_profile_templates/tasks/main.yml' 2023-04-28 05:57:49,734 wheel INFO adding 'ansible_collections/cisco/ucs/playbooks/roles/servers/service_profiles/tasks/main.yml' 2023-04-28 05:57:49,734 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/README.md' 2023-04-28 05:57:49,734 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/doc_fragments/ucs.py' 2023-04-28 05:57:49,735 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/module_utils/ucs.py' 2023-04-28 05:57:49,735 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_disk_group_policy.py' 2023-04-28 05:57:49,735 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_dns_server.py' 2023-04-28 05:57:49,735 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_graphics_card_policy.py' 2023-04-28 05:57:49,736 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_ip_pool.py' 2023-04-28 05:57:49,736 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_lan_connectivity.py' 2023-04-28 05:57:49,736 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_mac_pool.py' 2023-04-28 05:57:49,737 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_managed_objects.py' 2023-04-28 05:57:49,737 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_ntp_server.py' 2023-04-28 05:57:49,737 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_org.py' 2023-04-28 05:57:49,737 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_query.py' 2023-04-28 05:57:49,738 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_san_connectivity.py' 2023-04-28 05:57:49,738 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_scrub_policy.py' 2023-04-28 05:57:49,738 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_serial_over_lan_policy.py' 2023-04-28 05:57:49,738 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_server_maintenance.py' 2023-04-28 05:57:49,739 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_association.py' 2023-04-28 05:57:49,739 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_from_template.py' 2023-04-28 05:57:49,739 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_service_profile_template.py' 2023-04-28 05:57:49,739 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_sp_vnic_order.py' 2023-04-28 05:57:49,740 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_storage_profile.py' 2023-04-28 05:57:49,740 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_system_qos.py' 2023-04-28 05:57:49,740 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_timezone.py' 2023-04-28 05:57:49,740 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_uuid_pool.py' 2023-04-28 05:57:49,741 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_vhba_template.py' 2023-04-28 05:57:49,741 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_vlan_find.py' 2023-04-28 05:57:49,741 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_vlan_to_group.py' 2023-04-28 05:57:49,741 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_vlans.py' 2023-04-28 05:57:49,742 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_vnic_template.py' 2023-04-28 05:57:49,742 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_vsans.py' 2023-04-28 05:57:49,742 wheel INFO adding 'ansible_collections/cisco/ucs/plugins/modules/ucs_wwn_pool.py' 2023-04-28 05:57:49,743 wheel INFO adding 'ansible_collections/cloud/common/CHANGELOG.rst' 2023-04-28 05:57:49,743 wheel INFO adding 'ansible_collections/cloud/common/FILES.json' 2023-04-28 05:57:49,743 wheel INFO adding 'ansible_collections/cloud/common/LICENSE' 2023-04-28 05:57:49,744 wheel INFO adding 'ansible_collections/cloud/common/MANIFEST.json' 2023-04-28 05:57:49,744 wheel INFO adding 'ansible_collections/cloud/common/README.md' 2023-04-28 05:57:49,744 wheel INFO adding 'ansible_collections/cloud/common/requirements.txt' 2023-04-28 05:57:49,744 wheel INFO adding 'ansible_collections/cloud/common/test-requirements.txt' 2023-04-28 05:57:49,744 wheel INFO adding 'ansible_collections/cloud/common/tox.ini' 2023-04-28 05:57:49,745 wheel INFO adding 'ansible_collections/cloud/common/changelogs/changelog.yaml' 2023-04-28 05:57:49,745 wheel INFO adding 'ansible_collections/cloud/common/changelogs/config.yaml' 2023-04-28 05:57:49,745 wheel INFO adding 'ansible_collections/cloud/common/changelogs/fragments/.keep' 2023-04-28 05:57:49,745 wheel INFO adding 'ansible_collections/cloud/common/meta/runtime.yml' 2023-04-28 05:57:49,746 wheel INFO adding 'ansible_collections/cloud/common/plugins/lookup/turbo_demo.py' 2023-04-28 05:57:49,746 wheel INFO adding 'ansible_collections/cloud/common/plugins/module_utils/turbo_demo.py' 2023-04-28 05:57:49,746 wheel INFO adding 'ansible_collections/cloud/common/plugins/module_utils/turbo/common.py' 2023-04-28 05:57:49,746 wheel INFO adding 'ansible_collections/cloud/common/plugins/module_utils/turbo/exceptions.py' 2023-04-28 05:57:49,747 wheel INFO adding 'ansible_collections/cloud/common/plugins/module_utils/turbo/module.py' 2023-04-28 05:57:49,747 wheel INFO adding 'ansible_collections/cloud/common/plugins/module_utils/turbo/server.py' 2023-04-28 05:57:49,747 wheel INFO adding 'ansible_collections/cloud/common/plugins/modules/turbo_demo.py' 2023-04-28 05:57:49,747 wheel INFO adding 'ansible_collections/cloud/common/plugins/modules/turbo_fail.py' 2023-04-28 05:57:49,748 wheel INFO adding 'ansible_collections/cloud/common/plugins/modules/turbo_import.py' 2023-04-28 05:57:49,748 wheel INFO adding 'ansible_collections/cloud/common/plugins/plugin_utils/turbo/lookup.py' 2023-04-28 05:57:49,748 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/CHANGELOG.rst' 2023-04-28 05:57:49,749 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/CONTRIBUTING.md' 2023-04-28 05:57:49,749 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/COPYING' 2023-04-28 05:57:49,749 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/FILES.json' 2023-04-28 05:57:49,750 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/MANIFEST.json' 2023-04-28 05:57:49,750 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/README.md' 2023-04-28 05:57:49,750 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/codecov.yml' 2023-04-28 05:57:49,750 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/changelogs/.gitignore' 2023-04-28 05:57:49,750 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/changelogs/changelog.yaml' 2023-04-28 05:57:49,751 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/changelogs/config.yaml' 2023-04-28 05:57:49,751 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/changelogs/fragments/.keep' 2023-04-28 05:57:49,751 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/meta/runtime.yml' 2023-04-28 05:57:49,751 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:49,752 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/api_parameters.py' 2023-04-28 05:57:49,752 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/inventory/__init__.py' 2023-04-28 05:57:49,752 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/inventory/inventory.py' 2023-04-28 05:57:49,752 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/module_utils/api.py' 2023-04-28 05:57:49,753 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/__init__.py' 2023-04-28 05:57:49,753 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/custom_image.py' 2023-04-28 05:57:49,753 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/floating_ip.py' 2023-04-28 05:57:49,754 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/network.py' 2023-04-28 05:57:49,754 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/objects_user.py' 2023-04-28 05:57:49,755 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/server.py' 2023-04-28 05:57:49,755 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/server_group.py' 2023-04-28 05:57:49,755 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/subnet.py' 2023-04-28 05:57:49,755 wheel INFO adding 'ansible_collections/cloudscale_ch/cloud/plugins/modules/volume.py' 2023-04-28 05:57:49,756 wheel INFO adding 'ansible_collections/community/aws/CHANGELOG.rst' 2023-04-28 05:57:49,757 wheel INFO adding 'ansible_collections/community/aws/CONTRIBUTING.md' 2023-04-28 05:57:49,757 wheel INFO adding 'ansible_collections/community/aws/COPYING' 2023-04-28 05:57:49,759 wheel INFO adding 'ansible_collections/community/aws/FILES.json' 2023-04-28 05:57:49,761 wheel INFO adding 'ansible_collections/community/aws/MANIFEST.json' 2023-04-28 05:57:49,761 wheel INFO adding 'ansible_collections/community/aws/README.md' 2023-04-28 05:57:49,761 wheel INFO adding 'ansible_collections/community/aws/bindep.txt' 2023-04-28 05:57:49,761 wheel INFO adding 'ansible_collections/community/aws/requirements.txt' 2023-04-28 05:57:49,761 wheel INFO adding 'ansible_collections/community/aws/test-requirements.txt' 2023-04-28 05:57:49,762 wheel INFO adding 'ansible_collections/community/aws/changelogs/changelog.yaml' 2023-04-28 05:57:49,763 wheel INFO adding 'ansible_collections/community/aws/changelogs/config.yaml' 2023-04-28 05:57:49,763 wheel INFO adding 'ansible_collections/community/aws/changelogs/fragments/.keep' 2023-04-28 05:57:49,764 wheel INFO adding 'ansible_collections/community/aws/meta/runtime.yml' 2023-04-28 05:57:49,764 wheel INFO adding 'ansible_collections/community/aws/plugins/connection/__init__.py' 2023-04-28 05:57:49,764 wheel INFO adding 'ansible_collections/community/aws/plugins/connection/aws_ssm.py' 2023-04-28 05:57:49,765 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/base.py' 2023-04-28 05:57:49,765 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/ec2.py' 2023-04-28 05:57:49,765 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/etag.py' 2023-04-28 05:57:49,766 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/networkfirewall.py' 2023-04-28 05:57:49,766 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/opensearch.py' 2023-04-28 05:57:49,767 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/sns.py' 2023-04-28 05:57:49,767 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/transitgateway.py' 2023-04-28 05:57:49,767 wheel INFO adding 'ansible_collections/community/aws/plugins/module_utils/wafv2.py' 2023-04-28 05:57:49,768 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/__init__.py' 2023-04-28 05:57:49,768 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/accessanalyzer_validate_policy_info.py' 2023-04-28 05:57:49,768 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/acm_certificate.py' 2023-04-28 05:57:49,768 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/acm_certificate_info.py' 2023-04-28 05:57:49,769 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/api_gateway.py' 2023-04-28 05:57:49,769 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/api_gateway_domain.py' 2023-04-28 05:57:49,769 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/application_autoscaling_policy.py' 2023-04-28 05:57:49,770 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_complete_lifecycle_action.py' 2023-04-28 05:57:49,770 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_instance_refresh.py' 2023-04-28 05:57:49,770 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_instance_refresh_info.py' 2023-04-28 05:57:49,771 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_launch_config.py' 2023-04-28 05:57:49,771 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_launch_config_find.py' 2023-04-28 05:57:49,771 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_launch_config_info.py' 2023-04-28 05:57:49,771 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_lifecycle_hook.py' 2023-04-28 05:57:49,772 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_policy.py' 2023-04-28 05:57:49,772 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/autoscaling_scheduled_action.py' 2023-04-28 05:57:49,772 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/aws_region_info.py' 2023-04-28 05:57:49,773 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/batch_compute_environment.py' 2023-04-28 05:57:49,773 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/batch_job_definition.py' 2023-04-28 05:57:49,773 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/batch_job_queue.py' 2023-04-28 05:57:49,773 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/cloudformation_exports_info.py' 2023-04-28 05:57:49,774 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/cloudformation_stack_set.py' 2023-04-28 05:57:49,774 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/cloudfront_distribution.py' 2023-04-28 05:57:49,775 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/cloudfront_distribution_info.py' 2023-04-28 05:57:49,775 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/cloudfront_invalidation.py' 2023-04-28 05:57:49,776 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/cloudfront_origin_access_identity.py' 2023-04-28 05:57:49,776 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/cloudfront_response_headers_policy.py' 2023-04-28 05:57:49,776 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/codebuild_project.py' 2023-04-28 05:57:49,777 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/codecommit_repository.py' 2023-04-28 05:57:49,777 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/codepipeline.py' 2023-04-28 05:57:49,777 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/config_aggregation_authorization.py' 2023-04-28 05:57:49,777 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/config_aggregator.py' 2023-04-28 05:57:49,778 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/config_delivery_channel.py' 2023-04-28 05:57:49,778 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/config_recorder.py' 2023-04-28 05:57:49,778 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/config_rule.py' 2023-04-28 05:57:49,778 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/data_pipeline.py' 2023-04-28 05:57:49,779 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/directconnect_confirm_connection.py' 2023-04-28 05:57:49,779 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/directconnect_connection.py' 2023-04-28 05:57:49,779 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/directconnect_gateway.py' 2023-04-28 05:57:49,780 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/directconnect_link_aggregation_group.py' 2023-04-28 05:57:49,780 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/directconnect_virtual_interface.py' 2023-04-28 05:57:49,780 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/dms_endpoint.py' 2023-04-28 05:57:49,781 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/dms_replication_subnet_group.py' 2023-04-28 05:57:49,781 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/dynamodb_table.py' 2023-04-28 05:57:49,781 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/dynamodb_ttl.py' 2023-04-28 05:57:49,782 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_ami_copy.py' 2023-04-28 05:57:49,782 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_customer_gateway.py' 2023-04-28 05:57:49,782 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_customer_gateway_info.py' 2023-04-28 05:57:49,782 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_launch_template.py' 2023-04-28 05:57:49,783 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_placement_group.py' 2023-04-28 05:57:49,783 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_placement_group_info.py' 2023-04-28 05:57:49,783 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_snapshot_copy.py' 2023-04-28 05:57:49,784 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_transit_gateway.py' 2023-04-28 05:57:49,784 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_info.py' 2023-04-28 05:57:49,784 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_vpc_attachment.py' 2023-04-28 05:57:49,784 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_transit_gateway_vpc_attachment_info.py' 2023-04-28 05:57:49,785 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_egress_igw.py' 2023-04-28 05:57:49,785 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_nacl.py' 2023-04-28 05:57:49,785 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_nacl_info.py' 2023-04-28 05:57:49,786 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_peer.py' 2023-04-28 05:57:49,786 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_peering_info.py' 2023-04-28 05:57:49,786 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_vgw.py' 2023-04-28 05:57:49,787 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_vgw_info.py' 2023-04-28 05:57:49,787 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_vpn.py' 2023-04-28 05:57:49,787 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_vpc_vpn_info.py' 2023-04-28 05:57:49,787 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ec2_win_password.py' 2023-04-28 05:57:49,788 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_attribute.py' 2023-04-28 05:57:49,788 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_cluster.py' 2023-04-28 05:57:49,788 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_ecr.py' 2023-04-28 05:57:49,789 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_service.py' 2023-04-28 05:57:49,789 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_service_info.py' 2023-04-28 05:57:49,789 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_tag.py' 2023-04-28 05:57:49,790 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_task.py' 2023-04-28 05:57:49,790 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_taskdefinition.py' 2023-04-28 05:57:49,791 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ecs_taskdefinition_info.py' 2023-04-28 05:57:49,791 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/efs.py' 2023-04-28 05:57:49,791 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/efs_info.py' 2023-04-28 05:57:49,792 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/efs_tag.py' 2023-04-28 05:57:49,792 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/eks_cluster.py' 2023-04-28 05:57:49,792 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/eks_fargate_profile.py' 2023-04-28 05:57:49,793 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/eks_nodegroup.py' 2023-04-28 05:57:49,793 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elasticache.py' 2023-04-28 05:57:49,793 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elasticache_info.py' 2023-04-28 05:57:49,794 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elasticache_parameter_group.py' 2023-04-28 05:57:49,794 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elasticache_snapshot.py' 2023-04-28 05:57:49,794 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elasticache_subnet_group.py' 2023-04-28 05:57:49,794 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elasticbeanstalk_app.py' 2023-04-28 05:57:49,795 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elb_classic_lb_info.py' 2023-04-28 05:57:49,795 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elb_instance.py' 2023-04-28 05:57:49,795 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elb_network_lb.py' 2023-04-28 05:57:49,796 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elb_target.py' 2023-04-28 05:57:49,796 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elb_target_group.py' 2023-04-28 05:57:49,796 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elb_target_group_info.py' 2023-04-28 05:57:49,797 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/elb_target_info.py' 2023-04-28 05:57:49,797 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/glue_connection.py' 2023-04-28 05:57:49,797 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/glue_crawler.py' 2023-04-28 05:57:49,798 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/glue_job.py' 2023-04-28 05:57:49,798 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_access_key.py' 2023-04-28 05:57:49,798 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_access_key_info.py' 2023-04-28 05:57:49,799 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_group.py' 2023-04-28 05:57:49,799 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_managed_policy.py' 2023-04-28 05:57:49,799 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_mfa_device_info.py' 2023-04-28 05:57:49,799 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_password_policy.py' 2023-04-28 05:57:49,800 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_role.py' 2023-04-28 05:57:49,800 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_role_info.py' 2023-04-28 05:57:49,800 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_saml_federation.py' 2023-04-28 05:57:49,801 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_server_certificate.py' 2023-04-28 05:57:49,801 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/iam_server_certificate_info.py' 2023-04-28 05:57:49,801 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/inspector_target.py' 2023-04-28 05:57:49,801 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/kinesis_stream.py' 2023-04-28 05:57:49,802 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/lightsail.py' 2023-04-28 05:57:49,802 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/lightsail_static_ip.py' 2023-04-28 05:57:49,802 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/msk_cluster.py' 2023-04-28 05:57:49,803 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/msk_config.py' 2023-04-28 05:57:49,803 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/networkfirewall.py' 2023-04-28 05:57:49,803 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/networkfirewall_info.py' 2023-04-28 05:57:49,804 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/networkfirewall_policy.py' 2023-04-28 05:57:49,804 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/networkfirewall_policy_info.py' 2023-04-28 05:57:49,804 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/networkfirewall_rule_group.py' 2023-04-28 05:57:49,805 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/networkfirewall_rule_group_info.py' 2023-04-28 05:57:49,805 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/opensearch.py' 2023-04-28 05:57:49,806 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/opensearch_info.py' 2023-04-28 05:57:49,806 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/redshift.py' 2023-04-28 05:57:49,806 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/redshift_cross_region_snapshots.py' 2023-04-28 05:57:49,807 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/redshift_info.py' 2023-04-28 05:57:49,807 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/redshift_subnet_group.py' 2023-04-28 05:57:49,807 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_bucket_info.py' 2023-04-28 05:57:49,807 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_bucket_notification.py' 2023-04-28 05:57:49,808 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_cors.py' 2023-04-28 05:57:49,808 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_lifecycle.py' 2023-04-28 05:57:49,808 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_logging.py' 2023-04-28 05:57:49,809 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_metrics_configuration.py' 2023-04-28 05:57:49,809 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_sync.py' 2023-04-28 05:57:49,809 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/s3_website.py' 2023-04-28 05:57:49,810 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/secretsmanager_secret.py' 2023-04-28 05:57:49,810 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ses_identity.py' 2023-04-28 05:57:49,810 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ses_identity_policy.py' 2023-04-28 05:57:49,811 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ses_rule_set.py' 2023-04-28 05:57:49,811 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/sns.py' 2023-04-28 05:57:49,811 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/sns_topic.py' 2023-04-28 05:57:49,812 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/sns_topic_info.py' 2023-04-28 05:57:49,812 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/sqs_queue.py' 2023-04-28 05:57:49,812 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/ssm_parameter.py' 2023-04-28 05:57:49,812 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/stepfunctions_state_machine.py' 2023-04-28 05:57:49,813 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/stepfunctions_state_machine_execution.py' 2023-04-28 05:57:49,813 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/storagegateway_info.py' 2023-04-28 05:57:49,813 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/sts_assume_role.py' 2023-04-28 05:57:49,814 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/sts_session_token.py' 2023-04-28 05:57:49,814 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/waf_condition.py' 2023-04-28 05:57:49,814 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/waf_info.py' 2023-04-28 05:57:49,814 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/waf_rule.py' 2023-04-28 05:57:49,815 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/waf_web_acl.py' 2023-04-28 05:57:49,815 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_ip_set.py' 2023-04-28 05:57:49,815 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_ip_set_info.py' 2023-04-28 05:57:49,815 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_resources.py' 2023-04-28 05:57:49,816 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_resources_info.py' 2023-04-28 05:57:49,816 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_rule_group.py' 2023-04-28 05:57:49,816 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_rule_group_info.py' 2023-04-28 05:57:49,817 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_web_acl.py' 2023-04-28 05:57:49,817 wheel INFO adding 'ansible_collections/community/aws/plugins/modules/wafv2_web_acl_info.py' 2023-04-28 05:57:49,817 wheel INFO adding 'ansible_collections/community/azure/CHANGELOG.rst' 2023-04-28 05:57:49,818 wheel INFO adding 'ansible_collections/community/azure/COPYING' 2023-04-28 05:57:49,818 wheel INFO adding 'ansible_collections/community/azure/FILES.json' 2023-04-28 05:57:49,818 wheel INFO adding 'ansible_collections/community/azure/MANIFEST.json' 2023-04-28 05:57:49,818 wheel INFO adding 'ansible_collections/community/azure/README.md' 2023-04-28 05:57:49,819 wheel INFO adding 'ansible_collections/community/azure/shippable.yml' 2023-04-28 05:57:49,819 wheel INFO adding 'ansible_collections/community/azure/changelogs/changelog.yaml' 2023-04-28 05:57:49,819 wheel INFO adding 'ansible_collections/community/azure/changelogs/config.yaml' 2023-04-28 05:57:49,819 wheel INFO adding 'ansible_collections/community/azure/changelogs/fragments/.keep' 2023-04-28 05:57:49,820 wheel INFO adding 'ansible_collections/community/azure/meta/action_groups.yml' 2023-04-28 05:57:49,820 wheel INFO adding 'ansible_collections/community/azure/meta/runtime.yml' 2023-04-28 05:57:49,820 wheel INFO adding 'ansible_collections/community/ciscosmb/CHANGELOG.rst' 2023-04-28 05:57:49,821 wheel INFO adding 'ansible_collections/community/ciscosmb/CODE_OF_CONDUCT.md' 2023-04-28 05:57:49,821 wheel INFO adding 'ansible_collections/community/ciscosmb/CONTRIBUTING.md' 2023-04-28 05:57:49,821 wheel INFO adding 'ansible_collections/community/ciscosmb/FILES.json' 2023-04-28 05:57:49,822 wheel INFO adding 'ansible_collections/community/ciscosmb/LICENSE' 2023-04-28 05:57:49,822 wheel INFO adding 'ansible_collections/community/ciscosmb/MANIFEST.json' 2023-04-28 05:57:49,822 wheel INFO adding 'ansible_collections/community/ciscosmb/README.md' 2023-04-28 05:57:49,822 wheel INFO adding 'ansible_collections/community/ciscosmb/RELEASE_POLICY.md' 2023-04-28 05:57:49,823 wheel INFO adding 'ansible_collections/community/ciscosmb/galaxy-importer.cfg' 2023-04-28 05:57:49,823 wheel INFO adding 'ansible_collections/community/ciscosmb/requirements-dev.txt' 2023-04-28 05:57:49,823 wheel INFO adding 'ansible_collections/community/ciscosmb/changelogs/changelog.yaml' 2023-04-28 05:57:49,823 wheel INFO adding 'ansible_collections/community/ciscosmb/changelogs/config.yaml' 2023-04-28 05:57:49,823 wheel INFO adding 'ansible_collections/community/ciscosmb/changelogs/fragments/.keep' 2023-04-28 05:57:49,824 wheel INFO adding 'ansible_collections/community/ciscosmb/meta/runtime.yml' 2023-04-28 05:57:49,824 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/cliconf/ciscosmb.py' 2023-04-28 05:57:49,824 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/module_utils/__init__.py' 2023-04-28 05:57:49,824 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/module_utils/ciscosmb.py' 2023-04-28 05:57:49,825 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/module_utils/ciscosmb_canonical_map.py' 2023-04-28 05:57:49,825 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/modules/__init__.py' 2023-04-28 05:57:49,825 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/modules/command.py' 2023-04-28 05:57:49,826 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/modules/facts.py' 2023-04-28 05:57:49,826 wheel INFO adding 'ansible_collections/community/ciscosmb/plugins/terminal/ciscosmb.py' 2023-04-28 05:57:49,826 wheel INFO adding 'ansible_collections/community/crypto/CHANGELOG.rst' 2023-04-28 05:57:49,827 wheel INFO adding 'ansible_collections/community/crypto/CHANGELOG.rst.license' 2023-04-28 05:57:49,827 wheel INFO adding 'ansible_collections/community/crypto/COPYING' 2023-04-28 05:57:49,828 wheel INFO adding 'ansible_collections/community/crypto/FILES.json' 2023-04-28 05:57:49,829 wheel INFO adding 'ansible_collections/community/crypto/MANIFEST.json' 2023-04-28 05:57:49,829 wheel INFO adding 'ansible_collections/community/crypto/README.md' 2023-04-28 05:57:49,829 wheel INFO adding 'ansible_collections/community/crypto/LICENSES/Apache-2.0.txt' 2023-04-28 05:57:49,829 wheel INFO adding 'ansible_collections/community/crypto/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:49,830 wheel INFO adding 'ansible_collections/community/crypto/LICENSES/BSD-3-Clause.txt' 2023-04-28 05:57:49,830 wheel INFO adding 'ansible_collections/community/crypto/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:49,830 wheel INFO adding 'ansible_collections/community/crypto/LICENSES/PSF-2.0.txt' 2023-04-28 05:57:49,831 wheel INFO adding 'ansible_collections/community/crypto/changelogs/changelog.yaml' 2023-04-28 05:57:49,831 wheel INFO adding 'ansible_collections/community/crypto/changelogs/changelog.yaml.license' 2023-04-28 05:57:49,831 wheel INFO adding 'ansible_collections/community/crypto/changelogs/config.yaml' 2023-04-28 05:57:49,832 wheel INFO adding 'ansible_collections/community/crypto/changelogs/fragments/.keep' 2023-04-28 05:57:49,832 wheel INFO adding 'ansible_collections/community/crypto/meta/ee-bindep.txt' 2023-04-28 05:57:49,832 wheel INFO adding 'ansible_collections/community/crypto/meta/ee-requirements.txt' 2023-04-28 05:57:49,832 wheel INFO adding 'ansible_collections/community/crypto/meta/execution-environment.yml' 2023-04-28 05:57:49,833 wheel INFO adding 'ansible_collections/community/crypto/meta/runtime.yml' 2023-04-28 05:57:49,833 wheel INFO adding 'ansible_collections/community/crypto/plugins/action/openssl_privatekey_pipe.py' 2023-04-28 05:57:49,833 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/acme.py' 2023-04-28 05:57:49,833 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:49,834 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/ecs_credential.py' 2023-04-28 05:57:49,834 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/module_certificate.py' 2023-04-28 05:57:49,834 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/module_csr.py' 2023-04-28 05:57:49,834 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/module_privatekey.py' 2023-04-28 05:57:49,835 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/module_privatekey_convert.py' 2023-04-28 05:57:49,835 wheel INFO adding 'ansible_collections/community/crypto/plugins/doc_fragments/name_encoding.py' 2023-04-28 05:57:49,835 wheel INFO adding 'ansible_collections/community/crypto/plugins/filter/openssl_csr_info.py' 2023-04-28 05:57:49,835 wheel INFO adding 'ansible_collections/community/crypto/plugins/filter/openssl_privatekey_info.py' 2023-04-28 05:57:49,836 wheel INFO adding 'ansible_collections/community/crypto/plugins/filter/openssl_publickey_info.py' 2023-04-28 05:57:49,836 wheel INFO adding 'ansible_collections/community/crypto/plugins/filter/split_pem.py' 2023-04-28 05:57:49,836 wheel INFO adding 'ansible_collections/community/crypto/plugins/filter/x509_certificate_info.py' 2023-04-28 05:57:49,837 wheel INFO adding 'ansible_collections/community/crypto/plugins/filter/x509_crl_info.py' 2023-04-28 05:57:49,837 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/_version.py' 2023-04-28 05:57:49,837 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/io.py' 2023-04-28 05:57:49,837 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/version.py' 2023-04-28 05:57:49,838 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/account.py' 2023-04-28 05:57:49,838 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/acme.py' 2023-04-28 05:57:49,838 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/backend_cryptography.py' 2023-04-28 05:57:49,839 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/backend_openssl_cli.py' 2023-04-28 05:57:49,839 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/backends.py' 2023-04-28 05:57:49,839 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/certificates.py' 2023-04-28 05:57:49,839 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/challenges.py' 2023-04-28 05:57:49,840 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/errors.py' 2023-04-28 05:57:49,840 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/io.py' 2023-04-28 05:57:49,840 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/orders.py' 2023-04-28 05:57:49,840 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/acme/utils.py' 2023-04-28 05:57:49,841 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/_asn1.py' 2023-04-28 05:57:49,841 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/_obj2txt.py' 2023-04-28 05:57:49,841 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/_objects.py' 2023-04-28 05:57:49,841 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/_objects_data.py' 2023-04-28 05:57:49,842 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/basic.py' 2023-04-28 05:57:49,842 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/cryptography_crl.py' 2023-04-28 05:57:49,842 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/cryptography_support.py' 2023-04-28 05:57:49,843 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/math.py' 2023-04-28 05:57:49,843 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/openssh.py' 2023-04-28 05:57:49,843 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/pem.py' 2023-04-28 05:57:49,844 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/support.py' 2023-04-28 05:57:49,844 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate.py' 2023-04-28 05:57:49,844 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_acme.py' 2023-04-28 05:57:49,844 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_entrust.py' 2023-04-28 05:57:49,845 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_info.py' 2023-04-28 05:57:49,845 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_ownca.py' 2023-04-28 05:57:49,845 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/certificate_selfsigned.py' 2023-04-28 05:57:49,846 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/common.py' 2023-04-28 05:57:49,846 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/crl_info.py' 2023-04-28 05:57:49,846 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/csr.py' 2023-04-28 05:57:49,846 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/csr_info.py' 2023-04-28 05:57:49,847 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey.py' 2023-04-28 05:57:49,847 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey_convert.py' 2023-04-28 05:57:49,847 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/privatekey_info.py' 2023-04-28 05:57:49,848 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/publickey_info.py' 2023-04-28 05:57:49,848 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/ecs/api.py' 2023-04-28 05:57:49,848 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/openssh/certificate.py' 2023-04-28 05:57:49,849 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/openssh/cryptography.py' 2023-04-28 05:57:49,849 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/openssh/utils.py' 2023-04-28 05:57:49,849 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/openssh/backends/common.py' 2023-04-28 05:57:49,850 wheel INFO adding 'ansible_collections/community/crypto/plugins/module_utils/openssh/backends/keypair_backend.py' 2023-04-28 05:57:49,850 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/acme_account.py' 2023-04-28 05:57:49,850 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/acme_account_info.py' 2023-04-28 05:57:49,851 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/acme_certificate.py' 2023-04-28 05:57:49,851 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/acme_certificate_revoke.py' 2023-04-28 05:57:49,852 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/acme_challenge_cert_helper.py' 2023-04-28 05:57:49,852 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/acme_inspect.py' 2023-04-28 05:57:49,852 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/certificate_complete_chain.py' 2023-04-28 05:57:49,852 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/crypto_info.py' 2023-04-28 05:57:49,853 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/ecs_certificate.py' 2023-04-28 05:57:49,853 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/ecs_domain.py' 2023-04-28 05:57:49,854 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/get_certificate.py' 2023-04-28 05:57:49,854 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/luks_device.py' 2023-04-28 05:57:49,854 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssh_cert.py' 2023-04-28 05:57:49,855 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssh_keypair.py' 2023-04-28 05:57:49,855 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_csr.py' 2023-04-28 05:57:49,855 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_csr_info.py' 2023-04-28 05:57:49,856 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_csr_pipe.py' 2023-04-28 05:57:49,856 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_dhparam.py' 2023-04-28 05:57:49,856 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_pkcs12.py' 2023-04-28 05:57:49,857 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_privatekey.py' 2023-04-28 05:57:49,857 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_privatekey_convert.py' 2023-04-28 05:57:49,857 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_privatekey_info.py' 2023-04-28 05:57:49,857 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_privatekey_pipe.py' 2023-04-28 05:57:49,858 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_publickey.py' 2023-04-28 05:57:49,858 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_publickey_info.py' 2023-04-28 05:57:49,858 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_signature.py' 2023-04-28 05:57:49,858 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/openssl_signature_info.py' 2023-04-28 05:57:49,859 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/x509_certificate.py' 2023-04-28 05:57:49,859 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/x509_certificate_info.py' 2023-04-28 05:57:49,859 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/x509_certificate_pipe.py' 2023-04-28 05:57:49,860 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/x509_crl.py' 2023-04-28 05:57:49,860 wheel INFO adding 'ansible_collections/community/crypto/plugins/modules/x509_crl_info.py' 2023-04-28 05:57:49,860 wheel INFO adding 'ansible_collections/community/crypto/plugins/plugin_utils/action_module.py' 2023-04-28 05:57:49,861 wheel INFO adding 'ansible_collections/community/crypto/plugins/plugin_utils/filter_module.py' 2023-04-28 05:57:49,861 wheel INFO adding 'ansible_collections/community/digitalocean/CHANGELOG.rst' 2023-04-28 05:57:49,861 wheel INFO adding 'ansible_collections/community/digitalocean/COPYING' 2023-04-28 05:57:49,862 wheel INFO adding 'ansible_collections/community/digitalocean/FILES.json' 2023-04-28 05:57:49,863 wheel INFO adding 'ansible_collections/community/digitalocean/MANIFEST.json' 2023-04-28 05:57:49,863 wheel INFO adding 'ansible_collections/community/digitalocean/README.md' 2023-04-28 05:57:49,863 wheel INFO adding 'ansible_collections/community/digitalocean/codecov.yml' 2023-04-28 05:57:49,863 wheel INFO adding 'ansible_collections/community/digitalocean/changelogs/.gitignore' 2023-04-28 05:57:49,864 wheel INFO adding 'ansible_collections/community/digitalocean/changelogs/changelog.yaml' 2023-04-28 05:57:49,864 wheel INFO adding 'ansible_collections/community/digitalocean/changelogs/config.yaml' 2023-04-28 05:57:49,864 wheel INFO adding 'ansible_collections/community/digitalocean/changelogs/fragments/.keep' 2023-04-28 05:57:49,865 wheel INFO adding 'ansible_collections/community/digitalocean/meta/runtime.yml' 2023-04-28 05:57:49,865 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/doc_fragments/digital_ocean.py' 2023-04-28 05:57:49,865 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/inventory/digitalocean.py' 2023-04-28 05:57:49,865 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/module_utils/digital_ocean.py' 2023-04-28 05:57:49,866 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean.py' 2023-04-28 05:57:49,866 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_account_facts.py' 2023-04-28 05:57:49,866 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_account_info.py' 2023-04-28 05:57:49,867 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_balance_info.py' 2023-04-28 05:57:49,867 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_block_storage.py' 2023-04-28 05:57:49,867 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_cdn_endpoints.py' 2023-04-28 05:57:49,867 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_cdn_endpoints_info.py' 2023-04-28 05:57:49,868 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate.py' 2023-04-28 05:57:49,868 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate_facts.py' 2023-04-28 05:57:49,868 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_certificate_info.py' 2023-04-28 05:57:49,868 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_database.py' 2023-04-28 05:57:49,869 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_database_info.py' 2023-04-28 05:57:49,869 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain.py' 2023-04-28 05:57:49,869 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_facts.py' 2023-04-28 05:57:49,869 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_info.py' 2023-04-28 05:57:49,870 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_record.py' 2023-04-28 05:57:49,870 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_domain_record_info.py' 2023-04-28 05:57:49,870 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_droplet.py' 2023-04-28 05:57:49,871 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_droplet_info.py' 2023-04-28 05:57:49,871 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall.py' 2023-04-28 05:57:49,871 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall_facts.py' 2023-04-28 05:57:49,871 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_firewall_info.py' 2023-04-28 05:57:49,872 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip.py' 2023-04-28 05:57:49,872 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip_facts.py' 2023-04-28 05:57:49,872 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_floating_ip_info.py' 2023-04-28 05:57:49,872 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_image_facts.py' 2023-04-28 05:57:49,873 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_image_info.py' 2023-04-28 05:57:49,873 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_kubernetes.py' 2023-04-28 05:57:49,873 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_kubernetes_info.py' 2023-04-28 05:57:49,874 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer.py' 2023-04-28 05:57:49,874 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer_facts.py' 2023-04-28 05:57:49,874 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_load_balancer_info.py' 2023-04-28 05:57:49,874 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_monitoring_alerts.py' 2023-04-28 05:57:49,875 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_monitoring_alerts_info.py' 2023-04-28 05:57:49,875 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_project.py' 2023-04-28 05:57:49,875 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_project_info.py' 2023-04-28 05:57:49,875 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_region_facts.py' 2023-04-28 05:57:49,876 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_region_info.py' 2023-04-28 05:57:49,876 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_size_facts.py' 2023-04-28 05:57:49,876 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_size_info.py' 2023-04-28 05:57:49,876 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot.py' 2023-04-28 05:57:49,877 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot_facts.py' 2023-04-28 05:57:49,877 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_snapshot_info.py' 2023-04-28 05:57:49,877 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_spaces.py' 2023-04-28 05:57:49,877 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_spaces_info.py' 2023-04-28 05:57:49,878 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey.py' 2023-04-28 05:57:49,878 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey_facts.py' 2023-04-28 05:57:49,878 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_sshkey_info.py' 2023-04-28 05:57:49,878 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag.py' 2023-04-28 05:57:49,878 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag_facts.py' 2023-04-28 05:57:49,879 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_tag_info.py' 2023-04-28 05:57:49,879 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_volume_facts.py' 2023-04-28 05:57:49,880 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_volume_info.py' 2023-04-28 05:57:49,880 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_vpc.py' 2023-04-28 05:57:49,880 wheel INFO adding 'ansible_collections/community/digitalocean/plugins/modules/digital_ocean_vpc_info.py' 2023-04-28 05:57:49,880 wheel INFO adding 'ansible_collections/community/digitalocean/scripts/inventory/digital_ocean.ini' 2023-04-28 05:57:49,881 wheel INFO adding 'ansible_collections/community/digitalocean/scripts/inventory/digital_ocean.py' 2023-04-28 05:57:49,881 wheel INFO adding 'ansible_collections/community/dns/CHANGELOG.rst' 2023-04-28 05:57:49,881 wheel INFO adding 'ansible_collections/community/dns/CHANGELOG.rst.license' 2023-04-28 05:57:49,882 wheel INFO adding 'ansible_collections/community/dns/CODE_OF_CONDUCT.md' 2023-04-28 05:57:49,882 wheel INFO adding 'ansible_collections/community/dns/COPYING' 2023-04-28 05:57:49,882 wheel INFO adding 'ansible_collections/community/dns/FILES.json' 2023-04-28 05:57:49,883 wheel INFO adding 'ansible_collections/community/dns/MANIFEST.json' 2023-04-28 05:57:49,883 wheel INFO adding 'ansible_collections/community/dns/README.md' 2023-04-28 05:57:49,883 wheel INFO adding 'ansible_collections/community/dns/TESTING.md' 2023-04-28 05:57:49,883 wheel INFO adding 'ansible_collections/community/dns/codecov.yml' 2023-04-28 05:57:49,884 wheel INFO adding 'ansible_collections/community/dns/update-docs-fragments.py' 2023-04-28 05:57:49,884 wheel INFO adding 'ansible_collections/community/dns/update-psl.sh' 2023-04-28 05:57:49,884 wheel INFO adding 'ansible_collections/community/dns/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:49,885 wheel INFO adding 'ansible_collections/community/dns/LICENSES/MPL-2.0.txt' 2023-04-28 05:57:49,885 wheel INFO adding 'ansible_collections/community/dns/changelogs/changelog.yaml' 2023-04-28 05:57:49,885 wheel INFO adding 'ansible_collections/community/dns/changelogs/changelog.yaml.license' 2023-04-28 05:57:49,886 wheel INFO adding 'ansible_collections/community/dns/changelogs/config.yaml' 2023-04-28 05:57:49,886 wheel INFO adding 'ansible_collections/community/dns/changelogs/fragments/.keep' 2023-04-28 05:57:49,886 wheel INFO adding 'ansible_collections/community/dns/meta/ee-requirements.txt' 2023-04-28 05:57:49,886 wheel INFO adding 'ansible_collections/community/dns/meta/execution-environment.yml' 2023-04-28 05:57:49,887 wheel INFO adding 'ansible_collections/community/dns/meta/runtime.yml' 2023-04-28 05:57:49,887 wheel INFO adding 'ansible_collections/community/dns/plugins/public_suffix_list.dat' 2023-04-28 05:57:49,889 wheel INFO adding 'ansible_collections/community/dns/plugins/public_suffix_list.dat.license' 2023-04-28 05:57:49,889 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:49,889 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/filters.py' 2023-04-28 05:57:49,889 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/hetzner.py' 2023-04-28 05:57:49,889 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/hosttech.py' 2023-04-28 05:57:49,890 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/inventory_records.py' 2023-04-28 05:57:49,890 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/module_record.py' 2023-04-28 05:57:49,890 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/module_record_info.py' 2023-04-28 05:57:49,890 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/module_record_set.py' 2023-04-28 05:57:49,891 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/module_record_set_info.py' 2023-04-28 05:57:49,891 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/module_record_sets.py' 2023-04-28 05:57:49,891 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/module_zone_info.py' 2023-04-28 05:57:49,891 wheel INFO adding 'ansible_collections/community/dns/plugins/doc_fragments/options.py' 2023-04-28 05:57:49,892 wheel INFO adding 'ansible_collections/community/dns/plugins/filter/domain_suffix.py' 2023-04-28 05:57:49,892 wheel INFO adding 'ansible_collections/community/dns/plugins/filter/get_public_suffix.yml' 2023-04-28 05:57:49,892 wheel INFO adding 'ansible_collections/community/dns/plugins/filter/get_registrable_domain.yml' 2023-04-28 05:57:49,892 wheel INFO adding 'ansible_collections/community/dns/plugins/filter/remove_public_suffix.yml' 2023-04-28 05:57:49,892 wheel INFO adding 'ansible_collections/community/dns/plugins/filter/remove_registrable_domain.yml' 2023-04-28 05:57:49,893 wheel INFO adding 'ansible_collections/community/dns/plugins/inventory/hetzner_dns_records.py' 2023-04-28 05:57:49,893 wheel INFO adding 'ansible_collections/community/dns/plugins/inventory/hosttech_dns_records.py' 2023-04-28 05:57:49,893 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/argspec.py' 2023-04-28 05:57:49,893 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/http.py' 2023-04-28 05:57:49,894 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/json_api_helper.py' 2023-04-28 05:57:49,894 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/names.py' 2023-04-28 05:57:49,894 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/options.py' 2023-04-28 05:57:49,894 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/provider.py' 2023-04-28 05:57:49,895 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/record.py' 2023-04-28 05:57:49,895 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/resolver.py' 2023-04-28 05:57:49,895 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/wsdl.py' 2023-04-28 05:57:49,895 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/zone.py' 2023-04-28 05:57:49,896 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/zone_record_api.py' 2023-04-28 05:57:49,896 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/zone_record_helpers.py' 2023-04-28 05:57:49,896 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/conversion/base.py' 2023-04-28 05:57:49,896 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/conversion/converter.py' 2023-04-28 05:57:49,897 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/conversion/txt.py' 2023-04-28 05:57:49,897 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/hetzner/api.py' 2023-04-28 05:57:49,897 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/hosttech/api.py' 2023-04-28 05:57:49,898 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/hosttech/json_api.py' 2023-04-28 05:57:49,898 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/hosttech/wsdl_api.py' 2023-04-28 05:57:49,898 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/module/_utils.py' 2023-04-28 05:57:49,898 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/module/record.py' 2023-04-28 05:57:49,899 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/module/record_info.py' 2023-04-28 05:57:49,899 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/module/record_set.py' 2023-04-28 05:57:49,899 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/module/record_set_info.py' 2023-04-28 05:57:49,899 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/module/record_sets.py' 2023-04-28 05:57:49,900 wheel INFO adding 'ansible_collections/community/dns/plugins/module_utils/module/zone_info.py' 2023-04-28 05:57:49,900 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hetzner_dns_record.py' 2023-04-28 05:57:49,900 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hetzner_dns_record_info.py' 2023-04-28 05:57:49,900 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hetzner_dns_record_set.py' 2023-04-28 05:57:49,901 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hetzner_dns_record_set_info.py' 2023-04-28 05:57:49,901 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hetzner_dns_record_sets.py' 2023-04-28 05:57:49,901 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hetzner_dns_zone_info.py' 2023-04-28 05:57:49,901 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hosttech_dns_record.py' 2023-04-28 05:57:49,902 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hosttech_dns_record_info.py' 2023-04-28 05:57:49,902 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hosttech_dns_record_set.py' 2023-04-28 05:57:49,902 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hosttech_dns_record_set_info.py' 2023-04-28 05:57:49,902 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hosttech_dns_record_sets.py' 2023-04-28 05:57:49,903 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hosttech_dns_records.py' 2023-04-28 05:57:49,903 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/hosttech_dns_zone_info.py' 2023-04-28 05:57:49,903 wheel INFO adding 'ansible_collections/community/dns/plugins/modules/wait_for_txt.py' 2023-04-28 05:57:49,903 wheel INFO adding 'ansible_collections/community/dns/plugins/plugin_utils/public_suffix.py' 2023-04-28 05:57:49,904 wheel INFO adding 'ansible_collections/community/dns/plugins/plugin_utils/templated_options.py' 2023-04-28 05:57:49,904 wheel INFO adding 'ansible_collections/community/dns/plugins/plugin_utils/inventory/records.py' 2023-04-28 05:57:49,904 wheel INFO adding 'ansible_collections/community/docker/CHANGELOG.rst' 2023-04-28 05:57:49,905 wheel INFO adding 'ansible_collections/community/docker/CHANGELOG.rst.license' 2023-04-28 05:57:49,905 wheel INFO adding 'ansible_collections/community/docker/COPYING' 2023-04-28 05:57:49,906 wheel INFO adding 'ansible_collections/community/docker/FILES.json' 2023-04-28 05:57:49,907 wheel INFO adding 'ansible_collections/community/docker/MANIFEST.json' 2023-04-28 05:57:49,907 wheel INFO adding 'ansible_collections/community/docker/README.md' 2023-04-28 05:57:49,907 wheel INFO adding 'ansible_collections/community/docker/LICENSES/Apache-2.0.txt' 2023-04-28 05:57:49,907 wheel INFO adding 'ansible_collections/community/docker/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:49,908 wheel INFO adding 'ansible_collections/community/docker/changelogs/changelog.yaml' 2023-04-28 05:57:49,908 wheel INFO adding 'ansible_collections/community/docker/changelogs/changelog.yaml.license' 2023-04-28 05:57:49,909 wheel INFO adding 'ansible_collections/community/docker/changelogs/config.yaml' 2023-04-28 05:57:49,909 wheel INFO adding 'ansible_collections/community/docker/changelogs/fragments/.keep' 2023-04-28 05:57:49,909 wheel INFO adding 'ansible_collections/community/docker/meta/ee-bindep.txt' 2023-04-28 05:57:49,909 wheel INFO adding 'ansible_collections/community/docker/meta/ee-requirements.txt' 2023-04-28 05:57:49,910 wheel INFO adding 'ansible_collections/community/docker/meta/execution-environment.yml' 2023-04-28 05:57:49,910 wheel INFO adding 'ansible_collections/community/docker/meta/runtime.yml' 2023-04-28 05:57:49,910 wheel INFO adding 'ansible_collections/community/docker/plugins/action/docker_container_copy_into.py' 2023-04-28 05:57:49,910 wheel INFO adding 'ansible_collections/community/docker/plugins/connection/docker.py' 2023-04-28 05:57:49,911 wheel INFO adding 'ansible_collections/community/docker/plugins/connection/docker_api.py' 2023-04-28 05:57:49,911 wheel INFO adding 'ansible_collections/community/docker/plugins/connection/nsenter.py' 2023-04-28 05:57:49,911 wheel INFO adding 'ansible_collections/community/docker/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:49,912 wheel INFO adding 'ansible_collections/community/docker/plugins/doc_fragments/docker.py' 2023-04-28 05:57:49,912 wheel INFO adding 'ansible_collections/community/docker/plugins/inventory/docker_containers.py' 2023-04-28 05:57:49,912 wheel INFO adding 'ansible_collections/community/docker/plugins/inventory/docker_machine.py' 2023-04-28 05:57:49,913 wheel INFO adding 'ansible_collections/community/docker/plugins/inventory/docker_swarm.py' 2023-04-28 05:57:49,913 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_scramble.py' 2023-04-28 05:57:49,913 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/common.py' 2023-04-28 05:57:49,914 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/common_api.py' 2023-04-28 05:57:49,914 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/copy.py' 2023-04-28 05:57:49,914 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/image_archive.py' 2023-04-28 05:57:49,914 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/socket_handler.py' 2023-04-28 05:57:49,915 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/socket_helper.py' 2023-04-28 05:57:49,915 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/swarm.py' 2023-04-28 05:57:49,915 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/util.py' 2023-04-28 05:57:49,915 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/version.py' 2023-04-28 05:57:49,916 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/_import_helper.py' 2023-04-28 05:57:49,916 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/auth.py' 2023-04-28 05:57:49,916 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/constants.py' 2023-04-28 05:57:49,917 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/errors.py' 2023-04-28 05:57:49,917 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/tls.py' 2023-04-28 05:57:49,917 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/api/client.py' 2023-04-28 05:57:49,917 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/api/daemon.py' 2023-04-28 05:57:49,918 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/credentials/constants.py' 2023-04-28 05:57:49,918 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/credentials/errors.py' 2023-04-28 05:57:49,918 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/credentials/store.py' 2023-04-28 05:57:49,918 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/credentials/utils.py' 2023-04-28 05:57:49,919 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/transport/basehttpadapter.py' 2023-04-28 05:57:49,919 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/transport/npipeconn.py' 2023-04-28 05:57:49,919 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/transport/npipesocket.py' 2023-04-28 05:57:49,919 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/transport/sshconn.py' 2023-04-28 05:57:49,920 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/transport/ssladapter.py' 2023-04-28 05:57:49,920 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/transport/unixconn.py' 2023-04-28 05:57:49,920 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/types/daemon.py' 2023-04-28 05:57:49,920 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/build.py' 2023-04-28 05:57:49,921 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/config.py' 2023-04-28 05:57:49,921 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/decorators.py' 2023-04-28 05:57:49,921 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/fnmatch.py' 2023-04-28 05:57:49,921 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/json_stream.py' 2023-04-28 05:57:49,922 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/ports.py' 2023-04-28 05:57:49,922 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/proxy.py' 2023-04-28 05:57:49,922 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/socket.py' 2023-04-28 05:57:49,922 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/_api/utils/utils.py' 2023-04-28 05:57:49,923 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/module_container/base.py' 2023-04-28 05:57:49,923 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/module_container/docker_api.py' 2023-04-28 05:57:49,924 wheel INFO adding 'ansible_collections/community/docker/plugins/module_utils/module_container/module.py' 2023-04-28 05:57:49,924 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/current_container_facts.py' 2023-04-28 05:57:49,925 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_compose.py' 2023-04-28 05:57:49,925 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_config.py' 2023-04-28 05:57:49,925 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_container.py' 2023-04-28 05:57:49,926 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_container_copy_into.py' 2023-04-28 05:57:49,926 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_container_exec.py' 2023-04-28 05:57:49,927 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_container_info.py' 2023-04-28 05:57:49,927 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_host_info.py' 2023-04-28 05:57:49,927 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_image.py' 2023-04-28 05:57:49,928 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_image_info.py' 2023-04-28 05:57:49,928 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_image_load.py' 2023-04-28 05:57:49,928 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_login.py' 2023-04-28 05:57:49,929 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_network.py' 2023-04-28 05:57:49,929 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_network_info.py' 2023-04-28 05:57:49,929 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_node.py' 2023-04-28 05:57:49,929 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_node_info.py' 2023-04-28 05:57:49,930 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_plugin.py' 2023-04-28 05:57:49,930 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_prune.py' 2023-04-28 05:57:49,930 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_secret.py' 2023-04-28 05:57:49,931 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_stack.py' 2023-04-28 05:57:49,931 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_stack_info.py' 2023-04-28 05:57:49,931 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_stack_task_info.py' 2023-04-28 05:57:49,931 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_swarm.py' 2023-04-28 05:57:49,932 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_swarm_info.py' 2023-04-28 05:57:49,932 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_swarm_service.py' 2023-04-28 05:57:49,933 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_swarm_service_info.py' 2023-04-28 05:57:49,933 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_volume.py' 2023-04-28 05:57:49,933 wheel INFO adding 'ansible_collections/community/docker/plugins/modules/docker_volume_info.py' 2023-04-28 05:57:49,934 wheel INFO adding 'ansible_collections/community/docker/plugins/plugin_utils/common.py' 2023-04-28 05:57:49,934 wheel INFO adding 'ansible_collections/community/docker/plugins/plugin_utils/common_api.py' 2023-04-28 05:57:49,934 wheel INFO adding 'ansible_collections/community/docker/plugins/plugin_utils/socket_handler.py' 2023-04-28 05:57:49,934 wheel INFO adding 'ansible_collections/community/fortios/CHANGELOG.rst' 2023-04-28 05:57:49,935 wheel INFO adding 'ansible_collections/community/fortios/FILES.json' 2023-04-28 05:57:49,935 wheel INFO adding 'ansible_collections/community/fortios/LICENSE' 2023-04-28 05:57:49,935 wheel INFO adding 'ansible_collections/community/fortios/MANIFEST.json' 2023-04-28 05:57:49,936 wheel INFO adding 'ansible_collections/community/fortios/README.md' 2023-04-28 05:57:49,936 wheel INFO adding 'ansible_collections/community/fortios/changelogs/changelog.yaml' 2023-04-28 05:57:49,936 wheel INFO adding 'ansible_collections/community/fortios/changelogs/config.yaml' 2023-04-28 05:57:49,936 wheel INFO adding 'ansible_collections/community/fortios/changelogs/fragments/.keep' 2023-04-28 05:57:49,937 wheel INFO adding 'ansible_collections/community/fortios/meta/runtime.yml' 2023-04-28 05:57:49,937 wheel INFO adding 'ansible_collections/community/fortios/plugins/httpapi/fortianalyzer.py' 2023-04-28 05:57:49,937 wheel INFO adding 'ansible_collections/community/fortios/plugins/httpapi/fortimanager.py' 2023-04-28 05:57:49,938 wheel INFO adding 'ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/common.py' 2023-04-28 05:57:49,938 wheel INFO adding 'ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/fortianalyzer.py' 2023-04-28 05:57:49,938 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/faz_device.py' 2023-04-28 05:57:49,939 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_device.py' 2023-04-28 05:57:49,939 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_device_config.py' 2023-04-28 05:57:49,939 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_device_group.py' 2023-04-28 05:57:49,940 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_device_provision_template.py' 2023-04-28 05:57:49,940 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_address.py' 2023-04-28 05:57:49,940 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_ippool.py' 2023-04-28 05:57:49,941 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_ippool6.py' 2023-04-28 05:57:49,941 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_service.py' 2023-04-28 05:57:49,942 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_fwobj_vip.py' 2023-04-28 05:57:49,943 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_fwpol_ipv4.py' 2023-04-28 05:57:49,943 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_fwpol_package.py' 2023-04-28 05:57:49,943 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_ha.py' 2023-04-28 05:57:49,944 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_provisioning.py' 2023-04-28 05:57:49,944 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_query.py' 2023-04-28 05:57:49,944 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_script.py' 2023-04-28 05:57:49,944 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_appctrl.py' 2023-04-28 05:57:49,945 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_av.py' 2023-04-28 05:57:49,945 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_dns.py' 2023-04-28 05:57:49,946 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_ips.py' 2023-04-28 05:57:49,946 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_profile_group.py' 2023-04-28 05:57:49,946 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_proxy.py' 2023-04-28 05:57:49,947 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_spam.py' 2023-04-28 05:57:49,947 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_ssl_ssh.py' 2023-04-28 05:57:49,948 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_voip.py' 2023-04-28 05:57:49,948 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_waf.py' 2023-04-28 05:57:49,949 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_wanopt.py' 2023-04-28 05:57:49,949 wheel INFO adding 'ansible_collections/community/fortios/plugins/modules/fmgr_secprof_web.py' 2023-04-28 05:57:49,950 wheel INFO adding 'ansible_collections/community/general/CHANGELOG.rst' 2023-04-28 05:57:49,950 wheel INFO adding 'ansible_collections/community/general/CHANGELOG.rst.license' 2023-04-28 05:57:49,950 wheel INFO adding 'ansible_collections/community/general/CONTRIBUTING.md' 2023-04-28 05:57:49,951 wheel INFO adding 'ansible_collections/community/general/COPYING' 2023-04-28 05:57:49,953 wheel INFO adding 'ansible_collections/community/general/FILES.json' 2023-04-28 05:57:49,956 wheel INFO adding 'ansible_collections/community/general/MANIFEST.json' 2023-04-28 05:57:49,956 wheel INFO adding 'ansible_collections/community/general/README.md' 2023-04-28 05:57:49,957 wheel INFO adding 'ansible_collections/community/general/commit-rights.md' 2023-04-28 05:57:49,957 wheel INFO adding 'ansible_collections/community/general/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:49,957 wheel INFO adding 'ansible_collections/community/general/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:49,958 wheel INFO adding 'ansible_collections/community/general/LICENSES/MIT.txt' 2023-04-28 05:57:49,958 wheel INFO adding 'ansible_collections/community/general/LICENSES/PSF-2.0.txt' 2023-04-28 05:57:49,958 wheel INFO adding 'ansible_collections/community/general/changelogs/.gitignore' 2023-04-28 05:57:49,959 wheel INFO adding 'ansible_collections/community/general/changelogs/changelog.yaml' 2023-04-28 05:57:49,959 wheel INFO adding 'ansible_collections/community/general/changelogs/changelog.yaml.license' 2023-04-28 05:57:49,959 wheel INFO adding 'ansible_collections/community/general/changelogs/config.yaml' 2023-04-28 05:57:49,960 wheel INFO adding 'ansible_collections/community/general/changelogs/fragments/.keep' 2023-04-28 05:57:49,960 wheel INFO adding 'ansible_collections/community/general/meta/runtime.yml' 2023-04-28 05:57:49,962 wheel INFO adding 'ansible_collections/community/general/plugins/action/iptables_state.py' 2023-04-28 05:57:49,962 wheel INFO adding 'ansible_collections/community/general/plugins/action/shutdown.py' 2023-04-28 05:57:49,962 wheel INFO adding 'ansible_collections/community/general/plugins/become/doas.py' 2023-04-28 05:57:49,962 wheel INFO adding 'ansible_collections/community/general/plugins/become/dzdo.py' 2023-04-28 05:57:49,963 wheel INFO adding 'ansible_collections/community/general/plugins/become/ksu.py' 2023-04-28 05:57:49,963 wheel INFO adding 'ansible_collections/community/general/plugins/become/machinectl.py' 2023-04-28 05:57:49,963 wheel INFO adding 'ansible_collections/community/general/plugins/become/pbrun.py' 2023-04-28 05:57:49,963 wheel INFO adding 'ansible_collections/community/general/plugins/become/pfexec.py' 2023-04-28 05:57:49,964 wheel INFO adding 'ansible_collections/community/general/plugins/become/pmrun.py' 2023-04-28 05:57:49,964 wheel INFO adding 'ansible_collections/community/general/plugins/become/sesu.py' 2023-04-28 05:57:49,964 wheel INFO adding 'ansible_collections/community/general/plugins/become/sudosu.py' 2023-04-28 05:57:49,964 wheel INFO adding 'ansible_collections/community/general/plugins/cache/memcached.py' 2023-04-28 05:57:49,965 wheel INFO adding 'ansible_collections/community/general/plugins/cache/pickle.py' 2023-04-28 05:57:49,965 wheel INFO adding 'ansible_collections/community/general/plugins/cache/redis.py' 2023-04-28 05:57:49,965 wheel INFO adding 'ansible_collections/community/general/plugins/cache/yaml.py' 2023-04-28 05:57:49,965 wheel INFO adding 'ansible_collections/community/general/plugins/callback/cgroup_memory_recap.py' 2023-04-28 05:57:49,966 wheel INFO adding 'ansible_collections/community/general/plugins/callback/context_demo.py' 2023-04-28 05:57:49,966 wheel INFO adding 'ansible_collections/community/general/plugins/callback/counter_enabled.py' 2023-04-28 05:57:49,966 wheel INFO adding 'ansible_collections/community/general/plugins/callback/dense.py' 2023-04-28 05:57:49,966 wheel INFO adding 'ansible_collections/community/general/plugins/callback/diy.py' 2023-04-28 05:57:49,967 wheel INFO adding 'ansible_collections/community/general/plugins/callback/elastic.py' 2023-04-28 05:57:49,967 wheel INFO adding 'ansible_collections/community/general/plugins/callback/hipchat.py' 2023-04-28 05:57:49,967 wheel INFO adding 'ansible_collections/community/general/plugins/callback/jabber.py' 2023-04-28 05:57:49,968 wheel INFO adding 'ansible_collections/community/general/plugins/callback/log_plays.py' 2023-04-28 05:57:49,968 wheel INFO adding 'ansible_collections/community/general/plugins/callback/loganalytics.py' 2023-04-28 05:57:49,968 wheel INFO adding 'ansible_collections/community/general/plugins/callback/logdna.py' 2023-04-28 05:57:49,969 wheel INFO adding 'ansible_collections/community/general/plugins/callback/logentries.py' 2023-04-28 05:57:49,969 wheel INFO adding 'ansible_collections/community/general/plugins/callback/logstash.py' 2023-04-28 05:57:49,969 wheel INFO adding 'ansible_collections/community/general/plugins/callback/mail.py' 2023-04-28 05:57:49,969 wheel INFO adding 'ansible_collections/community/general/plugins/callback/nrdp.py' 2023-04-28 05:57:49,970 wheel INFO adding 'ansible_collections/community/general/plugins/callback/null.py' 2023-04-28 05:57:49,970 wheel INFO adding 'ansible_collections/community/general/plugins/callback/opentelemetry.py' 2023-04-28 05:57:49,970 wheel INFO adding 'ansible_collections/community/general/plugins/callback/say.py' 2023-04-28 05:57:49,970 wheel INFO adding 'ansible_collections/community/general/plugins/callback/selective.py' 2023-04-28 05:57:49,971 wheel INFO adding 'ansible_collections/community/general/plugins/callback/slack.py' 2023-04-28 05:57:49,971 wheel INFO adding 'ansible_collections/community/general/plugins/callback/splunk.py' 2023-04-28 05:57:49,971 wheel INFO adding 'ansible_collections/community/general/plugins/callback/sumologic.py' 2023-04-28 05:57:49,971 wheel INFO adding 'ansible_collections/community/general/plugins/callback/syslog_json.py' 2023-04-28 05:57:49,972 wheel INFO adding 'ansible_collections/community/general/plugins/callback/unixy.py' 2023-04-28 05:57:49,972 wheel INFO adding 'ansible_collections/community/general/plugins/callback/yaml.py' 2023-04-28 05:57:49,972 wheel INFO adding 'ansible_collections/community/general/plugins/connection/chroot.py' 2023-04-28 05:57:49,973 wheel INFO adding 'ansible_collections/community/general/plugins/connection/funcd.py' 2023-04-28 05:57:49,973 wheel INFO adding 'ansible_collections/community/general/plugins/connection/iocage.py' 2023-04-28 05:57:49,973 wheel INFO adding 'ansible_collections/community/general/plugins/connection/jail.py' 2023-04-28 05:57:49,973 wheel INFO adding 'ansible_collections/community/general/plugins/connection/lxc.py' 2023-04-28 05:57:49,974 wheel INFO adding 'ansible_collections/community/general/plugins/connection/lxd.py' 2023-04-28 05:57:49,974 wheel INFO adding 'ansible_collections/community/general/plugins/connection/qubes.py' 2023-04-28 05:57:49,974 wheel INFO adding 'ansible_collections/community/general/plugins/connection/saltstack.py' 2023-04-28 05:57:49,974 wheel INFO adding 'ansible_collections/community/general/plugins/connection/zone.py' 2023-04-28 05:57:49,975 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/alicloud.py' 2023-04-28 05:57:49,975 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:49,975 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/auth_basic.py' 2023-04-28 05:57:49,975 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/bitbucket.py' 2023-04-28 05:57:49,975 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/dimensiondata.py' 2023-04-28 05:57:49,976 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/dimensiondata_wait.py' 2023-04-28 05:57:49,976 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/emc.py' 2023-04-28 05:57:49,976 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/gitlab.py' 2023-04-28 05:57:49,976 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/hpe3par.py' 2023-04-28 05:57:49,977 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/hwc.py' 2023-04-28 05:57:49,977 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/ibm_storage.py' 2023-04-28 05:57:49,977 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/influxdb.py' 2023-04-28 05:57:49,977 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/ipa.py' 2023-04-28 05:57:49,977 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/keycloak.py' 2023-04-28 05:57:49,978 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/ldap.py' 2023-04-28 05:57:49,978 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/lxca_common.py' 2023-04-28 05:57:49,978 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/manageiq.py' 2023-04-28 05:57:49,978 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/nomad.py' 2023-04-28 05:57:49,979 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/oneview.py' 2023-04-28 05:57:49,979 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/online.py' 2023-04-28 05:57:49,979 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/opennebula.py' 2023-04-28 05:57:49,979 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/openswitch.py' 2023-04-28 05:57:49,979 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/oracle.py' 2023-04-28 05:57:49,980 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/oracle_creatable_resource.py' 2023-04-28 05:57:49,980 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/oracle_display_name_option.py' 2023-04-28 05:57:49,980 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/oracle_name_option.py' 2023-04-28 05:57:49,980 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/oracle_tags.py' 2023-04-28 05:57:49,980 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/oracle_wait_options.py' 2023-04-28 05:57:49,981 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/pritunl.py' 2023-04-28 05:57:49,981 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/proxmox.py' 2023-04-28 05:57:49,981 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/purestorage.py' 2023-04-28 05:57:49,981 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/rackspace.py' 2023-04-28 05:57:49,982 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/redis.py' 2023-04-28 05:57:49,982 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/rundeck.py' 2023-04-28 05:57:49,982 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/scaleway.py' 2023-04-28 05:57:49,982 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/scaleway_waitable_resource.py' 2023-04-28 05:57:49,982 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/utm.py' 2023-04-28 05:57:49,983 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/vexata.py' 2023-04-28 05:57:49,983 wheel INFO adding 'ansible_collections/community/general/plugins/doc_fragments/xenserver.py' 2023-04-28 05:57:49,983 wheel INFO adding 'ansible_collections/community/general/plugins/filter/counter.py' 2023-04-28 05:57:49,983 wheel INFO adding 'ansible_collections/community/general/plugins/filter/crc32.py' 2023-04-28 05:57:49,984 wheel INFO adding 'ansible_collections/community/general/plugins/filter/dict.py' 2023-04-28 05:57:49,984 wheel INFO adding 'ansible_collections/community/general/plugins/filter/dict_kv.py' 2023-04-28 05:57:49,984 wheel INFO adding 'ansible_collections/community/general/plugins/filter/from_csv.py' 2023-04-28 05:57:49,984 wheel INFO adding 'ansible_collections/community/general/plugins/filter/groupby_as_dict.py' 2023-04-28 05:57:49,984 wheel INFO adding 'ansible_collections/community/general/plugins/filter/hashids.py' 2023-04-28 05:57:49,985 wheel INFO adding 'ansible_collections/community/general/plugins/filter/hashids_decode.yml' 2023-04-28 05:57:49,985 wheel INFO adding 'ansible_collections/community/general/plugins/filter/hashids_encode.yml' 2023-04-28 05:57:49,985 wheel INFO adding 'ansible_collections/community/general/plugins/filter/jc.py' 2023-04-28 05:57:49,985 wheel INFO adding 'ansible_collections/community/general/plugins/filter/json_query.py' 2023-04-28 05:57:49,986 wheel INFO adding 'ansible_collections/community/general/plugins/filter/lists_mergeby.py' 2023-04-28 05:57:49,986 wheel INFO adding 'ansible_collections/community/general/plugins/filter/random_mac.py' 2023-04-28 05:57:49,986 wheel INFO adding 'ansible_collections/community/general/plugins/filter/time.py' 2023-04-28 05:57:49,986 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_days.yml' 2023-04-28 05:57:49,986 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_hours.yml' 2023-04-28 05:57:49,987 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_milliseconds.yml' 2023-04-28 05:57:49,987 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_minutes.yml' 2023-04-28 05:57:49,987 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_months.yml' 2023-04-28 05:57:49,987 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_seconds.yml' 2023-04-28 05:57:49,988 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_time_unit.yml' 2023-04-28 05:57:49,988 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_weeks.yml' 2023-04-28 05:57:49,988 wheel INFO adding 'ansible_collections/community/general/plugins/filter/to_years.yml' 2023-04-28 05:57:49,988 wheel INFO adding 'ansible_collections/community/general/plugins/filter/unicode_normalize.py' 2023-04-28 05:57:49,988 wheel INFO adding 'ansible_collections/community/general/plugins/filter/version_sort.py' 2023-04-28 05:57:49,989 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/cobbler.py' 2023-04-28 05:57:49,989 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/gitlab_runners.py' 2023-04-28 05:57:49,989 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/icinga2.py' 2023-04-28 05:57:49,990 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/linode.py' 2023-04-28 05:57:49,990 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/lxd.py' 2023-04-28 05:57:49,990 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/nmap.py' 2023-04-28 05:57:49,991 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/online.py' 2023-04-28 05:57:49,991 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/opennebula.py' 2023-04-28 05:57:49,991 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/proxmox.py' 2023-04-28 05:57:49,992 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/scaleway.py' 2023-04-28 05:57:49,992 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/stackpath_compute.py' 2023-04-28 05:57:49,992 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/virtualbox.py' 2023-04-28 05:57:49,992 wheel INFO adding 'ansible_collections/community/general/plugins/inventory/xen_orchestra.py' 2023-04-28 05:57:49,993 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/bitwarden.py' 2023-04-28 05:57:49,993 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/cartesian.py' 2023-04-28 05:57:49,993 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/chef_databag.py' 2023-04-28 05:57:49,993 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/collection_version.py' 2023-04-28 05:57:49,994 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/consul_kv.py' 2023-04-28 05:57:49,994 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/credstash.py' 2023-04-28 05:57:49,994 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/cyberarkpassword.py' 2023-04-28 05:57:49,994 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/dependent.py' 2023-04-28 05:57:49,995 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/dig.py' 2023-04-28 05:57:49,995 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/dnstxt.py' 2023-04-28 05:57:49,995 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/dsv.py' 2023-04-28 05:57:49,996 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/etcd.py' 2023-04-28 05:57:49,996 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/etcd3.py' 2023-04-28 05:57:49,996 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/filetree.py' 2023-04-28 05:57:49,996 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/flattened.py' 2023-04-28 05:57:49,997 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/hiera.py' 2023-04-28 05:57:49,997 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/keyring.py' 2023-04-28 05:57:49,997 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/lastpass.py' 2023-04-28 05:57:49,997 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/lmdb_kv.py' 2023-04-28 05:57:49,997 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/manifold.py' 2023-04-28 05:57:49,998 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/merge_variables.py' 2023-04-28 05:57:49,998 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/onepassword.py' 2023-04-28 05:57:49,998 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/onepassword_raw.py' 2023-04-28 05:57:49,999 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/passwordstore.py' 2023-04-28 05:57:49,999 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/random_pet.py' 2023-04-28 05:57:49,999 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/random_string.py' 2023-04-28 05:57:50,000 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/random_words.py' 2023-04-28 05:57:50,000 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/redis.py' 2023-04-28 05:57:50,000 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/revbitspss.py' 2023-04-28 05:57:50,000 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/shelvefile.py' 2023-04-28 05:57:50,000 wheel INFO adding 'ansible_collections/community/general/plugins/lookup/tss.py' 2023-04-28 05:57:50,001 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/_mount.py' 2023-04-28 05:57:50,001 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/_stormssh.py' 2023-04-28 05:57:50,001 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/alicloud_ecs.py' 2023-04-28 05:57:50,002 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/btrfs.py' 2023-04-28 05:57:50,002 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/cloud.py' 2023-04-28 05:57:50,002 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/cmd_runner.py' 2023-04-28 05:57:50,002 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/csv.py' 2023-04-28 05:57:50,003 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/database.py' 2023-04-28 05:57:50,003 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/deps.py' 2023-04-28 05:57:50,003 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/dimensiondata.py' 2023-04-28 05:57:50,003 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/gandi_livedns_api.py' 2023-04-28 05:57:50,004 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/gconftool2.py' 2023-04-28 05:57:50,004 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/gitlab.py' 2023-04-28 05:57:50,005 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/heroku.py' 2023-04-28 05:57:50,005 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/hwc_utils.py' 2023-04-28 05:57:50,005 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/ibm_sa_utils.py' 2023-04-28 05:57:50,005 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/ilo_redfish_utils.py' 2023-04-28 05:57:50,006 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/influxdb.py' 2023-04-28 05:57:50,007 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/ipa.py' 2023-04-28 05:57:50,007 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/jenkins.py' 2023-04-28 05:57:50,007 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/known_hosts.py' 2023-04-28 05:57:50,007 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/ldap.py' 2023-04-28 05:57:50,008 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/linode.py' 2023-04-28 05:57:50,008 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/lxd.py' 2023-04-28 05:57:50,008 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/manageiq.py' 2023-04-28 05:57:50,008 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/memset.py' 2023-04-28 05:57:50,009 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/module_helper.py' 2023-04-28 05:57:50,009 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/ocapi_utils.py' 2023-04-28 05:57:50,009 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/oneandone.py' 2023-04-28 05:57:50,010 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/onepassword.py' 2023-04-28 05:57:50,010 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/oneview.py' 2023-04-28 05:57:50,010 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/online.py' 2023-04-28 05:57:50,010 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/opennebula.py' 2023-04-28 05:57:50,011 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/pipx.py' 2023-04-28 05:57:50,011 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/proxmox.py' 2023-04-28 05:57:50,011 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/puppet.py' 2023-04-28 05:57:50,011 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/pure.py' 2023-04-28 05:57:50,012 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/rax.py' 2023-04-28 05:57:50,012 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/redfish_utils.py' 2023-04-28 05:57:50,013 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/redhat.py' 2023-04-28 05:57:50,013 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/redis.py' 2023-04-28 05:57:50,013 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/rundeck.py' 2023-04-28 05:57:50,014 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/saslprep.py' 2023-04-28 05:57:50,014 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/scaleway.py' 2023-04-28 05:57:50,014 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/ssh.py' 2023-04-28 05:57:50,014 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/univention_umc.py' 2023-04-28 05:57:50,015 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/utm_utils.py' 2023-04-28 05:57:50,015 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/version.py' 2023-04-28 05:57:50,015 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/vexata.py' 2023-04-28 05:57:50,015 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/wdc_redfish_utils.py' 2023-04-28 05:57:50,016 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/xenserver.py' 2023-04-28 05:57:50,016 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/xfconf.py' 2023-04-28 05:57:50,017 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/identity/keycloak/keycloak.py' 2023-04-28 05:57:50,018 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/identity/keycloak/keycloak_clientsecret.py' 2023-04-28 05:57:50,018 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/base.py' 2023-04-28 05:57:50,018 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/deco.py' 2023-04-28 05:57:50,018 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/exceptions.py' 2023-04-28 05:57:50,019 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/module_helper.py' 2023-04-28 05:57:50,019 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/mixins/cmd.py' 2023-04-28 05:57:50,019 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/mixins/deprecate_attrs.py' 2023-04-28 05:57:50,019 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/mixins/deps.py' 2023-04-28 05:57:50,019 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/mixins/state.py' 2023-04-28 05:57:50,020 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/mh/mixins/vars.py' 2023-04-28 05:57:50,020 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/net_tools/pritunl/api.py' 2023-04-28 05:57:50,021 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/oracle/oci_utils.py' 2023-04-28 05:57:50,021 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/remote_management/lxca/common.py' 2023-04-28 05:57:50,021 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/source_control/bitbucket.py' 2023-04-28 05:57:50,022 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/storage/emc/emc_vnx.py' 2023-04-28 05:57:50,022 wheel INFO adding 'ansible_collections/community/general/plugins/module_utils/storage/hpe3par/hpe3par.py' 2023-04-28 05:57:50,023 wheel INFO adding 'ansible_collections/community/general/plugins/modules/aerospike_migrations.py' 2023-04-28 05:57:50,023 wheel INFO adding 'ansible_collections/community/general/plugins/modules/airbrake_deployment.py' 2023-04-28 05:57:50,024 wheel INFO adding 'ansible_collections/community/general/plugins/modules/aix_devices.py' 2023-04-28 05:57:50,024 wheel INFO adding 'ansible_collections/community/general/plugins/modules/aix_filesystem.py' 2023-04-28 05:57:50,024 wheel INFO adding 'ansible_collections/community/general/plugins/modules/aix_inittab.py' 2023-04-28 05:57:50,024 wheel INFO adding 'ansible_collections/community/general/plugins/modules/aix_lvg.py' 2023-04-28 05:57:50,025 wheel INFO adding 'ansible_collections/community/general/plugins/modules/aix_lvol.py' 2023-04-28 05:57:50,025 wheel INFO adding 'ansible_collections/community/general/plugins/modules/alerta_customer.py' 2023-04-28 05:57:50,025 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ali_instance.py' 2023-04-28 05:57:50,026 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ali_instance_info.py' 2023-04-28 05:57:50,026 wheel INFO adding 'ansible_collections/community/general/plugins/modules/alternatives.py' 2023-04-28 05:57:50,026 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ansible_galaxy_install.py' 2023-04-28 05:57:50,027 wheel INFO adding 'ansible_collections/community/general/plugins/modules/apache2_mod_proxy.py' 2023-04-28 05:57:50,027 wheel INFO adding 'ansible_collections/community/general/plugins/modules/apache2_module.py' 2023-04-28 05:57:50,027 wheel INFO adding 'ansible_collections/community/general/plugins/modules/apk.py' 2023-04-28 05:57:50,028 wheel INFO adding 'ansible_collections/community/general/plugins/modules/apt_repo.py' 2023-04-28 05:57:50,028 wheel INFO adding 'ansible_collections/community/general/plugins/modules/apt_rpm.py' 2023-04-28 05:57:50,028 wheel INFO adding 'ansible_collections/community/general/plugins/modules/archive.py' 2023-04-28 05:57:50,029 wheel INFO adding 'ansible_collections/community/general/plugins/modules/atomic_container.py' 2023-04-28 05:57:50,029 wheel INFO adding 'ansible_collections/community/general/plugins/modules/atomic_host.py' 2023-04-28 05:57:50,029 wheel INFO adding 'ansible_collections/community/general/plugins/modules/atomic_image.py' 2023-04-28 05:57:50,029 wheel INFO adding 'ansible_collections/community/general/plugins/modules/awall.py' 2023-04-28 05:57:50,030 wheel INFO adding 'ansible_collections/community/general/plugins/modules/beadm.py' 2023-04-28 05:57:50,030 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bearychat.py' 2023-04-28 05:57:50,030 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bigpanda.py' 2023-04-28 05:57:50,031 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bitbucket_access_key.py' 2023-04-28 05:57:50,031 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bitbucket_pipeline_key_pair.py' 2023-04-28 05:57:50,032 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bitbucket_pipeline_known_host.py' 2023-04-28 05:57:50,033 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bitbucket_pipeline_variable.py' 2023-04-28 05:57:50,033 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bower.py' 2023-04-28 05:57:50,033 wheel INFO adding 'ansible_collections/community/general/plugins/modules/btrfs_info.py' 2023-04-28 05:57:50,034 wheel INFO adding 'ansible_collections/community/general/plugins/modules/btrfs_subvolume.py' 2023-04-28 05:57:50,034 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bundler.py' 2023-04-28 05:57:50,034 wheel INFO adding 'ansible_collections/community/general/plugins/modules/bzr.py' 2023-04-28 05:57:50,035 wheel INFO adding 'ansible_collections/community/general/plugins/modules/campfire.py' 2023-04-28 05:57:50,035 wheel INFO adding 'ansible_collections/community/general/plugins/modules/capabilities.py' 2023-04-28 05:57:50,035 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cargo.py' 2023-04-28 05:57:50,035 wheel INFO adding 'ansible_collections/community/general/plugins/modules/catapult.py' 2023-04-28 05:57:50,036 wheel INFO adding 'ansible_collections/community/general/plugins/modules/circonus_annotation.py' 2023-04-28 05:57:50,036 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cisco_webex.py' 2023-04-28 05:57:50,036 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_aa_policy.py' 2023-04-28 05:57:50,036 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_alert_policy.py' 2023-04-28 05:57:50,037 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_blueprint_package.py' 2023-04-28 05:57:50,037 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_firewall_policy.py' 2023-04-28 05:57:50,037 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_group.py' 2023-04-28 05:57:50,038 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_loadbalancer.py' 2023-04-28 05:57:50,038 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_modify_server.py' 2023-04-28 05:57:50,039 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_publicip.py' 2023-04-28 05:57:50,039 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_server.py' 2023-04-28 05:57:50,039 wheel INFO adding 'ansible_collections/community/general/plugins/modules/clc_server_snapshot.py' 2023-04-28 05:57:50,040 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cloud_init_data_facts.py' 2023-04-28 05:57:50,040 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cloudflare_dns.py' 2023-04-28 05:57:50,040 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cobbler_sync.py' 2023-04-28 05:57:50,041 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cobbler_system.py' 2023-04-28 05:57:50,041 wheel INFO adding 'ansible_collections/community/general/plugins/modules/composer.py' 2023-04-28 05:57:50,041 wheel INFO adding 'ansible_collections/community/general/plugins/modules/consul.py' 2023-04-28 05:57:50,042 wheel INFO adding 'ansible_collections/community/general/plugins/modules/consul_acl.py' 2023-04-28 05:57:50,042 wheel INFO adding 'ansible_collections/community/general/plugins/modules/consul_kv.py' 2023-04-28 05:57:50,042 wheel INFO adding 'ansible_collections/community/general/plugins/modules/consul_session.py' 2023-04-28 05:57:50,043 wheel INFO adding 'ansible_collections/community/general/plugins/modules/copr.py' 2023-04-28 05:57:50,043 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cpanm.py' 2023-04-28 05:57:50,043 wheel INFO adding 'ansible_collections/community/general/plugins/modules/cronvar.py' 2023-04-28 05:57:50,043 wheel INFO adding 'ansible_collections/community/general/plugins/modules/crypttab.py' 2023-04-28 05:57:50,044 wheel INFO adding 'ansible_collections/community/general/plugins/modules/datadog_downtime.py' 2023-04-28 05:57:50,044 wheel INFO adding 'ansible_collections/community/general/plugins/modules/datadog_event.py' 2023-04-28 05:57:50,044 wheel INFO adding 'ansible_collections/community/general/plugins/modules/datadog_monitor.py' 2023-04-28 05:57:50,045 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dconf.py' 2023-04-28 05:57:50,045 wheel INFO adding 'ansible_collections/community/general/plugins/modules/deploy_helper.py' 2023-04-28 05:57:50,045 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dimensiondata_network.py' 2023-04-28 05:57:50,046 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dimensiondata_vlan.py' 2023-04-28 05:57:50,046 wheel INFO adding 'ansible_collections/community/general/plugins/modules/discord.py' 2023-04-28 05:57:50,046 wheel INFO adding 'ansible_collections/community/general/plugins/modules/django_manage.py' 2023-04-28 05:57:50,046 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dnf_versionlock.py' 2023-04-28 05:57:50,047 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dnsimple.py' 2023-04-28 05:57:50,047 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dnsimple_info.py' 2023-04-28 05:57:50,047 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dnsmadeeasy.py' 2023-04-28 05:57:50,048 wheel INFO adding 'ansible_collections/community/general/plugins/modules/dpkg_divert.py' 2023-04-28 05:57:50,048 wheel INFO adding 'ansible_collections/community/general/plugins/modules/easy_install.py' 2023-04-28 05:57:50,048 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ejabberd_user.py' 2023-04-28 05:57:50,049 wheel INFO adding 'ansible_collections/community/general/plugins/modules/elasticsearch_plugin.py' 2023-04-28 05:57:50,049 wheel INFO adding 'ansible_collections/community/general/plugins/modules/emc_vnx_sg_member.py' 2023-04-28 05:57:50,049 wheel INFO adding 'ansible_collections/community/general/plugins/modules/etcd3.py' 2023-04-28 05:57:50,049 wheel INFO adding 'ansible_collections/community/general/plugins/modules/facter.py' 2023-04-28 05:57:50,050 wheel INFO adding 'ansible_collections/community/general/plugins/modules/filesize.py' 2023-04-28 05:57:50,050 wheel INFO adding 'ansible_collections/community/general/plugins/modules/filesystem.py' 2023-04-28 05:57:50,050 wheel INFO adding 'ansible_collections/community/general/plugins/modules/flatpak.py' 2023-04-28 05:57:50,051 wheel INFO adding 'ansible_collections/community/general/plugins/modules/flatpak_remote.py' 2023-04-28 05:57:50,051 wheel INFO adding 'ansible_collections/community/general/plugins/modules/flowdock.py' 2023-04-28 05:57:50,051 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gandi_livedns.py' 2023-04-28 05:57:50,051 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gconftool2.py' 2023-04-28 05:57:50,051 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gconftool2_info.py' 2023-04-28 05:57:50,052 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gem.py' 2023-04-28 05:57:50,052 wheel INFO adding 'ansible_collections/community/general/plugins/modules/git_config.py' 2023-04-28 05:57:50,052 wheel INFO adding 'ansible_collections/community/general/plugins/modules/github_deploy_key.py' 2023-04-28 05:57:50,053 wheel INFO adding 'ansible_collections/community/general/plugins/modules/github_issue.py' 2023-04-28 05:57:50,053 wheel INFO adding 'ansible_collections/community/general/plugins/modules/github_key.py' 2023-04-28 05:57:50,053 wheel INFO adding 'ansible_collections/community/general/plugins/modules/github_release.py' 2023-04-28 05:57:50,053 wheel INFO adding 'ansible_collections/community/general/plugins/modules/github_repo.py' 2023-04-28 05:57:50,054 wheel INFO adding 'ansible_collections/community/general/plugins/modules/github_webhook.py' 2023-04-28 05:57:50,054 wheel INFO adding 'ansible_collections/community/general/plugins/modules/github_webhook_info.py' 2023-04-28 05:57:50,054 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_branch.py' 2023-04-28 05:57:50,054 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_deploy_key.py' 2023-04-28 05:57:50,055 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_group.py' 2023-04-28 05:57:50,055 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_group_members.py' 2023-04-28 05:57:50,055 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_group_variable.py' 2023-04-28 05:57:50,056 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_hook.py' 2023-04-28 05:57:50,056 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_project.py' 2023-04-28 05:57:50,056 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_project_badge.py' 2023-04-28 05:57:50,057 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_project_members.py' 2023-04-28 05:57:50,057 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_project_variable.py' 2023-04-28 05:57:50,057 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_protected_branch.py' 2023-04-28 05:57:50,057 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_runner.py' 2023-04-28 05:57:50,058 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gitlab_user.py' 2023-04-28 05:57:50,058 wheel INFO adding 'ansible_collections/community/general/plugins/modules/grove.py' 2023-04-28 05:57:50,058 wheel INFO adding 'ansible_collections/community/general/plugins/modules/gunicorn.py' 2023-04-28 05:57:50,059 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hana_query.py' 2023-04-28 05:57:50,059 wheel INFO adding 'ansible_collections/community/general/plugins/modules/haproxy.py' 2023-04-28 05:57:50,059 wheel INFO adding 'ansible_collections/community/general/plugins/modules/heroku_collaborator.py' 2023-04-28 05:57:50,059 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hg.py' 2023-04-28 05:57:50,060 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hipchat.py' 2023-04-28 05:57:50,060 wheel INFO adding 'ansible_collections/community/general/plugins/modules/homebrew.py' 2023-04-28 05:57:50,060 wheel INFO adding 'ansible_collections/community/general/plugins/modules/homebrew_cask.py' 2023-04-28 05:57:50,061 wheel INFO adding 'ansible_collections/community/general/plugins/modules/homebrew_tap.py' 2023-04-28 05:57:50,061 wheel INFO adding 'ansible_collections/community/general/plugins/modules/homectl.py' 2023-04-28 05:57:50,061 wheel INFO adding 'ansible_collections/community/general/plugins/modules/honeybadger_deployment.py' 2023-04-28 05:57:50,062 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hpilo_boot.py' 2023-04-28 05:57:50,062 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hpilo_info.py' 2023-04-28 05:57:50,062 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hponcfg.py' 2023-04-28 05:57:50,062 wheel INFO adding 'ansible_collections/community/general/plugins/modules/htpasswd.py' 2023-04-28 05:57:50,063 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_ecs_instance.py' 2023-04-28 05:57:50,063 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_evs_disk.py' 2023-04-28 05:57:50,064 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_network_vpc.py' 2023-04-28 05:57:50,064 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_smn_topic.py' 2023-04-28 05:57:50,064 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_eip.py' 2023-04-28 05:57:50,065 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_peering_connect.py' 2023-04-28 05:57:50,065 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_port.py' 2023-04-28 05:57:50,066 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_private_ip.py' 2023-04-28 05:57:50,066 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_route.py' 2023-04-28 05:57:50,066 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_security_group.py' 2023-04-28 05:57:50,066 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_security_group_rule.py' 2023-04-28 05:57:50,067 wheel INFO adding 'ansible_collections/community/general/plugins/modules/hwc_vpc_subnet.py' 2023-04-28 05:57:50,067 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ibm_sa_domain.py' 2023-04-28 05:57:50,067 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ibm_sa_host.py' 2023-04-28 05:57:50,068 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ibm_sa_host_ports.py' 2023-04-28 05:57:50,068 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ibm_sa_pool.py' 2023-04-28 05:57:50,068 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ibm_sa_vol.py' 2023-04-28 05:57:50,068 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ibm_sa_vol_map.py' 2023-04-28 05:57:50,068 wheel INFO adding 'ansible_collections/community/general/plugins/modules/icinga2_feature.py' 2023-04-28 05:57:50,069 wheel INFO adding 'ansible_collections/community/general/plugins/modules/icinga2_host.py' 2023-04-28 05:57:50,069 wheel INFO adding 'ansible_collections/community/general/plugins/modules/idrac_redfish_command.py' 2023-04-28 05:57:50,069 wheel INFO adding 'ansible_collections/community/general/plugins/modules/idrac_redfish_config.py' 2023-04-28 05:57:50,070 wheel INFO adding 'ansible_collections/community/general/plugins/modules/idrac_redfish_info.py' 2023-04-28 05:57:50,070 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ilo_redfish_command.py' 2023-04-28 05:57:50,070 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ilo_redfish_config.py' 2023-04-28 05:57:50,070 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ilo_redfish_info.py' 2023-04-28 05:57:50,071 wheel INFO adding 'ansible_collections/community/general/plugins/modules/imc_rest.py' 2023-04-28 05:57:50,071 wheel INFO adding 'ansible_collections/community/general/plugins/modules/imgadm.py' 2023-04-28 05:57:50,071 wheel INFO adding 'ansible_collections/community/general/plugins/modules/infinity.py' 2023-04-28 05:57:50,072 wheel INFO adding 'ansible_collections/community/general/plugins/modules/influxdb_database.py' 2023-04-28 05:57:50,072 wheel INFO adding 'ansible_collections/community/general/plugins/modules/influxdb_query.py' 2023-04-28 05:57:50,072 wheel INFO adding 'ansible_collections/community/general/plugins/modules/influxdb_retention_policy.py' 2023-04-28 05:57:50,072 wheel INFO adding 'ansible_collections/community/general/plugins/modules/influxdb_user.py' 2023-04-28 05:57:50,073 wheel INFO adding 'ansible_collections/community/general/plugins/modules/influxdb_write.py' 2023-04-28 05:57:50,073 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ini_file.py' 2023-04-28 05:57:50,073 wheel INFO adding 'ansible_collections/community/general/plugins/modules/installp.py' 2023-04-28 05:57:50,073 wheel INFO adding 'ansible_collections/community/general/plugins/modules/interfaces_file.py' 2023-04-28 05:57:50,074 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ip_netns.py' 2023-04-28 05:57:50,074 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_config.py' 2023-04-28 05:57:50,074 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_dnsrecord.py' 2023-04-28 05:57:50,075 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_dnszone.py' 2023-04-28 05:57:50,075 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_group.py' 2023-04-28 05:57:50,075 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_hbacrule.py' 2023-04-28 05:57:50,075 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_host.py' 2023-04-28 05:57:50,076 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_hostgroup.py' 2023-04-28 05:57:50,076 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_otpconfig.py' 2023-04-28 05:57:50,076 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_otptoken.py' 2023-04-28 05:57:50,077 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_pwpolicy.py' 2023-04-28 05:57:50,077 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_role.py' 2023-04-28 05:57:50,077 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_service.py' 2023-04-28 05:57:50,077 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_subca.py' 2023-04-28 05:57:50,078 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_sudocmd.py' 2023-04-28 05:57:50,078 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_sudocmdgroup.py' 2023-04-28 05:57:50,078 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_sudorule.py' 2023-04-28 05:57:50,079 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_user.py' 2023-04-28 05:57:50,079 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipa_vault.py' 2023-04-28 05:57:50,079 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipify_facts.py' 2023-04-28 05:57:50,079 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipinfoio_facts.py' 2023-04-28 05:57:50,080 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipmi_boot.py' 2023-04-28 05:57:50,080 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipmi_power.py' 2023-04-28 05:57:50,080 wheel INFO adding 'ansible_collections/community/general/plugins/modules/iptables_state.py' 2023-04-28 05:57:50,080 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ipwcli_dns.py' 2023-04-28 05:57:50,081 wheel INFO adding 'ansible_collections/community/general/plugins/modules/irc.py' 2023-04-28 05:57:50,081 wheel INFO adding 'ansible_collections/community/general/plugins/modules/iso_create.py' 2023-04-28 05:57:50,081 wheel INFO adding 'ansible_collections/community/general/plugins/modules/iso_customize.py' 2023-04-28 05:57:50,082 wheel INFO adding 'ansible_collections/community/general/plugins/modules/iso_extract.py' 2023-04-28 05:57:50,082 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jabber.py' 2023-04-28 05:57:50,082 wheel INFO adding 'ansible_collections/community/general/plugins/modules/java_cert.py' 2023-04-28 05:57:50,082 wheel INFO adding 'ansible_collections/community/general/plugins/modules/java_keystore.py' 2023-04-28 05:57:50,083 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jboss.py' 2023-04-28 05:57:50,083 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jenkins_build.py' 2023-04-28 05:57:50,083 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jenkins_job.py' 2023-04-28 05:57:50,084 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jenkins_job_info.py' 2023-04-28 05:57:50,084 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jenkins_plugin.py' 2023-04-28 05:57:50,084 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jenkins_script.py' 2023-04-28 05:57:50,085 wheel INFO adding 'ansible_collections/community/general/plugins/modules/jira.py' 2023-04-28 05:57:50,085 wheel INFO adding 'ansible_collections/community/general/plugins/modules/kdeconfig.py' 2023-04-28 05:57:50,085 wheel INFO adding 'ansible_collections/community/general/plugins/modules/kernel_blacklist.py' 2023-04-28 05:57:50,085 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_authentication.py' 2023-04-28 05:57:50,086 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_authz_authorization_scope.py' 2023-04-28 05:57:50,086 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_client.py' 2023-04-28 05:57:50,086 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_client_rolemapping.py' 2023-04-28 05:57:50,087 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_clientscope.py' 2023-04-28 05:57:50,087 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_clientscope_type.py' 2023-04-28 05:57:50,087 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_clientsecret_info.py' 2023-04-28 05:57:50,088 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_clientsecret_regenerate.py' 2023-04-28 05:57:50,088 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_clienttemplate.py' 2023-04-28 05:57:50,088 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_group.py' 2023-04-28 05:57:50,089 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_identity_provider.py' 2023-04-28 05:57:50,089 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_realm.py' 2023-04-28 05:57:50,089 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_realm_info.py' 2023-04-28 05:57:50,090 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_role.py' 2023-04-28 05:57:50,090 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_user_federation.py' 2023-04-28 05:57:50,090 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keycloak_user_rolemapping.py' 2023-04-28 05:57:50,091 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keyring.py' 2023-04-28 05:57:50,091 wheel INFO adding 'ansible_collections/community/general/plugins/modules/keyring_info.py' 2023-04-28 05:57:50,091 wheel INFO adding 'ansible_collections/community/general/plugins/modules/kibana_plugin.py' 2023-04-28 05:57:50,091 wheel INFO adding 'ansible_collections/community/general/plugins/modules/launchd.py' 2023-04-28 05:57:50,092 wheel INFO adding 'ansible_collections/community/general/plugins/modules/layman.py' 2023-04-28 05:57:50,092 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lbu.py' 2023-04-28 05:57:50,092 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ldap_attrs.py' 2023-04-28 05:57:50,092 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ldap_entry.py' 2023-04-28 05:57:50,093 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ldap_passwd.py' 2023-04-28 05:57:50,093 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ldap_search.py' 2023-04-28 05:57:50,093 wheel INFO adding 'ansible_collections/community/general/plugins/modules/librato_annotation.py' 2023-04-28 05:57:50,093 wheel INFO adding 'ansible_collections/community/general/plugins/modules/linode.py' 2023-04-28 05:57:50,094 wheel INFO adding 'ansible_collections/community/general/plugins/modules/linode_v4.py' 2023-04-28 05:57:50,094 wheel INFO adding 'ansible_collections/community/general/plugins/modules/listen_ports_facts.py' 2023-04-28 05:57:50,094 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lldp.py' 2023-04-28 05:57:50,095 wheel INFO adding 'ansible_collections/community/general/plugins/modules/locale_gen.py' 2023-04-28 05:57:50,095 wheel INFO adding 'ansible_collections/community/general/plugins/modules/logentries.py' 2023-04-28 05:57:50,095 wheel INFO adding 'ansible_collections/community/general/plugins/modules/logentries_msg.py' 2023-04-28 05:57:50,095 wheel INFO adding 'ansible_collections/community/general/plugins/modules/logstash_plugin.py' 2023-04-28 05:57:50,096 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lvg.py' 2023-04-28 05:57:50,096 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lvol.py' 2023-04-28 05:57:50,096 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lxc_container.py' 2023-04-28 05:57:50,097 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lxca_cmms.py' 2023-04-28 05:57:50,097 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lxca_nodes.py' 2023-04-28 05:57:50,097 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lxd_container.py' 2023-04-28 05:57:50,098 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lxd_profile.py' 2023-04-28 05:57:50,098 wheel INFO adding 'ansible_collections/community/general/plugins/modules/lxd_project.py' 2023-04-28 05:57:50,098 wheel INFO adding 'ansible_collections/community/general/plugins/modules/macports.py' 2023-04-28 05:57:50,099 wheel INFO adding 'ansible_collections/community/general/plugins/modules/mail.py' 2023-04-28 05:57:50,099 wheel INFO adding 'ansible_collections/community/general/plugins/modules/make.py' 2023-04-28 05:57:50,099 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_alert_profiles.py' 2023-04-28 05:57:50,099 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_alerts.py' 2023-04-28 05:57:50,100 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_group.py' 2023-04-28 05:57:50,100 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_policies.py' 2023-04-28 05:57:50,100 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_policies_info.py' 2023-04-28 05:57:50,101 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_provider.py' 2023-04-28 05:57:50,101 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_tags.py' 2023-04-28 05:57:50,101 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_tags_info.py' 2023-04-28 05:57:50,102 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_tenant.py' 2023-04-28 05:57:50,102 wheel INFO adding 'ansible_collections/community/general/plugins/modules/manageiq_user.py' 2023-04-28 05:57:50,102 wheel INFO adding 'ansible_collections/community/general/plugins/modules/mas.py' 2023-04-28 05:57:50,102 wheel INFO adding 'ansible_collections/community/general/plugins/modules/matrix.py' 2023-04-28 05:57:50,103 wheel INFO adding 'ansible_collections/community/general/plugins/modules/mattermost.py' 2023-04-28 05:57:50,103 wheel INFO adding 'ansible_collections/community/general/plugins/modules/maven_artifact.py' 2023-04-28 05:57:50,103 wheel INFO adding 'ansible_collections/community/general/plugins/modules/memset_dns_reload.py' 2023-04-28 05:57:50,104 wheel INFO adding 'ansible_collections/community/general/plugins/modules/memset_memstore_info.py' 2023-04-28 05:57:50,104 wheel INFO adding 'ansible_collections/community/general/plugins/modules/memset_server_info.py' 2023-04-28 05:57:50,104 wheel INFO adding 'ansible_collections/community/general/plugins/modules/memset_zone.py' 2023-04-28 05:57:50,104 wheel INFO adding 'ansible_collections/community/general/plugins/modules/memset_zone_domain.py' 2023-04-28 05:57:50,105 wheel INFO adding 'ansible_collections/community/general/plugins/modules/memset_zone_record.py' 2023-04-28 05:57:50,105 wheel INFO adding 'ansible_collections/community/general/plugins/modules/mksysb.py' 2023-04-28 05:57:50,105 wheel INFO adding 'ansible_collections/community/general/plugins/modules/modprobe.py' 2023-04-28 05:57:50,106 wheel INFO adding 'ansible_collections/community/general/plugins/modules/monit.py' 2023-04-28 05:57:50,106 wheel INFO adding 'ansible_collections/community/general/plugins/modules/mqtt.py' 2023-04-28 05:57:50,106 wheel INFO adding 'ansible_collections/community/general/plugins/modules/mssql_db.py' 2023-04-28 05:57:50,106 wheel INFO adding 'ansible_collections/community/general/plugins/modules/mssql_script.py' 2023-04-28 05:57:50,107 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nagios.py' 2023-04-28 05:57:50,107 wheel INFO adding 'ansible_collections/community/general/plugins/modules/netcup_dns.py' 2023-04-28 05:57:50,107 wheel INFO adding 'ansible_collections/community/general/plugins/modules/newrelic_deployment.py' 2023-04-28 05:57:50,108 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nexmo.py' 2023-04-28 05:57:50,108 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nginx_status_info.py' 2023-04-28 05:57:50,108 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nictagadm.py' 2023-04-28 05:57:50,109 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nmcli.py' 2023-04-28 05:57:50,109 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nomad_job.py' 2023-04-28 05:57:50,110 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nomad_job_info.py' 2023-04-28 05:57:50,110 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nosh.py' 2023-04-28 05:57:50,110 wheel INFO adding 'ansible_collections/community/general/plugins/modules/npm.py' 2023-04-28 05:57:50,110 wheel INFO adding 'ansible_collections/community/general/plugins/modules/nsupdate.py' 2023-04-28 05:57:50,111 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ocapi_command.py' 2023-04-28 05:57:50,111 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ocapi_info.py' 2023-04-28 05:57:50,111 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oci_vcn.py' 2023-04-28 05:57:50,112 wheel INFO adding 'ansible_collections/community/general/plugins/modules/odbc.py' 2023-04-28 05:57:50,112 wheel INFO adding 'ansible_collections/community/general/plugins/modules/office_365_connector_card.py' 2023-04-28 05:57:50,112 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ohai.py' 2023-04-28 05:57:50,112 wheel INFO adding 'ansible_collections/community/general/plugins/modules/omapi_host.py' 2023-04-28 05:57:50,113 wheel INFO adding 'ansible_collections/community/general/plugins/modules/one_host.py' 2023-04-28 05:57:50,113 wheel INFO adding 'ansible_collections/community/general/plugins/modules/one_image.py' 2023-04-28 05:57:50,113 wheel INFO adding 'ansible_collections/community/general/plugins/modules/one_image_info.py' 2023-04-28 05:57:50,113 wheel INFO adding 'ansible_collections/community/general/plugins/modules/one_service.py' 2023-04-28 05:57:50,114 wheel INFO adding 'ansible_collections/community/general/plugins/modules/one_template.py' 2023-04-28 05:57:50,114 wheel INFO adding 'ansible_collections/community/general/plugins/modules/one_vm.py' 2023-04-28 05:57:50,115 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneandone_firewall_policy.py' 2023-04-28 05:57:50,115 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneandone_load_balancer.py' 2023-04-28 05:57:50,115 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneandone_monitoring_policy.py' 2023-04-28 05:57:50,116 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneandone_private_network.py' 2023-04-28 05:57:50,116 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneandone_public_ip.py' 2023-04-28 05:57:50,116 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneandone_server.py' 2023-04-28 05:57:50,117 wheel INFO adding 'ansible_collections/community/general/plugins/modules/onepassword_info.py' 2023-04-28 05:57:50,117 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_datacenter_info.py' 2023-04-28 05:57:50,117 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_enclosure_info.py' 2023-04-28 05:57:50,118 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_ethernet_network.py' 2023-04-28 05:57:50,118 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_ethernet_network_info.py' 2023-04-28 05:57:50,118 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_fc_network.py' 2023-04-28 05:57:50,118 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_fc_network_info.py' 2023-04-28 05:57:50,119 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_fcoe_network.py' 2023-04-28 05:57:50,119 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_fcoe_network_info.py' 2023-04-28 05:57:50,119 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_logical_interconnect_group.py' 2023-04-28 05:57:50,119 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_logical_interconnect_group_info.py' 2023-04-28 05:57:50,119 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_network_set.py' 2023-04-28 05:57:50,120 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_network_set_info.py' 2023-04-28 05:57:50,120 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_san_manager.py' 2023-04-28 05:57:50,120 wheel INFO adding 'ansible_collections/community/general/plugins/modules/oneview_san_manager_info.py' 2023-04-28 05:57:50,120 wheel INFO adding 'ansible_collections/community/general/plugins/modules/online_server_info.py' 2023-04-28 05:57:50,121 wheel INFO adding 'ansible_collections/community/general/plugins/modules/online_user_info.py' 2023-04-28 05:57:50,121 wheel INFO adding 'ansible_collections/community/general/plugins/modules/open_iscsi.py' 2023-04-28 05:57:50,121 wheel INFO adding 'ansible_collections/community/general/plugins/modules/openbsd_pkg.py' 2023-04-28 05:57:50,122 wheel INFO adding 'ansible_collections/community/general/plugins/modules/opendj_backendprop.py' 2023-04-28 05:57:50,122 wheel INFO adding 'ansible_collections/community/general/plugins/modules/openwrt_init.py' 2023-04-28 05:57:50,122 wheel INFO adding 'ansible_collections/community/general/plugins/modules/opkg.py' 2023-04-28 05:57:50,122 wheel INFO adding 'ansible_collections/community/general/plugins/modules/osx_defaults.py' 2023-04-28 05:57:50,123 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ovh_ip_failover.py' 2023-04-28 05:57:50,123 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ovh_ip_loadbalancing_backend.py' 2023-04-28 05:57:50,123 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ovh_monthly_billing.py' 2023-04-28 05:57:50,123 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pacemaker_cluster.py' 2023-04-28 05:57:50,124 wheel INFO adding 'ansible_collections/community/general/plugins/modules/packet_device.py' 2023-04-28 05:57:50,124 wheel INFO adding 'ansible_collections/community/general/plugins/modules/packet_ip_subnet.py' 2023-04-28 05:57:50,124 wheel INFO adding 'ansible_collections/community/general/plugins/modules/packet_project.py' 2023-04-28 05:57:50,125 wheel INFO adding 'ansible_collections/community/general/plugins/modules/packet_sshkey.py' 2023-04-28 05:57:50,125 wheel INFO adding 'ansible_collections/community/general/plugins/modules/packet_volume.py' 2023-04-28 05:57:50,125 wheel INFO adding 'ansible_collections/community/general/plugins/modules/packet_volume_attachment.py' 2023-04-28 05:57:50,126 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pacman.py' 2023-04-28 05:57:50,126 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pacman_key.py' 2023-04-28 05:57:50,126 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pagerduty.py' 2023-04-28 05:57:50,126 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pagerduty_alert.py' 2023-04-28 05:57:50,127 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pagerduty_change.py' 2023-04-28 05:57:50,127 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pagerduty_user.py' 2023-04-28 05:57:50,127 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pam_limits.py' 2023-04-28 05:57:50,128 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pamd.py' 2023-04-28 05:57:50,128 wheel INFO adding 'ansible_collections/community/general/plugins/modules/parted.py' 2023-04-28 05:57:50,128 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pear.py' 2023-04-28 05:57:50,129 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pids.py' 2023-04-28 05:57:50,129 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pingdom.py' 2023-04-28 05:57:50,129 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pip_package_info.py' 2023-04-28 05:57:50,130 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pipx.py' 2023-04-28 05:57:50,130 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pipx_info.py' 2023-04-28 05:57:50,130 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pkg5.py' 2023-04-28 05:57:50,130 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pkg5_publisher.py' 2023-04-28 05:57:50,131 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pkgin.py' 2023-04-28 05:57:50,131 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pkgng.py' 2023-04-28 05:57:50,131 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pkgutil.py' 2023-04-28 05:57:50,132 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pmem.py' 2023-04-28 05:57:50,132 wheel INFO adding 'ansible_collections/community/general/plugins/modules/portage.py' 2023-04-28 05:57:50,132 wheel INFO adding 'ansible_collections/community/general/plugins/modules/portinstall.py' 2023-04-28 05:57:50,133 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pritunl_org.py' 2023-04-28 05:57:50,133 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pritunl_org_info.py' 2023-04-28 05:57:50,133 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pritunl_user.py' 2023-04-28 05:57:50,133 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pritunl_user_info.py' 2023-04-28 05:57:50,134 wheel INFO adding 'ansible_collections/community/general/plugins/modules/profitbricks.py' 2023-04-28 05:57:50,134 wheel INFO adding 'ansible_collections/community/general/plugins/modules/profitbricks_datacenter.py' 2023-04-28 05:57:50,134 wheel INFO adding 'ansible_collections/community/general/plugins/modules/profitbricks_nic.py' 2023-04-28 05:57:50,134 wheel INFO adding 'ansible_collections/community/general/plugins/modules/profitbricks_volume.py' 2023-04-28 05:57:50,135 wheel INFO adding 'ansible_collections/community/general/plugins/modules/profitbricks_volume_attachments.py' 2023-04-28 05:57:50,135 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox.py' 2023-04-28 05:57:50,136 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_disk.py' 2023-04-28 05:57:50,136 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_domain_info.py' 2023-04-28 05:57:50,136 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_group_info.py' 2023-04-28 05:57:50,137 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_kvm.py' 2023-04-28 05:57:50,137 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_nic.py' 2023-04-28 05:57:50,137 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_snap.py' 2023-04-28 05:57:50,138 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_storage_info.py' 2023-04-28 05:57:50,138 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_tasks_info.py' 2023-04-28 05:57:50,138 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_template.py' 2023-04-28 05:57:50,138 wheel INFO adding 'ansible_collections/community/general/plugins/modules/proxmox_user_info.py' 2023-04-28 05:57:50,139 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pubnub_blocks.py' 2023-04-28 05:57:50,139 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pulp_repo.py' 2023-04-28 05:57:50,139 wheel INFO adding 'ansible_collections/community/general/plugins/modules/puppet.py' 2023-04-28 05:57:50,140 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pushbullet.py' 2023-04-28 05:57:50,140 wheel INFO adding 'ansible_collections/community/general/plugins/modules/pushover.py' 2023-04-28 05:57:50,140 wheel INFO adding 'ansible_collections/community/general/plugins/modules/python_requirements_info.py' 2023-04-28 05:57:50,141 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax.py' 2023-04-28 05:57:50,141 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_cbs.py' 2023-04-28 05:57:50,141 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_cbs_attachments.py' 2023-04-28 05:57:50,141 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_cdb.py' 2023-04-28 05:57:50,142 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_cdb_database.py' 2023-04-28 05:57:50,142 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_cdb_user.py' 2023-04-28 05:57:50,142 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_clb.py' 2023-04-28 05:57:50,142 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_clb_nodes.py' 2023-04-28 05:57:50,143 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_clb_ssl.py' 2023-04-28 05:57:50,143 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_dns.py' 2023-04-28 05:57:50,143 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_dns_record.py' 2023-04-28 05:57:50,144 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_facts.py' 2023-04-28 05:57:50,144 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_files.py' 2023-04-28 05:57:50,144 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_files_objects.py' 2023-04-28 05:57:50,144 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_identity.py' 2023-04-28 05:57:50,145 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_keypair.py' 2023-04-28 05:57:50,145 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_meta.py' 2023-04-28 05:57:50,145 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_mon_alarm.py' 2023-04-28 05:57:50,145 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_mon_check.py' 2023-04-28 05:57:50,146 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_mon_entity.py' 2023-04-28 05:57:50,146 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_mon_notification.py' 2023-04-28 05:57:50,146 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_mon_notification_plan.py' 2023-04-28 05:57:50,146 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_network.py' 2023-04-28 05:57:50,147 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_queue.py' 2023-04-28 05:57:50,147 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_scaling_group.py' 2023-04-28 05:57:50,147 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rax_scaling_policy.py' 2023-04-28 05:57:50,147 wheel INFO adding 'ansible_collections/community/general/plugins/modules/read_csv.py' 2023-04-28 05:57:50,148 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redfish_command.py' 2023-04-28 05:57:50,148 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redfish_config.py' 2023-04-28 05:57:50,148 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redfish_info.py' 2023-04-28 05:57:50,149 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redhat_subscription.py' 2023-04-28 05:57:50,149 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redis.py' 2023-04-28 05:57:50,150 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redis_data.py' 2023-04-28 05:57:50,150 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redis_data_incr.py' 2023-04-28 05:57:50,150 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redis_data_info.py' 2023-04-28 05:57:50,150 wheel INFO adding 'ansible_collections/community/general/plugins/modules/redis_info.py' 2023-04-28 05:57:50,151 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rhevm.py' 2023-04-28 05:57:50,151 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rhn_channel.py' 2023-04-28 05:57:50,151 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rhn_register.py' 2023-04-28 05:57:50,152 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rhsm_release.py' 2023-04-28 05:57:50,152 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rhsm_repository.py' 2023-04-28 05:57:50,152 wheel INFO adding 'ansible_collections/community/general/plugins/modules/riak.py' 2023-04-28 05:57:50,152 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rocketchat.py' 2023-04-28 05:57:50,153 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rollbar_deployment.py' 2023-04-28 05:57:50,153 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rpm_ostree_pkg.py' 2023-04-28 05:57:50,153 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rundeck_acl_policy.py' 2023-04-28 05:57:50,153 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rundeck_job_executions_info.py' 2023-04-28 05:57:50,154 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rundeck_job_run.py' 2023-04-28 05:57:50,154 wheel INFO adding 'ansible_collections/community/general/plugins/modules/rundeck_project.py' 2023-04-28 05:57:50,154 wheel INFO adding 'ansible_collections/community/general/plugins/modules/runit.py' 2023-04-28 05:57:50,154 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sap_task_list_execute.py' 2023-04-28 05:57:50,155 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sapcar_extract.py' 2023-04-28 05:57:50,155 wheel INFO adding 'ansible_collections/community/general/plugins/modules/say.py' 2023-04-28 05:57:50,155 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_compute.py' 2023-04-28 05:57:50,156 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_compute_private_network.py' 2023-04-28 05:57:50,156 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_container.py' 2023-04-28 05:57:50,156 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_container_info.py' 2023-04-28 05:57:50,156 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_container_namespace.py' 2023-04-28 05:57:50,157 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_container_namespace_info.py' 2023-04-28 05:57:50,157 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_container_registry.py' 2023-04-28 05:57:50,157 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_container_registry_info.py' 2023-04-28 05:57:50,157 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_database_backup.py' 2023-04-28 05:57:50,158 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_function.py' 2023-04-28 05:57:50,158 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_function_info.py' 2023-04-28 05:57:50,158 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_function_namespace.py' 2023-04-28 05:57:50,158 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_function_namespace_info.py' 2023-04-28 05:57:50,159 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_image_info.py' 2023-04-28 05:57:50,159 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_ip.py' 2023-04-28 05:57:50,159 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_ip_info.py' 2023-04-28 05:57:50,159 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_lb.py' 2023-04-28 05:57:50,160 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_organization_info.py' 2023-04-28 05:57:50,160 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_private_network.py' 2023-04-28 05:57:50,160 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_security_group.py' 2023-04-28 05:57:50,160 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_security_group_info.py' 2023-04-28 05:57:50,161 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_security_group_rule.py' 2023-04-28 05:57:50,161 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_server_info.py' 2023-04-28 05:57:50,161 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_snapshot_info.py' 2023-04-28 05:57:50,161 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_sshkey.py' 2023-04-28 05:57:50,162 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_user_data.py' 2023-04-28 05:57:50,162 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_volume.py' 2023-04-28 05:57:50,162 wheel INFO adding 'ansible_collections/community/general/plugins/modules/scaleway_volume_info.py' 2023-04-28 05:57:50,162 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sefcontext.py' 2023-04-28 05:57:50,163 wheel INFO adding 'ansible_collections/community/general/plugins/modules/selinux_permissive.py' 2023-04-28 05:57:50,163 wheel INFO adding 'ansible_collections/community/general/plugins/modules/selogin.py' 2023-04-28 05:57:50,163 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sendgrid.py' 2023-04-28 05:57:50,163 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sensu_check.py' 2023-04-28 05:57:50,164 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sensu_client.py' 2023-04-28 05:57:50,164 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sensu_handler.py' 2023-04-28 05:57:50,164 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sensu_silence.py' 2023-04-28 05:57:50,164 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sensu_subscription.py' 2023-04-28 05:57:50,165 wheel INFO adding 'ansible_collections/community/general/plugins/modules/seport.py' 2023-04-28 05:57:50,165 wheel INFO adding 'ansible_collections/community/general/plugins/modules/serverless.py' 2023-04-28 05:57:50,165 wheel INFO adding 'ansible_collections/community/general/plugins/modules/shutdown.py' 2023-04-28 05:57:50,165 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sl_vm.py' 2023-04-28 05:57:50,166 wheel INFO adding 'ansible_collections/community/general/plugins/modules/slack.py' 2023-04-28 05:57:50,166 wheel INFO adding 'ansible_collections/community/general/plugins/modules/slackpkg.py' 2023-04-28 05:57:50,166 wheel INFO adding 'ansible_collections/community/general/plugins/modules/smartos_image_info.py' 2023-04-28 05:57:50,167 wheel INFO adding 'ansible_collections/community/general/plugins/modules/snap.py' 2023-04-28 05:57:50,167 wheel INFO adding 'ansible_collections/community/general/plugins/modules/snap_alias.py' 2023-04-28 05:57:50,167 wheel INFO adding 'ansible_collections/community/general/plugins/modules/snmp_facts.py' 2023-04-28 05:57:50,167 wheel INFO adding 'ansible_collections/community/general/plugins/modules/solaris_zone.py' 2023-04-28 05:57:50,168 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sorcery.py' 2023-04-28 05:57:50,168 wheel INFO adding 'ansible_collections/community/general/plugins/modules/spectrum_device.py' 2023-04-28 05:57:50,168 wheel INFO adding 'ansible_collections/community/general/plugins/modules/spectrum_model_attrs.py' 2023-04-28 05:57:50,169 wheel INFO adding 'ansible_collections/community/general/plugins/modules/spotinst_aws_elastigroup.py' 2023-04-28 05:57:50,169 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ss_3par_cpg.py' 2023-04-28 05:57:50,170 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ssh_config.py' 2023-04-28 05:57:50,170 wheel INFO adding 'ansible_collections/community/general/plugins/modules/stackdriver.py' 2023-04-28 05:57:50,170 wheel INFO adding 'ansible_collections/community/general/plugins/modules/stacki_host.py' 2023-04-28 05:57:50,170 wheel INFO adding 'ansible_collections/community/general/plugins/modules/statsd.py' 2023-04-28 05:57:50,171 wheel INFO adding 'ansible_collections/community/general/plugins/modules/statusio_maintenance.py' 2023-04-28 05:57:50,171 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sudoers.py' 2023-04-28 05:57:50,171 wheel INFO adding 'ansible_collections/community/general/plugins/modules/supervisorctl.py' 2023-04-28 05:57:50,171 wheel INFO adding 'ansible_collections/community/general/plugins/modules/svc.py' 2023-04-28 05:57:50,172 wheel INFO adding 'ansible_collections/community/general/plugins/modules/svr4pkg.py' 2023-04-28 05:57:50,172 wheel INFO adding 'ansible_collections/community/general/plugins/modules/swdepot.py' 2023-04-28 05:57:50,172 wheel INFO adding 'ansible_collections/community/general/plugins/modules/swupd.py' 2023-04-28 05:57:50,172 wheel INFO adding 'ansible_collections/community/general/plugins/modules/syslogger.py' 2023-04-28 05:57:50,173 wheel INFO adding 'ansible_collections/community/general/plugins/modules/syspatch.py' 2023-04-28 05:57:50,173 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sysrc.py' 2023-04-28 05:57:50,173 wheel INFO adding 'ansible_collections/community/general/plugins/modules/sysupgrade.py' 2023-04-28 05:57:50,173 wheel INFO adding 'ansible_collections/community/general/plugins/modules/taiga_issue.py' 2023-04-28 05:57:50,174 wheel INFO adding 'ansible_collections/community/general/plugins/modules/telegram.py' 2023-04-28 05:57:50,174 wheel INFO adding 'ansible_collections/community/general/plugins/modules/terraform.py' 2023-04-28 05:57:50,174 wheel INFO adding 'ansible_collections/community/general/plugins/modules/timezone.py' 2023-04-28 05:57:50,175 wheel INFO adding 'ansible_collections/community/general/plugins/modules/twilio.py' 2023-04-28 05:57:50,175 wheel INFO adding 'ansible_collections/community/general/plugins/modules/typetalk.py' 2023-04-28 05:57:50,175 wheel INFO adding 'ansible_collections/community/general/plugins/modules/udm_dns_record.py' 2023-04-28 05:57:50,176 wheel INFO adding 'ansible_collections/community/general/plugins/modules/udm_dns_zone.py' 2023-04-28 05:57:50,176 wheel INFO adding 'ansible_collections/community/general/plugins/modules/udm_group.py' 2023-04-28 05:57:50,176 wheel INFO adding 'ansible_collections/community/general/plugins/modules/udm_share.py' 2023-04-28 05:57:50,176 wheel INFO adding 'ansible_collections/community/general/plugins/modules/udm_user.py' 2023-04-28 05:57:50,177 wheel INFO adding 'ansible_collections/community/general/plugins/modules/ufw.py' 2023-04-28 05:57:50,177 wheel INFO adding 'ansible_collections/community/general/plugins/modules/uptimerobot.py' 2023-04-28 05:57:50,177 wheel INFO adding 'ansible_collections/community/general/plugins/modules/urpmi.py' 2023-04-28 05:57:50,178 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_aaa_group.py' 2023-04-28 05:57:50,178 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_aaa_group_info.py' 2023-04-28 05:57:50,178 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_ca_host_key_cert.py' 2023-04-28 05:57:50,178 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_ca_host_key_cert_info.py' 2023-04-28 05:57:50,179 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_dns_host.py' 2023-04-28 05:57:50,179 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_network_interface_address.py' 2023-04-28 05:57:50,179 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_network_interface_address_info.py' 2023-04-28 05:57:50,179 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_proxy_auth_profile.py' 2023-04-28 05:57:50,180 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_proxy_exception.py' 2023-04-28 05:57:50,180 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_proxy_frontend.py' 2023-04-28 05:57:50,180 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_proxy_frontend_info.py' 2023-04-28 05:57:50,180 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_proxy_location.py' 2023-04-28 05:57:50,181 wheel INFO adding 'ansible_collections/community/general/plugins/modules/utm_proxy_location_info.py' 2023-04-28 05:57:50,181 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vdo.py' 2023-04-28 05:57:50,181 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vertica_configuration.py' 2023-04-28 05:57:50,182 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vertica_info.py' 2023-04-28 05:57:50,182 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vertica_role.py' 2023-04-28 05:57:50,182 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vertica_schema.py' 2023-04-28 05:57:50,182 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vertica_user.py' 2023-04-28 05:57:50,183 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vexata_eg.py' 2023-04-28 05:57:50,183 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vexata_volume.py' 2023-04-28 05:57:50,183 wheel INFO adding 'ansible_collections/community/general/plugins/modules/vmadm.py' 2023-04-28 05:57:50,184 wheel INFO adding 'ansible_collections/community/general/plugins/modules/wakeonlan.py' 2023-04-28 05:57:50,184 wheel INFO adding 'ansible_collections/community/general/plugins/modules/wdc_redfish_command.py' 2023-04-28 05:57:50,184 wheel INFO adding 'ansible_collections/community/general/plugins/modules/wdc_redfish_info.py' 2023-04-28 05:57:50,184 wheel INFO adding 'ansible_collections/community/general/plugins/modules/webfaction_app.py' 2023-04-28 05:57:50,185 wheel INFO adding 'ansible_collections/community/general/plugins/modules/webfaction_db.py' 2023-04-28 05:57:50,185 wheel INFO adding 'ansible_collections/community/general/plugins/modules/webfaction_domain.py' 2023-04-28 05:57:50,185 wheel INFO adding 'ansible_collections/community/general/plugins/modules/webfaction_mailbox.py' 2023-04-28 05:57:50,185 wheel INFO adding 'ansible_collections/community/general/plugins/modules/webfaction_site.py' 2023-04-28 05:57:50,186 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xattr.py' 2023-04-28 05:57:50,186 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xbps.py' 2023-04-28 05:57:50,186 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xcc_redfish_command.py' 2023-04-28 05:57:50,187 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xenserver_facts.py' 2023-04-28 05:57:50,187 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xenserver_guest.py' 2023-04-28 05:57:50,188 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xenserver_guest_info.py' 2023-04-28 05:57:50,188 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xenserver_guest_powerstate.py' 2023-04-28 05:57:50,188 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xfconf.py' 2023-04-28 05:57:50,188 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xfconf_info.py' 2023-04-28 05:57:50,189 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xfs_quota.py' 2023-04-28 05:57:50,189 wheel INFO adding 'ansible_collections/community/general/plugins/modules/xml.py' 2023-04-28 05:57:50,189 wheel INFO adding 'ansible_collections/community/general/plugins/modules/yarn.py' 2023-04-28 05:57:50,190 wheel INFO adding 'ansible_collections/community/general/plugins/modules/yum_versionlock.py' 2023-04-28 05:57:50,190 wheel INFO adding 'ansible_collections/community/general/plugins/modules/zfs.py' 2023-04-28 05:57:50,190 wheel INFO adding 'ansible_collections/community/general/plugins/modules/zfs_delegate_admin.py' 2023-04-28 05:57:50,191 wheel INFO adding 'ansible_collections/community/general/plugins/modules/zfs_facts.py' 2023-04-28 05:57:50,191 wheel INFO adding 'ansible_collections/community/general/plugins/modules/znode.py' 2023-04-28 05:57:50,191 wheel INFO adding 'ansible_collections/community/general/plugins/modules/zpool_facts.py' 2023-04-28 05:57:50,191 wheel INFO adding 'ansible_collections/community/general/plugins/modules/zypper.py' 2023-04-28 05:57:50,192 wheel INFO adding 'ansible_collections/community/general/plugins/modules/zypper_repository.py' 2023-04-28 05:57:50,192 wheel INFO adding 'ansible_collections/community/general/plugins/test/a_module.py' 2023-04-28 05:57:50,192 wheel INFO adding 'ansible_collections/community/google/CHANGELOG.rst' 2023-04-28 05:57:50,193 wheel INFO adding 'ansible_collections/community/google/FILES.json' 2023-04-28 05:57:50,193 wheel INFO adding 'ansible_collections/community/google/LICENSE' 2023-04-28 05:57:50,193 wheel INFO adding 'ansible_collections/community/google/MANIFEST.json' 2023-04-28 05:57:50,193 wheel INFO adding 'ansible_collections/community/google/README.md' 2023-04-28 05:57:50,194 wheel INFO adding 'ansible_collections/community/google/changelogs/changelog.yaml' 2023-04-28 05:57:50,194 wheel INFO adding 'ansible_collections/community/google/changelogs/config.yaml' 2023-04-28 05:57:50,194 wheel INFO adding 'ansible_collections/community/google/changelogs/fragments/.keep' 2023-04-28 05:57:50,194 wheel INFO adding 'ansible_collections/community/google/meta/runtime.yml' 2023-04-28 05:57:50,195 wheel INFO adding 'ansible_collections/community/google/plugins/doc_fragments/_gcp.py' 2023-04-28 05:57:50,195 wheel INFO adding 'ansible_collections/community/google/plugins/lookup/gcp_storage_file.py' 2023-04-28 05:57:50,195 wheel INFO adding 'ansible_collections/community/google/plugins/module_utils/gce.py' 2023-04-28 05:57:50,196 wheel INFO adding 'ansible_collections/community/google/plugins/module_utils/gcp.py' 2023-04-28 05:57:50,196 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gc_storage.py' 2023-04-28 05:57:50,196 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_eip.py' 2023-04-28 05:57:50,197 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_img.py' 2023-04-28 05:57:50,197 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_instance_template.py' 2023-04-28 05:57:50,197 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_labels.py' 2023-04-28 05:57:50,197 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_lb.py' 2023-04-28 05:57:50,198 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_mig.py' 2023-04-28 05:57:50,198 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_net.py' 2023-04-28 05:57:50,198 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_pd.py' 2023-04-28 05:57:50,199 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_snapshot.py' 2023-04-28 05:57:50,199 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gce_tag.py' 2023-04-28 05:57:50,199 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gcpubsub.py' 2023-04-28 05:57:50,200 wheel INFO adding 'ansible_collections/community/google/plugins/modules/gcpubsub_info.py' 2023-04-28 05:57:50,200 wheel INFO adding 'ansible_collections/community/google/scripts/inventory/gce.ini' 2023-04-28 05:57:50,200 wheel INFO adding 'ansible_collections/community/google/scripts/inventory/gce.py' 2023-04-28 05:57:50,201 wheel INFO adding 'ansible_collections/community/grafana/CHANGELOG.rst' 2023-04-28 05:57:50,201 wheel INFO adding 'ansible_collections/community/grafana/FILES.json' 2023-04-28 05:57:50,201 wheel INFO adding 'ansible_collections/community/grafana/LICENSE' 2023-04-28 05:57:50,202 wheel INFO adding 'ansible_collections/community/grafana/MANIFEST.json' 2023-04-28 05:57:50,202 wheel INFO adding 'ansible_collections/community/grafana/README.md' 2023-04-28 05:57:50,202 wheel INFO adding 'ansible_collections/community/grafana/codecov.yml' 2023-04-28 05:57:50,202 wheel INFO adding 'ansible_collections/community/grafana/changelogs/changelog.yaml' 2023-04-28 05:57:50,203 wheel INFO adding 'ansible_collections/community/grafana/changelogs/config.yaml' 2023-04-28 05:57:50,203 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/0-copy_ignore_txt.yml' 2023-04-28 05:57:50,203 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/0.1.0.yml' 2023-04-28 05:57:50,204 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/0.2.0.yml' 2023-04-28 05:57:50,204 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/0.2.1.yml' 2023-04-28 05:57:50,204 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/0.2.2.yml' 2023-04-28 05:57:50,204 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/00_drop_eol_ansible.yml' 2023-04-28 05:57:50,204 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/01_grafana_bump.yml' 2023-04-28 05:57:50,205 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/1.0.0.yml' 2023-04-28 05:57:50,205 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/1.2.0.yml' 2023-04-28 05:57:50,205 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/1.2.1.yml' 2023-04-28 05:57:50,205 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/1.2.2.yml' 2023-04-28 05:57:50,205 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/1.2.3.yml' 2023-04-28 05:57:50,206 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/1.3.1.yml' 2023-04-28 05:57:50,206 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/1.5.3.yml' 2023-04-28 05:57:50,206 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/136_add_grafana_action_groups.yml' 2023-04-28 05:57:50,206 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/158-grafana_dashboard-lookup-api-key.yml' 2023-04-28 05:57:50,206 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/170_remove_requirement_ds_type_ds_url.yml' 2023-04-28 05:57:50,207 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/172_support_azure_datasource.yml' 2023-04-28 05:57:50,207 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/186_check_fragments.yml' 2023-04-28 05:57:50,207 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/191.yml' 2023-04-28 05:57:50,207 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/230-uid-datasource.yml' 2023-04-28 05:57:50,207 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/239_keyerror_grafana_url.yml' 2023-04-28 05:57:50,208 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/248_ds_update_error_grafana_9.yml' 2023-04-28 05:57:50,208 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/257_pretty_printed_dashboard_export.yml' 2023-04-28 05:57:50,208 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/265-url-encode-user.yml' 2023-04-28 05:57:50,208 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/270-gha--ansible-test--integration.yml' 2023-04-28 05:57:50,208 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/277-gha-ansible-test-versions.yml' 2023-04-28 05:57:50,209 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/288_get_actual_org_encode.yml' 2023-04-28 05:57:50,209 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/add-units-datasource.yml' 2023-04-28 05:57:50,209 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/ci.yml' 2023-04-28 05:57:50,209 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/datasource-issue-204.yml' 2023-04-28 05:57:50,209 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/fix-263.yaml' 2023-04-28 05:57:50,210 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/fix_slashes_in_datasources.yml' 2023-04-28 05:57:50,210 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/grafana_users_note.yaml' 2023-04-28 05:57:50,210 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/notifi_channel_refacto.yml' 2023-04-28 05:57:50,210 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/threema.yml' 2023-04-28 05:57:50,210 wheel INFO adding 'ansible_collections/community/grafana/changelogs/fragments/update_deprecation.yml' 2023-04-28 05:57:50,211 wheel INFO adding 'ansible_collections/community/grafana/hacking/NEED_FRAGMENT' 2023-04-28 05:57:50,211 wheel INFO adding 'ansible_collections/community/grafana/hacking/check_fragment.sh' 2023-04-28 05:57:50,211 wheel INFO adding 'ansible_collections/community/grafana/hacking/find_grafana_versions.py' 2023-04-28 05:57:50,211 wheel INFO adding 'ansible_collections/community/grafana/hacking/requirements.txt' 2023-04-28 05:57:50,211 wheel INFO adding 'ansible_collections/community/grafana/meta/runtime.yml' 2023-04-28 05:57:50,212 wheel INFO adding 'ansible_collections/community/grafana/plugins/callback/__init__.py' 2023-04-28 05:57:50,212 wheel INFO adding 'ansible_collections/community/grafana/plugins/callback/grafana_annotations.py' 2023-04-28 05:57:50,212 wheel INFO adding 'ansible_collections/community/grafana/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,212 wheel INFO adding 'ansible_collections/community/grafana/plugins/doc_fragments/api_key.py' 2023-04-28 05:57:50,213 wheel INFO adding 'ansible_collections/community/grafana/plugins/doc_fragments/basic_auth.py' 2023-04-28 05:57:50,213 wheel INFO adding 'ansible_collections/community/grafana/plugins/lookup/__init__.py' 2023-04-28 05:57:50,213 wheel INFO adding 'ansible_collections/community/grafana/plugins/lookup/grafana_dashboard.py' 2023-04-28 05:57:50,213 wheel INFO adding 'ansible_collections/community/grafana/plugins/module_utils/base.py' 2023-04-28 05:57:50,214 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/__init__.py' 2023-04-28 05:57:50,214 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_dashboard.py' 2023-04-28 05:57:50,214 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_datasource.py' 2023-04-28 05:57:50,215 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_folder.py' 2023-04-28 05:57:50,215 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_notification_channel.py' 2023-04-28 05:57:50,215 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_organization.py' 2023-04-28 05:57:50,216 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_plugin.py' 2023-04-28 05:57:50,216 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_team.py' 2023-04-28 05:57:50,216 wheel INFO adding 'ansible_collections/community/grafana/plugins/modules/grafana_user.py' 2023-04-28 05:57:50,217 wheel INFO adding 'ansible_collections/community/hashi_vault/CHANGELOG.rst' 2023-04-28 05:57:50,217 wheel INFO adding 'ansible_collections/community/hashi_vault/FILES.json' 2023-04-28 05:57:50,218 wheel INFO adding 'ansible_collections/community/hashi_vault/LICENSE' 2023-04-28 05:57:50,218 wheel INFO adding 'ansible_collections/community/hashi_vault/MANIFEST.json' 2023-04-28 05:57:50,219 wheel INFO adding 'ansible_collections/community/hashi_vault/README.md' 2023-04-28 05:57:50,219 wheel INFO adding 'ansible_collections/community/hashi_vault/codecov.yml' 2023-04-28 05:57:50,219 wheel INFO adding 'ansible_collections/community/hashi_vault/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:50,219 wheel INFO adding 'ansible_collections/community/hashi_vault/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:50,220 wheel INFO adding 'ansible_collections/community/hashi_vault/changelogs/changelog.yaml' 2023-04-28 05:57:50,220 wheel INFO adding 'ansible_collections/community/hashi_vault/changelogs/config.yaml' 2023-04-28 05:57:50,221 wheel INFO adding 'ansible_collections/community/hashi_vault/changelogs/fragments/.keep' 2023-04-28 05:57:50,221 wheel INFO adding 'ansible_collections/community/hashi_vault/meta/ee-requirements.txt' 2023-04-28 05:57:50,221 wheel INFO adding 'ansible_collections/community/hashi_vault/meta/execution-environment.yml' 2023-04-28 05:57:50,221 wheel INFO adding 'ansible_collections/community/hashi_vault/meta/runtime.yml' 2023-04-28 05:57:50,221 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:50,222 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/doc_fragments/auth.py' 2023-04-28 05:57:50,222 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/doc_fragments/connection.py' 2023-04-28 05:57:50,222 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/doc_fragments/engine_mount.py' 2023-04-28 05:57:50,222 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/doc_fragments/token_create.py' 2023-04-28 05:57:50,223 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/doc_fragments/wrapping.py' 2023-04-28 05:57:50,223 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/filter/vault_login_token.py' 2023-04-28 05:57:50,223 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/filter/vault_login_token.yml' 2023-04-28 05:57:50,223 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/hashi_vault.py' 2023-04-28 05:57:50,224 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_ansible_settings.py' 2023-04-28 05:57:50,224 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_kv1_get.py' 2023-04-28 05:57:50,224 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_kv2_get.py' 2023-04-28 05:57:50,225 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_list.py' 2023-04-28 05:57:50,225 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_login.py' 2023-04-28 05:57:50,225 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_read.py' 2023-04-28 05:57:50,225 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_token_create.py' 2023-04-28 05:57:50,226 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/lookup/vault_write.py' 2023-04-28 05:57:50,226 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_approle.py' 2023-04-28 05:57:50,226 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_aws_iam.py' 2023-04-28 05:57:50,226 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_azure.py' 2023-04-28 05:57:50,226 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_cert.py' 2023-04-28 05:57:50,227 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_jwt.py' 2023-04-28 05:57:50,227 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_ldap.py' 2023-04-28 05:57:50,227 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_none.py' 2023-04-28 05:57:50,227 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_token.py' 2023-04-28 05:57:50,228 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_auth_method_userpass.py' 2023-04-28 05:57:50,228 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_authenticator.py' 2023-04-28 05:57:50,228 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_connection_options.py' 2023-04-28 05:57:50,228 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_hashi_vault_common.py' 2023-04-28 05:57:50,229 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/module_utils/_hashi_vault_module.py' 2023-04-28 05:57:50,229 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_kv1_get.py' 2023-04-28 05:57:50,229 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_delete.py' 2023-04-28 05:57:50,229 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_get.py' 2023-04-28 05:57:50,230 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_kv2_write.py' 2023-04-28 05:57:50,230 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_list.py' 2023-04-28 05:57:50,230 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_login.py' 2023-04-28 05:57:50,230 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_pki_generate_certificate.py' 2023-04-28 05:57:50,231 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_read.py' 2023-04-28 05:57:50,231 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_token_create.py' 2023-04-28 05:57:50,231 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/modules/vault_write.py' 2023-04-28 05:57:50,231 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/plugin_utils/_hashi_vault_lookup_base.py' 2023-04-28 05:57:50,232 wheel INFO adding 'ansible_collections/community/hashi_vault/plugins/plugin_utils/_hashi_vault_plugin.py' 2023-04-28 05:57:50,232 wheel INFO adding 'ansible_collections/community/hrobot/CHANGELOG.rst' 2023-04-28 05:57:50,232 wheel INFO adding 'ansible_collections/community/hrobot/CHANGELOG.rst.license' 2023-04-28 05:57:50,233 wheel INFO adding 'ansible_collections/community/hrobot/COPYING' 2023-04-28 05:57:50,233 wheel INFO adding 'ansible_collections/community/hrobot/FILES.json' 2023-04-28 05:57:50,233 wheel INFO adding 'ansible_collections/community/hrobot/MANIFEST.json' 2023-04-28 05:57:50,233 wheel INFO adding 'ansible_collections/community/hrobot/README.md' 2023-04-28 05:57:50,234 wheel INFO adding 'ansible_collections/community/hrobot/codecov.yml' 2023-04-28 05:57:50,234 wheel INFO adding 'ansible_collections/community/hrobot/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:50,234 wheel INFO adding 'ansible_collections/community/hrobot/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:50,235 wheel INFO adding 'ansible_collections/community/hrobot/changelogs/changelog.yaml' 2023-04-28 05:57:50,235 wheel INFO adding 'ansible_collections/community/hrobot/changelogs/changelog.yaml.license' 2023-04-28 05:57:50,235 wheel INFO adding 'ansible_collections/community/hrobot/changelogs/config.yaml' 2023-04-28 05:57:50,235 wheel INFO adding 'ansible_collections/community/hrobot/changelogs/fragments/.keep' 2023-04-28 05:57:50,236 wheel INFO adding 'ansible_collections/community/hrobot/meta/execution-environment.yml' 2023-04-28 05:57:50,236 wheel INFO adding 'ansible_collections/community/hrobot/meta/runtime.yml' 2023-04-28 05:57:50,236 wheel INFO adding 'ansible_collections/community/hrobot/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:50,236 wheel INFO adding 'ansible_collections/community/hrobot/plugins/doc_fragments/robot.py' 2023-04-28 05:57:50,237 wheel INFO adding 'ansible_collections/community/hrobot/plugins/inventory/robot.py' 2023-04-28 05:57:50,237 wheel INFO adding 'ansible_collections/community/hrobot/plugins/module_utils/failover.py' 2023-04-28 05:57:50,237 wheel INFO adding 'ansible_collections/community/hrobot/plugins/module_utils/robot.py' 2023-04-28 05:57:50,237 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/boot.py' 2023-04-28 05:57:50,238 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/failover_ip.py' 2023-04-28 05:57:50,238 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/failover_ip_info.py' 2023-04-28 05:57:50,238 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/firewall.py' 2023-04-28 05:57:50,239 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/firewall_info.py' 2023-04-28 05:57:50,239 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/reset.py' 2023-04-28 05:57:50,239 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/reverse_dns.py' 2023-04-28 05:57:50,239 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/server.py' 2023-04-28 05:57:50,240 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/server_info.py' 2023-04-28 05:57:50,240 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/ssh_key.py' 2023-04-28 05:57:50,240 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/ssh_key_info.py' 2023-04-28 05:57:50,240 wheel INFO adding 'ansible_collections/community/hrobot/plugins/modules/v_switch.py' 2023-04-28 05:57:50,241 wheel INFO adding 'ansible_collections/community/libvirt/CHANGELOG.rst' 2023-04-28 05:57:50,241 wheel INFO adding 'ansible_collections/community/libvirt/CONTRIBUTING.md' 2023-04-28 05:57:50,241 wheel INFO adding 'ansible_collections/community/libvirt/COPYING' 2023-04-28 05:57:50,242 wheel INFO adding 'ansible_collections/community/libvirt/FILES.json' 2023-04-28 05:57:50,242 wheel INFO adding 'ansible_collections/community/libvirt/MAINTAINERS' 2023-04-28 05:57:50,242 wheel INFO adding 'ansible_collections/community/libvirt/MAINTAINING.md' 2023-04-28 05:57:50,242 wheel INFO adding 'ansible_collections/community/libvirt/MANIFEST.json' 2023-04-28 05:57:50,243 wheel INFO adding 'ansible_collections/community/libvirt/README.md' 2023-04-28 05:57:50,243 wheel INFO adding 'ansible_collections/community/libvirt/REVIEW_CHECKLIST.md' 2023-04-28 05:57:50,243 wheel INFO adding 'ansible_collections/community/libvirt/shippable.yml' 2023-04-28 05:57:50,243 wheel INFO adding 'ansible_collections/community/libvirt/changelogs/changelog.yaml' 2023-04-28 05:57:50,244 wheel INFO adding 'ansible_collections/community/libvirt/changelogs/config.yaml' 2023-04-28 05:57:50,244 wheel INFO adding 'ansible_collections/community/libvirt/meta/runtime.yml' 2023-04-28 05:57:50,244 wheel INFO adding 'ansible_collections/community/libvirt/plugins/connection/libvirt_lxc.py' 2023-04-28 05:57:50,244 wheel INFO adding 'ansible_collections/community/libvirt/plugins/connection/libvirt_qemu.py' 2023-04-28 05:57:50,245 wheel INFO adding 'ansible_collections/community/libvirt/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,245 wheel INFO adding 'ansible_collections/community/libvirt/plugins/doc_fragments/requirements.py' 2023-04-28 05:57:50,245 wheel INFO adding 'ansible_collections/community/libvirt/plugins/doc_fragments/virt.py' 2023-04-28 05:57:50,245 wheel INFO adding 'ansible_collections/community/libvirt/plugins/inventory/__init__.py' 2023-04-28 05:57:50,246 wheel INFO adding 'ansible_collections/community/libvirt/plugins/inventory/libvirt.py' 2023-04-28 05:57:50,246 wheel INFO adding 'ansible_collections/community/libvirt/plugins/modules/virt.py' 2023-04-28 05:57:50,246 wheel INFO adding 'ansible_collections/community/libvirt/plugins/modules/virt_net.py' 2023-04-28 05:57:50,247 wheel INFO adding 'ansible_collections/community/libvirt/plugins/modules/virt_pool.py' 2023-04-28 05:57:50,247 wheel INFO adding 'ansible_collections/community/mongodb/CHANGELOG.rst' 2023-04-28 05:57:50,247 wheel INFO adding 'ansible_collections/community/mongodb/COPYING' 2023-04-28 05:57:50,248 wheel INFO adding 'ansible_collections/community/mongodb/FILES.json' 2023-04-28 05:57:50,248 wheel INFO adding 'ansible_collections/community/mongodb/MANIFEST.json' 2023-04-28 05:57:50,248 wheel INFO adding 'ansible_collections/community/mongodb/README.md' 2023-04-28 05:57:50,249 wheel INFO adding 'ansible_collections/community/mongodb/requirements-3.6.txt' 2023-04-28 05:57:50,249 wheel INFO adding 'ansible_collections/community/mongodb/requirements-3.8.txt' 2023-04-28 05:57:50,249 wheel INFO adding 'ansible_collections/community/mongodb/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:50,249 wheel INFO adding 'ansible_collections/community/mongodb/changelogs/changelog.yaml' 2023-04-28 05:57:50,250 wheel INFO adding 'ansible_collections/community/mongodb/changelogs/config.yaml' 2023-04-28 05:57:50,250 wheel INFO adding 'ansible_collections/community/mongodb/meta/runtime.yml' 2023-04-28 05:57:50,250 wheel INFO adding 'ansible_collections/community/mongodb/plugins/cache/__init__.py' 2023-04-28 05:57:50,250 wheel INFO adding 'ansible_collections/community/mongodb/plugins/cache/mongodb.py' 2023-04-28 05:57:50,251 wheel INFO adding 'ansible_collections/community/mongodb/plugins/doc_fragments/login_options.py' 2023-04-28 05:57:50,251 wheel INFO adding 'ansible_collections/community/mongodb/plugins/doc_fragments/ssl_options.py' 2023-04-28 05:57:50,251 wheel INFO adding 'ansible_collections/community/mongodb/plugins/lookup/__init__.py' 2023-04-28 05:57:50,251 wheel INFO adding 'ansible_collections/community/mongodb/plugins/lookup/mongodb.py' 2023-04-28 05:57:50,252 wheel INFO adding 'ansible_collections/community/mongodb/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,252 wheel INFO adding 'ansible_collections/community/mongodb/plugins/module_utils/mongodb_common.py' 2023-04-28 05:57:50,252 wheel INFO adding 'ansible_collections/community/mongodb/plugins/module_utils/mongodb_shell.py' 2023-04-28 05:57:50,253 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/__init__.py' 2023-04-28 05:57:50,253 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_balancer.py' 2023-04-28 05:57:50,253 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_index.py' 2023-04-28 05:57:50,253 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_info.py' 2023-04-28 05:57:50,254 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_maintenance.py' 2023-04-28 05:57:50,254 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_monitoring.py' 2023-04-28 05:57:50,255 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_oplog.py' 2023-04-28 05:57:50,255 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_parameter.py' 2023-04-28 05:57:50,255 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_replicaset.py' 2023-04-28 05:57:50,255 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_role.py' 2023-04-28 05:57:50,256 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_schema.py' 2023-04-28 05:57:50,256 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_shard.py' 2023-04-28 05:57:50,256 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_shard_tag.py' 2023-04-28 05:57:50,256 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_shard_zone.py' 2023-04-28 05:57:50,257 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_shell.py' 2023-04-28 05:57:50,257 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_shutdown.py' 2023-04-28 05:57:50,257 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_status.py' 2023-04-28 05:57:50,258 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_stepdown.py' 2023-04-28 05:57:50,258 wheel INFO adding 'ansible_collections/community/mongodb/plugins/modules/mongodb_user.py' 2023-04-28 05:57:50,258 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/.yamllint' 2023-04-28 05:57:50,258 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/README.md' 2023-04-28 05:57:50,259 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/defaults/main.yml' 2023-04-28 05:57:50,259 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/meta/main.yml' 2023-04-28 05:57:50,259 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,259 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/molecule.yml' 2023-04-28 05:57:50,260 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/playbook.yml' 2023-04-28 05:57:50,260 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/prepare.yml' 2023-04-28 05:57:50,260 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,260 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,261 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,261 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/prepare.yml' 2023-04-28 05:57:50,261 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,261 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/tasks/main.yml' 2023-04-28 05:57:50,262 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/tasks/mongodb_auth_user.yml' 2023-04-28 05:57:50,262 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/vars/Amazon.yml' 2023-04-28 05:57:50,262 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/vars/RedHat-7.yml' 2023-04-28 05:57:50,262 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/vars/RedHat-8.yml' 2023-04-28 05:57:50,262 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/vars/default.yml' 2023-04-28 05:57:50,263 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_auth/vars/main.yml' 2023-04-28 05:57:50,263 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/.yamllint' 2023-04-28 05:57:50,263 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/README.md' 2023-04-28 05:57:50,263 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/defaults/main.yml' 2023-04-28 05:57:50,264 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/handlers/main.yml' 2023-04-28 05:57:50,264 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/meta/main.yml' 2023-04-28 05:57:50,264 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/Dockerfile.j2' 2023-04-28 05:57:50,264 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/molecule.yml' 2023-04-28 05:57:50,265 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/playbook.yml' 2023-04-28 05:57:50,265 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/prepare.yml' 2023-04-28 05:57:50,265 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests/test_default.py' 2023-04-28 05:57:50,265 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,266 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/molecule.yml' 2023-04-28 05:57:50,266 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/playbook.yml' 2023-04-28 05:57:50,266 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/prepare.yml' 2023-04-28 05:57:50,266 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,267 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,267 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,267 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/prepare.yml' 2023-04-28 05:57:50,267 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,267 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/tasks/main.yml' 2023-04-28 05:57:50,268 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/templates/configsrv.conf.j2' 2023-04-28 05:57:50,268 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/vars/Debian.yml' 2023-04-28 05:57:50,268 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/vars/RedHat.yml' 2023-04-28 05:57:50,268 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/vars/default.yml' 2023-04-28 05:57:50,269 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_config/vars/main.yml' 2023-04-28 05:57:50,269 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/.yamllint' 2023-04-28 05:57:50,269 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/README.md' 2023-04-28 05:57:50,269 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/files/lock_mongodb_packages.sh' 2023-04-28 05:57:50,270 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/meta/main.yml' 2023-04-28 05:57:50,270 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,270 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/molecule.yml' 2023-04-28 05:57:50,270 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/playbook.yml' 2023-04-28 05:57:50,271 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,271 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/Dockerfile.j2' 2023-04-28 05:57:50,271 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/molecule.yml' 2023-04-28 05:57:50,271 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/playbook.yml' 2023-04-28 05:57:50,271 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/prepare.yml' 2023-04-28 05:57:50,272 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests/test_default.py' 2023-04-28 05:57:50,272 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/Dockerfile.j2' 2023-04-28 05:57:50,272 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/molecule.yml' 2023-04-28 05:57:50,272 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/playbook.yml' 2023-04-28 05:57:50,273 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/prepare.yml' 2023-04-28 05:57:50,273 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests/test_default.py' 2023-04-28 05:57:50,273 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/Dockerfile.j2' 2023-04-28 05:57:50,273 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/molecule.yml' 2023-04-28 05:57:50,273 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/playbook.yml' 2023-04-28 05:57:50,274 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests/test_default.py' 2023-04-28 05:57:50,274 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,274 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,274 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/prepare.yml' 2023-04-28 05:57:50,275 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,275 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_install/tasks/main.yml' 2023-04-28 05:57:50,275 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/README.md' 2023-04-28 05:57:50,275 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/defaults/main.yml' 2023-04-28 05:57:50,276 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/files/thp-disable.service' 2023-04-28 05:57:50,276 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/meta/main.yml' 2023-04-28 05:57:50,276 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,276 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/molecule.yml' 2023-04-28 05:57:50,277 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/playbook.yml' 2023-04-28 05:57:50,277 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,277 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,277 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,278 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/prepare.yml' 2023-04-28 05:57:50,278 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,278 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/tasks/main.yml' 2023-04-28 05:57:50,278 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/vars/Debian.yml' 2023-04-28 05:57:50,279 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/vars/Fedora.yml' 2023-04-28 05:57:50,279 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/vars/RedHat-8.yml' 2023-04-28 05:57:50,279 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/vars/RedHat.yml' 2023-04-28 05:57:50,279 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/vars/default.yml' 2023-04-28 05:57:50,279 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_linux/vars/main.yml' 2023-04-28 05:57:50,280 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/.yamllint' 2023-04-28 05:57:50,280 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/README.md' 2023-04-28 05:57:50,280 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/defaults/main.yml' 2023-04-28 05:57:50,280 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/handlers/main.yml' 2023-04-28 05:57:50,281 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/meta/main.yml' 2023-04-28 05:57:50,281 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/Dockerfile.j2' 2023-04-28 05:57:50,281 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/molecule.yml' 2023-04-28 05:57:50,281 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/playbook.yml' 2023-04-28 05:57:50,282 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/prepare.yml' 2023-04-28 05:57:50,282 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests/test_default.py' 2023-04-28 05:57:50,282 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,282 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/molecule.yml' 2023-04-28 05:57:50,283 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/playbook.yml' 2023-04-28 05:57:50,283 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/prepare.yml' 2023-04-28 05:57:50,283 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,283 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/Dockerfile.j2' 2023-04-28 05:57:50,283 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/molecule.yml' 2023-04-28 05:57:50,284 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/playbook.yml' 2023-04-28 05:57:50,284 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/prepare.yml' 2023-04-28 05:57:50,284 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests/test_default.py' 2023-04-28 05:57:50,284 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,285 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,285 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/prepare.yml' 2023-04-28 05:57:50,285 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,285 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/tasks/main.yml' 2023-04-28 05:57:50,286 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/templates/mongod.conf.j2' 2023-04-28 05:57:50,286 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/vars/Debian.yml' 2023-04-28 05:57:50,286 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/vars/RedHat.yml' 2023-04-28 05:57:50,286 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/vars/default.yml' 2023-04-28 05:57:50,286 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongod/vars/main.yml' 2023-04-28 05:57:50,287 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/.yamllint' 2023-04-28 05:57:50,287 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/README.md' 2023-04-28 05:57:50,287 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/defaults/main.yml' 2023-04-28 05:57:50,287 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/handlers/main.yml' 2023-04-28 05:57:50,288 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/meta/main.yml' 2023-04-28 05:57:50,288 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,288 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/molecule.yml' 2023-04-28 05:57:50,288 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/playbook.yml' 2023-04-28 05:57:50,289 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/prepare.yml' 2023-04-28 05:57:50,289 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,289 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,289 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,290 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/prepare.yml' 2023-04-28 05:57:50,290 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,290 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/tasks/main.yml' 2023-04-28 05:57:50,290 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos.conf.j2' 2023-04-28 05:57:50,291 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos.service.j2' 2023-04-28 05:57:50,291 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/templates/mongos_pre.sh.j2' 2023-04-28 05:57:50,291 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/vars/Debian.yml' 2023-04-28 05:57:50,291 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/vars/RedHat.yml' 2023-04-28 05:57:50,291 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_mongos/vars/default.yml' 2023-04-28 05:57:50,292 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/.yamllint' 2023-04-28 05:57:50,292 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/README.md' 2023-04-28 05:57:50,292 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/defaults/main.yml' 2023-04-28 05:57:50,292 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/meta/main.yml' 2023-04-28 05:57:50,293 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,293 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/molecule.yml' 2023-04-28 05:57:50,293 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/playbook.yml' 2023-04-28 05:57:50,293 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,294 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,294 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,294 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,294 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/tasks/Debian.yml' 2023-04-28 05:57:50,295 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/tasks/RedHat.yml' 2023-04-28 05:57:50,295 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_repository/tasks/main.yml' 2023-04-28 05:57:50,295 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/.yamllint' 2023-04-28 05:57:50,295 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/README.md' 2023-04-28 05:57:50,295 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/files/compile_mongodb_selinux.sh' 2023-04-28 05:57:50,296 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/meta/main.yml' 2023-04-28 05:57:50,296 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/Dockerfile.j2' 2023-04-28 05:57:50,296 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/molecule.yml' 2023-04-28 05:57:50,296 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/playbook.yml' 2023-04-28 05:57:50,297 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,297 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/molecule.yml' 2023-04-28 05:57:50,297 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/playbook.yml' 2023-04-28 05:57:50,297 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests/test_default.py' 2023-04-28 05:57:50,298 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/tasks/main.yml' 2023-04-28 05:57:50,298 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Amazon.yml' 2023-04-28 05:57:50,298 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Debian.yml' 2023-04-28 05:57:50,298 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Fedora.yml' 2023-04-28 05:57:50,299 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/vars/RedHat-7.yml' 2023-04-28 05:57:50,299 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/vars/RedHat-8.yml' 2023-04-28 05:57:50,299 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/vars/Ubuntu-16.04.yml' 2023-04-28 05:57:50,299 wheel INFO adding 'ansible_collections/community/mongodb/roles/mongodb_selinux/vars/default.yml' 2023-04-28 05:57:50,299 wheel INFO adding 'ansible_collections/community/mysql/CHANGELOG.rst' 2023-04-28 05:57:50,300 wheel INFO adding 'ansible_collections/community/mysql/CONTRIBUTING.md' 2023-04-28 05:57:50,300 wheel INFO adding 'ansible_collections/community/mysql/CONTRIBUTORS' 2023-04-28 05:57:50,300 wheel INFO adding 'ansible_collections/community/mysql/COPYING' 2023-04-28 05:57:50,301 wheel INFO adding 'ansible_collections/community/mysql/FILES.json' 2023-04-28 05:57:50,301 wheel INFO adding 'ansible_collections/community/mysql/MAINTAINERS' 2023-04-28 05:57:50,301 wheel INFO adding 'ansible_collections/community/mysql/MAINTAINING.md' 2023-04-28 05:57:50,301 wheel INFO adding 'ansible_collections/community/mysql/MANIFEST.json' 2023-04-28 05:57:50,302 wheel INFO adding 'ansible_collections/community/mysql/PSF-license.txt' 2023-04-28 05:57:50,302 wheel INFO adding 'ansible_collections/community/mysql/README.md' 2023-04-28 05:57:50,302 wheel INFO adding 'ansible_collections/community/mysql/codecov.yml' 2023-04-28 05:57:50,302 wheel INFO adding 'ansible_collections/community/mysql/simplified_bsd.txt' 2023-04-28 05:57:50,303 wheel INFO adding 'ansible_collections/community/mysql/changelogs/changelog.yaml' 2023-04-28 05:57:50,303 wheel INFO adding 'ansible_collections/community/mysql/changelogs/config.yaml' 2023-04-28 05:57:50,303 wheel INFO adding 'ansible_collections/community/mysql/changelogs/fragments/.keep' 2023-04-28 05:57:50,303 wheel INFO adding 'ansible_collections/community/mysql/meta/runtime.yml' 2023-04-28 05:57:50,304 wheel INFO adding 'ansible_collections/community/mysql/plugins/README.md' 2023-04-28 05:57:50,304 wheel INFO adding 'ansible_collections/community/mysql/plugins/doc_fragments/mysql.py' 2023-04-28 05:57:50,304 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/_version.py' 2023-04-28 05:57:50,305 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/database.py' 2023-04-28 05:57:50,305 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/mysql.py' 2023-04-28 05:57:50,305 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/user.py' 2023-04-28 05:57:50,305 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/version.py' 2023-04-28 05:57:50,306 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/replication.py' 2023-04-28 05:57:50,306 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/role.py' 2023-04-28 05:57:50,306 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/user.py' 2023-04-28 05:57:50,306 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/replication.py' 2023-04-28 05:57:50,307 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/role.py' 2023-04-28 05:57:50,307 wheel INFO adding 'ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/user.py' 2023-04-28 05:57:50,307 wheel INFO adding 'ansible_collections/community/mysql/plugins/modules/mysql_db.py' 2023-04-28 05:57:50,308 wheel INFO adding 'ansible_collections/community/mysql/plugins/modules/mysql_info.py' 2023-04-28 05:57:50,308 wheel INFO adding 'ansible_collections/community/mysql/plugins/modules/mysql_query.py' 2023-04-28 05:57:50,308 wheel INFO adding 'ansible_collections/community/mysql/plugins/modules/mysql_replication.py' 2023-04-28 05:57:50,309 wheel INFO adding 'ansible_collections/community/mysql/plugins/modules/mysql_role.py' 2023-04-28 05:57:50,309 wheel INFO adding 'ansible_collections/community/mysql/plugins/modules/mysql_user.py' 2023-04-28 05:57:50,309 wheel INFO adding 'ansible_collections/community/mysql/plugins/modules/mysql_variables.py' 2023-04-28 05:57:50,310 wheel INFO adding 'ansible_collections/community/network/103-nclu-check-diff.yaml' 2023-04-28 05:57:50,310 wheel INFO adding 'ansible_collections/community/network/CHANGELOG.rst' 2023-04-28 05:57:50,310 wheel INFO adding 'ansible_collections/community/network/CONTRIBUTING.md' 2023-04-28 05:57:50,310 wheel INFO adding 'ansible_collections/community/network/COPYING' 2023-04-28 05:57:50,312 wheel INFO adding 'ansible_collections/community/network/FILES.json' 2023-04-28 05:57:50,313 wheel INFO adding 'ansible_collections/community/network/MANIFEST.json' 2023-04-28 05:57:50,313 wheel INFO adding 'ansible_collections/community/network/PSF-license.txt' 2023-04-28 05:57:50,314 wheel INFO adding 'ansible_collections/community/network/README.md' 2023-04-28 05:57:50,314 wheel INFO adding 'ansible_collections/community/network/shippable.yml' 2023-04-28 05:57:50,314 wheel INFO adding 'ansible_collections/community/network/simplified_bsd.txt' 2023-04-28 05:57:50,314 wheel INFO adding 'ansible_collections/community/network/changelogs/.gitignore' 2023-04-28 05:57:50,315 wheel INFO adding 'ansible_collections/community/network/changelogs/changelog.yaml' 2023-04-28 05:57:50,315 wheel INFO adding 'ansible_collections/community/network/changelogs/config.yaml' 2023-04-28 05:57:50,315 wheel INFO adding 'ansible_collections/community/network/changelogs/fragments/.keep' 2023-04-28 05:57:50,316 wheel INFO adding 'ansible_collections/community/network/meta/runtime.yml' 2023-04-28 05:57:50,316 wheel INFO adding 'ansible_collections/community/network/plugins/action/__init__.py' 2023-04-28 05:57:50,317 wheel INFO adding 'ansible_collections/community/network/plugins/action/aireos.py' 2023-04-28 05:57:50,317 wheel INFO adding 'ansible_collections/community/network/plugins/action/aruba.py' 2023-04-28 05:57:50,317 wheel INFO adding 'ansible_collections/community/network/plugins/action/ce.py' 2023-04-28 05:57:50,317 wheel INFO adding 'ansible_collections/community/network/plugins/action/ce_template.py' 2023-04-28 05:57:50,318 wheel INFO adding 'ansible_collections/community/network/plugins/action/cnos.py' 2023-04-28 05:57:50,318 wheel INFO adding 'ansible_collections/community/network/plugins/action/edgeos_config.py' 2023-04-28 05:57:50,318 wheel INFO adding 'ansible_collections/community/network/plugins/action/enos.py' 2023-04-28 05:57:50,318 wheel INFO adding 'ansible_collections/community/network/plugins/action/exos.py' 2023-04-28 05:57:50,318 wheel INFO adding 'ansible_collections/community/network/plugins/action/ironware.py' 2023-04-28 05:57:50,319 wheel INFO adding 'ansible_collections/community/network/plugins/action/nos_config.py' 2023-04-28 05:57:50,319 wheel INFO adding 'ansible_collections/community/network/plugins/action/slxos.py' 2023-04-28 05:57:50,319 wheel INFO adding 'ansible_collections/community/network/plugins/action/sros.py' 2023-04-28 05:57:50,319 wheel INFO adding 'ansible_collections/community/network/plugins/action/voss.py' 2023-04-28 05:57:50,320 wheel INFO adding 'ansible_collections/community/network/plugins/become/__init__.py' 2023-04-28 05:57:50,320 wheel INFO adding 'ansible_collections/community/network/plugins/cache/__init__.py' 2023-04-28 05:57:50,320 wheel INFO adding 'ansible_collections/community/network/plugins/callback/__init__.py' 2023-04-28 05:57:50,320 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/__init__.py' 2023-04-28 05:57:50,320 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/aireos.py' 2023-04-28 05:57:50,321 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/apconos.py' 2023-04-28 05:57:50,321 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/aruba.py' 2023-04-28 05:57:50,321 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/ce.py' 2023-04-28 05:57:50,321 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/cnos.py' 2023-04-28 05:57:50,322 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/edgeos.py' 2023-04-28 05:57:50,322 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/edgeswitch.py' 2023-04-28 05:57:50,322 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/enos.py' 2023-04-28 05:57:50,322 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/eric_eccli.py' 2023-04-28 05:57:50,323 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/exos.py' 2023-04-28 05:57:50,323 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/icx.py' 2023-04-28 05:57:50,323 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/ironware.py' 2023-04-28 05:57:50,323 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/netvisor.py' 2023-04-28 05:57:50,324 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/nos.py' 2023-04-28 05:57:50,324 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/slxos.py' 2023-04-28 05:57:50,324 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/voss.py' 2023-04-28 05:57:50,324 wheel INFO adding 'ansible_collections/community/network/plugins/cliconf/weos4.py' 2023-04-28 05:57:50,325 wheel INFO adding 'ansible_collections/community/network/plugins/connection/__init__.py' 2023-04-28 05:57:50,325 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,325 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/a10.py' 2023-04-28 05:57:50,325 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/aireos.py' 2023-04-28 05:57:50,325 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/aruba.py' 2023-04-28 05:57:50,326 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/avi.py' 2023-04-28 05:57:50,326 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/ce.py' 2023-04-28 05:57:50,326 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/cnos.py' 2023-04-28 05:57:50,326 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/enos.py' 2023-04-28 05:57:50,327 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/ingate.py' 2023-04-28 05:57:50,327 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/ironware.py' 2023-04-28 05:57:50,327 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/netscaler.py' 2023-04-28 05:57:50,327 wheel INFO adding 'ansible_collections/community/network/plugins/doc_fragments/sros.py' 2023-04-28 05:57:50,327 wheel INFO adding 'ansible_collections/community/network/plugins/filter/__init__.py' 2023-04-28 05:57:50,328 wheel INFO adding 'ansible_collections/community/network/plugins/httpapi/__init__.py' 2023-04-28 05:57:50,328 wheel INFO adding 'ansible_collections/community/network/plugins/httpapi/exos.py' 2023-04-28 05:57:50,328 wheel INFO adding 'ansible_collections/community/network/plugins/httpapi/ftd.py' 2023-04-28 05:57:50,329 wheel INFO adding 'ansible_collections/community/network/plugins/inventory/__init__.py' 2023-04-28 05:57:50,329 wheel INFO adding 'ansible_collections/community/network/plugins/lookup/__init__.py' 2023-04-28 05:57:50,329 wheel INFO adding 'ansible_collections/community/network/plugins/lookup/avi.py' 2023-04-28 05:57:50,329 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,329 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/_version.py' 2023-04-28 05:57:50,330 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/version.py' 2023-04-28 05:57:50,330 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:50,330 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/a10/__init__.py' 2023-04-28 05:57:50,331 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/a10/a10.py' 2023-04-28 05:57:50,331 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/aireos/__init__.py' 2023-04-28 05:57:50,331 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/aireos/aireos.py' 2023-04-28 05:57:50,331 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/aos/__init__.py' 2023-04-28 05:57:50,331 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/aos/aos.py' 2023-04-28 05:57:50,332 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/apconos/__init__.py' 2023-04-28 05:57:50,332 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/apconos/apconos.py' 2023-04-28 05:57:50,332 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/aruba/__init__.py' 2023-04-28 05:57:50,333 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/aruba/aruba.py' 2023-04-28 05:57:50,333 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/avi/__init__.py' 2023-04-28 05:57:50,333 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/avi/ansible_utils.py' 2023-04-28 05:57:50,333 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/avi/avi.py' 2023-04-28 05:57:50,334 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/avi/avi_api.py' 2023-04-28 05:57:50,334 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/bigswitch/__init__.py' 2023-04-28 05:57:50,334 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/bigswitch/bigswitch.py' 2023-04-28 05:57:50,335 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/cloudengine/__init__.py' 2023-04-28 05:57:50,335 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/cloudengine/ce.py' 2023-04-28 05:57:50,335 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/cnos/__init__.py' 2023-04-28 05:57:50,335 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/cnos/cnos.py' 2023-04-28 05:57:50,336 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/cnos/cnos_devicerules.py' 2023-04-28 05:57:50,337 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/cnos/cnos_errorcodes.py' 2023-04-28 05:57:50,337 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/edgeos/__init__.py' 2023-04-28 05:57:50,337 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/edgeos/edgeos.py' 2023-04-28 05:57:50,337 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/edgeswitch/__init__.py' 2023-04-28 05:57:50,338 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/edgeswitch/edgeswitch.py' 2023-04-28 05:57:50,338 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/edgeswitch/edgeswitch_interface.py' 2023-04-28 05:57:50,338 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/enos/__init__.py' 2023-04-28 05:57:50,338 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/enos/enos.py' 2023-04-28 05:57:50,339 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/eric_eccli/__init__.py' 2023-04-28 05:57:50,339 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/eric_eccli/eric_eccli.py' 2023-04-28 05:57:50,339 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/__init__.py' 2023-04-28 05:57:50,339 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/exos.py' 2023-04-28 05:57:50,340 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/__init__.py' 2023-04-28 05:57:50,340 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/__init__.py' 2023-04-28 05:57:50,340 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/facts.py' 2023-04-28 05:57:50,340 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/__init__.py' 2023-04-28 05:57:50,341 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:50,341 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/__init__.py' 2023-04-28 05:57:50,341 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/lldp_global.py' 2023-04-28 05:57:50,341 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/__init__.py' 2023-04-28 05:57:50,341 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:50,342 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/__init__.py' 2023-04-28 05:57:50,342 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/vlans.py' 2023-04-28 05:57:50,342 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/__init__.py' 2023-04-28 05:57:50,342 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/__init__.py' 2023-04-28 05:57:50,343 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:50,343 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/__init__.py' 2023-04-28 05:57:50,343 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/lldp_global.py' 2023-04-28 05:57:50,343 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/__init__.py' 2023-04-28 05:57:50,344 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:50,344 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/__init__.py' 2023-04-28 05:57:50,344 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/vlans.py' 2023-04-28 05:57:50,344 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/__init__.py' 2023-04-28 05:57:50,345 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/facts.py' 2023-04-28 05:57:50,345 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/__init__.py' 2023-04-28 05:57:50,345 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:50,345 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/__init__.py' 2023-04-28 05:57:50,346 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/base.py' 2023-04-28 05:57:50,346 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/__init__.py' 2023-04-28 05:57:50,346 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/lldp_global.py' 2023-04-28 05:57:50,346 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/__init__.py' 2023-04-28 05:57:50,347 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:50,347 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/__init__.py' 2023-04-28 05:57:50,347 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/vlans.py' 2023-04-28 05:57:50,347 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/utils/__init__.py' 2023-04-28 05:57:50,348 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/exos/utils/utils.py' 2023-04-28 05:57:50,348 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ftd/__init__.py' 2023-04-28 05:57:50,348 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ftd/common.py' 2023-04-28 05:57:50,348 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ftd/configuration.py' 2023-04-28 05:57:50,349 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ftd/device.py' 2023-04-28 05:57:50,349 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ftd/fdm_swagger_client.py' 2023-04-28 05:57:50,349 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ftd/operation.py' 2023-04-28 05:57:50,350 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/icx/__init__.py' 2023-04-28 05:57:50,350 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/icx/icx.py' 2023-04-28 05:57:50,350 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ingate/__init__.py' 2023-04-28 05:57:50,350 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ingate/common.py' 2023-04-28 05:57:50,351 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ironware/__init__.py' 2023-04-28 05:57:50,351 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ironware/ironware.py' 2023-04-28 05:57:50,351 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/netscaler/__init__.py' 2023-04-28 05:57:50,351 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/netscaler/netscaler.py' 2023-04-28 05:57:50,352 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/netvisor/__init__.py' 2023-04-28 05:57:50,352 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/netvisor/netvisor.py' 2023-04-28 05:57:50,352 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/netvisor/pn_nvos.py' 2023-04-28 05:57:50,352 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/nos/__init__.py' 2023-04-28 05:57:50,352 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/nos/nos.py' 2023-04-28 05:57:50,353 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ordnance/__init__.py' 2023-04-28 05:57:50,353 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/ordnance/ordnance.py' 2023-04-28 05:57:50,353 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/slxos/__init__.py' 2023-04-28 05:57:50,353 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/slxos/slxos.py' 2023-04-28 05:57:50,354 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/sros/__init__.py' 2023-04-28 05:57:50,354 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/sros/sros.py' 2023-04-28 05:57:50,354 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/voss/__init__.py' 2023-04-28 05:57:50,354 wheel INFO adding 'ansible_collections/community/network/plugins/module_utils/network/voss/voss.py' 2023-04-28 05:57:50,355 wheel INFO adding 'ansible_collections/community/network/plugins/modules/__init__.py' 2023-04-28 05:57:50,355 wheel INFO adding 'ansible_collections/community/network/plugins/modules/a10_server.py' 2023-04-28 05:57:50,356 wheel INFO adding 'ansible_collections/community/network/plugins/modules/a10_server_axapi3.py' 2023-04-28 05:57:50,356 wheel INFO adding 'ansible_collections/community/network/plugins/modules/a10_service_group.py' 2023-04-28 05:57:50,356 wheel INFO adding 'ansible_collections/community/network/plugins/modules/a10_virtual_server.py' 2023-04-28 05:57:50,356 wheel INFO adding 'ansible_collections/community/network/plugins/modules/aireos_command.py' 2023-04-28 05:57:50,357 wheel INFO adding 'ansible_collections/community/network/plugins/modules/aireos_config.py' 2023-04-28 05:57:50,357 wheel INFO adding 'ansible_collections/community/network/plugins/modules/apconos_command.py' 2023-04-28 05:57:50,357 wheel INFO adding 'ansible_collections/community/network/plugins/modules/aruba_command.py' 2023-04-28 05:57:50,357 wheel INFO adding 'ansible_collections/community/network/plugins/modules/aruba_config.py' 2023-04-28 05:57:50,358 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_actiongroupconfig.py' 2023-04-28 05:57:50,358 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_alertconfig.py' 2023-04-28 05:57:50,358 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_alertemailconfig.py' 2023-04-28 05:57:50,359 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_alertscriptconfig.py' 2023-04-28 05:57:50,359 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_alertsyslogconfig.py' 2023-04-28 05:57:50,359 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_analyticsprofile.py' 2023-04-28 05:57:50,359 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_api_session.py' 2023-04-28 05:57:50,360 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_api_version.py' 2023-04-28 05:57:50,360 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_applicationpersistenceprofile.py' 2023-04-28 05:57:50,360 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_applicationprofile.py' 2023-04-28 05:57:50,360 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_authprofile.py' 2023-04-28 05:57:50,361 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_autoscalelaunchconfig.py' 2023-04-28 05:57:50,361 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_backup.py' 2023-04-28 05:57:50,361 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_backupconfiguration.py' 2023-04-28 05:57:50,361 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_certificatemanagementprofile.py' 2023-04-28 05:57:50,362 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_cloud.py' 2023-04-28 05:57:50,362 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_cloudconnectoruser.py' 2023-04-28 05:57:50,362 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_cloudproperties.py' 2023-04-28 05:57:50,362 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_cluster.py' 2023-04-28 05:57:50,363 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_clusterclouddetails.py' 2023-04-28 05:57:50,363 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_controllerproperties.py' 2023-04-28 05:57:50,363 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_customipamdnsprofile.py' 2023-04-28 05:57:50,363 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_dnspolicy.py' 2023-04-28 05:57:50,364 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_errorpagebody.py' 2023-04-28 05:57:50,364 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_errorpageprofile.py' 2023-04-28 05:57:50,364 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_gslb.py' 2023-04-28 05:57:50,364 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_gslbgeodbprofile.py' 2023-04-28 05:57:50,365 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_gslbservice.py' 2023-04-28 05:57:50,365 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_gslbservice_patch_member.py' 2023-04-28 05:57:50,365 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_hardwaresecuritymodulegroup.py' 2023-04-28 05:57:50,365 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_healthmonitor.py' 2023-04-28 05:57:50,366 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_httppolicyset.py' 2023-04-28 05:57:50,366 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_ipaddrgroup.py' 2023-04-28 05:57:50,366 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_ipamdnsproviderprofile.py' 2023-04-28 05:57:50,366 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_l4policyset.py' 2023-04-28 05:57:50,367 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_microservicegroup.py' 2023-04-28 05:57:50,367 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_network.py' 2023-04-28 05:57:50,367 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_networkprofile.py' 2023-04-28 05:57:50,367 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_networksecuritypolicy.py' 2023-04-28 05:57:50,368 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_pkiprofile.py' 2023-04-28 05:57:50,368 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_pool.py' 2023-04-28 05:57:50,368 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_poolgroup.py' 2023-04-28 05:57:50,368 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_poolgroupdeploymentpolicy.py' 2023-04-28 05:57:50,369 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_prioritylabels.py' 2023-04-28 05:57:50,369 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_role.py' 2023-04-28 05:57:50,369 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_scheduler.py' 2023-04-28 05:57:50,369 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_seproperties.py' 2023-04-28 05:57:50,370 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_serverautoscalepolicy.py' 2023-04-28 05:57:50,370 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_serviceengine.py' 2023-04-28 05:57:50,370 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_serviceenginegroup.py' 2023-04-28 05:57:50,371 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_snmptrapprofile.py' 2023-04-28 05:57:50,371 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_sslkeyandcertificate.py' 2023-04-28 05:57:50,371 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_sslprofile.py' 2023-04-28 05:57:50,371 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_stringgroup.py' 2023-04-28 05:57:50,372 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_systemconfiguration.py' 2023-04-28 05:57:50,372 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_tenant.py' 2023-04-28 05:57:50,372 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_trafficcloneprofile.py' 2023-04-28 05:57:50,372 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_user.py' 2023-04-28 05:57:50,373 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_useraccount.py' 2023-04-28 05:57:50,373 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_useraccountprofile.py' 2023-04-28 05:57:50,373 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_virtualservice.py' 2023-04-28 05:57:50,373 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_vrfcontext.py' 2023-04-28 05:57:50,374 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_vsdatascriptset.py' 2023-04-28 05:57:50,374 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_vsvip.py' 2023-04-28 05:57:50,374 wheel INFO adding 'ansible_collections/community/network/plugins/modules/avi_webhook.py' 2023-04-28 05:57:50,374 wheel INFO adding 'ansible_collections/community/network/plugins/modules/bcf_switch.py' 2023-04-28 05:57:50,375 wheel INFO adding 'ansible_collections/community/network/plugins/modules/bigmon_chain.py' 2023-04-28 05:57:50,375 wheel INFO adding 'ansible_collections/community/network/plugins/modules/bigmon_policy.py' 2023-04-28 05:57:50,375 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_aaa_server.py' 2023-04-28 05:57:50,376 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_aaa_server_host.py' 2023-04-28 05:57:50,377 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_acl.py' 2023-04-28 05:57:50,377 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_acl_advance.py' 2023-04-28 05:57:50,378 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_acl_interface.py' 2023-04-28 05:57:50,378 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_bfd_global.py' 2023-04-28 05:57:50,379 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_bfd_session.py' 2023-04-28 05:57:50,379 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_bfd_view.py' 2023-04-28 05:57:50,380 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_bgp.py' 2023-04-28 05:57:50,381 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_bgp_af.py' 2023-04-28 05:57:50,382 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_bgp_neighbor.py' 2023-04-28 05:57:50,382 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_bgp_neighbor_af.py' 2023-04-28 05:57:50,383 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_command.py' 2023-04-28 05:57:50,383 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_config.py' 2023-04-28 05:57:50,384 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_dldp.py' 2023-04-28 05:57:50,384 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_dldp_interface.py' 2023-04-28 05:57:50,384 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_eth_trunk.py' 2023-04-28 05:57:50,385 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_evpn_bd_vni.py' 2023-04-28 05:57:50,385 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_evpn_bgp.py' 2023-04-28 05:57:50,386 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_evpn_bgp_rr.py' 2023-04-28 05:57:50,386 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_evpn_global.py' 2023-04-28 05:57:50,386 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_facts.py' 2023-04-28 05:57:50,387 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_file_copy.py' 2023-04-28 05:57:50,387 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_info_center_debug.py' 2023-04-28 05:57:50,387 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_info_center_global.py' 2023-04-28 05:57:50,389 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_info_center_log.py' 2023-04-28 05:57:50,389 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_info_center_trap.py' 2023-04-28 05:57:50,389 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_interface.py' 2023-04-28 05:57:50,390 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_interface_ospf.py' 2023-04-28 05:57:50,390 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_ip_interface.py' 2023-04-28 05:57:50,391 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_is_is_instance.py' 2023-04-28 05:57:50,391 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_is_is_interface.py' 2023-04-28 05:57:50,391 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_is_is_view.py' 2023-04-28 05:57:50,392 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_lacp.py' 2023-04-28 05:57:50,392 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_link_status.py' 2023-04-28 05:57:50,393 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_lldp.py' 2023-04-28 05:57:50,393 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_lldp_interface.py' 2023-04-28 05:57:50,394 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_mdn_interface.py' 2023-04-28 05:57:50,394 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_mlag_config.py' 2023-04-28 05:57:50,395 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_mlag_interface.py' 2023-04-28 05:57:50,395 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_mtu.py' 2023-04-28 05:57:50,395 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_multicast_global.py' 2023-04-28 05:57:50,396 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_multicast_igmp_enable.py' 2023-04-28 05:57:50,396 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_netconf.py' 2023-04-28 05:57:50,396 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_netstream_aging.py' 2023-04-28 05:57:50,397 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_netstream_export.py' 2023-04-28 05:57:50,397 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_netstream_global.py' 2023-04-28 05:57:50,397 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_netstream_template.py' 2023-04-28 05:57:50,398 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_ntp.py' 2023-04-28 05:57:50,398 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_ntp_auth.py' 2023-04-28 05:57:50,398 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_ospf.py' 2023-04-28 05:57:50,399 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_ospf_vrf.py' 2023-04-28 05:57:50,399 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_reboot.py' 2023-04-28 05:57:50,400 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_rollback.py' 2023-04-28 05:57:50,400 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_sflow.py' 2023-04-28 05:57:50,401 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_snmp_community.py' 2023-04-28 05:57:50,401 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_snmp_contact.py' 2023-04-28 05:57:50,401 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_snmp_location.py' 2023-04-28 05:57:50,402 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_snmp_target_host.py' 2023-04-28 05:57:50,402 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_snmp_traps.py' 2023-04-28 05:57:50,402 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_snmp_user.py' 2023-04-28 05:57:50,403 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_startup.py' 2023-04-28 05:57:50,403 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_static_route.py' 2023-04-28 05:57:50,404 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_static_route_bfd.py' 2023-04-28 05:57:50,404 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_stp.py' 2023-04-28 05:57:50,405 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_switchport.py' 2023-04-28 05:57:50,405 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vlan.py' 2023-04-28 05:57:50,405 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vrf.py' 2023-04-28 05:57:50,406 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vrf_af.py' 2023-04-28 05:57:50,406 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vrf_interface.py' 2023-04-28 05:57:50,407 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vrrp.py' 2023-04-28 05:57:50,407 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vxlan_arp.py' 2023-04-28 05:57:50,407 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vxlan_gateway.py' 2023-04-28 05:57:50,408 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vxlan_global.py' 2023-04-28 05:57:50,408 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vxlan_tunnel.py' 2023-04-28 05:57:50,409 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ce_vxlan_vap.py' 2023-04-28 05:57:50,409 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_backup.py' 2023-04-28 05:57:50,409 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_banner.py' 2023-04-28 05:57:50,410 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_bgp.py' 2023-04-28 05:57:50,410 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_command.py' 2023-04-28 05:57:50,410 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_conditional_command.py' 2023-04-28 05:57:50,411 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_conditional_template.py' 2023-04-28 05:57:50,411 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_config.py' 2023-04-28 05:57:50,411 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_factory.py' 2023-04-28 05:57:50,411 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_facts.py' 2023-04-28 05:57:50,412 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_image.py' 2023-04-28 05:57:50,412 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_interface.py' 2023-04-28 05:57:50,412 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_l2_interface.py' 2023-04-28 05:57:50,413 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_l3_interface.py' 2023-04-28 05:57:50,413 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_linkagg.py' 2023-04-28 05:57:50,413 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_lldp.py' 2023-04-28 05:57:50,413 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_logging.py' 2023-04-28 05:57:50,414 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_reload.py' 2023-04-28 05:57:50,414 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_rollback.py' 2023-04-28 05:57:50,414 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_save.py' 2023-04-28 05:57:50,414 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_showrun.py' 2023-04-28 05:57:50,415 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_static_route.py' 2023-04-28 05:57:50,415 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_system.py' 2023-04-28 05:57:50,415 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_template.py' 2023-04-28 05:57:50,415 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_user.py' 2023-04-28 05:57:50,416 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_vlag.py' 2023-04-28 05:57:50,416 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_vlan.py' 2023-04-28 05:57:50,416 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cnos_vrf.py' 2023-04-28 05:57:50,417 wheel INFO adding 'ansible_collections/community/network/plugins/modules/cv_server_provision.py' 2023-04-28 05:57:50,417 wheel INFO adding 'ansible_collections/community/network/plugins/modules/dladm_etherstub.py' 2023-04-28 05:57:50,417 wheel INFO adding 'ansible_collections/community/network/plugins/modules/dladm_iptun.py' 2023-04-28 05:57:50,417 wheel INFO adding 'ansible_collections/community/network/plugins/modules/dladm_linkprop.py' 2023-04-28 05:57:50,418 wheel INFO adding 'ansible_collections/community/network/plugins/modules/dladm_vlan.py' 2023-04-28 05:57:50,418 wheel INFO adding 'ansible_collections/community/network/plugins/modules/dladm_vnic.py' 2023-04-28 05:57:50,418 wheel INFO adding 'ansible_collections/community/network/plugins/modules/edgeos_command.py' 2023-04-28 05:57:50,418 wheel INFO adding 'ansible_collections/community/network/plugins/modules/edgeos_config.py' 2023-04-28 05:57:50,419 wheel INFO adding 'ansible_collections/community/network/plugins/modules/edgeos_facts.py' 2023-04-28 05:57:50,419 wheel INFO adding 'ansible_collections/community/network/plugins/modules/edgeswitch_facts.py' 2023-04-28 05:57:50,419 wheel INFO adding 'ansible_collections/community/network/plugins/modules/edgeswitch_vlan.py' 2023-04-28 05:57:50,420 wheel INFO adding 'ansible_collections/community/network/plugins/modules/enos_command.py' 2023-04-28 05:57:50,420 wheel INFO adding 'ansible_collections/community/network/plugins/modules/enos_config.py' 2023-04-28 05:57:50,420 wheel INFO adding 'ansible_collections/community/network/plugins/modules/enos_facts.py' 2023-04-28 05:57:50,420 wheel INFO adding 'ansible_collections/community/network/plugins/modules/eric_eccli_command.py' 2023-04-28 05:57:50,421 wheel INFO adding 'ansible_collections/community/network/plugins/modules/exos_command.py' 2023-04-28 05:57:50,421 wheel INFO adding 'ansible_collections/community/network/plugins/modules/exos_config.py' 2023-04-28 05:57:50,421 wheel INFO adding 'ansible_collections/community/network/plugins/modules/exos_facts.py' 2023-04-28 05:57:50,422 wheel INFO adding 'ansible_collections/community/network/plugins/modules/exos_l2_interfaces.py' 2023-04-28 05:57:50,422 wheel INFO adding 'ansible_collections/community/network/plugins/modules/exos_lldp_global.py' 2023-04-28 05:57:50,422 wheel INFO adding 'ansible_collections/community/network/plugins/modules/exos_lldp_interfaces.py' 2023-04-28 05:57:50,422 wheel INFO adding 'ansible_collections/community/network/plugins/modules/exos_vlans.py' 2023-04-28 05:57:50,423 wheel INFO adding 'ansible_collections/community/network/plugins/modules/flowadm.py' 2023-04-28 05:57:50,423 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ftd_configuration.py' 2023-04-28 05:57:50,423 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ftd_file_download.py' 2023-04-28 05:57:50,424 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ftd_file_upload.py' 2023-04-28 05:57:50,424 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ftd_install.py' 2023-04-28 05:57:50,424 wheel INFO adding 'ansible_collections/community/network/plugins/modules/iap_start_workflow.py' 2023-04-28 05:57:50,424 wheel INFO adding 'ansible_collections/community/network/plugins/modules/iap_token.py' 2023-04-28 05:57:50,424 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_banner.py' 2023-04-28 05:57:50,425 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_command.py' 2023-04-28 05:57:50,425 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_config.py' 2023-04-28 05:57:50,425 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_copy.py' 2023-04-28 05:57:50,426 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_facts.py' 2023-04-28 05:57:50,426 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_interface.py' 2023-04-28 05:57:50,426 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_l3_interface.py' 2023-04-28 05:57:50,427 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_linkagg.py' 2023-04-28 05:57:50,427 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_lldp.py' 2023-04-28 05:57:50,427 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_logging.py' 2023-04-28 05:57:50,427 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_ping.py' 2023-04-28 05:57:50,428 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_static_route.py' 2023-04-28 05:57:50,428 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_system.py' 2023-04-28 05:57:50,428 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_user.py' 2023-04-28 05:57:50,429 wheel INFO adding 'ansible_collections/community/network/plugins/modules/icx_vlan.py' 2023-04-28 05:57:50,429 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ig_config.py' 2023-04-28 05:57:50,429 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ig_unit_information.py' 2023-04-28 05:57:50,430 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ipadm_addr.py' 2023-04-28 05:57:50,430 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ipadm_addrprop.py' 2023-04-28 05:57:50,430 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ipadm_if.py' 2023-04-28 05:57:50,430 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ipadm_ifprop.py' 2023-04-28 05:57:50,431 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ipadm_prop.py' 2023-04-28 05:57:50,431 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ironware_command.py' 2023-04-28 05:57:50,431 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ironware_config.py' 2023-04-28 05:57:50,431 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ironware_facts.py' 2023-04-28 05:57:50,432 wheel INFO adding 'ansible_collections/community/network/plugins/modules/nclu.py' 2023-04-28 05:57:50,432 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netact_cm_command.py' 2023-04-28 05:57:50,432 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_cs_action.py' 2023-04-28 05:57:50,432 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_cs_policy.py' 2023-04-28 05:57:50,433 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_cs_vserver.py' 2023-04-28 05:57:50,433 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_gslb_service.py' 2023-04-28 05:57:50,434 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_gslb_site.py' 2023-04-28 05:57:50,434 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_gslb_vserver.py' 2023-04-28 05:57:50,434 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_lb_monitor.py' 2023-04-28 05:57:50,435 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_lb_vserver.py' 2023-04-28 05:57:50,436 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_nitro_request.py' 2023-04-28 05:57:50,436 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_save_config.py' 2023-04-28 05:57:50,436 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_server.py' 2023-04-28 05:57:50,437 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_service.py' 2023-04-28 05:57:50,437 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_servicegroup.py' 2023-04-28 05:57:50,437 wheel INFO adding 'ansible_collections/community/network/plugins/modules/netscaler_ssl_certkey.py' 2023-04-28 05:57:50,438 wheel INFO adding 'ansible_collections/community/network/plugins/modules/nos_command.py' 2023-04-28 05:57:50,438 wheel INFO adding 'ansible_collections/community/network/plugins/modules/nos_config.py' 2023-04-28 05:57:50,438 wheel INFO adding 'ansible_collections/community/network/plugins/modules/nos_facts.py' 2023-04-28 05:57:50,439 wheel INFO adding 'ansible_collections/community/network/plugins/modules/nuage_vspk.py' 2023-04-28 05:57:50,439 wheel INFO adding 'ansible_collections/community/network/plugins/modules/opx_cps.py' 2023-04-28 05:57:50,439 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ordnance_config.py' 2023-04-28 05:57:50,440 wheel INFO adding 'ansible_collections/community/network/plugins/modules/ordnance_facts.py' 2023-04-28 05:57:50,440 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_access_list.py' 2023-04-28 05:57:50,440 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_access_list_ip.py' 2023-04-28 05:57:50,440 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_admin_service.py' 2023-04-28 05:57:50,441 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_admin_session_timeout.py' 2023-04-28 05:57:50,441 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_admin_syslog.py' 2023-04-28 05:57:50,441 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_connection_stats_settings.py' 2023-04-28 05:57:50,441 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_cpu_class.py' 2023-04-28 05:57:50,442 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_cpu_mgmt_class.py' 2023-04-28 05:57:50,442 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_dhcp_filter.py' 2023-04-28 05:57:50,442 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_dscp_map.py' 2023-04-28 05:57:50,442 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_dscp_map_pri_map.py' 2023-04-28 05:57:50,443 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_fabric_local.py' 2023-04-28 05:57:50,443 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_igmp_snooping.py' 2023-04-28 05:57:50,443 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard.py' 2023-04-28 05:57:50,443 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard_port.py' 2023-04-28 05:57:50,443 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_ipv6security_raguard_vlan.py' 2023-04-28 05:57:50,444 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_log_audit_exception.py' 2023-04-28 05:57:50,444 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_port_config.py' 2023-04-28 05:57:50,444 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_port_cos_bw.py' 2023-04-28 05:57:50,444 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_port_cos_rate_setting.py' 2023-04-28 05:57:50,445 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_prefix_list.py' 2023-04-28 05:57:50,445 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_prefix_list_network.py' 2023-04-28 05:57:50,445 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_role.py' 2023-04-28 05:57:50,445 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_snmp_community.py' 2023-04-28 05:57:50,446 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_snmp_trap_sink.py' 2023-04-28 05:57:50,446 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_snmp_vacm.py' 2023-04-28 05:57:50,446 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_stp.py' 2023-04-28 05:57:50,446 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_stp_port.py' 2023-04-28 05:57:50,447 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_switch_setup.py' 2023-04-28 05:57:50,447 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_user.py' 2023-04-28 05:57:50,447 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vflow_table_profile.py' 2023-04-28 05:57:50,447 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_bgp.py' 2023-04-28 05:57:50,448 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_bgp_network.py' 2023-04-28 05:57:50,448 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_interface_ip.py' 2023-04-28 05:57:50,448 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_loopback_interface.py' 2023-04-28 05:57:50,448 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_ospf.py' 2023-04-28 05:57:50,449 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_ospf6.py' 2023-04-28 05:57:50,449 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_packet_relay.py' 2023-04-28 05:57:50,449 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vrouter_pim_config.py' 2023-04-28 05:57:50,449 wheel INFO adding 'ansible_collections/community/network/plugins/modules/pn_vtep.py' 2023-04-28 05:57:50,450 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_command.py' 2023-04-28 05:57:50,450 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_config.py' 2023-04-28 05:57:50,450 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_facts.py' 2023-04-28 05:57:50,451 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_interface.py' 2023-04-28 05:57:50,451 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_l2_interface.py' 2023-04-28 05:57:50,451 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_l3_interface.py' 2023-04-28 05:57:50,451 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_linkagg.py' 2023-04-28 05:57:50,452 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_lldp.py' 2023-04-28 05:57:50,452 wheel INFO adding 'ansible_collections/community/network/plugins/modules/slxos_vlan.py' 2023-04-28 05:57:50,452 wheel INFO adding 'ansible_collections/community/network/plugins/modules/sros_command.py' 2023-04-28 05:57:50,452 wheel INFO adding 'ansible_collections/community/network/plugins/modules/sros_config.py' 2023-04-28 05:57:50,453 wheel INFO adding 'ansible_collections/community/network/plugins/modules/sros_rollback.py' 2023-04-28 05:57:50,453 wheel INFO adding 'ansible_collections/community/network/plugins/modules/vdirect_commit.py' 2023-04-28 05:57:50,453 wheel INFO adding 'ansible_collections/community/network/plugins/modules/vdirect_file.py' 2023-04-28 05:57:50,453 wheel INFO adding 'ansible_collections/community/network/plugins/modules/vdirect_runnable.py' 2023-04-28 05:57:50,454 wheel INFO adding 'ansible_collections/community/network/plugins/modules/voss_command.py' 2023-04-28 05:57:50,454 wheel INFO adding 'ansible_collections/community/network/plugins/modules/voss_config.py' 2023-04-28 05:57:50,454 wheel INFO adding 'ansible_collections/community/network/plugins/modules/voss_facts.py' 2023-04-28 05:57:50,455 wheel INFO adding 'ansible_collections/community/network/plugins/netconf/__init__.py' 2023-04-28 05:57:50,455 wheel INFO adding 'ansible_collections/community/network/plugins/netconf/ce.py' 2023-04-28 05:57:50,455 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/__init__.py' 2023-04-28 05:57:50,455 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/aireos.py' 2023-04-28 05:57:50,456 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/apconos.py' 2023-04-28 05:57:50,456 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/aruba.py' 2023-04-28 05:57:50,456 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/ce.py' 2023-04-28 05:57:50,456 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/cnos.py' 2023-04-28 05:57:50,457 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/edgeos.py' 2023-04-28 05:57:50,457 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/edgeswitch.py' 2023-04-28 05:57:50,457 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/enos.py' 2023-04-28 05:57:50,457 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/eric_eccli.py' 2023-04-28 05:57:50,457 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/exos.py' 2023-04-28 05:57:50,458 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/icx.py' 2023-04-28 05:57:50,458 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/ironware.py' 2023-04-28 05:57:50,458 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/netvisor.py' 2023-04-28 05:57:50,458 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/nos.py' 2023-04-28 05:57:50,459 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/slxos.py' 2023-04-28 05:57:50,459 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/sros.py' 2023-04-28 05:57:50,459 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/voss.py' 2023-04-28 05:57:50,459 wheel INFO adding 'ansible_collections/community/network/plugins/terminal/weos4.py' 2023-04-28 05:57:50,460 wheel INFO adding 'ansible_collections/community/okd/CHANGELOG.rst' 2023-04-28 05:57:50,460 wheel INFO adding 'ansible_collections/community/okd/CONTRIBUTING.md' 2023-04-28 05:57:50,460 wheel INFO adding 'ansible_collections/community/okd/FILES.json' 2023-04-28 05:57:50,461 wheel INFO adding 'ansible_collections/community/okd/LICENSE' 2023-04-28 05:57:50,461 wheel INFO adding 'ansible_collections/community/okd/MANIFEST.json' 2023-04-28 05:57:50,461 wheel INFO adding 'ansible_collections/community/okd/Makefile' 2023-04-28 05:57:50,461 wheel INFO adding 'ansible_collections/community/okd/OWNERS' 2023-04-28 05:57:50,462 wheel INFO adding 'ansible_collections/community/okd/OWNERS_ALIASES' 2023-04-28 05:57:50,462 wheel INFO adding 'ansible_collections/community/okd/README.md' 2023-04-28 05:57:50,462 wheel INFO adding 'ansible_collections/community/okd/codecov.yml' 2023-04-28 05:57:50,462 wheel INFO adding 'ansible_collections/community/okd/requirements.txt' 2023-04-28 05:57:50,462 wheel INFO adding 'ansible_collections/community/okd/requirements.yml' 2023-04-28 05:57:50,463 wheel INFO adding 'ansible_collections/community/okd/setup.cfg' 2023-04-28 05:57:50,463 wheel INFO adding 'ansible_collections/community/okd/test-requirements.txt' 2023-04-28 05:57:50,463 wheel INFO adding 'ansible_collections/community/okd/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:50,463 wheel INFO adding 'ansible_collections/community/okd/changelogs/changelog.yaml' 2023-04-28 05:57:50,464 wheel INFO adding 'ansible_collections/community/okd/changelogs/config.yaml' 2023-04-28 05:57:50,464 wheel INFO adding 'ansible_collections/community/okd/ci/Dockerfile' 2023-04-28 05:57:50,464 wheel INFO adding 'ansible_collections/community/okd/ci/doc_fragment_modules.py' 2023-04-28 05:57:50,464 wheel INFO adding 'ansible_collections/community/okd/ci/downstream.sh' 2023-04-28 05:57:50,465 wheel INFO adding 'ansible_collections/community/okd/ci/downstream_fragments.py' 2023-04-28 05:57:50,465 wheel INFO adding 'ansible_collections/community/okd/ci/incluster_integration.sh' 2023-04-28 05:57:50,465 wheel INFO adding 'ansible_collections/community/okd/meta/runtime.yml' 2023-04-28 05:57:50,465 wheel INFO adding 'ansible_collections/community/okd/molecule/default/README.md' 2023-04-28 05:57:50,465 wheel INFO adding 'ansible_collections/community/okd/molecule/default/converge.yml' 2023-04-28 05:57:50,466 wheel INFO adding 'ansible_collections/community/okd/molecule/default/destroy.yml' 2023-04-28 05:57:50,466 wheel INFO adding 'ansible_collections/community/okd/molecule/default/molecule.yml' 2023-04-28 05:57:50,466 wheel INFO adding 'ansible_collections/community/okd/molecule/default/prepare.yml' 2023-04-28 05:57:50,466 wheel INFO adding 'ansible_collections/community/okd/molecule/default/verify.yml' 2023-04-28 05:57:50,467 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/crd-resource.yml' 2023-04-28 05:57:50,467 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/example.env' 2023-04-28 05:57:50,467 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/kuard-extra-property.yml' 2023-04-28 05:57:50,467 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/kuard-invalid-type.yml' 2023-04-28 05:57:50,467 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/nginx.env' 2023-04-28 05:57:50,468 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/pod-template.yaml' 2023-04-28 05:57:50,468 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/setup-crd.yml' 2023-04-28 05:57:50,468 wheel INFO adding 'ansible_collections/community/okd/molecule/default/files/simple-template.yaml' 2023-04-28 05:57:50,468 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/defaults/main.yml' 2023-04-28 05:57:50,469 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/openshift_ldap_entry.py' 2023-04-28 05:57:50,469 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/openshift_ldap_entry_info.py' 2023-04-28 05:57:50,469 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/meta/main.yml' 2023-04-28 05:57:50,469 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/activeDirectory.yml' 2023-04-28 05:57:50,470 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/augmentedActiveDirectory.yml' 2023-04-28 05:57:50,470 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/main.yml' 2023-04-28 05:57:50,470 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/python-ldap-not-installed.yml' 2023-04-28 05:57:50,470 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/tasks/rfc2307.yml' 2023-04-28 05:57:50,471 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad/definition.j2' 2023-04-28 05:57:50,471 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/ad/sync-config.j2' 2023-04-28 05:57:50,471 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad/definition.j2' 2023-04-28 05:57:50,471 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/augmented-ad/sync-config.j2' 2023-04-28 05:57:50,472 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307/definition.j2' 2023-04-28 05:57:50,472 wheel INFO adding 'ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/templates/rfc2307/sync-config.j2' 2023-04-28 05:57:50,472 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_auth_clusterroles.yml' 2023-04-28 05:57:50,472 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_auth_roles.yml' 2023-04-28 05:57:50,473 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_adm_prune_deployments.yml' 2023-04-28 05:57:50,473 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_auth.yml' 2023-04-28 05:57:50,473 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_builds.yml' 2023-04-28 05:57:50,473 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_import_images.yml' 2023-04-28 05:57:50,474 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_process.yml' 2023-04-28 05:57:50,474 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_prune_images.yml' 2023-04-28 05:57:50,474 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/openshift_route.yml' 2023-04-28 05:57:50,474 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/validate_installed.yml' 2023-04-28 05:57:50,475 wheel INFO adding 'ansible_collections/community/okd/molecule/default/tasks/validate_not_installed.yml' 2023-04-28 05:57:50,475 wheel INFO adding 'ansible_collections/community/okd/molecule/default/vars/main.yml' 2023-04-28 05:57:50,475 wheel INFO adding 'ansible_collections/community/okd/plugins/connection/oc.py' 2023-04-28 05:57:50,475 wheel INFO adding 'ansible_collections/community/okd/plugins/inventory/openshift.py' 2023-04-28 05:57:50,476 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/k8s.py' 2023-04-28 05:57:50,476 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_auth.py' 2023-04-28 05:57:50,476 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_deployments.py' 2023-04-28 05:57:50,477 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_adm_prune_images.py' 2023-04-28 05:57:50,477 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_builds.py' 2023-04-28 05:57:50,477 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_common.py' 2023-04-28 05:57:50,477 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_docker_image.py' 2023-04-28 05:57:50,478 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_groups.py' 2023-04-28 05:57:50,478 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_images_common.py' 2023-04-28 05:57:50,478 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_import_image.py' 2023-04-28 05:57:50,479 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_ldap.py' 2023-04-28 05:57:50,479 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_process.py' 2023-04-28 05:57:50,479 wheel INFO adding 'ansible_collections/community/okd/plugins/module_utils/openshift_registry.py' 2023-04-28 05:57:50,480 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/k8s.py' 2023-04-28 05:57:50,480 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_adm_groups_sync.py' 2023-04-28 05:57:50,480 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_adm_migrate_template_instances.py' 2023-04-28 05:57:50,480 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_adm_prune_auth.py' 2023-04-28 05:57:50,481 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_adm_prune_builds.py' 2023-04-28 05:57:50,481 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_adm_prune_deployments.py' 2023-04-28 05:57:50,481 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_adm_prune_images.py' 2023-04-28 05:57:50,481 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_auth.py' 2023-04-28 05:57:50,482 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_build.py' 2023-04-28 05:57:50,482 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_import_image.py' 2023-04-28 05:57:50,482 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_process.py' 2023-04-28 05:57:50,483 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_registry_info.py' 2023-04-28 05:57:50,483 wheel INFO adding 'ansible_collections/community/okd/plugins/modules/openshift_route.py' 2023-04-28 05:57:50,483 wheel INFO adding 'ansible_collections/community/postgresql/CHANGELOG.rst' 2023-04-28 05:57:50,483 wheel INFO adding 'ansible_collections/community/postgresql/CONTRIBUTING.md' 2023-04-28 05:57:50,484 wheel INFO adding 'ansible_collections/community/postgresql/CONTRIBUTORS' 2023-04-28 05:57:50,484 wheel INFO adding 'ansible_collections/community/postgresql/COPYING' 2023-04-28 05:57:50,485 wheel INFO adding 'ansible_collections/community/postgresql/FILES.json' 2023-04-28 05:57:50,485 wheel INFO adding 'ansible_collections/community/postgresql/MAINTAINERS' 2023-04-28 05:57:50,485 wheel INFO adding 'ansible_collections/community/postgresql/MAINTAINING.md' 2023-04-28 05:57:50,486 wheel INFO adding 'ansible_collections/community/postgresql/MANIFEST.json' 2023-04-28 05:57:50,486 wheel INFO adding 'ansible_collections/community/postgresql/PSF-license.txt' 2023-04-28 05:57:50,486 wheel INFO adding 'ansible_collections/community/postgresql/README.md' 2023-04-28 05:57:50,486 wheel INFO adding 'ansible_collections/community/postgresql/requirements.txt' 2023-04-28 05:57:50,486 wheel INFO adding 'ansible_collections/community/postgresql/shippable.yml' 2023-04-28 05:57:50,487 wheel INFO adding 'ansible_collections/community/postgresql/simplified_bsd.txt' 2023-04-28 05:57:50,487 wheel INFO adding 'ansible_collections/community/postgresql/changelogs/changelog.yaml' 2023-04-28 05:57:50,487 wheel INFO adding 'ansible_collections/community/postgresql/changelogs/config.yaml' 2023-04-28 05:57:50,488 wheel INFO adding 'ansible_collections/community/postgresql/changelogs/fragments/.keep' 2023-04-28 05:57:50,488 wheel INFO adding 'ansible_collections/community/postgresql/meta/runtime.yml' 2023-04-28 05:57:50,488 wheel INFO adding 'ansible_collections/community/postgresql/plugins/doc_fragments/postgres.py' 2023-04-28 05:57:50,488 wheel INFO adding 'ansible_collections/community/postgresql/plugins/module_utils/_version.py' 2023-04-28 05:57:50,489 wheel INFO adding 'ansible_collections/community/postgresql/plugins/module_utils/database.py' 2023-04-28 05:57:50,489 wheel INFO adding 'ansible_collections/community/postgresql/plugins/module_utils/postgres.py' 2023-04-28 05:57:50,489 wheel INFO adding 'ansible_collections/community/postgresql/plugins/module_utils/saslprep.py' 2023-04-28 05:57:50,489 wheel INFO adding 'ansible_collections/community/postgresql/plugins/module_utils/version.py' 2023-04-28 05:57:50,490 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_copy.py' 2023-04-28 05:57:50,490 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_db.py' 2023-04-28 05:57:50,490 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_ext.py' 2023-04-28 05:57:50,491 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_idx.py' 2023-04-28 05:57:50,491 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_info.py' 2023-04-28 05:57:50,491 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_lang.py' 2023-04-28 05:57:50,492 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_membership.py' 2023-04-28 05:57:50,492 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_owner.py' 2023-04-28 05:57:50,492 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_pg_hba.py' 2023-04-28 05:57:50,493 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_ping.py' 2023-04-28 05:57:50,493 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_privs.py' 2023-04-28 05:57:50,494 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_publication.py' 2023-04-28 05:57:50,494 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_query.py' 2023-04-28 05:57:50,494 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_schema.py' 2023-04-28 05:57:50,495 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_script.py' 2023-04-28 05:57:50,495 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_sequence.py' 2023-04-28 05:57:50,495 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_set.py' 2023-04-28 05:57:50,496 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_slot.py' 2023-04-28 05:57:50,496 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_subscription.py' 2023-04-28 05:57:50,496 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_table.py' 2023-04-28 05:57:50,497 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_tablespace.py' 2023-04-28 05:57:50,497 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_user.py' 2023-04-28 05:57:50,497 wheel INFO adding 'ansible_collections/community/postgresql/plugins/modules/postgresql_user_obj_stat_info.py' 2023-04-28 05:57:50,498 wheel INFO adding 'ansible_collections/community/proxysql/CHANGELOG.rst' 2023-04-28 05:57:50,498 wheel INFO adding 'ansible_collections/community/proxysql/CONTRIBUTING.md' 2023-04-28 05:57:50,498 wheel INFO adding 'ansible_collections/community/proxysql/CONTRIBUTORS' 2023-04-28 05:57:50,498 wheel INFO adding 'ansible_collections/community/proxysql/FILES.json' 2023-04-28 05:57:50,499 wheel INFO adding 'ansible_collections/community/proxysql/LICENSE' 2023-04-28 05:57:50,499 wheel INFO adding 'ansible_collections/community/proxysql/MAINTAINERS' 2023-04-28 05:57:50,500 wheel INFO adding 'ansible_collections/community/proxysql/MAINTAINING.md' 2023-04-28 05:57:50,500 wheel INFO adding 'ansible_collections/community/proxysql/MANIFEST.json' 2023-04-28 05:57:50,500 wheel INFO adding 'ansible_collections/community/proxysql/README.md' 2023-04-28 05:57:50,500 wheel INFO adding 'ansible_collections/community/proxysql/REVIEW_CHECKLIST.md' 2023-04-28 05:57:50,500 wheel INFO adding 'ansible_collections/community/proxysql/codecov.yml' 2023-04-28 05:57:50,501 wheel INFO adding 'ansible_collections/community/proxysql/changelogs/changelog.yaml' 2023-04-28 05:57:50,501 wheel INFO adding 'ansible_collections/community/proxysql/changelogs/config.yaml' 2023-04-28 05:57:50,501 wheel INFO adding 'ansible_collections/community/proxysql/meta/runtime.yml' 2023-04-28 05:57:50,501 wheel INFO adding 'ansible_collections/community/proxysql/plugins/README.md' 2023-04-28 05:57:50,502 wheel INFO adding 'ansible_collections/community/proxysql/plugins/doc_fragments/proxysql.py' 2023-04-28 05:57:50,502 wheel INFO adding 'ansible_collections/community/proxysql/plugins/module_utils/mysql.py' 2023-04-28 05:57:50,502 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_backend_servers.py' 2023-04-28 05:57:50,503 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_global_variables.py' 2023-04-28 05:57:50,503 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_info.py' 2023-04-28 05:57:50,503 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_manage_config.py' 2023-04-28 05:57:50,503 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_mysql_users.py' 2023-04-28 05:57:50,504 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_query_rules.py' 2023-04-28 05:57:50,504 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_query_rules_fast_routing.py' 2023-04-28 05:57:50,505 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_replication_hostgroups.py' 2023-04-28 05:57:50,505 wheel INFO adding 'ansible_collections/community/proxysql/plugins/modules/proxysql_scheduler.py' 2023-04-28 05:57:50,505 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/.yamllint' 2023-04-28 05:57:50,505 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/README.md' 2023-04-28 05:57:50,506 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/defaults/main.yml' 2023-04-28 05:57:50,506 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/handlers/main.yml' 2023-04-28 05:57:50,506 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/meta/main.yml' 2023-04-28 05:57:50,507 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/molecule/default/converge.yml' 2023-04-28 05:57:50,507 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/molecule/default/molecule.yml' 2023-04-28 05:57:50,507 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/molecule/default/prepare.yml' 2023-04-28 05:57:50,507 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests/test_default.py' 2023-04-28 05:57:50,507 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/tasks/config.yml' 2023-04-28 05:57:50,508 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/tasks/install.yml' 2023-04-28 05:57:50,508 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/tasks/main.yml' 2023-04-28 05:57:50,508 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/tasks/setvars.yml' 2023-04-28 05:57:50,508 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/tasks/users.yml' 2023-04-28 05:57:50,509 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/templates/client.my.cnf.j2' 2023-04-28 05:57:50,509 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/templates/proxysql.cnf.j2' 2023-04-28 05:57:50,509 wheel INFO adding 'ansible_collections/community/proxysql/roles/proxysql/vars/main.yml' 2023-04-28 05:57:50,509 wheel INFO adding 'ansible_collections/community/rabbitmq/CHANGELOG.rst' 2023-04-28 05:57:50,510 wheel INFO adding 'ansible_collections/community/rabbitmq/CONTRIBUTING.md' 2023-04-28 05:57:50,510 wheel INFO adding 'ansible_collections/community/rabbitmq/COPYING' 2023-04-28 05:57:50,510 wheel INFO adding 'ansible_collections/community/rabbitmq/FILES.json' 2023-04-28 05:57:50,511 wheel INFO adding 'ansible_collections/community/rabbitmq/MAINTAINERS' 2023-04-28 05:57:50,511 wheel INFO adding 'ansible_collections/community/rabbitmq/MAINTAINING.md' 2023-04-28 05:57:50,511 wheel INFO adding 'ansible_collections/community/rabbitmq/MANIFEST.json' 2023-04-28 05:57:50,511 wheel INFO adding 'ansible_collections/community/rabbitmq/PSF-license.txt' 2023-04-28 05:57:50,512 wheel INFO adding 'ansible_collections/community/rabbitmq/README.md' 2023-04-28 05:57:50,512 wheel INFO adding 'ansible_collections/community/rabbitmq/changelogs/changelog.yaml' 2023-04-28 05:57:50,512 wheel INFO adding 'ansible_collections/community/rabbitmq/changelogs/config.yaml' 2023-04-28 05:57:50,512 wheel INFO adding 'ansible_collections/community/rabbitmq/meta/runtime.yml' 2023-04-28 05:57:50,513 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,513 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/doc_fragments/rabbitmq.py' 2023-04-28 05:57:50,513 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/lookup/rabbitmq.py' 2023-04-28 05:57:50,514 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/module_utils/_version.py' 2023-04-28 05:57:50,514 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/module_utils/rabbitmq.py' 2023-04-28 05:57:50,514 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/module_utils/version.py' 2023-04-28 05:57:50,514 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_binding.py' 2023-04-28 05:57:50,515 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_exchange.py' 2023-04-28 05:57:50,515 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_feature_flag.py' 2023-04-28 05:57:50,515 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_global_parameter.py' 2023-04-28 05:57:50,515 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_parameter.py' 2023-04-28 05:57:50,516 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_plugin.py' 2023-04-28 05:57:50,516 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_policy.py' 2023-04-28 05:57:50,516 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_publish.py' 2023-04-28 05:57:50,516 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_queue.py' 2023-04-28 05:57:50,517 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_upgrade.py' 2023-04-28 05:57:50,517 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_user.py' 2023-04-28 05:57:50,517 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_user_limits.py' 2023-04-28 05:57:50,517 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_vhost.py' 2023-04-28 05:57:50,518 wheel INFO adding 'ansible_collections/community/rabbitmq/plugins/modules/rabbitmq_vhost_limits.py' 2023-04-28 05:57:50,518 wheel INFO adding 'ansible_collections/community/routeros/CHANGELOG.rst' 2023-04-28 05:57:50,518 wheel INFO adding 'ansible_collections/community/routeros/CHANGELOG.rst.license' 2023-04-28 05:57:50,519 wheel INFO adding 'ansible_collections/community/routeros/COPYING' 2023-04-28 05:57:50,519 wheel INFO adding 'ansible_collections/community/routeros/FILES.json' 2023-04-28 05:57:50,519 wheel INFO adding 'ansible_collections/community/routeros/MANIFEST.json' 2023-04-28 05:57:50,520 wheel INFO adding 'ansible_collections/community/routeros/README.md' 2023-04-28 05:57:50,520 wheel INFO adding 'ansible_collections/community/routeros/codecov.yml' 2023-04-28 05:57:50,520 wheel INFO adding 'ansible_collections/community/routeros/update-docs.py' 2023-04-28 05:57:50,520 wheel INFO adding 'ansible_collections/community/routeros/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:50,521 wheel INFO adding 'ansible_collections/community/routeros/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:50,521 wheel INFO adding 'ansible_collections/community/routeros/LICENSES/PSF-2.0.txt' 2023-04-28 05:57:50,521 wheel INFO adding 'ansible_collections/community/routeros/changelogs/changelog.yaml' 2023-04-28 05:57:50,522 wheel INFO adding 'ansible_collections/community/routeros/changelogs/changelog.yaml.license' 2023-04-28 05:57:50,522 wheel INFO adding 'ansible_collections/community/routeros/changelogs/config.yaml' 2023-04-28 05:57:50,522 wheel INFO adding 'ansible_collections/community/routeros/changelogs/fragments/.keep' 2023-04-28 05:57:50,522 wheel INFO adding 'ansible_collections/community/routeros/meta/ee-requirements.txt' 2023-04-28 05:57:50,523 wheel INFO adding 'ansible_collections/community/routeros/meta/execution-environment.yml' 2023-04-28 05:57:50,523 wheel INFO adding 'ansible_collections/community/routeros/meta/runtime.yml' 2023-04-28 05:57:50,523 wheel INFO adding 'ansible_collections/community/routeros/plugins/cliconf/routeros.py' 2023-04-28 05:57:50,523 wheel INFO adding 'ansible_collections/community/routeros/plugins/doc_fragments/api.py' 2023-04-28 05:57:50,524 wheel INFO adding 'ansible_collections/community/routeros/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:50,524 wheel INFO adding 'ansible_collections/community/routeros/plugins/filter/join.yml' 2023-04-28 05:57:50,524 wheel INFO adding 'ansible_collections/community/routeros/plugins/filter/list_to_dict.yml' 2023-04-28 05:57:50,524 wheel INFO adding 'ansible_collections/community/routeros/plugins/filter/quote_argument.yml' 2023-04-28 05:57:50,525 wheel INFO adding 'ansible_collections/community/routeros/plugins/filter/quote_argument_value.yml' 2023-04-28 05:57:50,525 wheel INFO adding 'ansible_collections/community/routeros/plugins/filter/quoting.py' 2023-04-28 05:57:50,525 wheel INFO adding 'ansible_collections/community/routeros/plugins/filter/split.yml' 2023-04-28 05:57:50,526 wheel INFO adding 'ansible_collections/community/routeros/plugins/module_utils/_api_data.py' 2023-04-28 05:57:50,526 wheel INFO adding 'ansible_collections/community/routeros/plugins/module_utils/_version.py' 2023-04-28 05:57:50,527 wheel INFO adding 'ansible_collections/community/routeros/plugins/module_utils/api.py' 2023-04-28 05:57:50,527 wheel INFO adding 'ansible_collections/community/routeros/plugins/module_utils/quoting.py' 2023-04-28 05:57:50,527 wheel INFO adding 'ansible_collections/community/routeros/plugins/module_utils/routeros.py' 2023-04-28 05:57:50,527 wheel INFO adding 'ansible_collections/community/routeros/plugins/module_utils/version.py' 2023-04-28 05:57:50,528 wheel INFO adding 'ansible_collections/community/routeros/plugins/modules/api.py' 2023-04-28 05:57:50,528 wheel INFO adding 'ansible_collections/community/routeros/plugins/modules/api_facts.py' 2023-04-28 05:57:50,528 wheel INFO adding 'ansible_collections/community/routeros/plugins/modules/api_find_and_modify.py' 2023-04-28 05:57:50,528 wheel INFO adding 'ansible_collections/community/routeros/plugins/modules/api_info.py' 2023-04-28 05:57:50,529 wheel INFO adding 'ansible_collections/community/routeros/plugins/modules/api_modify.py' 2023-04-28 05:57:50,529 wheel INFO adding 'ansible_collections/community/routeros/plugins/modules/command.py' 2023-04-28 05:57:50,530 wheel INFO adding 'ansible_collections/community/routeros/plugins/modules/facts.py' 2023-04-28 05:57:50,530 wheel INFO adding 'ansible_collections/community/routeros/plugins/terminal/routeros.py' 2023-04-28 05:57:50,530 wheel INFO adding 'ansible_collections/community/sap/CHANGELOG.rst' 2023-04-28 05:57:50,530 wheel INFO adding 'ansible_collections/community/sap/CODE_OF_CONDUCT.md' 2023-04-28 05:57:50,531 wheel INFO adding 'ansible_collections/community/sap/CONTRIBUTING.md' 2023-04-28 05:57:50,531 wheel INFO adding 'ansible_collections/community/sap/FILES.json' 2023-04-28 05:57:50,531 wheel INFO adding 'ansible_collections/community/sap/LICENSE' 2023-04-28 05:57:50,532 wheel INFO adding 'ansible_collections/community/sap/MAINTAINERS' 2023-04-28 05:57:50,532 wheel INFO adding 'ansible_collections/community/sap/MAINTAINING.md' 2023-04-28 05:57:50,532 wheel INFO adding 'ansible_collections/community/sap/MANIFEST.json' 2023-04-28 05:57:50,532 wheel INFO adding 'ansible_collections/community/sap/README.md' 2023-04-28 05:57:50,532 wheel INFO adding 'ansible_collections/community/sap/REVIEW_CHECKLIST.md' 2023-04-28 05:57:50,533 wheel INFO adding 'ansible_collections/community/sap/codecov.yml' 2023-04-28 05:57:50,533 wheel INFO adding 'ansible_collections/community/sap/changelogs/changelog.yaml' 2023-04-28 05:57:50,533 wheel INFO adding 'ansible_collections/community/sap/changelogs/config.yaml' 2023-04-28 05:57:50,533 wheel INFO adding 'ansible_collections/community/sap/changelogs/fragments/.keep' 2023-04-28 05:57:50,534 wheel INFO adding 'ansible_collections/community/sap/meta/runtime.yml' 2023-04-28 05:57:50,534 wheel INFO adding 'ansible_collections/community/sap/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,534 wheel INFO adding 'ansible_collections/community/sap/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,534 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/hana_query.py' 2023-04-28 05:57:50,535 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/sap_company.py' 2023-04-28 05:57:50,535 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/sap_snote.py' 2023-04-28 05:57:50,535 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/sap_system_facts.py' 2023-04-28 05:57:50,535 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/sap_task_list_execute.py' 2023-04-28 05:57:50,536 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/sap_user.py' 2023-04-28 05:57:50,536 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/sapcar_extract.py' 2023-04-28 05:57:50,536 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/database/saphana/hana_query.py' 2023-04-28 05:57:50,537 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/files/sapcar_extract.py' 2023-04-28 05:57:50,537 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/identity/sap_company.py' 2023-04-28 05:57:50,537 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/identity/sap_user.py' 2023-04-28 05:57:50,538 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/system/sap_snote.py' 2023-04-28 05:57:50,538 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/system/sap_system_facts.py' 2023-04-28 05:57:50,538 wheel INFO adding 'ansible_collections/community/sap/plugins/modules/system/sap_task_list_execute.py' 2023-04-28 05:57:50,538 wheel INFO adding 'ansible_collections/community/sap_libs/CHANGELOG.rst' 2023-04-28 05:57:50,539 wheel INFO adding 'ansible_collections/community/sap_libs/CODE_OF_CONDUCT.md' 2023-04-28 05:57:50,539 wheel INFO adding 'ansible_collections/community/sap_libs/CONTRIBUTING.md' 2023-04-28 05:57:50,539 wheel INFO adding 'ansible_collections/community/sap_libs/FILES.json' 2023-04-28 05:57:50,539 wheel INFO adding 'ansible_collections/community/sap_libs/LICENSE' 2023-04-28 05:57:50,540 wheel INFO adding 'ansible_collections/community/sap_libs/MAINTAINERS' 2023-04-28 05:57:50,540 wheel INFO adding 'ansible_collections/community/sap_libs/MAINTAINING.md' 2023-04-28 05:57:50,540 wheel INFO adding 'ansible_collections/community/sap_libs/MANIFEST.json' 2023-04-28 05:57:50,540 wheel INFO adding 'ansible_collections/community/sap_libs/README.md' 2023-04-28 05:57:50,540 wheel INFO adding 'ansible_collections/community/sap_libs/REVIEW_CHECKLIST.md' 2023-04-28 05:57:50,541 wheel INFO adding 'ansible_collections/community/sap_libs/codecov.yml' 2023-04-28 05:57:50,541 wheel INFO adding 'ansible_collections/community/sap_libs/changelogs/changelog.yaml' 2023-04-28 05:57:50,541 wheel INFO adding 'ansible_collections/community/sap_libs/changelogs/config.yaml' 2023-04-28 05:57:50,541 wheel INFO adding 'ansible_collections/community/sap_libs/changelogs/fragments/.keep' 2023-04-28 05:57:50,542 wheel INFO adding 'ansible_collections/community/sap_libs/meta/runtime.yml' 2023-04-28 05:57:50,542 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,542 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,542 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/module_utils/pyrfc_handler.py' 2023-04-28 05:57:50,543 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/module_utils/swpm2_parameters_inifile_generate.py' 2023-04-28 05:57:50,543 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_company.py' 2023-04-28 05:57:50,543 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_control_exec.py' 2023-04-28 05:57:50,544 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_hdbsql.py' 2023-04-28 05:57:50,544 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_pyrfc.py' 2023-04-28 05:57:50,544 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_snote.py' 2023-04-28 05:57:50,544 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_system_facts.py' 2023-04-28 05:57:50,545 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_task_list_execute.py' 2023-04-28 05:57:50,545 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sap_user.py' 2023-04-28 05:57:50,545 wheel INFO adding 'ansible_collections/community/sap_libs/plugins/modules/sapcar_extract.py' 2023-04-28 05:57:50,545 wheel INFO adding 'ansible_collections/community/skydive/CHANGELOG.rst' 2023-04-28 05:57:50,546 wheel INFO adding 'ansible_collections/community/skydive/FILES.json' 2023-04-28 05:57:50,546 wheel INFO adding 'ansible_collections/community/skydive/LICENSE' 2023-04-28 05:57:50,546 wheel INFO adding 'ansible_collections/community/skydive/MANIFEST.json' 2023-04-28 05:57:50,547 wheel INFO adding 'ansible_collections/community/skydive/README.md' 2023-04-28 05:57:50,547 wheel INFO adding 'ansible_collections/community/skydive/bindep.txt' 2023-04-28 05:57:50,547 wheel INFO adding 'ansible_collections/community/skydive/requirements.txt' 2023-04-28 05:57:50,547 wheel INFO adding 'ansible_collections/community/skydive/test-requirements.txt' 2023-04-28 05:57:50,547 wheel INFO adding 'ansible_collections/community/skydive/tox.ini' 2023-04-28 05:57:50,548 wheel INFO adding 'ansible_collections/community/skydive/changelogs/changelog.yaml' 2023-04-28 05:57:50,548 wheel INFO adding 'ansible_collections/community/skydive/changelogs/config.yaml' 2023-04-28 05:57:50,548 wheel INFO adding 'ansible_collections/community/skydive/meta/runtime.yml' 2023-04-28 05:57:50,548 wheel INFO adding 'ansible_collections/community/skydive/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,549 wheel INFO adding 'ansible_collections/community/skydive/plugins/doc_fragments/skydive.py' 2023-04-28 05:57:50,549 wheel INFO adding 'ansible_collections/community/skydive/plugins/lookup/__init__.py' 2023-04-28 05:57:50,549 wheel INFO adding 'ansible_collections/community/skydive/plugins/lookup/skydive.py' 2023-04-28 05:57:50,549 wheel INFO adding 'ansible_collections/community/skydive/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,550 wheel INFO adding 'ansible_collections/community/skydive/plugins/module_utils/network/skydive/__init__.py' 2023-04-28 05:57:50,550 wheel INFO adding 'ansible_collections/community/skydive/plugins/module_utils/network/skydive/api.py' 2023-04-28 05:57:50,550 wheel INFO adding 'ansible_collections/community/skydive/plugins/modules/__init__.py' 2023-04-28 05:57:50,550 wheel INFO adding 'ansible_collections/community/skydive/plugins/modules/skydive_capture.py' 2023-04-28 05:57:50,551 wheel INFO adding 'ansible_collections/community/skydive/plugins/modules/skydive_edge.py' 2023-04-28 05:57:50,551 wheel INFO adding 'ansible_collections/community/skydive/plugins/modules/skydive_node.py' 2023-04-28 05:57:50,551 wheel INFO adding 'ansible_collections/community/sops/CHANGELOG.rst' 2023-04-28 05:57:50,551 wheel INFO adding 'ansible_collections/community/sops/CHANGELOG.rst.license' 2023-04-28 05:57:50,552 wheel INFO adding 'ansible_collections/community/sops/CONTRIBUTING.md' 2023-04-28 05:57:50,552 wheel INFO adding 'ansible_collections/community/sops/COPYING' 2023-04-28 05:57:50,552 wheel INFO adding 'ansible_collections/community/sops/FILES.json' 2023-04-28 05:57:50,553 wheel INFO adding 'ansible_collections/community/sops/MANIFEST.json' 2023-04-28 05:57:50,553 wheel INFO adding 'ansible_collections/community/sops/README.md' 2023-04-28 05:57:50,554 wheel INFO adding 'ansible_collections/community/sops/codecov.yml' 2023-04-28 05:57:50,554 wheel INFO adding 'ansible_collections/community/sops/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:50,554 wheel INFO adding 'ansible_collections/community/sops/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:50,554 wheel INFO adding 'ansible_collections/community/sops/changelogs/changelog.yaml' 2023-04-28 05:57:50,555 wheel INFO adding 'ansible_collections/community/sops/changelogs/changelog.yaml.license' 2023-04-28 05:57:50,555 wheel INFO adding 'ansible_collections/community/sops/changelogs/config.yaml' 2023-04-28 05:57:50,555 wheel INFO adding 'ansible_collections/community/sops/changelogs/fragments/.keep' 2023-04-28 05:57:50,555 wheel INFO adding 'ansible_collections/community/sops/meta/ee-bindep.txt' 2023-04-28 05:57:50,556 wheel INFO adding 'ansible_collections/community/sops/meta/execution-environment.yml' 2023-04-28 05:57:50,556 wheel INFO adding 'ansible_collections/community/sops/meta/runtime.yml' 2023-04-28 05:57:50,556 wheel INFO adding 'ansible_collections/community/sops/playbooks/install.yml' 2023-04-28 05:57:50,556 wheel INFO adding 'ansible_collections/community/sops/playbooks/install_localhost.yml' 2023-04-28 05:57:50,557 wheel INFO adding 'ansible_collections/community/sops/plugins/action/load_vars.py' 2023-04-28 05:57:50,557 wheel INFO adding 'ansible_collections/community/sops/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:50,557 wheel INFO adding 'ansible_collections/community/sops/plugins/doc_fragments/sops.py' 2023-04-28 05:57:50,557 wheel INFO adding 'ansible_collections/community/sops/plugins/filter/_latest_version.py' 2023-04-28 05:57:50,558 wheel INFO adding 'ansible_collections/community/sops/plugins/filter/decrypt.py' 2023-04-28 05:57:50,558 wheel INFO adding 'ansible_collections/community/sops/plugins/lookup/sops.py' 2023-04-28 05:57:50,558 wheel INFO adding 'ansible_collections/community/sops/plugins/module_utils/io.py' 2023-04-28 05:57:50,558 wheel INFO adding 'ansible_collections/community/sops/plugins/module_utils/sops.py' 2023-04-28 05:57:50,559 wheel INFO adding 'ansible_collections/community/sops/plugins/modules/load_vars.py' 2023-04-28 05:57:50,559 wheel INFO adding 'ansible_collections/community/sops/plugins/modules/sops_encrypt.py' 2023-04-28 05:57:50,559 wheel INFO adding 'ansible_collections/community/sops/plugins/plugin_utils/action_module.py' 2023-04-28 05:57:50,560 wheel INFO adding 'ansible_collections/community/sops/plugins/vars/sops.py' 2023-04-28 05:57:50,560 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/README.md' 2023-04-28 05:57:50,560 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/defaults/main.yml' 2023-04-28 05:57:50,561 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/meta/main.yml' 2023-04-28 05:57:50,561 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/tasks/main.yml' 2023-04-28 05:57:50,561 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/D-Alpine.yml' 2023-04-28 05:57:50,561 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/D-Archlinux.yml' 2023-04-28 05:57:50,561 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/D-Debian-10.yml' 2023-04-28 05:57:50,562 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/D-Fedora.yml' 2023-04-28 05:57:50,562 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-16.yml' 2023-04-28 05:57:50,562 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-18.yml' 2023-04-28 05:57:50,562 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/D-Ubuntu-20.yml' 2023-04-28 05:57:50,562 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/OS-Debian.yml' 2023-04-28 05:57:50,563 wheel INFO adding 'ansible_collections/community/sops/roles/_install_age/vars/default.yml' 2023-04-28 05:57:50,563 wheel INFO adding 'ansible_collections/community/sops/roles/install/README.md' 2023-04-28 05:57:50,563 wheel INFO adding 'ansible_collections/community/sops/roles/install/defaults/main.yml' 2023-04-28 05:57:50,563 wheel INFO adding 'ansible_collections/community/sops/roles/install/meta/argument_specs.yml' 2023-04-28 05:57:50,564 wheel INFO adding 'ansible_collections/community/sops/roles/install/meta/main.yml' 2023-04-28 05:57:50,564 wheel INFO adding 'ansible_collections/community/sops/roles/install/tasks/detect_source.yml' 2023-04-28 05:57:50,564 wheel INFO adding 'ansible_collections/community/sops/roles/install/tasks/github.yml' 2023-04-28 05:57:50,564 wheel INFO adding 'ansible_collections/community/sops/roles/install/tasks/github_api.yml' 2023-04-28 05:57:50,565 wheel INFO adding 'ansible_collections/community/sops/roles/install/tasks/github_latest_release.yml' 2023-04-28 05:57:50,565 wheel INFO adding 'ansible_collections/community/sops/roles/install/tasks/main.yml' 2023-04-28 05:57:50,565 wheel INFO adding 'ansible_collections/community/sops/roles/install/tasks/system.yml' 2023-04-28 05:57:50,565 wheel INFO adding 'ansible_collections/community/sops/roles/install/vars/D-Alpine.yml' 2023-04-28 05:57:50,565 wheel INFO adding 'ansible_collections/community/sops/roles/install/vars/D-Archlinux.yml' 2023-04-28 05:57:50,566 wheel INFO adding 'ansible_collections/community/sops/roles/install/vars/OS-Debian.yml' 2023-04-28 05:57:50,566 wheel INFO adding 'ansible_collections/community/sops/roles/install/vars/OS-RedHat.yml' 2023-04-28 05:57:50,566 wheel INFO adding 'ansible_collections/community/sops/roles/install/vars/default.yml' 2023-04-28 05:57:50,567 wheel INFO adding 'ansible_collections/community/vmware/CHANGELOG.rst' 2023-04-28 05:57:50,567 wheel INFO adding 'ansible_collections/community/vmware/COPYING' 2023-04-28 05:57:50,568 wheel INFO adding 'ansible_collections/community/vmware/FILES.json' 2023-04-28 05:57:50,569 wheel INFO adding 'ansible_collections/community/vmware/LICENSE' 2023-04-28 05:57:50,570 wheel INFO adding 'ansible_collections/community/vmware/MANIFEST.json' 2023-04-28 05:57:50,570 wheel INFO adding 'ansible_collections/community/vmware/README.md' 2023-04-28 05:57:50,570 wheel INFO adding 'ansible_collections/community/vmware/requirements.txt' 2023-04-28 05:57:50,571 wheel INFO adding 'ansible_collections/community/vmware/test-requirements.txt' 2023-04-28 05:57:50,571 wheel INFO adding 'ansible_collections/community/vmware/testing.md' 2023-04-28 05:57:50,571 wheel INFO adding 'ansible_collections/community/vmware/tox.ini' 2023-04-28 05:57:50,571 wheel INFO adding 'ansible_collections/community/vmware/LICENSES/BSD-2-Clause.txt' 2023-04-28 05:57:50,572 wheel INFO adding 'ansible_collections/community/vmware/LICENSES/GPL-3.0-or-later.txt' 2023-04-28 05:57:50,572 wheel INFO adding 'ansible_collections/community/vmware/changelogs/changelog.yaml' 2023-04-28 05:57:50,573 wheel INFO adding 'ansible_collections/community/vmware/changelogs/config.yaml' 2023-04-28 05:57:50,573 wheel INFO adding 'ansible_collections/community/vmware/meta/runtime.yml' 2023-04-28 05:57:50,574 wheel INFO adding 'ansible_collections/community/vmware/plugins/connection/__init__.py' 2023-04-28 05:57:50,574 wheel INFO adding 'ansible_collections/community/vmware/plugins/connection/vmware_tools.py' 2023-04-28 05:57:50,574 wheel INFO adding 'ansible_collections/community/vmware/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,574 wheel INFO adding 'ansible_collections/community/vmware/plugins/doc_fragments/vmware.py' 2023-04-28 05:57:50,575 wheel INFO adding 'ansible_collections/community/vmware/plugins/doc_fragments/vmware_rest_client.py' 2023-04-28 05:57:50,575 wheel INFO adding 'ansible_collections/community/vmware/plugins/httpapi/__init__.py' 2023-04-28 05:57:50,575 wheel INFO adding 'ansible_collections/community/vmware/plugins/httpapi/vmware.py' 2023-04-28 05:57:50,575 wheel INFO adding 'ansible_collections/community/vmware/plugins/inventory/__init__.py' 2023-04-28 05:57:50,576 wheel INFO adding 'ansible_collections/community/vmware/plugins/inventory/vmware_host_inventory.py' 2023-04-28 05:57:50,576 wheel INFO adding 'ansible_collections/community/vmware/plugins/inventory/vmware_vm_inventory.py' 2023-04-28 05:57:50,576 wheel INFO adding 'ansible_collections/community/vmware/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,577 wheel INFO adding 'ansible_collections/community/vmware/plugins/module_utils/version.py' 2023-04-28 05:57:50,577 wheel INFO adding 'ansible_collections/community/vmware/plugins/module_utils/vm_device_helper.py' 2023-04-28 05:57:50,577 wheel INFO adding 'ansible_collections/community/vmware/plugins/module_utils/vmware.py' 2023-04-28 05:57:50,578 wheel INFO adding 'ansible_collections/community/vmware/plugins/module_utils/vmware_rest_client.py' 2023-04-28 05:57:50,578 wheel INFO adding 'ansible_collections/community/vmware/plugins/module_utils/vmware_spbm.py' 2023-04-28 05:57:50,579 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/__init__.py' 2023-04-28 05:57:50,579 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vcenter_domain_user_group_info.py' 2023-04-28 05:57:50,579 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vcenter_extension.py' 2023-04-28 05:57:50,579 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vcenter_extension_info.py' 2023-04-28 05:57:50,580 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vcenter_folder.py' 2023-04-28 05:57:50,580 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vcenter_license.py' 2023-04-28 05:57:50,580 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vcenter_standard_key_provider.py' 2023-04-28 05:57:50,581 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_about_info.py' 2023-04-28 05:57:50,581 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_category.py' 2023-04-28 05:57:50,581 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_category_info.py' 2023-04-28 05:57:50,582 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cfg_backup.py' 2023-04-28 05:57:50,582 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cluster.py' 2023-04-28 05:57:50,582 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cluster_dpm.py' 2023-04-28 05:57:50,582 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cluster_drs.py' 2023-04-28 05:57:50,583 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cluster_ha.py' 2023-04-28 05:57:50,583 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cluster_info.py' 2023-04-28 05:57:50,583 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cluster_vcls.py' 2023-04-28 05:57:50,583 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_cluster_vsan.py' 2023-04-28 05:57:50,584 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_content_deploy_ovf_template.py' 2023-04-28 05:57:50,584 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_content_deploy_template.py' 2023-04-28 05:57:50,584 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_content_library_info.py' 2023-04-28 05:57:50,585 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_content_library_manager.py' 2023-04-28 05:57:50,585 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_custom_attribute.py' 2023-04-28 05:57:50,585 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_custom_attribute_manager.py' 2023-04-28 05:57:50,585 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_datacenter.py' 2023-04-28 05:57:50,586 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_datacenter_info.py' 2023-04-28 05:57:50,586 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_datastore.py' 2023-04-28 05:57:50,586 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_datastore_cluster.py' 2023-04-28 05:57:50,586 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_datastore_cluster_manager.py' 2023-04-28 05:57:50,587 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_datastore_info.py' 2023-04-28 05:57:50,587 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_datastore_maintenancemode.py' 2023-04-28 05:57:50,587 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_deploy_ovf.py' 2023-04-28 05:57:50,588 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_drs_group.py' 2023-04-28 05:57:50,588 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_drs_group_info.py' 2023-04-28 05:57:50,588 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_drs_group_manager.py' 2023-04-28 05:57:50,589 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_drs_rule_info.py' 2023-04-28 05:57:50,589 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvs_host.py' 2023-04-28 05:57:50,589 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup.py' 2023-04-28 05:57:50,590 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup_find.py' 2023-04-28 05:57:50,590 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvs_portgroup_info.py' 2023-04-28 05:57:50,590 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvswitch.py' 2023-04-28 05:57:50,591 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_info.py' 2023-04-28 05:57:50,591 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_lacp.py' 2023-04-28 05:57:50,592 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_nioc.py' 2023-04-28 05:57:50,592 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_pvlans.py' 2023-04-28 05:57:50,592 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_dvswitch_uplink_pg.py' 2023-04-28 05:57:50,593 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_evc_mode.py' 2023-04-28 05:57:50,593 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_export_ovf.py' 2023-04-28 05:57:50,593 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_first_class_disk.py' 2023-04-28 05:57:50,593 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_folder_info.py' 2023-04-28 05:57:50,594 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest.py' 2023-04-28 05:57:50,595 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_boot_info.py' 2023-04-28 05:57:50,595 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_boot_manager.py' 2023-04-28 05:57:50,596 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_controller.py' 2023-04-28 05:57:50,596 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_cross_vc_clone.py' 2023-04-28 05:57:50,596 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_custom_attribute_defs.py' 2023-04-28 05:57:50,597 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_custom_attributes.py' 2023-04-28 05:57:50,597 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_customization_info.py' 2023-04-28 05:57:50,597 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_disk.py' 2023-04-28 05:57:50,598 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_disk_info.py' 2023-04-28 05:57:50,598 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_file_operation.py' 2023-04-28 05:57:50,598 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_find.py' 2023-04-28 05:57:50,599 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_info.py' 2023-04-28 05:57:50,599 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_instant_clone.py' 2023-04-28 05:57:50,599 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_move.py' 2023-04-28 05:57:50,600 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_network.py' 2023-04-28 05:57:50,600 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_powerstate.py' 2023-04-28 05:57:50,600 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_register_operation.py' 2023-04-28 05:57:50,600 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_screenshot.py' 2023-04-28 05:57:50,601 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_sendkey.py' 2023-04-28 05:57:50,601 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_serial_port.py' 2023-04-28 05:57:50,601 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_snapshot.py' 2023-04-28 05:57:50,602 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_snapshot_info.py' 2023-04-28 05:57:50,602 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_storage_policy.py' 2023-04-28 05:57:50,602 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_info.py' 2023-04-28 05:57:50,603 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_upgrade.py' 2023-04-28 05:57:50,603 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_tools_wait.py' 2023-04-28 05:57:50,603 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_tpm.py' 2023-04-28 05:57:50,603 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_vgpu.py' 2023-04-28 05:57:50,604 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_vgpu_info.py' 2023-04-28 05:57:50,604 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_guest_video.py' 2023-04-28 05:57:50,604 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host.py' 2023-04-28 05:57:50,605 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_acceptance.py' 2023-04-28 05:57:50,605 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_active_directory.py' 2023-04-28 05:57:50,605 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_auto_start.py' 2023-04-28 05:57:50,606 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_capability_info.py' 2023-04-28 05:57:50,606 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_config_info.py' 2023-04-28 05:57:50,606 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_config_manager.py' 2023-04-28 05:57:50,606 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_custom_attributes.py' 2023-04-28 05:57:50,607 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_datastore.py' 2023-04-28 05:57:50,607 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_disk_info.py' 2023-04-28 05:57:50,607 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_dns.py' 2023-04-28 05:57:50,607 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_dns_info.py' 2023-04-28 05:57:50,608 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_facts.py' 2023-04-28 05:57:50,608 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_feature_info.py' 2023-04-28 05:57:50,608 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_firewall_info.py' 2023-04-28 05:57:50,608 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_firewall_manager.py' 2023-04-28 05:57:50,609 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_hyperthreading.py' 2023-04-28 05:57:50,609 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_ipv6.py' 2023-04-28 05:57:50,609 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_iscsi.py' 2023-04-28 05:57:50,610 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_iscsi_info.py' 2023-04-28 05:57:50,610 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_kernel_manager.py' 2023-04-28 05:57:50,610 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_lockdown.py' 2023-04-28 05:57:50,611 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_lockdown_exceptions.py' 2023-04-28 05:57:50,611 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_logbundle.py' 2023-04-28 05:57:50,611 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_logbundle_info.py' 2023-04-28 05:57:50,611 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_ntp.py' 2023-04-28 05:57:50,612 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_ntp_info.py' 2023-04-28 05:57:50,612 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_package_info.py' 2023-04-28 05:57:50,612 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_passthrough.py' 2023-04-28 05:57:50,612 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_powermgmt_policy.py' 2023-04-28 05:57:50,613 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_powerstate.py' 2023-04-28 05:57:50,613 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_scanhba.py' 2023-04-28 05:57:50,613 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_scsidisk_info.py' 2023-04-28 05:57:50,613 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_service_info.py' 2023-04-28 05:57:50,614 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_service_manager.py' 2023-04-28 05:57:50,614 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_snmp.py' 2023-04-28 05:57:50,614 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_sriov.py' 2023-04-28 05:57:50,615 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_ssl_info.py' 2023-04-28 05:57:50,615 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_tcpip_stacks.py' 2023-04-28 05:57:50,615 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_user_manager.py' 2023-04-28 05:57:50,615 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_vmhba_info.py' 2023-04-28 05:57:50,616 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_host_vmnic_info.py' 2023-04-28 05:57:50,616 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_local_role_info.py' 2023-04-28 05:57:50,616 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_local_role_manager.py' 2023-04-28 05:57:50,617 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_local_user_info.py' 2023-04-28 05:57:50,617 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_local_user_manager.py' 2023-04-28 05:57:50,617 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_maintenancemode.py' 2023-04-28 05:57:50,617 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_migrate_vmk.py' 2023-04-28 05:57:50,618 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_object_custom_attributes_info.py' 2023-04-28 05:57:50,618 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_object_rename.py' 2023-04-28 05:57:50,618 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_object_role_permission.py' 2023-04-28 05:57:50,618 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_object_role_permission_info.py' 2023-04-28 05:57:50,619 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_portgroup.py' 2023-04-28 05:57:50,619 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_portgroup_info.py' 2023-04-28 05:57:50,619 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_recommended_datastore.py' 2023-04-28 05:57:50,620 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_resource_pool.py' 2023-04-28 05:57:50,620 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_resource_pool_info.py' 2023-04-28 05:57:50,620 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_tag.py' 2023-04-28 05:57:50,621 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_tag_info.py' 2023-04-28 05:57:50,621 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_tag_manager.py' 2023-04-28 05:57:50,621 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_target_canonical_info.py' 2023-04-28 05:57:50,621 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vc_infraprofile_info.py' 2023-04-28 05:57:50,622 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vcenter_settings.py' 2023-04-28 05:57:50,622 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vcenter_settings_info.py' 2023-04-28 05:57:50,622 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vcenter_statistics.py' 2023-04-28 05:57:50,623 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_config_option.py' 2023-04-28 05:57:50,623 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_host_drs_rule.py' 2023-04-28 05:57:50,623 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_info.py' 2023-04-28 05:57:50,624 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_shell.py' 2023-04-28 05:57:50,624 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_storage_policy.py' 2023-04-28 05:57:50,624 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_storage_policy_info.py' 2023-04-28 05:57:50,625 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_vm_drs_rule.py' 2023-04-28 05:57:50,625 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vm_vss_dvs_migrate.py' 2023-04-28 05:57:50,625 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vmkernel.py' 2023-04-28 05:57:50,626 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vmkernel_info.py' 2023-04-28 05:57:50,626 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vmotion.py' 2023-04-28 05:57:50,626 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vsan_cluster.py' 2023-04-28 05:57:50,627 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vsan_hcl_db.py' 2023-04-28 05:57:50,627 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vsan_health_info.py' 2023-04-28 05:57:50,627 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vspan_session.py' 2023-04-28 05:57:50,627 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vswitch.py' 2023-04-28 05:57:50,628 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vmware_vswitch_info.py' 2023-04-28 05:57:50,628 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vsphere_copy.py' 2023-04-28 05:57:50,628 wheel INFO adding 'ansible_collections/community/vmware/plugins/modules/vsphere_file.py' 2023-04-28 05:57:50,629 wheel INFO adding 'ansible_collections/community/vmware/plugins/plugin_utils/inventory.py' 2023-04-28 05:57:50,629 wheel INFO adding 'ansible_collections/community/vmware/scripts/inventory/__init__.py' 2023-04-28 05:57:50,630 wheel INFO adding 'ansible_collections/community/vmware/scripts/inventory/vmware.ini' 2023-04-28 05:57:50,630 wheel INFO adding 'ansible_collections/community/vmware/scripts/inventory/vmware.py' 2023-04-28 05:57:50,630 wheel INFO adding 'ansible_collections/community/vmware/scripts/inventory/vmware_inventory.ini' 2023-04-28 05:57:50,631 wheel INFO adding 'ansible_collections/community/vmware/scripts/inventory/vmware_inventory.py' 2023-04-28 05:57:50,631 wheel INFO adding 'ansible_collections/community/vmware/tools/check-ignores-order' 2023-04-28 05:57:50,631 wheel INFO adding 'ansible_collections/community/vmware/tools/create_documentation_tasks.yml' 2023-04-28 05:57:50,631 wheel INFO adding 'ansible_collections/community/vmware/tools/prepare_release.yml' 2023-04-28 05:57:50,632 wheel INFO adding 'ansible_collections/community/vmware/tools/unset_version.yml' 2023-04-28 05:57:50,632 wheel INFO adding 'ansible_collections/community/vmware/tools/update_documentation.yml' 2023-04-28 05:57:50,632 wheel INFO adding 'ansible_collections/community/windows/CHANGELOG.rst' 2023-04-28 05:57:50,632 wheel INFO adding 'ansible_collections/community/windows/COPYING' 2023-04-28 05:57:50,633 wheel INFO adding 'ansible_collections/community/windows/FILES.json' 2023-04-28 05:57:50,634 wheel INFO adding 'ansible_collections/community/windows/MANIFEST.json' 2023-04-28 05:57:50,634 wheel INFO adding 'ansible_collections/community/windows/README.md' 2023-04-28 05:57:50,635 wheel INFO adding 'ansible_collections/community/windows/changelogs/changelog.yaml' 2023-04-28 05:57:50,635 wheel INFO adding 'ansible_collections/community/windows/changelogs/config.yaml' 2023-04-28 05:57:50,635 wheel INFO adding 'ansible_collections/community/windows/changelogs/fragments/.keep' 2023-04-28 05:57:50,636 wheel INFO adding 'ansible_collections/community/windows/meta/runtime.yml' 2023-04-28 05:57:50,636 wheel INFO adding 'ansible_collections/community/windows/plugins/action/win_pssession_configuration.py' 2023-04-28 05:57:50,636 wheel INFO adding 'ansible_collections/community/windows/plugins/lookup/__init__.py' 2023-04-28 05:57:50,636 wheel INFO adding 'ansible_collections/community/windows/plugins/lookup/laps_password.py' 2023-04-28 05:57:50,637 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/__init__.py' 2023-04-28 05:57:50,637 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/psexec.py' 2023-04-28 05:57:50,637 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_audit_policy_system.ps1' 2023-04-28 05:57:50,638 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_audit_policy_system.py' 2023-04-28 05:57:50,638 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_audit_rule.ps1' 2023-04-28 05:57:50,638 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_audit_rule.py' 2023-04-28 05:57:50,638 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_auto_logon.ps1' 2023-04-28 05:57:50,639 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_auto_logon.py' 2023-04-28 05:57:50,639 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_certificate_info.ps1' 2023-04-28 05:57:50,639 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_certificate_info.py' 2023-04-28 05:57:50,639 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_computer_description.ps1' 2023-04-28 05:57:50,640 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_computer_description.py' 2023-04-28 05:57:50,640 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_credential.ps1' 2023-04-28 05:57:50,640 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_credential.py' 2023-04-28 05:57:50,641 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_data_deduplication.ps1' 2023-04-28 05:57:50,641 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_data_deduplication.py' 2023-04-28 05:57:50,641 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_defrag.ps1' 2023-04-28 05:57:50,641 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_defrag.py' 2023-04-28 05:57:50,641 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dhcp_lease.ps1' 2023-04-28 05:57:50,642 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dhcp_lease.py' 2023-04-28 05:57:50,642 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_disk_facts.ps1' 2023-04-28 05:57:50,642 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_disk_facts.py' 2023-04-28 05:57:50,643 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_disk_image.ps1' 2023-04-28 05:57:50,643 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_disk_image.py' 2023-04-28 05:57:50,643 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dns_record.ps1' 2023-04-28 05:57:50,644 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dns_record.py' 2023-04-28 05:57:50,644 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dns_zone.ps1' 2023-04-28 05:57:50,644 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dns_zone.py' 2023-04-28 05:57:50,644 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_computer.ps1' 2023-04-28 05:57:50,645 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_computer.py' 2023-04-28 05:57:50,645 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_group.ps1' 2023-04-28 05:57:50,645 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_group.py' 2023-04-28 05:57:50,645 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_group_membership.ps1' 2023-04-28 05:57:50,646 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_group_membership.py' 2023-04-28 05:57:50,646 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_object_info.ps1' 2023-04-28 05:57:50,646 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_object_info.py' 2023-04-28 05:57:50,646 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_ou.ps1' 2023-04-28 05:57:50,647 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_ou.py' 2023-04-28 05:57:50,647 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_user.ps1' 2023-04-28 05:57:50,647 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_domain_user.py' 2023-04-28 05:57:50,648 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dotnet_ngen.ps1' 2023-04-28 05:57:50,648 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_dotnet_ngen.py' 2023-04-28 05:57:50,648 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_eventlog.ps1' 2023-04-28 05:57:50,648 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_eventlog.py' 2023-04-28 05:57:50,648 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_eventlog_entry.ps1' 2023-04-28 05:57:50,649 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_eventlog_entry.py' 2023-04-28 05:57:50,649 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_feature_info.ps1' 2023-04-28 05:57:50,649 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_feature_info.py' 2023-04-28 05:57:50,649 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_file_compression.ps1' 2023-04-28 05:57:50,650 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_file_compression.py' 2023-04-28 05:57:50,650 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_file_version.ps1' 2023-04-28 05:57:50,650 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_file_version.py' 2023-04-28 05:57:50,650 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_firewall.ps1' 2023-04-28 05:57:50,651 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_firewall.py' 2023-04-28 05:57:50,651 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_firewall_rule.ps1' 2023-04-28 05:57:50,651 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_firewall_rule.py' 2023-04-28 05:57:50,651 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_format.ps1' 2023-04-28 05:57:50,652 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_format.py' 2023-04-28 05:57:50,652 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_hosts.ps1' 2023-04-28 05:57:50,652 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_hosts.py' 2023-04-28 05:57:50,652 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_hotfix.ps1' 2023-04-28 05:57:50,653 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_hotfix.py' 2023-04-28 05:57:50,653 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_http_proxy.ps1' 2023-04-28 05:57:50,653 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_http_proxy.py' 2023-04-28 05:57:50,653 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_virtualdirectory.ps1' 2023-04-28 05:57:50,654 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_virtualdirectory.py' 2023-04-28 05:57:50,654 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_webapplication.ps1' 2023-04-28 05:57:50,654 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_webapplication.py' 2023-04-28 05:57:50,654 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_webapppool.ps1' 2023-04-28 05:57:50,654 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_webapppool.py' 2023-04-28 05:57:50,655 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_webbinding.ps1' 2023-04-28 05:57:50,655 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_webbinding.py' 2023-04-28 05:57:50,655 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_website.ps1' 2023-04-28 05:57:50,656 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_iis_website.py' 2023-04-28 05:57:50,656 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_inet_proxy.ps1' 2023-04-28 05:57:50,656 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_inet_proxy.py' 2023-04-28 05:57:50,656 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_initialize_disk.ps1' 2023-04-28 05:57:50,657 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_initialize_disk.py' 2023-04-28 05:57:50,657 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_lineinfile.ps1' 2023-04-28 05:57:50,657 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_lineinfile.py' 2023-04-28 05:57:50,657 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_listen_ports_facts.ps1' 2023-04-28 05:57:50,658 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_listen_ports_facts.py' 2023-04-28 05:57:50,658 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_mapped_drive.ps1' 2023-04-28 05:57:50,658 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_mapped_drive.py' 2023-04-28 05:57:50,658 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_msg.ps1' 2023-04-28 05:57:50,659 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_msg.py' 2023-04-28 05:57:50,659 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_net_adapter_feature.ps1' 2023-04-28 05:57:50,659 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_net_adapter_feature.py' 2023-04-28 05:57:50,659 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_netbios.ps1' 2023-04-28 05:57:50,660 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_netbios.py' 2023-04-28 05:57:50,660 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_nssm.ps1' 2023-04-28 05:57:50,660 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_nssm.py' 2023-04-28 05:57:50,660 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_pagefile.ps1' 2023-04-28 05:57:50,661 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_pagefile.py' 2023-04-28 05:57:50,661 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_partition.ps1' 2023-04-28 05:57:50,661 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_partition.py' 2023-04-28 05:57:50,661 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_pester.ps1' 2023-04-28 05:57:50,662 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_pester.py' 2023-04-28 05:57:50,662 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_power_plan.ps1' 2023-04-28 05:57:50,662 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_power_plan.py' 2023-04-28 05:57:50,662 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_product_facts.ps1' 2023-04-28 05:57:50,663 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_product_facts.py' 2023-04-28 05:57:50,663 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psexec.ps1' 2023-04-28 05:57:50,663 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psexec.py' 2023-04-28 05:57:50,663 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psmodule.ps1' 2023-04-28 05:57:50,664 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psmodule.py' 2023-04-28 05:57:50,664 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psmodule_info.ps1' 2023-04-28 05:57:50,664 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psmodule_info.py' 2023-04-28 05:57:50,664 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psrepository.ps1' 2023-04-28 05:57:50,665 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psrepository.py' 2023-04-28 05:57:50,665 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psrepository_copy.ps1' 2023-04-28 05:57:50,665 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psrepository_copy.py' 2023-04-28 05:57:50,665 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psrepository_info.ps1' 2023-04-28 05:57:50,666 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psrepository_info.py' 2023-04-28 05:57:50,666 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psscript.ps1' 2023-04-28 05:57:50,666 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psscript.py' 2023-04-28 05:57:50,666 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psscript_info.ps1' 2023-04-28 05:57:50,667 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_psscript_info.py' 2023-04-28 05:57:50,667 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_pssession_configuration.ps1' 2023-04-28 05:57:50,667 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_pssession_configuration.py' 2023-04-28 05:57:50,667 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rabbitmq_plugin.ps1' 2023-04-28 05:57:50,668 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rabbitmq_plugin.py' 2023-04-28 05:57:50,668 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rds_cap.ps1' 2023-04-28 05:57:50,668 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rds_cap.py' 2023-04-28 05:57:50,668 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rds_rap.ps1' 2023-04-28 05:57:50,669 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rds_rap.py' 2023-04-28 05:57:50,669 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rds_settings.ps1' 2023-04-28 05:57:50,669 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_rds_settings.py' 2023-04-28 05:57:50,669 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_region.ps1' 2023-04-28 05:57:50,670 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_region.py' 2023-04-28 05:57:50,670 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_regmerge.ps1' 2023-04-28 05:57:50,670 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_regmerge.py' 2023-04-28 05:57:50,670 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_robocopy.ps1' 2023-04-28 05:57:50,671 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_robocopy.py' 2023-04-28 05:57:50,671 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_route.ps1' 2023-04-28 05:57:50,671 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_route.py' 2023-04-28 05:57:50,671 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_say.ps1' 2023-04-28 05:57:50,672 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_say.py' 2023-04-28 05:57:50,672 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scheduled_task.ps1' 2023-04-28 05:57:50,672 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scheduled_task.py' 2023-04-28 05:57:50,673 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scheduled_task_stat.ps1' 2023-04-28 05:57:50,673 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scheduled_task_stat.py' 2023-04-28 05:57:50,673 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scoop.ps1' 2023-04-28 05:57:50,674 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scoop.py' 2023-04-28 05:57:50,674 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scoop_bucket.ps1' 2023-04-28 05:57:50,674 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_scoop_bucket.py' 2023-04-28 05:57:50,674 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_security_policy.ps1' 2023-04-28 05:57:50,674 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_security_policy.py' 2023-04-28 05:57:50,675 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_shortcut.ps1' 2023-04-28 05:57:50,675 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_shortcut.py' 2023-04-28 05:57:50,675 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_snmp.ps1' 2023-04-28 05:57:50,675 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_snmp.py' 2023-04-28 05:57:50,676 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_timezone.ps1' 2023-04-28 05:57:50,676 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_timezone.py' 2023-04-28 05:57:50,676 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_toast.ps1' 2023-04-28 05:57:50,676 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_toast.py' 2023-04-28 05:57:50,677 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_unzip.ps1' 2023-04-28 05:57:50,677 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_unzip.py' 2023-04-28 05:57:50,677 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_user_profile.ps1' 2023-04-28 05:57:50,677 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_user_profile.py' 2023-04-28 05:57:50,678 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_wait_for_process.ps1' 2023-04-28 05:57:50,678 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_wait_for_process.py' 2023-04-28 05:57:50,678 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_wakeonlan.ps1' 2023-04-28 05:57:50,678 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_wakeonlan.py' 2023-04-28 05:57:50,678 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_webpicmd.ps1' 2023-04-28 05:57:50,679 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_webpicmd.py' 2023-04-28 05:57:50,679 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_xml.ps1' 2023-04-28 05:57:50,679 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_xml.py' 2023-04-28 05:57:50,679 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_zip.ps1' 2023-04-28 05:57:50,680 wheel INFO adding 'ansible_collections/community/windows/plugins/modules/win_zip.py' 2023-04-28 05:57:50,680 wheel INFO adding 'ansible_collections/community/zabbix/CHANGELOG.rst' 2023-04-28 05:57:50,680 wheel INFO adding 'ansible_collections/community/zabbix/CODE_OF_CONDUCT.md' 2023-04-28 05:57:50,681 wheel INFO adding 'ansible_collections/community/zabbix/CONTRIBUTING.md' 2023-04-28 05:57:50,681 wheel INFO adding 'ansible_collections/community/zabbix/FILES.json' 2023-04-28 05:57:50,682 wheel INFO adding 'ansible_collections/community/zabbix/LICENSE' 2023-04-28 05:57:50,682 wheel INFO adding 'ansible_collections/community/zabbix/MAINTAINERS' 2023-04-28 05:57:50,682 wheel INFO adding 'ansible_collections/community/zabbix/MANIFEST.json' 2023-04-28 05:57:50,683 wheel INFO adding 'ansible_collections/community/zabbix/PSF-license.txt' 2023-04-28 05:57:50,683 wheel INFO adding 'ansible_collections/community/zabbix/README.md' 2023-04-28 05:57:50,683 wheel INFO adding 'ansible_collections/community/zabbix/docker-compose.yml' 2023-04-28 05:57:50,683 wheel INFO adding 'ansible_collections/community/zabbix/requirements.txt' 2023-04-28 05:57:50,684 wheel INFO adding 'ansible_collections/community/zabbix/tox.ini' 2023-04-28 05:57:50,684 wheel INFO adding 'ansible_collections/community/zabbix/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:50,684 wheel INFO adding 'ansible_collections/community/zabbix/changelogs/changelog.yaml' 2023-04-28 05:57:50,685 wheel INFO adding 'ansible_collections/community/zabbix/changelogs/config.yaml' 2023-04-28 05:57:50,685 wheel INFO adding 'ansible_collections/community/zabbix/changelogs/roles_zabbix64.yml' 2023-04-28 05:57:50,685 wheel INFO adding 'ansible_collections/community/zabbix/changelogs/fragments/.gitkeep' 2023-04-28 05:57:50,685 wheel INFO adding 'ansible_collections/community/zabbix/meta/runtime.yml' 2023-04-28 05:57:50,686 wheel INFO adding 'ansible_collections/community/zabbix/molecule/requirements.txt' 2023-04-28 05:57:50,686 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/molecule.yml' 2023-04-28 05:57:50,686 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks/converge.yml' 2023-04-28 05:57:50,686 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/playbooks/prepare.yml' 2023-04-28 05:57:50,687 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/test_docker.py' 2023-04-28 05:57:50,687 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common/test_agent2.py' 2023-04-28 05:57:50,687 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk/test_auto_psk.py' 2023-04-28 05:57:50,687 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common/test_agent.py' 2023-04-28 05:57:50,688 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk/test_no_auto_psk.py' 2023-04-28 05:57:50,688 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/molecule.yml' 2023-04-28 05:57:50,688 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/conftest.py' 2023-04-28 05:57:50,688 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common/test_agent2.py' 2023-04-28 05:57:50,689 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common/test_agent.py' 2023-04-28 05:57:50,689 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk/test_no_auto_psk.py' 2023-04-28 05:57:50,689 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/molecule.yml' 2023-04-28 05:57:50,689 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/conftest.py' 2023-04-28 05:57:50,690 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common/test_agent2.py' 2023-04-28 05:57:50,690 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk/test_auto_psk.py' 2023-04-28 05:57:50,690 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common/test_agent.py' 2023-04-28 05:57:50,690 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/molecule.yml' 2023-04-28 05:57:50,691 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/conftest.py' 2023-04-28 05:57:50,691 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk/test_auto_psk.py' 2023-04-28 05:57:50,691 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common/test_agent.py' 2023-04-28 05:57:50,691 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/molecule.yml' 2023-04-28 05:57:50,692 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/conftest.py' 2023-04-28 05:57:50,692 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common/test_agent.py' 2023-04-28 05:57:50,692 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk/test_no_auto_psk.py' 2023-04-28 05:57:50,692 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_javagateway/converge.yml' 2023-04-28 05:57:50,693 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_javagateway/molecule.yml' 2023-04-28 05:57:50,693 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_javagateway/prepare.yml' 2023-04-28 05:57:50,693 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests/test_default.py' 2023-04-28 05:57:50,693 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_proxy/converge.yml' 2023-04-28 05:57:50,693 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_proxy/destroy.yml' 2023-04-28 05:57:50,694 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_proxy/molecule.yml' 2023-04-28 05:57:50,694 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_proxy/prepare.yml' 2023-04-28 05:57:50,694 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_proxy/tests/test_default.py' 2023-04-28 05:57:50,694 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_server/converge.yml' 2023-04-28 05:57:50,695 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_server/destroy.yml' 2023-04-28 05:57:50,695 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_server/molecule.yml' 2023-04-28 05:57:50,695 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_server/prepare.yml' 2023-04-28 05:57:50,695 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_server/tests/test_default.py' 2023-04-28 05:57:50,696 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_web/converge.yml' 2023-04-28 05:57:50,696 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_web/destroy.yml' 2023-04-28 05:57:50,696 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_web/molecule.yml' 2023-04-28 05:57:50,696 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_web/prepare.yml' 2023-04-28 05:57:50,696 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_web/requirements.yml' 2023-04-28 05:57:50,697 wheel INFO adding 'ansible_collections/community/zabbix/molecule/zabbix_web/tests/test_default.py' 2023-04-28 05:57:50,697 wheel INFO adding 'ansible_collections/community/zabbix/plugins/doc_fragments/connection_persistent.py' 2023-04-28 05:57:50,697 wheel INFO adding 'ansible_collections/community/zabbix/plugins/doc_fragments/zabbix.py' 2023-04-28 05:57:50,698 wheel INFO adding 'ansible_collections/community/zabbix/plugins/httpapi/zabbix.py' 2023-04-28 05:57:50,698 wheel INFO adding 'ansible_collections/community/zabbix/plugins/inventory/zabbix_inventory.py' 2023-04-28 05:57:50,698 wheel INFO adding 'ansible_collections/community/zabbix/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,698 wheel INFO adding 'ansible_collections/community/zabbix/plugins/module_utils/_version.py' 2023-04-28 05:57:50,699 wheel INFO adding 'ansible_collections/community/zabbix/plugins/module_utils/api_request.py' 2023-04-28 05:57:50,699 wheel INFO adding 'ansible_collections/community/zabbix/plugins/module_utils/base.py' 2023-04-28 05:57:50,699 wheel INFO adding 'ansible_collections/community/zabbix/plugins/module_utils/helpers.py' 2023-04-28 05:57:50,699 wheel INFO adding 'ansible_collections/community/zabbix/plugins/module_utils/wrappers.py' 2023-04-28 05:57:50,700 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/__init__.py' 2023-04-28 05:57:50,700 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_action.py' 2023-04-28 05:57:50,701 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_authentication.py' 2023-04-28 05:57:50,701 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_autoregister.py' 2023-04-28 05:57:50,701 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_discovery_rule.py' 2023-04-28 05:57:50,702 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_globalmacro.py' 2023-04-28 05:57:50,702 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_group.py' 2023-04-28 05:57:50,702 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_group_facts.py' 2023-04-28 05:57:50,703 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_group_info.py' 2023-04-28 05:57:50,703 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_host.py' 2023-04-28 05:57:50,703 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_host_events_info.py' 2023-04-28 05:57:50,704 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_host_facts.py' 2023-04-28 05:57:50,704 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_host_info.py' 2023-04-28 05:57:50,704 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_hostmacro.py' 2023-04-28 05:57:50,704 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_housekeeping.py' 2023-04-28 05:57:50,705 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_maintenance.py' 2023-04-28 05:57:50,705 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_map.py' 2023-04-28 05:57:50,706 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_mediatype.py' 2023-04-28 05:57:50,706 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_proxy.py' 2023-04-28 05:57:50,706 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_proxy_info.py' 2023-04-28 05:57:50,707 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_screen.py' 2023-04-28 05:57:50,707 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_script.py' 2023-04-28 05:57:50,707 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_service.py' 2023-04-28 05:57:50,708 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_template.py' 2023-04-28 05:57:50,708 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_template_info.py' 2023-04-28 05:57:50,708 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_user.py' 2023-04-28 05:57:50,709 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_user_directory.py' 2023-04-28 05:57:50,709 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_user_info.py' 2023-04-28 05:57:50,709 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_user_role.py' 2023-04-28 05:57:50,710 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_usergroup.py' 2023-04-28 05:57:50,710 wheel INFO adding 'ansible_collections/community/zabbix/plugins/modules/zabbix_valuemap.py' 2023-04-28 05:57:50,711 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/README.md' 2023-04-28 05:57:50,711 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/defaults/main.yml' 2023-04-28 05:57:50,711 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/files/sample.conf' 2023-04-28 05:57:50,712 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/files/win_sample/doSomething.ps1' 2023-04-28 05:57:50,712 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/handlers/main.yml' 2023-04-28 05:57:50,712 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/meta/main.yml' 2023-04-28 05:57:50,712 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/Dockerfile.j2' 2023-04-28 05:57:50,713 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/INSTALL.rst' 2023-04-28 05:57:50,713 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/molecule.yml' 2023-04-28 05:57:50,713 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/playbook.yml' 2023-04-28 05:57:50,713 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/prepare.yml' 2023-04-28 05:57:50,713 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/requirements.yml' 2023-04-28 05:57:50,714 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/test_agent.py' 2023-04-28 05:57:50,714 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/test_default.py' 2023-04-28 05:57:50,714 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Darwin.yml' 2023-04-28 05:57:50,714 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Debian.yml' 2023-04-28 05:57:50,715 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Docker.yml' 2023-04-28 05:57:50,715 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Linux.yml' 2023-04-28 05:57:50,715 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/RedHat.yml' 2023-04-28 05:57:50,715 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Suse.yml' 2023-04-28 05:57:50,716 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Windows.yml' 2023-04-28 05:57:50,716 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/Windows_conf.yml' 2023-04-28 05:57:50,716 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/api.yml' 2023-04-28 05:57:50,716 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/firewall.yml' 2023-04-28 05:57:50,717 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/macOS.yml' 2023-04-28 05:57:50,717 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/main.yml' 2023-04-28 05:57:50,717 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/remove.yml' 2023-04-28 05:57:50,717 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/selinux.yml' 2023-04-28 05:57:50,717 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto.yml' 2023-04-28 05:57:50,718 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2.yml' 2023-04-28 05:57:50,718 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_common.yml' 2023-04-28 05:57:50,718 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_linux.yml' 2023-04-28 05:57:50,718 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_agent2_windows.yml' 2023-04-28 05:57:50,719 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_common.yml' 2023-04-28 05:57:50,719 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_linux.yml' 2023-04-28 05:57:50,719 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/tlspsk_auto_windows.yml' 2023-04-28 05:57:50,719 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/tasks/userparameter.yml' 2023-04-28 05:57:50,719 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/templates/zabbix_agent2.conf.j2' 2023-04-28 05:57:50,720 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/templates/zabbix_agentd.conf.j2' 2023-04-28 05:57:50,720 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters/mysql.j2' 2023-04-28 05:57:50,720 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/templates/userparameters/win_sample.j2' 2023-04-28 05:57:50,720 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/Darwin.yml' 2023-04-28 05:57:50,721 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/Debian.yml' 2023-04-28 05:57:50,721 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/RedHat.yml' 2023-04-28 05:57:50,721 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/Sangoma.yml' 2023-04-28 05:57:50,721 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/Suse.yml' 2023-04-28 05:57:50,721 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/Windows.yml' 2023-04-28 05:57:50,722 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/main.yml' 2023-04-28 05:57:50,722 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_agent/vars/zabbix.yml' 2023-04-28 05:57:50,722 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/README.md' 2023-04-28 05:57:50,723 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/defaults/main.yml' 2023-04-28 05:57:50,723 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/files/systemd.service' 2023-04-28 05:57:50,723 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/handlers/main.yml' 2023-04-28 05:57:50,723 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/meta/main.yml' 2023-04-28 05:57:50,724 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/Debian.yml' 2023-04-28 05:57:50,724 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/RedHat.yml' 2023-04-28 05:57:50,724 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/tasks/main.yml' 2023-04-28 05:57:50,724 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/templates/zabbix_java_gateway.conf.j2' 2023-04-28 05:57:50,724 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/Debian.yml' 2023-04-28 05:57:50,725 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/RedHat.yml' 2023-04-28 05:57:50,725 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/main.yml' 2023-04-28 05:57:50,725 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_javagateway/vars/zabbix.yml' 2023-04-28 05:57:50,725 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/README.md' 2023-04-28 05:57:50,726 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/requirements.yml' 2023-04-28 05:57:50,726 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/defaults/main.yml' 2023-04-28 05:57:50,726 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/files/install_semodule.bsx' 2023-04-28 05:57:50,727 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/handlers/main.yml' 2023-04-28 05:57:50,727 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/meta/main.yml' 2023-04-28 05:57:50,727 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/Debian.yml' 2023-04-28 05:57:50,727 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/RedHat.yml' 2023-04-28 05:57:50,728 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/main.yml' 2023-04-28 05:57:50,728 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/mysql.yml' 2023-04-28 05:57:50,728 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/postgresql.yml' 2023-04-28 05:57:50,728 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/selinux.yml' 2023-04-28 05:57:50,728 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/tasks/sqlite3.yml' 2023-04-28 05:57:50,729 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/templates/zabbix_proxy.conf.j2' 2023-04-28 05:57:50,729 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/vars/Amazon.yml' 2023-04-28 05:57:50,729 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/vars/Debian.yml' 2023-04-28 05:57:50,729 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/vars/RedHat.yml' 2023-04-28 05:57:50,730 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/vars/main.yml' 2023-04-28 05:57:50,730 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_proxy/vars/zabbix.yml' 2023-04-28 05:57:50,730 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/README.md' 2023-04-28 05:57:50,731 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/requirements.yml' 2023-04-28 05:57:50,731 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/defaults/main.yml' 2023-04-28 05:57:50,731 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/files/install_semodule.bsx' 2023-04-28 05:57:50,731 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/handlers/main.yml' 2023-04-28 05:57:50,732 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/meta/main.yml' 2023-04-28 05:57:50,732 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/tasks/Debian.yml' 2023-04-28 05:57:50,732 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/tasks/RedHat.yml' 2023-04-28 05:57:50,732 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/tasks/main.yml' 2023-04-28 05:57:50,733 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/tasks/mysql.yml' 2023-04-28 05:57:50,733 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/tasks/postgresql.yml' 2023-04-28 05:57:50,733 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/tasks/scripts.yml' 2023-04-28 05:57:50,733 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/tasks/selinux.yml' 2023-04-28 05:57:50,734 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/templates/zabbix_server.conf.j2' 2023-04-28 05:57:50,734 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/vars/Debian.yml' 2023-04-28 05:57:50,734 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/vars/RedHat.yml' 2023-04-28 05:57:50,734 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/vars/main.yml' 2023-04-28 05:57:50,735 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_server/vars/zabbix.yml' 2023-04-28 05:57:50,735 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/README.md' 2023-04-28 05:57:50,735 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/defaults/main.yml' 2023-04-28 05:57:50,736 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/handlers/main.yml' 2023-04-28 05:57:50,736 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/meta/main.yml' 2023-04-28 05:57:50,736 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/Debian.yml' 2023-04-28 05:57:50,736 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/RedHat.yml' 2023-04-28 05:57:50,737 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/access.yml' 2023-04-28 05:57:50,737 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache.yml' 2023-04-28 05:57:50,737 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache_Debian.yml' 2023-04-28 05:57:50,737 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/apache_RedHat.yml' 2023-04-28 05:57:50,737 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/main.yml' 2023-04-28 05:57:50,738 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/nginx.yml' 2023-04-28 05:57:50,738 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/php_Debian.yml' 2023-04-28 05:57:50,738 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/tasks/selinux.yml' 2023-04-28 05:57:50,738 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/templates/apache_vhost.conf.j2' 2023-04-28 05:57:50,739 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/templates/nginx_vhost.conf.j2' 2023-04-28 05:57:50,739 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/templates/php-fpm.conf.j2' 2023-04-28 05:57:50,739 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/templates/zabbix.conf.php.j2' 2023-04-28 05:57:50,739 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-10.yml' 2023-04-28 05:57:50,740 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-11.yml' 2023-04-28 05:57:50,740 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-8.yml' 2023-04-28 05:57:50,740 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian-9.yml' 2023-04-28 05:57:50,740 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Debian.yml' 2023-04-28 05:57:50,740 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-7.yml' 2023-04-28 05:57:50,741 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-8.yml' 2023-04-28 05:57:50,741 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat-9.yml' 2023-04-28 05:57:50,741 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/RedHat.yml' 2023-04-28 05:57:50,741 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-18.yml' 2023-04-28 05:57:50,741 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-20.yml' 2023-04-28 05:57:50,742 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/Ubuntu-22.yml' 2023-04-28 05:57:50,742 wheel INFO adding 'ansible_collections/community/zabbix/roles/zabbix_web/vars/zabbix.yml' 2023-04-28 05:57:50,742 wheel INFO adding 'ansible_collections/community/zabbix/scripts/inventory/zabbix.ini' 2023-04-28 05:57:50,742 wheel INFO adding 'ansible_collections/community/zabbix/scripts/inventory/zabbix.py' 2023-04-28 05:57:50,743 wheel INFO adding 'ansible_collections/containers/podman/CHANGELOG.rst' 2023-04-28 05:57:50,743 wheel INFO adding 'ansible_collections/containers/podman/CODE-OF-CONDUCT.md' 2023-04-28 05:57:50,743 wheel INFO adding 'ansible_collections/containers/podman/COPYING' 2023-04-28 05:57:50,744 wheel INFO adding 'ansible_collections/containers/podman/FILES.json' 2023-04-28 05:57:50,744 wheel INFO adding 'ansible_collections/containers/podman/MANIFEST.json' 2023-04-28 05:57:50,744 wheel INFO adding 'ansible_collections/containers/podman/Makefile' 2023-04-28 05:57:50,745 wheel INFO adding 'ansible_collections/containers/podman/README.md' 2023-04-28 05:57:50,745 wheel INFO adding 'ansible_collections/containers/podman/SECURITY.md' 2023-04-28 05:57:50,745 wheel INFO adding 'ansible_collections/containers/podman/ansible-collection-containers-podman.spec' 2023-04-28 05:57:50,745 wheel INFO adding 'ansible_collections/containers/podman/galaxy.yml.in' 2023-04-28 05:57:50,745 wheel INFO adding 'ansible_collections/containers/podman/setup.cfg' 2023-04-28 05:57:50,746 wheel INFO adding 'ansible_collections/containers/podman/setup.py' 2023-04-28 05:57:50,746 wheel INFO adding 'ansible_collections/containers/podman/test-requirements.txt' 2023-04-28 05:57:50,746 wheel INFO adding 'ansible_collections/containers/podman/changelogs/changelog.yaml' 2023-04-28 05:57:50,746 wheel INFO adding 'ansible_collections/containers/podman/changelogs/config.yaml' 2023-04-28 05:57:50,747 wheel INFO adding 'ansible_collections/containers/podman/meta/runtime.yml' 2023-04-28 05:57:50,747 wheel INFO adding 'ansible_collections/containers/podman/plugins/become/podman_unshare.py' 2023-04-28 05:57:50,747 wheel INFO adding 'ansible_collections/containers/podman/plugins/connection/__init__.py' 2023-04-28 05:57:50,747 wheel INFO adding 'ansible_collections/containers/podman/plugins/connection/buildah.py' 2023-04-28 05:57:50,748 wheel INFO adding 'ansible_collections/containers/podman/plugins/connection/podman.py' 2023-04-28 05:57:50,748 wheel INFO adding 'ansible_collections/containers/podman/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,748 wheel INFO adding 'ansible_collections/containers/podman/plugins/module_utils/podman/__init__.py' 2023-04-28 05:57:50,748 wheel INFO adding 'ansible_collections/containers/podman/plugins/module_utils/podman/common.py' 2023-04-28 05:57:50,749 wheel INFO adding 'ansible_collections/containers/podman/plugins/module_utils/podman/podman_container_lib.py' 2023-04-28 05:57:50,749 wheel INFO adding 'ansible_collections/containers/podman/plugins/module_utils/podman/podman_pod_lib.py' 2023-04-28 05:57:50,750 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/__init__.py' 2023-04-28 05:57:50,750 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_container.py' 2023-04-28 05:57:50,751 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_container_info.py' 2023-04-28 05:57:50,751 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_containers.py' 2023-04-28 05:57:50,751 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_export.py' 2023-04-28 05:57:50,751 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_generate_systemd.py' 2023-04-28 05:57:50,752 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_image.py' 2023-04-28 05:57:50,752 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_image_info.py' 2023-04-28 05:57:50,752 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_import.py' 2023-04-28 05:57:50,753 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_load.py' 2023-04-28 05:57:50,753 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_login.py' 2023-04-28 05:57:50,753 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_login_info.py' 2023-04-28 05:57:50,753 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_logout.py' 2023-04-28 05:57:50,754 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_network.py' 2023-04-28 05:57:50,754 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_network_info.py' 2023-04-28 05:57:50,755 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_play.py' 2023-04-28 05:57:50,755 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_pod.py' 2023-04-28 05:57:50,755 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_pod_info.py' 2023-04-28 05:57:50,755 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_save.py' 2023-04-28 05:57:50,756 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_secret.py' 2023-04-28 05:57:50,756 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_tag.py' 2023-04-28 05:57:50,756 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_volume.py' 2023-04-28 05:57:50,756 wheel INFO adding 'ansible_collections/containers/podman/plugins/modules/podman_volume_info.py' 2023-04-28 05:57:50,757 wheel INFO adding 'ansible_collections/cyberark/conjur/CHANGELOG.md' 2023-04-28 05:57:50,757 wheel INFO adding 'ansible_collections/cyberark/conjur/CONTRIBUTING.md' 2023-04-28 05:57:50,757 wheel INFO adding 'ansible_collections/cyberark/conjur/FILES.json' 2023-04-28 05:57:50,758 wheel INFO adding 'ansible_collections/cyberark/conjur/Jenkinsfile' 2023-04-28 05:57:50,758 wheel INFO adding 'ansible_collections/cyberark/conjur/LICENSE' 2023-04-28 05:57:50,758 wheel INFO adding 'ansible_collections/cyberark/conjur/MANIFEST.json' 2023-04-28 05:57:50,758 wheel INFO adding 'ansible_collections/cyberark/conjur/README.md' 2023-04-28 05:57:50,759 wheel INFO adding 'ansible_collections/cyberark/conjur/SECURITY.md' 2023-04-28 05:57:50,759 wheel INFO adding 'ansible_collections/cyberark/conjur/requirements.txt' 2023-04-28 05:57:50,759 wheel INFO adding 'ansible_collections/cyberark/conjur/secrets.yml' 2023-04-28 05:57:50,759 wheel INFO adding 'ansible_collections/cyberark/conjur/ci/build_release' 2023-04-28 05:57:50,759 wheel INFO adding 'ansible_collections/cyberark/conjur/ci/parse-changelog.sh' 2023-04-28 05:57:50,760 wheel INFO adding 'ansible_collections/cyberark/conjur/ci/publish_to_galaxy' 2023-04-28 05:57:50,760 wheel INFO adding 'ansible_collections/cyberark/conjur/ci/test.sh' 2023-04-28 05:57:50,760 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/Dockerfile' 2023-04-28 05:57:50,760 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/Dockerfile_nginx' 2023-04-28 05:57:50,761 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/ansible.cfg' 2023-04-28 05:57:50,761 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/docker-compose.yml' 2023-04-28 05:57:50,761 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/start.sh' 2023-04-28 05:57:50,761 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/test_unit.sh' 2023-04-28 05:57:50,761 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/playbooks/conjur-identity-setup/conjur_role_playbook.yml' 2023-04-28 05:57:50,762 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-playbook-v2.yml' 2023-04-28 05:57:50,762 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-playbook.yml' 2023-04-28 05:57:50,762 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory-v2.j2' 2023-04-28 05:57:50,762 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/playbooks/inventory-setup/inventory.j2' 2023-04-28 05:57:50,763 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/policy/root.yml' 2023-04-28 05:57:50,763 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/proxy/default.conf' 2023-04-28 05:57:50,763 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/proxy/ssl.conf' 2023-04-28 05:57:50,763 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/test_app_centos/Dockerfile' 2023-04-28 05:57:50,764 wheel INFO adding 'ansible_collections/cyberark/conjur/dev/test_app_ubuntu/Dockerfile' 2023-04-28 05:57:50,764 wheel INFO adding 'ansible_collections/cyberark/conjur/examples/test.yml' 2023-04-28 05:57:50,764 wheel INFO adding 'ansible_collections/cyberark/conjur/meta/runtime.yml' 2023-04-28 05:57:50,764 wheel INFO adding 'ansible_collections/cyberark/conjur/plugins/lookup/conjur_variable.py' 2023-04-28 05:57:50,765 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/README.md' 2023-04-28 05:57:50,765 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/defaults/main.yml' 2023-04-28 05:57:50,765 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/meta/main.yml' 2023-04-28 05:57:50,765 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/identity.yml' 2023-04-28 05:57:50,766 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/identity_check.yml' 2023-04-28 05:57:50,766 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/install.yml' 2023-04-28 05:57:50,766 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/main.yml' 2023-04-28 05:57:50,766 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/summon-conjur.yml' 2023-04-28 05:57:50,766 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/summon.yml' 2023-04-28 05:57:50,767 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tasks/uninstall.yml' 2023-04-28 05:57:50,767 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates/conjur.conf.j2' 2023-04-28 05:57:50,767 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/templates/conjur.identity.j2' 2023-04-28 05:57:50,767 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.dockerignore' 2023-04-28 05:57:50,768 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/Dockerfile' 2023-04-28 05:57:50,768 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/Dockerfile_nginx' 2023-04-28 05:57:50,768 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/ansible.cfg' 2023-04-28 05:57:50,768 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/docker-compose.yml' 2023-04-28 05:57:50,768 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-playbook-v2.yml' 2023-04-28 05:57:50,769 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-playbook.yml' 2023-04-28 05:57:50,769 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory-v2.j2' 2023-04-28 05:57:50,769 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/inventory.j2' 2023-04-28 05:57:50,769 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test.sh' 2023-04-28 05:57:50,769 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/.gitignore' 2023-04-28 05:57:50,770 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/CACHEDIR.TAG' 2023-04-28 05:57:50,770 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/README.md' 2023-04-28 05:57:50,770 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache/nodeids' 2023-04-28 05:57:50,770 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/.pytest_cache/v/cache/stepwise' 2023-04-28 05:57:50,771 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit/cleanup-conjur-identity' 2023-04-28 05:57:50,771 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/junit/configure-conjur-identity' 2023-04-28 05:57:50,771 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/policy/root.yml' 2023-04-28 05:57:50,771 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy/default.conf' 2023-04-28 05:57:50,772 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/proxy/ssl.conf' 2023-04-28 05:57:50,772 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_centos/Dockerfile' 2023-04-28 05:57:50,772 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_app_ubuntu/Dockerfile' 2023-04-28 05:57:50,772 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/playbook.yml' 2023-04-28 05:57:50,773 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests/test_default.py' 2023-04-28 05:57:50,773 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/playbook.yml' 2023-04-28 05:57:50,773 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests/test_default.py' 2023-04-28 05:57:50,773 wheel INFO adding 'ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/misconfig-conjur-identity/playbook.yml' 2023-04-28 05:57:50,774 wheel INFO adding 'ansible_collections/cyberark/pas/CONTRIBUTING.md' 2023-04-28 05:57:50,774 wheel INFO adding 'ansible_collections/cyberark/pas/FILES.json' 2023-04-28 05:57:50,774 wheel INFO adding 'ansible_collections/cyberark/pas/LICENSE' 2023-04-28 05:57:50,774 wheel INFO adding 'ansible_collections/cyberark/pas/MANIFEST.json' 2023-04-28 05:57:50,774 wheel INFO adding 'ansible_collections/cyberark/pas/README.md' 2023-04-28 05:57:50,775 wheel INFO adding 'ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/README.md' 2023-04-28 05:57:50,775 wheel INFO adding 'ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/injector.yml' 2023-04-28 05:57:50,775 wheel INFO adding 'ansible_collections/cyberark/pas/custom-cred-types/cyberark-pas-restapi/input.yml' 2023-04-28 05:57:50,775 wheel INFO adding 'ansible_collections/cyberark/pas/meta/runtime.yml' 2023-04-28 05:57:50,776 wheel INFO adding 'ansible_collections/cyberark/pas/plugins/modules/cyberark_account.py' 2023-04-28 05:57:50,776 wheel INFO adding 'ansible_collections/cyberark/pas/plugins/modules/cyberark_authentication.py' 2023-04-28 05:57:50,777 wheel INFO adding 'ansible_collections/cyberark/pas/plugins/modules/cyberark_credential.py' 2023-04-28 05:57:50,777 wheel INFO adding 'ansible_collections/cyberark/pas/plugins/modules/cyberark_user.py' 2023-04-28 05:57:50,777 wheel INFO adding 'ansible_collections/cyberark/pas/roles/aimprovider/README.md' 2023-04-28 05:57:50,778 wheel INFO adding 'ansible_collections/cyberark/pas/roles/aimprovider/defaults/main.yml' 2023-04-28 05:57:50,778 wheel INFO adding 'ansible_collections/cyberark/pas/roles/aimprovider/tasks/installAIMProvider.yml' 2023-04-28 05:57:50,778 wheel INFO adding 'ansible_collections/cyberark/pas/roles/aimprovider/tasks/main.yml' 2023-04-28 05:57:50,778 wheel INFO adding 'ansible_collections/cyberark/pas/roles/aimprovider/tasks/uninstallAIMProvider.yml' 2023-04-28 05:57:50,779 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/FILES.json' 2023-04-28 05:57:50,780 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/LICENSE' 2023-04-28 05:57:50,780 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/MANIFEST.json' 2023-04-28 05:57:50,780 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/README.md' 2023-04-28 05:57:50,781 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/rebuild.sh' 2023-04-28 05:57:50,781 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/requirements.txt' 2023-04-28 05:57:50,781 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:50,781 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/CHANGELOG.rst' 2023-04-28 05:57:50,782 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/changelog.yaml' 2023-04-28 05:57:50,782 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/config.yaml' 2023-04-28 05:57:50,782 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/100-prefix_lists-resource-module.yaml' 2023-04-28 05:57:50,782 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/101-bgp-prefix_lists.yaml' 2023-04-28 05:57:50,783 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/102-playbook-example-updates.yaml' 2023-04-28 05:57:50,783 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/103-standard-interface-naming-and-other-bugfixes.yaml' 2023-04-28 05:57:50,783 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/105-vxlan-regression-test-fix.yaml' 2023-04-28 05:57:50,783 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/2.0.0.yaml' 2023-04-28 05:57:50,784 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/53-oc-yang-compliance.yaml' 2023-04-28 05:57:50,784 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/58-vxlan-primary-ip.yaml' 2023-04-28 05:57:50,784 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/60-bgp-regression-test_fixes.yaml' 2023-04-28 05:57:50,784 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/62-bgp-vxlan-primary-ip.yaml' 2023-04-28 05:57:50,784 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/63-bgp_af-route_advertise_list.yaml' 2023-04-28 05:57:50,785 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/67-bgp_neighbors-auth_pwd-and-neighbor_description.yaml' 2023-04-28 05:57:50,785 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/72-bgp_neighbors-add-attributes.yaml' 2023-04-28 05:57:50,785 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/76-CLI-command-prompt-answer-fix.yaml' 2023-04-28 05:57:50,785 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/78-aaa-regression-fix.yaml' 2023-04-28 05:57:50,785 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/81-add-bgp-peer-group-attributes.yaml' 2023-04-28 05:57:50,786 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/82-static_routes.yaml' 2023-04-28 05:57:50,786 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/85-regression-test-fixes.yaml' 2023-04-28 05:57:50,786 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/88-port_breakout-and-execution-environment.yaml' 2023-04-28 05:57:50,786 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/90-aaa-and-users-bugfix.yaml' 2023-04-28 05:57:50,786 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/98-vlans-description.yaml' 2023-04-28 05:57:50,787 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/changelogs/archive_fragments/2.0.0/99-ntp-resource-module.yaml' 2023-04-28 05:57:50,787 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/meta/execution-environment.yml' 2023-04-28 05:57:50,787 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/meta/runtime.yml' 2023-04-28 05:57:50,787 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/clos-fabric.yaml' 2023-04-28 05:57:50,788 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/inventory.yaml' 2023-04-28 05:57:50,788 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/all.yaml' 2023-04-28 05:57:50,788 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/leaf.yaml' 2023-04-28 05:57:50,788 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/group_vars/spine.yaml' 2023-04-28 05:57:50,789 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/bgp_l3_fabric/templates/clos_fabric_cfg.j2' 2023-04-28 05:57:50,789 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/hosts' 2023-04-28 05:57:50,789 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/interface_naming.yaml' 2023-04-28 05:57:50,789 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/patch.txt' 2023-04-28 05:57:50,789 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_aaa.yaml' 2023-04-28 05:57:50,790 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_api.yaml' 2023-04-28 05:57:50,790 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_bgp.yaml' 2023-04-28 05:57:50,790 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_bgp_communities.yaml' 2023-04-28 05:57:50,790 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_command.yaml' 2023-04-28 05:57:50,791 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_config.yaml' 2023-04-28 05:57:50,791 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_facts.yaml' 2023-04-28 05:57:50,791 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_interfaces_config.yaml' 2023-04-28 05:57:50,791 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_system.yaml' 2023-04-28 05:57:50,791 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/sonic_vxlans_config.yaml' 2023-04-28 05:57:50,792 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/playbooks/common_examples/src.txt' 2023-04-28 05:57:50,792 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/action/__init__.py' 2023-04-28 05:57:50,792 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/action/sonic.py' 2023-04-28 05:57:50,792 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/__init__.py' 2023-04-28 05:57:50,793 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/sonic.py' 2023-04-28 05:57:50,793 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/__init__.py' 2023-04-28 05:57:50,793 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/sonic.py' 2023-04-28 05:57:50,793 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,794 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:50,794 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/__init__.py' 2023-04-28 05:57:50,794 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/sonic.py' 2023-04-28 05:57:50,794 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/__init__.py' 2023-04-28 05:57:50,795 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/__init__.py' 2023-04-28 05:57:50,795 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/aaa.py' 2023-04-28 05:57:50,795 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/__init__.py' 2023-04-28 05:57:50,795 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/bgp.py' 2023-04-28 05:57:50,796 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/__init__.py' 2023-04-28 05:57:50,796 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/bgp_af.py' 2023-04-28 05:57:50,796 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/__init__.py' 2023-04-28 05:57:50,796 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/bgp_as_paths.py' 2023-04-28 05:57:50,797 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/__init__.py' 2023-04-28 05:57:50,797 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/bgp_communities.py' 2023-04-28 05:57:50,797 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/__init__.py' 2023-04-28 05:57:50,797 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/bgp_ext_communities.py' 2023-04-28 05:57:50,797 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/__init__.py' 2023-04-28 05:57:50,798 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/bgp_neighbors.py' 2023-04-28 05:57:50,798 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/__init__.py' 2023-04-28 05:57:50,798 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/bgp_neighbors_af.py' 2023-04-28 05:57:50,798 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/__init__.py' 2023-04-28 05:57:50,799 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/facts.py' 2023-04-28 05:57:50,799 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/__init__.py' 2023-04-28 05:57:50,799 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/interfaces.py' 2023-04-28 05:57:50,799 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:50,800 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/__init__.py' 2023-04-28 05:57:50,800 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:50,800 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/__init__.py' 2023-04-28 05:57:50,800 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:50,801 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag/mclag.py' 2023-04-28 05:57:50,801 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp/ntp.py' 2023-04-28 05:57:50,801 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout/port_breakout.py' 2023-04-28 05:57:50,801 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/__init__.py' 2023-04-28 05:57:50,802 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/prefix_lists.py' 2023-04-28 05:57:50,802 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server/radius_server.py' 2023-04-28 05:57:50,802 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/__init__.py' 2023-04-28 05:57:50,802 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/static_routes.py' 2023-04-28 05:57:50,803 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/__init__.py' 2023-04-28 05:57:50,803 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/system.py' 2023-04-28 05:57:50,803 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server/tacacs_server.py' 2023-04-28 05:57:50,803 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users/users.py' 2023-04-28 05:57:50,804 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/__init__.py' 2023-04-28 05:57:50,804 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/vlans.py' 2023-04-28 05:57:50,804 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs/vrfs.py' 2023-04-28 05:57:50,804 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/__init__.py' 2023-04-28 05:57:50,805 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/vxlans.py' 2023-04-28 05:57:50,805 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/__init__.py' 2023-04-28 05:57:50,805 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/__init__.py' 2023-04-28 05:57:50,805 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/aaa.py' 2023-04-28 05:57:50,806 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp/bgp.py' 2023-04-28 05:57:50,806 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af/bgp_af.py' 2023-04-28 05:57:50,807 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths/bgp_as_paths.py' 2023-04-28 05:57:50,807 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/__init__.py' 2023-04-28 05:57:50,807 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/bgp_communities.py' 2023-04-28 05:57:50,807 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/__init__.py' 2023-04-28 05:57:50,808 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/bgp_ext_communities.py' 2023-04-28 05:57:50,808 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors/bgp_neighbors.py' 2023-04-28 05:57:50,809 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af/bgp_neighbors_af.py' 2023-04-28 05:57:50,809 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces/interfaces.py' 2023-04-28 05:57:50,810 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:50,810 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:50,810 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:50,811 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag/mclag.py' 2023-04-28 05:57:50,811 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp/ntp.py' 2023-04-28 05:57:50,811 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout/port_breakout.py' 2023-04-28 05:57:50,812 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/__init__.py' 2023-04-28 05:57:50,812 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/prefix_lists.py' 2023-04-28 05:57:50,812 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server/radius_server.py' 2023-04-28 05:57:50,813 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/__init__.py' 2023-04-28 05:57:50,813 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/static_routes.py' 2023-04-28 05:57:50,813 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/__init__.py' 2023-04-28 05:57:50,813 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/system.py' 2023-04-28 05:57:50,814 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server/tacacs_server.py' 2023-04-28 05:57:50,814 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users/users.py' 2023-04-28 05:57:50,814 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans/vlans.py' 2023-04-28 05:57:50,815 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs/vrfs.py' 2023-04-28 05:57:50,815 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans/vxlans.py' 2023-04-28 05:57:50,815 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/__init__.py' 2023-04-28 05:57:50,816 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/facts.py' 2023-04-28 05:57:50,816 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/__init__.py' 2023-04-28 05:57:50,816 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/aaa.py' 2023-04-28 05:57:50,816 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/__init__.py' 2023-04-28 05:57:50,817 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/bgp.py' 2023-04-28 05:57:50,817 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/__init__.py' 2023-04-28 05:57:50,817 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/bgp_af.py' 2023-04-28 05:57:50,817 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/__init__.py' 2023-04-28 05:57:50,818 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/bgp_as_paths.py' 2023-04-28 05:57:50,818 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/__init__.py' 2023-04-28 05:57:50,818 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/bgp_communities.py' 2023-04-28 05:57:50,818 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/__init__.py' 2023-04-28 05:57:50,819 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/bgp_ext_communities.py' 2023-04-28 05:57:50,819 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/__init__.py' 2023-04-28 05:57:50,819 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/bgp_neighbors.py' 2023-04-28 05:57:50,819 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/__init__.py' 2023-04-28 05:57:50,820 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/bgp_neighbors_af.py' 2023-04-28 05:57:50,820 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/__init__.py' 2023-04-28 05:57:50,820 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/interfaces.py' 2023-04-28 05:57:50,820 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:50,821 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/__init__.py' 2023-04-28 05:57:50,821 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:50,821 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/__init__.py' 2023-04-28 05:57:50,821 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:50,822 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag/mclag.py' 2023-04-28 05:57:50,822 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/__init__.py' 2023-04-28 05:57:50,822 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/ntp.py' 2023-04-28 05:57:50,822 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout/port_breakout.py' 2023-04-28 05:57:50,823 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/__init__.py' 2023-04-28 05:57:50,823 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/prefix_lists.py' 2023-04-28 05:57:50,823 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server/radius_server.py' 2023-04-28 05:57:50,824 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/__init__.py' 2023-04-28 05:57:50,824 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/static_routes.py' 2023-04-28 05:57:50,824 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/__init__.py' 2023-04-28 05:57:50,824 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/system.py' 2023-04-28 05:57:50,825 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server/tacacs_server.py' 2023-04-28 05:57:50,825 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users/users.py' 2023-04-28 05:57:50,825 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/__init__.py' 2023-04-28 05:57:50,825 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/vlans.py' 2023-04-28 05:57:50,826 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs/vrfs.py' 2023-04-28 05:57:50,826 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/__init__.py' 2023-04-28 05:57:50,826 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/vxlans.py' 2023-04-28 05:57:50,826 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/__init__.py' 2023-04-28 05:57:50,827 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/bgp_utils.py' 2023-04-28 05:57:50,827 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/interfaces_util.py' 2023-04-28 05:57:50,827 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/utils.py' 2023-04-28 05:57:50,828 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/__init__.py' 2023-04-28 05:57:50,828 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_aaa.py' 2023-04-28 05:57:50,828 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_api.py' 2023-04-28 05:57:50,828 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp.py' 2023-04-28 05:57:50,829 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_af.py' 2023-04-28 05:57:50,829 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_as_paths.py' 2023-04-28 05:57:50,829 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_communities.py' 2023-04-28 05:57:50,830 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_ext_communities.py' 2023-04-28 05:57:50,830 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_neighbors.py' 2023-04-28 05:57:50,830 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_bgp_neighbors_af.py' 2023-04-28 05:57:50,831 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_command.py' 2023-04-28 05:57:50,831 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_config.py' 2023-04-28 05:57:50,831 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_facts.py' 2023-04-28 05:57:50,831 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_interfaces.py' 2023-04-28 05:57:50,832 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_l2_interfaces.py' 2023-04-28 05:57:50,832 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_l3_interfaces.py' 2023-04-28 05:57:50,832 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_lag_interfaces.py' 2023-04-28 05:57:50,832 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_mclag.py' 2023-04-28 05:57:50,833 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_ntp.py' 2023-04-28 05:57:50,833 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_port_breakout.py' 2023-04-28 05:57:50,833 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_prefix_lists.py' 2023-04-28 05:57:50,833 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_radius_server.py' 2023-04-28 05:57:50,834 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_static_routes.py' 2023-04-28 05:57:50,834 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_system.py' 2023-04-28 05:57:50,834 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_tacacs_server.py' 2023-04-28 05:57:50,834 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_users.py' 2023-04-28 05:57:50,835 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vlans.py' 2023-04-28 05:57:50,835 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vrfs.py' 2023-04-28 05:57:50,835 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/modules/sonic_vxlans.py' 2023-04-28 05:57:50,836 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/terminal/__init__.py' 2023-04-28 05:57:50,836 wheel INFO adding 'ansible_collections/dellemc/enterprise_sonic/plugins/terminal/sonic.py' 2023-04-28 05:57:50,836 wheel INFO adding 'ansible_collections/dellemc/openmanage/CHANGELOG.rst' 2023-04-28 05:57:50,837 wheel INFO adding 'ansible_collections/dellemc/openmanage/FILES.json' 2023-04-28 05:57:50,838 wheel INFO adding 'ansible_collections/dellemc/openmanage/LICENSE' 2023-04-28 05:57:50,838 wheel INFO adding 'ansible_collections/dellemc/openmanage/MANIFEST.json' 2023-04-28 05:57:50,838 wheel INFO adding 'ansible_collections/dellemc/openmanage/README.md' 2023-04-28 05:57:50,838 wheel INFO adding 'ansible_collections/dellemc/openmanage/requirements.txt' 2023-04-28 05:57:50,839 wheel INFO adding 'ansible_collections/dellemc/openmanage/requirements.yml' 2023-04-28 05:57:50,839 wheel INFO adding 'ansible_collections/dellemc/openmanage/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:50,839 wheel INFO adding 'ansible_collections/dellemc/openmanage/changelogs/changelog.yaml' 2023-04-28 05:57:50,840 wheel INFO adding 'ansible_collections/dellemc/openmanage/changelogs/config.yaml' 2023-04-28 05:57:50,840 wheel INFO adding 'ansible_collections/dellemc/openmanage/meta/execution-environment.yml' 2023-04-28 05:57:50,840 wheel INFO adding 'ansible_collections/dellemc/openmanage/meta/runtime.yml' 2023-04-28 05:57:50,841 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/dellemc_idrac_storage_volume.yml' 2023-04-28 05:57:50,841 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_attributes.yml' 2023-04-28 05:57:50,841 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_bios.yml' 2023-04-28 05:57:50,841 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_boot.yml' 2023-04-28 05:57:50,842 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_boot_virtual_media_workflow.yml' 2023-04-28 05:57:50,842 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_certificates.yml' 2023-04-28 05:57:50,842 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_firmware.yml' 2023-04-28 05:57:50,842 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_firmware_info.yml' 2023-04-28 05:57:50,842 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_job_status_info.yml' 2023-04-28 05:57:50,843 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_jobs.yml' 2023-04-28 05:57:50,843 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_logs.yml' 2023-04-28 05:57:50,843 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_lifecycle_controller_status_info.yml' 2023-04-28 05:57:50,843 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_os_deployment.yml' 2023-04-28 05:57:50,843 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_redfish_storage_controller.yml' 2023-04-28 05:57:50,844 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_redfish_storage_controller_job_tracking.yml' 2023-04-28 05:57:50,844 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_reset.yml' 2023-04-28 05:57:50,844 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_reset_result_tracking.yml' 2023-04-28 05:57:50,844 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_server_config_profile.yml' 2023-04-28 05:57:50,845 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_syslog.yml' 2023-04-28 05:57:50,845 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_system_info.yml' 2023-04-28 05:57:50,845 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_user.yml' 2023-04-28 05:57:50,845 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/idrac_virtual_media.yml' 2023-04-28 05:57:50,845 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_configure_idrac_eventing.yml' 2023-04-28 05:57:50,846 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_configure_idrac_services.yml' 2023-04-28 05:57:50,846 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_get_firmware_inventory.yml' 2023-04-28 05:57:50,846 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_get_system_inventory.yml' 2023-04-28 05:57:50,846 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_idrac_lc_attributes.yml' 2023-04-28 05:57:50,847 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/dellemc_system_lockdown_mode.yml' 2023-04-28 05:57:50,847 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/idrac_network.yml' 2023-04-28 05:57:50,847 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/idrac/deprecated/idrac_timezone_ntp.yml' 2023-04-28 05:57:50,847 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_active_directory.yml' 2023-04-28 05:57:50,847 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_chassis_slots.yml' 2023-04-28 05:57:50,848 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_group.yml' 2023-04-28 05:57:50,848 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_info.yml' 2023-04-28 05:57:50,848 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_local_access_configuration.yml' 2023-04-28 05:57:50,848 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_location.yml' 2023-04-28 05:57:50,849 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_mgmt_network.yml' 2023-04-28 05:57:50,849 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_network_services.yml' 2023-04-28 05:57:50,849 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_power_settings.yml' 2023-04-28 05:57:50,849 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_device_quick_deploy.yml' 2023-04-28 05:57:50,849 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_devices.yml' 2023-04-28 05:57:50,850 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_diagnostics.yml' 2023-04-28 05:57:50,850 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_discovery.yml' 2023-04-28 05:57:50,850 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_domain_user_groups.yml' 2023-04-28 05:57:50,850 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_group_device_action.yml' 2023-04-28 05:57:50,851 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_groups.yml' 2023-04-28 05:57:50,851 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_identity_pool.yml' 2023-04-28 05:57:50,851 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_job_info.yml' 2023-04-28 05:57:50,851 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_port_breakout.yml' 2023-04-28 05:57:50,851 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_port_breakout_job_traking.yml' 2023-04-28 05:57:50,852 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_vlan.yml' 2023-04-28 05:57:50,852 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_network_vlan_info.yml' 2023-04-28 05:57:50,852 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profile_info.yml' 2023-04-28 05:57:50,852 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profile_workflow.yml' 2023-04-28 05:57:50,852 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_server_interface_profiles.yml' 2023-04-28 05:57:50,853 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_smart_fabric.yml' 2023-04-28 05:57:50,853 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_smart_fabric_uplink.yml' 2023-04-28 05:57:50,853 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/ome_template_identity_pool.yml' 2023-04-28 05:57:50,853 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_alerts_smtp.yml' 2023-04-28 05:57:50,854 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_alerts_syslog.yml' 2023-04-28 05:57:50,854 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_certificate.yml' 2023-04-28 05:57:50,854 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_console_preferences.yml' 2023-04-28 05:57:50,854 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_address.yml' 2023-04-28 05:57:50,855 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_address_with_job_tracking.yml' 2023-04-28 05:57:50,855 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_proxy.yml' 2023-04-28 05:57:50,855 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_settings.yml' 2023-04-28 05:57:50,855 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_time.yml' 2023-04-28 05:57:50,855 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_time_zone_info.yml' 2023-04-28 05:57:50,856 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_webserver.yml' 2023-04-28 05:57:50,856 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_network_webserver_port_changed_tracking.yml' 2023-04-28 05:57:50,856 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/application/ome_application_security_settings.yml' 2023-04-28 05:57:50,856 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_baseline.yml' 2023-04-28 05:57:50,857 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_baseline_workflow.yml' 2023-04-28 05:57:50,857 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/compliance/ome_configuration_compliance_info.yml' 2023-04-28 05:57:50,857 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/ome_firmware.yml' 2023-04-28 05:57:50,857 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/ome_firmware_with_job_tracking.yml' 2023-04-28 05:57:50,858 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline.yml' 2023-04-28 05:57:50,858 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_compliance_info.yml' 2023-04-28 05:57:50,858 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_compliance_info_filters.yml' 2023-04-28 05:57:50,858 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/ome_firmware_baseline_info.yml' 2023-04-28 05:57:50,858 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering/component_complaince_report_with_baseline.yml' 2023-04-28 05:57:50,859 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/baseline/component_reports_filtering/component_complaince_report_with_devices.yml' 2023-04-28 05:57:50,859 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/firmware/catalog/ome_firmware_catalog.yml' 2023-04-28 05:57:50,859 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/powerstate/ome_powerstate.yml' 2023-04-28 05:57:50,859 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/powerstate/ome_powerstate_with_job_tracking.yml' 2023-04-28 05:57:50,860 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile.yml' 2023-04-28 05:57:50,860 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_assign_job_tracking.yml' 2023-04-28 05:57:50,860 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_migrate_job_tracking.yml' 2023-04-28 05:57:50,860 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/profile/ome_profile_unassign_job_tracking.yml' 2023-04-28 05:57:50,861 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template.yml' 2023-04-28 05:57:50,861 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_create_modify_lcd_display.yml' 2023-04-28 05:57:50,861 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_info.yml' 2023-04-28 05:57:50,861 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_info_with_filter.yml' 2023-04-28 05:57:50,862 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_lcd_display_string_deploy.yml' 2023-04-28 05:57:50,862 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_network_vlan.yml' 2023-04-28 05:57:50,862 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/template/ome_template_with_job_tracking.yml' 2023-04-28 05:57:50,862 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/user/ome_user.yml' 2023-04-28 05:57:50,862 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/ome/user/ome_user_info.yml' 2023-04-28 05:57:50,863 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/redfish_event_subscription.yml' 2023-04-28 05:57:50,863 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/redfish_powerstate.yml' 2023-04-28 05:57:50,863 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware.yml' 2023-04-28 05:57:50,863 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware_from_http_jobtracking.yml' 2023-04-28 05:57:50,864 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/firmware/redfish_firmware_from_local_jobtracking.yml' 2023-04-28 05:57:50,864 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume.yml' 2023-04-28 05:57:50,864 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_create_job_tracking.yml' 2023-04-28 05:57:50,864 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_delete_job_tracking.yml' 2023-04-28 05:57:50,865 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_initialize_job_tracking.yml' 2023-04-28 05:57:50,865 wheel INFO adding 'ansible_collections/dellemc/openmanage/playbooks/redfish/storage/redfish_storage_volume_modify_job_tracking.yml' 2023-04-28 05:57:50,865 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/README.md' 2023-04-28 05:57:50,865 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:50,866 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/doc_fragments/idrac_auth_options.py' 2023-04-28 05:57:50,866 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/doc_fragments/network_share_options.py' 2023-04-28 05:57:50,866 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/doc_fragments/ome_auth_options.py' 2023-04-28 05:57:50,866 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/doc_fragments/omem_auth_options.py' 2023-04-28 05:57:50,866 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/doc_fragments/oment_auth_options.py' 2023-04-28 05:57:50,867 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/doc_fragments/redfish_auth_options.py' 2023-04-28 05:57:50,867 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/module_utils/__init__.py' 2023-04-28 05:57:50,867 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/module_utils/dellemc_idrac.py' 2023-04-28 05:57:50,867 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/module_utils/idrac_redfish.py' 2023-04-28 05:57:50,868 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/module_utils/ome.py' 2023-04-28 05:57:50,868 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/module_utils/redfish.py' 2023-04-28 05:57:50,868 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/module_utils/utils.py' 2023-04-28 05:57:50,869 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/__init__.py' 2023-04-28 05:57:50,869 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/dellemc_configure_idrac_eventing.py' 2023-04-28 05:57:50,869 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/dellemc_configure_idrac_services.py' 2023-04-28 05:57:50,869 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/dellemc_get_firmware_inventory.py' 2023-04-28 05:57:50,870 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/dellemc_get_system_inventory.py' 2023-04-28 05:57:50,870 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/dellemc_idrac_lc_attributes.py' 2023-04-28 05:57:50,870 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/dellemc_idrac_storage_volume.py' 2023-04-28 05:57:50,871 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/dellemc_system_lockdown_mode.py' 2023-04-28 05:57:50,871 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_attributes.py' 2023-04-28 05:57:50,871 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_bios.py' 2023-04-28 05:57:50,872 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_boot.py' 2023-04-28 05:57:50,872 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_certificates.py' 2023-04-28 05:57:50,872 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_firmware.py' 2023-04-28 05:57:50,873 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_firmware_info.py' 2023-04-28 05:57:50,873 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_job_status_info.py' 2023-04-28 05:57:50,873 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_jobs.py' 2023-04-28 05:57:50,874 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_logs.py' 2023-04-28 05:57:50,874 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_lifecycle_controller_status_info.py' 2023-04-28 05:57:50,874 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_network.py' 2023-04-28 05:57:50,874 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_os_deployment.py' 2023-04-28 05:57:50,875 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_redfish_storage_controller.py' 2023-04-28 05:57:50,875 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_reset.py' 2023-04-28 05:57:50,875 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_server_config_profile.py' 2023-04-28 05:57:50,876 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_syslog.py' 2023-04-28 05:57:50,876 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_system_info.py' 2023-04-28 05:57:50,876 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_timezone_ntp.py' 2023-04-28 05:57:50,876 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_user.py' 2023-04-28 05:57:50,877 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/idrac_virtual_media.py' 2023-04-28 05:57:50,877 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_active_directory.py' 2023-04-28 05:57:50,877 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_alerts_smtp.py' 2023-04-28 05:57:50,878 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_alerts_syslog.py' 2023-04-28 05:57:50,878 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_certificate.py' 2023-04-28 05:57:50,878 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_console_preferences.py' 2023-04-28 05:57:50,879 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_address.py' 2023-04-28 05:57:50,879 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_proxy.py' 2023-04-28 05:57:50,880 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_settings.py' 2023-04-28 05:57:50,880 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_time.py' 2023-04-28 05:57:50,880 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_network_webserver.py' 2023-04-28 05:57:50,880 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_application_security_settings.py' 2023-04-28 05:57:50,881 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_chassis_slots.py' 2023-04-28 05:57:50,881 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_configuration_compliance_baseline.py' 2023-04-28 05:57:50,882 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_configuration_compliance_info.py' 2023-04-28 05:57:50,882 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_group.py' 2023-04-28 05:57:50,882 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_info.py' 2023-04-28 05:57:50,883 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_local_access_configuration.py' 2023-04-28 05:57:50,883 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_location.py' 2023-04-28 05:57:50,883 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_mgmt_network.py' 2023-04-28 05:57:50,884 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_network_services.py' 2023-04-28 05:57:50,884 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_power_settings.py' 2023-04-28 05:57:50,884 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_device_quick_deploy.py' 2023-04-28 05:57:50,885 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_devices.py' 2023-04-28 05:57:50,885 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_diagnostics.py' 2023-04-28 05:57:50,885 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_discovery.py' 2023-04-28 05:57:50,886 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_domain_user_groups.py' 2023-04-28 05:57:50,886 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware.py' 2023-04-28 05:57:50,887 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline.py' 2023-04-28 05:57:50,887 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline_compliance_info.py' 2023-04-28 05:57:50,887 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_baseline_info.py' 2023-04-28 05:57:50,887 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_firmware_catalog.py' 2023-04-28 05:57:50,888 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_groups.py' 2023-04-28 05:57:50,888 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_identity_pool.py' 2023-04-28 05:57:50,888 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_job_info.py' 2023-04-28 05:57:50,889 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_network_port_breakout.py' 2023-04-28 05:57:50,889 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_network_vlan.py' 2023-04-28 05:57:50,889 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_network_vlan_info.py' 2023-04-28 05:57:50,890 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_powerstate.py' 2023-04-28 05:57:50,890 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_profile.py' 2023-04-28 05:57:50,890 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_server_interface_profile_info.py' 2023-04-28 05:57:50,891 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_server_interface_profiles.py' 2023-04-28 05:57:50,891 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_smart_fabric.py' 2023-04-28 05:57:50,891 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_smart_fabric_uplink.py' 2023-04-28 05:57:50,892 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_template.py' 2023-04-28 05:57:50,892 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_template_identity_pool.py' 2023-04-28 05:57:50,892 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_template_info.py' 2023-04-28 05:57:50,893 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_template_network_vlan.py' 2023-04-28 05:57:50,893 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_user.py' 2023-04-28 05:57:50,893 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/ome_user_info.py' 2023-04-28 05:57:50,894 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/redfish_event_subscription.py' 2023-04-28 05:57:50,894 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/redfish_firmware.py' 2023-04-28 05:57:50,894 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/redfish_powerstate.py' 2023-04-28 05:57:50,894 wheel INFO adding 'ansible_collections/dellemc/openmanage/plugins/modules/redfish_storage_volume.py' 2023-04-28 05:57:50,895 wheel INFO adding 'ansible_collections/dellemc/os10/FILES.json' 2023-04-28 05:57:50,897 wheel INFO adding 'ansible_collections/dellemc/os10/LICENSE' 2023-04-28 05:57:50,897 wheel INFO adding 'ansible_collections/dellemc/os10/MANIFEST.json' 2023-04-28 05:57:50,897 wheel INFO adding 'ansible_collections/dellemc/os10/README.md' 2023-04-28 05:57:50,898 wheel INFO adding 'ansible_collections/dellemc/os10/changelogs/CHANGELOG.rst' 2023-04-28 05:57:50,898 wheel INFO adding 'ansible_collections/dellemc/os10/changelogs/changelog.yaml' 2023-04-28 05:57:50,898 wheel INFO adding 'ansible_collections/dellemc/os10/changelogs/config.yaml' 2023-04-28 05:57:50,898 wheel INFO adding 'ansible_collections/dellemc/os10/meta/runtime.yml' 2023-04-28 05:57:50,899 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/README.md' 2023-04-28 05:57:50,899 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/datacenter.yaml' 2023-04-28 05:57:50,899 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/inventory.yaml' 2023-04-28 05:57:50,899 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars/all' 2023-04-28 05:57:50,899 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/group_vars/spine.yaml' 2023-04-28 05:57:50,900 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf1.yaml' 2023-04-28 05:57:50,900 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf2.yaml' 2023-04-28 05:57:50,900 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf3.yaml' 2023-04-28 05:57:50,900 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/leaf4.yaml' 2023-04-28 05:57:50,901 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/spine1.yaml' 2023-04-28 05:57:50,901 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/clos_fabric_ebgp/host_vars/spine2.yaml' 2023-04-28 05:57:50,901 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/README.md' 2023-04-28 05:57:50,901 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/datacenter.yaml' 2023-04-28 05:57:50,902 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/inventory.yaml' 2023-04-28 05:57:50,902 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/vxlan_evpn_topology.png' 2023-04-28 05:57:50,903 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/prim-vtep1.yaml' 2023-04-28 05:57:50,903 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/prim-vtep2.yaml' 2023-04-28 05:57:50,903 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/sec-vtep1.yaml' 2023-04-28 05:57:50,903 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/sec-vtep2.yaml' 2023-04-28 05:57:50,904 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/spine1.yaml' 2023-04-28 05:57:50,904 wheel INFO adding 'ansible_collections/dellemc/os10/playbooks/vxlan_evpn/host_vars/spine2.yaml' 2023-04-28 05:57:50,904 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/action/os10.py' 2023-04-28 05:57:50,904 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/action/textfsm_parser.py' 2023-04-28 05:57:50,905 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/cliconf/os10.py' 2023-04-28 05:57:50,905 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/doc_fragments/os10.py' 2023-04-28 05:57:50,905 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:50,905 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/module_utils/network/base_network_show.py' 2023-04-28 05:57:50,906 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/module_utils/network/os10.py' 2023-04-28 05:57:50,906 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/__init__.py' 2023-04-28 05:57:50,906 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/base_xml_to_dict.py' 2023-04-28 05:57:50,906 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/bgp_validate.py' 2023-04-28 05:57:50,907 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/mtu_validate.py' 2023-04-28 05:57:50,907 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/os10_command.py' 2023-04-28 05:57:50,907 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/os10_config.py' 2023-04-28 05:57:50,907 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/os10_facts.py' 2023-04-28 05:57:50,908 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/show_system_network_summary.py' 2023-04-28 05:57:50,908 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/vlt_validate.py' 2023-04-28 05:57:50,908 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/modules/wiring_validate.py' 2023-04-28 05:57:50,909 wheel INFO adding 'ansible_collections/dellemc/os10/plugins/terminal/os10.py' 2023-04-28 05:57:50,909 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/LICENSE' 2023-04-28 05:57:50,909 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/README.md' 2023-04-28 05:57:50,910 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/defaults/main.yml' 2023-04-28 05:57:50,910 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/handlers/main.yml' 2023-04-28 05:57:50,910 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/meta/main.yml' 2023-04-28 05:57:50,910 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/tasks/main.yml' 2023-04-28 05:57:50,911 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/templates/os10_aaa.j2' 2023-04-28 05:57:50,911 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/tests/inventory.yaml' 2023-04-28 05:57:50,911 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/tests/main.os10.yaml' 2023-04-28 05:57:50,911 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/tests/test.yaml' 2023-04-28 05:57:50,912 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_aaa/vars/main.yml' 2023-04-28 05:57:50,912 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/LICENSE' 2023-04-28 05:57:50,912 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/README.md' 2023-04-28 05:57:50,913 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/defaults/main.yml' 2023-04-28 05:57:50,913 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/handlers/main.yml' 2023-04-28 05:57:50,913 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/meta/main.yml' 2023-04-28 05:57:50,913 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/tasks/main.yml' 2023-04-28 05:57:50,914 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/templates/os10_acl.j2' 2023-04-28 05:57:50,914 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/tests/inventory.yaml' 2023-04-28 05:57:50,914 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/tests/main.os10.yaml' 2023-04-28 05:57:50,914 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/tests/test.yaml' 2023-04-28 05:57:50,915 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_acl/vars/main.yml' 2023-04-28 05:57:50,915 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/LICENSE' 2023-04-28 05:57:50,915 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/README.md' 2023-04-28 05:57:50,916 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/defaults/main.yml' 2023-04-28 05:57:50,916 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/handlers/main.yml' 2023-04-28 05:57:50,916 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/meta/main.yml' 2023-04-28 05:57:50,916 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/tasks/main.yml' 2023-04-28 05:57:50,917 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/templates/os10_bfd.j2' 2023-04-28 05:57:50,917 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/tests/inventory.yaml' 2023-04-28 05:57:50,917 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/tests/main.yaml' 2023-04-28 05:57:50,917 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/tests/test.yaml' 2023-04-28 05:57:50,918 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bfd/vars/main.yml' 2023-04-28 05:57:50,918 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/LICENSE' 2023-04-28 05:57:50,918 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/README.md' 2023-04-28 05:57:50,919 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/defaults/main.yml' 2023-04-28 05:57:50,919 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/handlers/main.yml' 2023-04-28 05:57:50,919 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/meta/main.yml' 2023-04-28 05:57:50,920 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/tasks/main.yml' 2023-04-28 05:57:50,920 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/templates/os10_bgp.j2' 2023-04-28 05:57:50,920 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/tests/inventory.yaml' 2023-04-28 05:57:50,921 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/tests/main.os10.yaml' 2023-04-28 05:57:50,921 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/tests/test.yaml' 2023-04-28 05:57:50,921 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_bgp/vars/main.yml' 2023-04-28 05:57:50,921 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/LICENSE' 2023-04-28 05:57:50,922 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/README.md' 2023-04-28 05:57:50,922 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/defaults/main.yml' 2023-04-28 05:57:50,922 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/handlers/main.yml' 2023-04-28 05:57:50,923 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/meta/main.yml' 2023-04-28 05:57:50,923 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/tasks/main.yml' 2023-04-28 05:57:50,923 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/templates/leaf1.j2' 2023-04-28 05:57:50,923 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/tests/inventory' 2023-04-28 05:57:50,924 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/tests/main.yml' 2023-04-28 05:57:50,924 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/tests/test.yml' 2023-04-28 05:57:50,924 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_copy_config/vars/main.yml' 2023-04-28 05:57:50,924 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/LICENSE' 2023-04-28 05:57:50,925 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/README.md' 2023-04-28 05:57:50,925 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/defaults/main.yml' 2023-04-28 05:57:50,925 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/handlers/main.yml' 2023-04-28 05:57:50,925 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/meta/main.yml' 2023-04-28 05:57:50,926 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/tasks/main.yml' 2023-04-28 05:57:50,926 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/templates/os10_dns.j2' 2023-04-28 05:57:50,926 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/tests/inventory.yaml' 2023-04-28 05:57:50,926 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/tests/main.yaml' 2023-04-28 05:57:50,927 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/tests/test.yaml' 2023-04-28 05:57:50,927 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_dns/vars/main.yml' 2023-04-28 05:57:50,927 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/LICENSE' 2023-04-28 05:57:50,928 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/README.md' 2023-04-28 05:57:50,928 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/defaults/main.yml' 2023-04-28 05:57:50,928 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/handlers/main.yml' 2023-04-28 05:57:50,928 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/meta/main.yml' 2023-04-28 05:57:50,929 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/tasks/main.yml' 2023-04-28 05:57:50,929 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/templates/os10_ecmp.j2' 2023-04-28 05:57:50,929 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/tests/inventory.yaml' 2023-04-28 05:57:50,929 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/tests/main.os10.yaml' 2023-04-28 05:57:50,930 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/tests/test.yaml' 2023-04-28 05:57:50,930 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ecmp/vars/main.yml' 2023-04-28 05:57:50,930 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/LICENSE' 2023-04-28 05:57:50,930 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/README.md' 2023-04-28 05:57:50,931 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/meta/main.yml' 2023-04-28 05:57:50,931 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tasks/main.yml' 2023-04-28 05:57:50,931 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/inventory.yaml' 2023-04-28 05:57:50,931 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/main.yaml' 2023-04-28 05:57:50,932 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/test.yml' 2023-04-28 05:57:50,932 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site1-spine1' 2023-04-28 05:57:50,932 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site1-spine2' 2023-04-28 05:57:50,932 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site2-spine1' 2023-04-28 05:57:50,933 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_fabric_summary/tests/host_vars/site2-spine2' 2023-04-28 05:57:50,933 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/LICENSE' 2023-04-28 05:57:50,933 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/README.md' 2023-04-28 05:57:50,934 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/defaults/main.yml' 2023-04-28 05:57:50,934 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/handlers/main.yml' 2023-04-28 05:57:50,934 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/meta/main.yml' 2023-04-28 05:57:50,934 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/tasks/main.yml' 2023-04-28 05:57:50,935 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/templates/os10_flow_monitor.j2' 2023-04-28 05:57:50,935 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/inventory.yaml' 2023-04-28 05:57:50,935 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/main.yaml' 2023-04-28 05:57:50,935 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/tests/test.yaml' 2023-04-28 05:57:50,935 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_flow_monitor/vars/main.yml' 2023-04-28 05:57:50,936 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/LICENSE' 2023-04-28 05:57:50,936 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/README.md' 2023-04-28 05:57:50,936 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/defaults/main.yml' 2023-04-28 05:57:50,937 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/handlers/main.yml' 2023-04-28 05:57:50,937 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/meta/main.yml' 2023-04-28 05:57:50,937 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/tasks/main.yml' 2023-04-28 05:57:50,937 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/inventory' 2023-04-28 05:57:50,938 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/main.yml' 2023-04-28 05:57:50,938 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/tests/test.yml' 2023-04-28 05:57:50,938 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_image_upgrade/vars/main.yml' 2023-04-28 05:57:50,938 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/LICENSE' 2023-04-28 05:57:50,939 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/README.md' 2023-04-28 05:57:50,939 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/defaults/main.yml' 2023-04-28 05:57:50,939 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/handlers/main.yml' 2023-04-28 05:57:50,940 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/meta/main.yml' 2023-04-28 05:57:50,940 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/tasks/main.yml' 2023-04-28 05:57:50,940 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/templates/os10_interface.j2' 2023-04-28 05:57:50,940 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/tests/inventory.yaml' 2023-04-28 05:57:50,941 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/tests/main.os10.yaml' 2023-04-28 05:57:50,941 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/tests/test.yaml' 2023-04-28 05:57:50,941 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_interface/vars/main.yml' 2023-04-28 05:57:50,941 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/LICENSE' 2023-04-28 05:57:50,942 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/README.md' 2023-04-28 05:57:50,942 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/defaults/main.yml' 2023-04-28 05:57:50,942 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/handlers/main.yml' 2023-04-28 05:57:50,943 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/meta/main.yml' 2023-04-28 05:57:50,943 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/tasks/main.yml' 2023-04-28 05:57:50,943 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/templates/os10_lag.j2' 2023-04-28 05:57:50,943 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/tests/inventory.yaml' 2023-04-28 05:57:50,944 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/tests/main.os10.yaml' 2023-04-28 05:57:50,944 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/tests/test.yaml' 2023-04-28 05:57:50,944 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lag/vars/main.yml' 2023-04-28 05:57:50,944 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/LICENSE' 2023-04-28 05:57:50,945 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/README.md' 2023-04-28 05:57:50,945 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/defaults/main.yml' 2023-04-28 05:57:50,945 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/handlers/main.yml' 2023-04-28 05:57:50,946 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/meta/main.yml' 2023-04-28 05:57:50,946 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/tasks/main.yml' 2023-04-28 05:57:50,946 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/templates/os10_lldp.j2' 2023-04-28 05:57:50,946 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/tests/inventory.yaml' 2023-04-28 05:57:50,947 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/tests/main.os10.yaml' 2023-04-28 05:57:50,947 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/tests/test.yaml' 2023-04-28 05:57:50,947 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_lldp/vars/main.yml' 2023-04-28 05:57:50,947 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/LICENSE' 2023-04-28 05:57:50,948 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/README.md' 2023-04-28 05:57:50,948 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/defaults/main.yml' 2023-04-28 05:57:50,948 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/handlers/main.yml' 2023-04-28 05:57:50,948 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/meta/main.yml' 2023-04-28 05:57:50,949 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/tasks/main.yml' 2023-04-28 05:57:50,949 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/templates/os10_logging.j2' 2023-04-28 05:57:50,949 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/tests/inventory.yaml' 2023-04-28 05:57:50,949 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/tests/main.os10.yaml' 2023-04-28 05:57:50,950 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/tests/test.yaml' 2023-04-28 05:57:50,950 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_logging/vars/main.yml' 2023-04-28 05:57:50,950 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/LICENSE' 2023-04-28 05:57:50,951 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/README.md' 2023-04-28 05:57:50,951 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/meta/main.yml' 2023-04-28 05:57:50,951 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/bgp_validation.yaml' 2023-04-28 05:57:50,951 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/main.yaml' 2023-04-28 05:57:50,952 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/mtu_validation.yaml' 2023-04-28 05:57:50,952 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/vlt_validation.yaml' 2023-04-28 05:57:50,952 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tasks/wiring_validation.yaml' 2023-04-28 05:57:50,952 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/inventory.yaml' 2023-04-28 05:57:50,952 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/main.yaml' 2023-04-28 05:57:50,953 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/test.yaml' 2023-04-28 05:57:50,953 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/group_vars/all' 2023-04-28 05:57:50,953 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site1-spine1' 2023-04-28 05:57:50,953 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site1-spine2' 2023-04-28 05:57:50,954 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site2-spine1' 2023-04-28 05:57:50,954 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_network_validation/tests/host_vars/site2-spine2' 2023-04-28 05:57:50,954 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/LICENSE' 2023-04-28 05:57:50,955 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/README.md' 2023-04-28 05:57:50,955 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/defaults/main.yml' 2023-04-28 05:57:50,955 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/handlers/main.yml' 2023-04-28 05:57:50,955 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/meta/main.yml' 2023-04-28 05:57:50,956 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/tasks/main.yml' 2023-04-28 05:57:50,956 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/templates/os10_ntp.j2' 2023-04-28 05:57:50,956 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/templates/os10_ntp_vrf.j2' 2023-04-28 05:57:50,956 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/tests/inventory' 2023-04-28 05:57:50,957 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/tests/main.os10.yaml' 2023-04-28 05:57:50,957 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/tests/test.yml' 2023-04-28 05:57:50,957 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_ntp/vars/main.yml' 2023-04-28 05:57:50,957 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/LICENSE' 2023-04-28 05:57:50,958 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/README.md' 2023-04-28 05:57:50,958 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/defaults/main.yml' 2023-04-28 05:57:50,958 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/handlers/main.yml' 2023-04-28 05:57:50,958 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/meta/.galaxy_install_info' 2023-04-28 05:57:50,959 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/meta/main.yml' 2023-04-28 05:57:50,959 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/tasks/main.yml' 2023-04-28 05:57:50,959 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/templates/os10_prefix_list.j2' 2023-04-28 05:57:50,959 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/inventory.yaml' 2023-04-28 05:57:50,960 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/main.os10.yaml' 2023-04-28 05:57:50,960 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/tests/test.yaml' 2023-04-28 05:57:50,960 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_prefix_list/vars/main.yml' 2023-04-28 05:57:50,960 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/LICENSE' 2023-04-28 05:57:50,961 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/README.md' 2023-04-28 05:57:50,961 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/defaults/main.yml' 2023-04-28 05:57:50,961 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/handlers/main.yml' 2023-04-28 05:57:50,962 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/meta/main.yml' 2023-04-28 05:57:50,962 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/tasks/main.yml' 2023-04-28 05:57:50,962 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/templates/os10_qos.j2' 2023-04-28 05:57:50,962 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/tests/inventory' 2023-04-28 05:57:50,963 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/tests/main.os10.yaml' 2023-04-28 05:57:50,963 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/tests/test.yml' 2023-04-28 05:57:50,963 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_qos/vars/main.yml' 2023-04-28 05:57:50,963 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/LICENSE' 2023-04-28 05:57:50,964 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/README.md' 2023-04-28 05:57:50,964 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/defaults/main.yml' 2023-04-28 05:57:50,964 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/handlers/main.yml' 2023-04-28 05:57:50,965 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/meta/main.yml' 2023-04-28 05:57:50,965 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/tasks/main.yml' 2023-04-28 05:57:50,965 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/templates/os10_raguard.j2' 2023-04-28 05:57:50,965 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/tests/inventory.yaml' 2023-04-28 05:57:50,966 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/tests/main.os10.yaml' 2023-04-28 05:57:50,966 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/tests/test.yaml' 2023-04-28 05:57:50,966 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_raguard/vars/main.yml' 2023-04-28 05:57:50,966 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/LICENSE' 2023-04-28 05:57:50,967 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/README.md' 2023-04-28 05:57:50,967 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/defaults/main.yml' 2023-04-28 05:57:50,967 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/handlers/main.yml' 2023-04-28 05:57:50,968 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/meta/main.yml' 2023-04-28 05:57:50,968 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/tasks/main.yml' 2023-04-28 05:57:50,968 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/templates/os10_route_map.j2' 2023-04-28 05:57:50,968 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/tests/inventory' 2023-04-28 05:57:50,969 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/tests/main.yaml' 2023-04-28 05:57:50,969 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/tests/test.yml' 2023-04-28 05:57:50,969 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_route_map/vars/main.yml' 2023-04-28 05:57:50,970 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/LICENSE' 2023-04-28 05:57:50,970 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/README.md' 2023-04-28 05:57:50,970 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/defaults/main.yml' 2023-04-28 05:57:50,971 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/handlers/main.yml' 2023-04-28 05:57:50,971 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/meta/main.yml' 2023-04-28 05:57:50,971 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/tasks/main.yml' 2023-04-28 05:57:50,971 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/templates/os10_snmp.j2' 2023-04-28 05:57:50,972 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/tests/inventory.yaml' 2023-04-28 05:57:50,972 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/tests/main.os10.yaml' 2023-04-28 05:57:50,972 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/tests/test.yaml' 2023-04-28 05:57:50,972 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_snmp/vars/main.yml' 2023-04-28 05:57:50,973 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/LICENSE' 2023-04-28 05:57:50,973 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/README.md' 2023-04-28 05:57:50,974 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/defaults/main.yml' 2023-04-28 05:57:50,974 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/handlers/main.yml' 2023-04-28 05:57:50,974 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/meta/main.yml' 2023-04-28 05:57:50,974 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/tasks/main.yml' 2023-04-28 05:57:50,975 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/templates/os10_system.j2' 2023-04-28 05:57:50,975 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/tests/inventory.yaml' 2023-04-28 05:57:50,975 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/tests/main.os10.yaml' 2023-04-28 05:57:50,975 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/tests/test.yaml' 2023-04-28 05:57:50,975 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_system/vars/main.yml' 2023-04-28 05:57:50,976 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/LICENSE' 2023-04-28 05:57:50,976 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/README.md' 2023-04-28 05:57:50,976 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/meta/main.yml' 2023-04-28 05:57:50,977 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/main.yml' 2023-04-28 05:57:50,977 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_bgp_summary.yaml' 2023-04-28 05:57:50,977 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_interface_brief.yaml' 2023-04-28 05:57:50,977 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_ip_vrf.yaml' 2023-04-28 05:57:50,978 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_lldp_neighbors.yaml' 2023-04-28 05:57:50,978 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_port-channel_summary.yaml' 2023-04-28 05:57:50,978 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_spanning_tree_compatibility_mode.yaml' 2023-04-28 05:57:50,978 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_vlan.yaml' 2023-04-28 05:57:50,978 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/show_vlt_err_disabled_ports.yaml' 2023-04-28 05:57:50,979 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tasks/textfsm.yaml' 2023-04-28 05:57:50,979 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_bgp_summary.template' 2023-04-28 05:57:50,979 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_interface_brief.template' 2023-04-28 05:57:50,979 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_ip_vrf.template' 2023-04-28 05:57:50,980 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_lldp_neighbors.template' 2023-04-28 05:57:50,980 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_port-channel_summary.template' 2023-04-28 05:57:50,980 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_spanning_tree_compatibility_mode.template' 2023-04-28 05:57:50,980 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_vlan.template' 2023-04-28 05:57:50,980 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/templates/os10_show_vlt_err_disabled_ports.template' 2023-04-28 05:57:50,981 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tests/inventory.yaml' 2023-04-28 05:57:50,981 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tests/main.yaml' 2023-04-28 05:57:50,981 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tests/test.yaml' 2023-04-28 05:57:50,981 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_template/tests/group_vars/all' 2023-04-28 05:57:50,982 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/LICENSE' 2023-04-28 05:57:50,982 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/README.md' 2023-04-28 05:57:50,982 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/defaults/main.yml' 2023-04-28 05:57:50,983 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/handlers/main.yml' 2023-04-28 05:57:50,983 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/meta/main.yml' 2023-04-28 05:57:50,983 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/tasks/main.yml' 2023-04-28 05:57:50,983 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/templates/os10_uplink.j2' 2023-04-28 05:57:50,984 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/tests/inventory.yaml' 2023-04-28 05:57:50,984 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/tests/main.yaml' 2023-04-28 05:57:50,984 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/tests/test.yaml' 2023-04-28 05:57:50,984 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_uplink/vars/main.yml' 2023-04-28 05:57:50,985 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/LICENSE' 2023-04-28 05:57:50,985 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/README.md' 2023-04-28 05:57:50,985 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/defaults/main.yml' 2023-04-28 05:57:50,986 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/handlers/main.yml' 2023-04-28 05:57:50,986 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/meta/main.yml' 2023-04-28 05:57:50,986 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/tasks/main.yml' 2023-04-28 05:57:50,986 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/templates/os10_users.j2' 2023-04-28 05:57:50,987 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/tests/inventory.yaml' 2023-04-28 05:57:50,987 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/tests/main.os10.yaml' 2023-04-28 05:57:50,987 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/tests/test.yaml' 2023-04-28 05:57:50,987 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_users/vars/main.yml' 2023-04-28 05:57:50,988 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/LICENSE' 2023-04-28 05:57:50,988 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/README.md' 2023-04-28 05:57:50,988 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/defaults/main.yml' 2023-04-28 05:57:50,989 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/handlers/main.yml' 2023-04-28 05:57:50,989 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/meta/main.yml' 2023-04-28 05:57:50,989 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/tasks/main.yml' 2023-04-28 05:57:50,989 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/templates/os10_vlan.j2' 2023-04-28 05:57:50,990 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/tests/inventory.yaml' 2023-04-28 05:57:50,990 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/tests/main.os10.yaml' 2023-04-28 05:57:50,990 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/tests/test.yaml' 2023-04-28 05:57:50,990 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlan/vars/main.yml' 2023-04-28 05:57:50,991 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/LICENSE' 2023-04-28 05:57:50,991 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/README.md' 2023-04-28 05:57:50,991 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/defaults/main.yml' 2023-04-28 05:57:50,992 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/handlers/main.yml' 2023-04-28 05:57:50,992 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/meta/main.yml' 2023-04-28 05:57:50,992 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/tasks/main.yml' 2023-04-28 05:57:50,992 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/templates/os10_vlt.j2' 2023-04-28 05:57:50,993 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/tests/inventory.yaml' 2023-04-28 05:57:50,993 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/tests/main.os10.yaml' 2023-04-28 05:57:50,993 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/tests/test.yaml' 2023-04-28 05:57:50,993 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vlt/vars/main.yml' 2023-04-28 05:57:50,994 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/LICENSE' 2023-04-28 05:57:50,994 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/README.md' 2023-04-28 05:57:50,994 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/defaults/main.yml' 2023-04-28 05:57:50,995 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/handlers/main.yml' 2023-04-28 05:57:50,995 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/meta/main.yml' 2023-04-28 05:57:50,995 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/tasks/main.yml' 2023-04-28 05:57:50,995 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/templates/os10_vrf.j2' 2023-04-28 05:57:50,996 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/tests/inventory.yaml' 2023-04-28 05:57:50,996 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/tests/main.os10.yaml' 2023-04-28 05:57:50,996 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/tests/test.yaml' 2023-04-28 05:57:50,996 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrf/vars/main.yml' 2023-04-28 05:57:50,997 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/LICENSE' 2023-04-28 05:57:50,997 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/README.md' 2023-04-28 05:57:50,997 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/defaults/main.yml' 2023-04-28 05:57:50,998 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/handlers/main.yml' 2023-04-28 05:57:50,998 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/meta/main.yml' 2023-04-28 05:57:50,998 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/tasks/main.yml' 2023-04-28 05:57:50,998 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/templates/os10_vrrp.j2' 2023-04-28 05:57:50,999 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/tests/inventory.yaml' 2023-04-28 05:57:50,999 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/tests/main.os10.yaml' 2023-04-28 05:57:50,999 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/tests/test.yaml' 2023-04-28 05:57:50,999 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vrrp/vars/main.yml' 2023-04-28 05:57:51,000 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/LICENSE' 2023-04-28 05:57:51,000 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/README.md' 2023-04-28 05:57:51,000 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/defaults/main.yml' 2023-04-28 05:57:51,001 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/handlers/main.yml' 2023-04-28 05:57:51,001 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/meta/main.yml' 2023-04-28 05:57:51,001 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/tasks/main.yml' 2023-04-28 05:57:51,002 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/templates/os10_vxlan.j2' 2023-04-28 05:57:51,002 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/tests/inventory.yaml' 2023-04-28 05:57:51,002 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/tests/main.yaml' 2023-04-28 05:57:51,002 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/tests/test.yml' 2023-04-28 05:57:51,003 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_vxlan/vars/main.yml' 2023-04-28 05:57:51,003 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/LICENSE' 2023-04-28 05:57:51,003 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/README.md' 2023-04-28 05:57:51,004 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/defaults/main.yml' 2023-04-28 05:57:51,004 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/handlers/main.yml' 2023-04-28 05:57:51,004 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/meta/main.yml' 2023-04-28 05:57:51,005 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/tasks/main.yml' 2023-04-28 05:57:51,005 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/templates/os10_xstp.j2' 2023-04-28 05:57:51,005 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/tests/inventory.yaml' 2023-04-28 05:57:51,006 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/tests/main.yaml' 2023-04-28 05:57:51,006 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/tests/test.yaml' 2023-04-28 05:57:51,006 wheel INFO adding 'ansible_collections/dellemc/os10/roles/os10_xstp/vars/main.yml' 2023-04-28 05:57:51,006 wheel INFO adding 'ansible_collections/dellemc/os6/COPYING' 2023-04-28 05:57:51,007 wheel INFO adding 'ansible_collections/dellemc/os6/FILES.json' 2023-04-28 05:57:51,008 wheel INFO adding 'ansible_collections/dellemc/os6/LICENSE' 2023-04-28 05:57:51,008 wheel INFO adding 'ansible_collections/dellemc/os6/MANIFEST.json' 2023-04-28 05:57:51,008 wheel INFO adding 'ansible_collections/dellemc/os6/README.md' 2023-04-28 05:57:51,008 wheel INFO adding 'ansible_collections/dellemc/os6/changelogs/CHANGELOG.rst' 2023-04-28 05:57:51,009 wheel INFO adding 'ansible_collections/dellemc/os6/changelogs/changelog.yaml' 2023-04-28 05:57:51,009 wheel INFO adding 'ansible_collections/dellemc/os6/changelogs/config.yaml' 2023-04-28 05:57:51,009 wheel INFO adding 'ansible_collections/dellemc/os6/meta/runtime.yml' 2023-04-28 05:57:51,009 wheel INFO adding 'ansible_collections/dellemc/os6/playbooks/ibgp/README.md' 2023-04-28 05:57:51,010 wheel INFO adding 'ansible_collections/dellemc/os6/playbooks/ibgp/inventory.yaml' 2023-04-28 05:57:51,010 wheel INFO adding 'ansible_collections/dellemc/os6/playbooks/ibgp/os6switch.yaml' 2023-04-28 05:57:51,010 wheel INFO adding 'ansible_collections/dellemc/os6/playbooks/ibgp/group_vars/all' 2023-04-28 05:57:51,010 wheel INFO adding 'ansible_collections/dellemc/os6/playbooks/ibgp/host_vars/switch1.yaml' 2023-04-28 05:57:51,011 wheel INFO adding 'ansible_collections/dellemc/os6/playbooks/ibgp/host_vars/switch2.yaml' 2023-04-28 05:57:51,011 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/action/__init__.py' 2023-04-28 05:57:51,011 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/action/os6.py' 2023-04-28 05:57:51,011 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/cliconf/__init__.py' 2023-04-28 05:57:51,012 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/cliconf/os6.py' 2023-04-28 05:57:51,012 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:51,012 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/doc_fragments/os6.py' 2023-04-28 05:57:51,012 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:51,013 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/module_utils/network/os6.py' 2023-04-28 05:57:51,013 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/modules/__init__.py' 2023-04-28 05:57:51,013 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/modules/os6_command.py' 2023-04-28 05:57:51,014 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/modules/os6_config.py' 2023-04-28 05:57:51,014 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/modules/os6_facts.py' 2023-04-28 05:57:51,014 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/terminal/__init__.py' 2023-04-28 05:57:51,014 wheel INFO adding 'ansible_collections/dellemc/os6/plugins/terminal/os6.py' 2023-04-28 05:57:51,015 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/LICENSE' 2023-04-28 05:57:51,015 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/README.md' 2023-04-28 05:57:51,016 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/defaults/main.yml' 2023-04-28 05:57:51,016 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/handlers/main.yml' 2023-04-28 05:57:51,016 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/meta/main.yml' 2023-04-28 05:57:51,016 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/tasks/main.yml' 2023-04-28 05:57:51,017 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/templates/os6_aaa.j2' 2023-04-28 05:57:51,017 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/tests/inventory.yaml' 2023-04-28 05:57:51,017 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/tests/main.os6.yaml' 2023-04-28 05:57:51,017 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/tests/test.yaml' 2023-04-28 05:57:51,018 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_aaa/vars/main.yml' 2023-04-28 05:57:51,018 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/LICENSE' 2023-04-28 05:57:51,018 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/README.md' 2023-04-28 05:57:51,019 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/defaults/main.yml' 2023-04-28 05:57:51,019 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/handlers/main.yml' 2023-04-28 05:57:51,019 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/meta/main.yml' 2023-04-28 05:57:51,019 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/tasks/main.yml' 2023-04-28 05:57:51,020 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/templates/os6_acl.j2' 2023-04-28 05:57:51,020 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/tests/inventory.yaml' 2023-04-28 05:57:51,020 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/tests/main.os6.yaml' 2023-04-28 05:57:51,020 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/tests/test.yaml' 2023-04-28 05:57:51,021 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_acl/vars/main.yml' 2023-04-28 05:57:51,021 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/LICENSE' 2023-04-28 05:57:51,021 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/README.md' 2023-04-28 05:57:51,022 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/defaults/main.yml' 2023-04-28 05:57:51,022 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/handlers/main.yml' 2023-04-28 05:57:51,022 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/meta/main.yml' 2023-04-28 05:57:51,022 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/tasks/main.yml' 2023-04-28 05:57:51,023 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/templates/os6_bgp.j2' 2023-04-28 05:57:51,023 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/tests/inventory.yaml' 2023-04-28 05:57:51,023 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/tests/main.os6.yaml' 2023-04-28 05:57:51,023 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/tests/test.yaml' 2023-04-28 05:57:51,024 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_bgp/vars/main.yml' 2023-04-28 05:57:51,024 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/LICENSE' 2023-04-28 05:57:51,024 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/README.md' 2023-04-28 05:57:51,025 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/defaults/main.yml' 2023-04-28 05:57:51,025 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/handlers/main.yml' 2023-04-28 05:57:51,025 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/meta/main.yml' 2023-04-28 05:57:51,026 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/tasks/main.yml' 2023-04-28 05:57:51,026 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/templates/os6_interface.j2' 2023-04-28 05:57:51,026 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/tests/inventory.yaml' 2023-04-28 05:57:51,026 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/tests/main.os6.yaml' 2023-04-28 05:57:51,027 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/tests/test.yaml' 2023-04-28 05:57:51,027 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_interface/vars/main.yml' 2023-04-28 05:57:51,027 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/LICENSE' 2023-04-28 05:57:51,028 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/README.md' 2023-04-28 05:57:51,028 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/defaults/main.yml' 2023-04-28 05:57:51,028 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/handlers/main.yml' 2023-04-28 05:57:51,028 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/meta/main.yml' 2023-04-28 05:57:51,029 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/tasks/main.yml' 2023-04-28 05:57:51,029 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/templates/os6_lag.j2' 2023-04-28 05:57:51,029 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/tests/inventory.yaml' 2023-04-28 05:57:51,029 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/tests/main.os6.yaml' 2023-04-28 05:57:51,030 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/tests/test.yaml' 2023-04-28 05:57:51,030 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lag/vars/main.yml' 2023-04-28 05:57:51,030 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/LICENSE' 2023-04-28 05:57:51,031 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/README.md' 2023-04-28 05:57:51,031 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/defaults/main.yml' 2023-04-28 05:57:51,031 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/handlers/main.yml' 2023-04-28 05:57:51,031 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/meta/main.yml' 2023-04-28 05:57:51,032 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/tasks/main.yml' 2023-04-28 05:57:51,032 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/templates/os6_lldp.j2' 2023-04-28 05:57:51,032 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/tests/inventory.yaml' 2023-04-28 05:57:51,032 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/tests/main.os6.yaml' 2023-04-28 05:57:51,033 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/tests/test.yaml' 2023-04-28 05:57:51,033 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_lldp/vars/main.yml' 2023-04-28 05:57:51,033 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/LICENSE' 2023-04-28 05:57:51,034 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/README.md' 2023-04-28 05:57:51,034 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/defaults/main.yml' 2023-04-28 05:57:51,034 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/handlers/main.yml' 2023-04-28 05:57:51,034 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/meta/main.yml' 2023-04-28 05:57:51,035 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/tasks/main.yml' 2023-04-28 05:57:51,035 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/templates/os6_logging.j2' 2023-04-28 05:57:51,035 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/tests/inventory.yaml' 2023-04-28 05:57:51,035 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/tests/main.os6.yaml' 2023-04-28 05:57:51,036 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/tests/test.yaml' 2023-04-28 05:57:51,036 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_logging/vars/main.yml' 2023-04-28 05:57:51,036 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/LICENSE' 2023-04-28 05:57:51,037 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/README.md' 2023-04-28 05:57:51,037 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/defaults/main.yml' 2023-04-28 05:57:51,037 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/handlers/main.yml' 2023-04-28 05:57:51,037 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/meta/main.yml' 2023-04-28 05:57:51,038 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/tasks/main.yml' 2023-04-28 05:57:51,038 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/templates/os6_ntp.j2' 2023-04-28 05:57:51,038 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/tests/inventory' 2023-04-28 05:57:51,038 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/tests/main.os6.yaml' 2023-04-28 05:57:51,038 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/tests/test.yml' 2023-04-28 05:57:51,039 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_ntp/vars/main.yml' 2023-04-28 05:57:51,039 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/LICENSE' 2023-04-28 05:57:51,039 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/README.md' 2023-04-28 05:57:51,040 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/defaults/main.yml' 2023-04-28 05:57:51,040 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/handlers/main.yml' 2023-04-28 05:57:51,040 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/meta/main.yml' 2023-04-28 05:57:51,041 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/tasks/main.yml' 2023-04-28 05:57:51,041 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/templates/os6_qos.j2' 2023-04-28 05:57:51,041 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/tests/inventory' 2023-04-28 05:57:51,041 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/tests/main.os6.yaml' 2023-04-28 05:57:51,041 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/tests/test.yml' 2023-04-28 05:57:51,042 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_qos/vars/main.yml' 2023-04-28 05:57:51,042 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/LICENSE' 2023-04-28 05:57:51,042 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/README.md' 2023-04-28 05:57:51,043 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/defaults/main.yml' 2023-04-28 05:57:51,043 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/handlers/main.yml' 2023-04-28 05:57:51,043 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/meta/main.yml' 2023-04-28 05:57:51,043 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/tasks/main.yml' 2023-04-28 05:57:51,044 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/templates/os6_snmp.j2' 2023-04-28 05:57:51,044 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/tests/inventory.yaml' 2023-04-28 05:57:51,044 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/tests/main.os6.yaml' 2023-04-28 05:57:51,044 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/tests/test.yaml' 2023-04-28 05:57:51,045 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_snmp/vars/main.yml' 2023-04-28 05:57:51,045 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/LICENSE' 2023-04-28 05:57:51,045 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/README.md' 2023-04-28 05:57:51,046 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/defaults/main.yml' 2023-04-28 05:57:51,046 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/handlers/main.yml' 2023-04-28 05:57:51,046 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/meta/main.yml' 2023-04-28 05:57:51,046 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/tasks/main.yml' 2023-04-28 05:57:51,047 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/templates/os6_system.j2' 2023-04-28 05:57:51,047 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/tests/inventory.yaml' 2023-04-28 05:57:51,047 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/tests/main.os6.yaml' 2023-04-28 05:57:51,047 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/tests/test.yaml' 2023-04-28 05:57:51,048 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_system/vars/main.yml' 2023-04-28 05:57:51,048 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/LICENSE' 2023-04-28 05:57:51,048 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/README.md' 2023-04-28 05:57:51,049 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/defaults/main.yml' 2023-04-28 05:57:51,049 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/handlers/main.yml' 2023-04-28 05:57:51,049 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/meta/main.yml' 2023-04-28 05:57:51,049 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/tasks/main.yml' 2023-04-28 05:57:51,050 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/templates/os6_users.j2' 2023-04-28 05:57:51,050 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/tests/inventory.yaml' 2023-04-28 05:57:51,050 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/tests/main.os6.yaml' 2023-04-28 05:57:51,050 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/tests/test.yaml' 2023-04-28 05:57:51,051 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_users/vars/main.yml' 2023-04-28 05:57:51,051 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/LICENSE' 2023-04-28 05:57:51,051 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/README.md' 2023-04-28 05:57:51,052 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/defaults/main.yml' 2023-04-28 05:57:51,052 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/handlers/main.yml' 2023-04-28 05:57:51,052 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/meta/main.yml' 2023-04-28 05:57:51,052 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/tasks/main.yml' 2023-04-28 05:57:51,053 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/templates/os6_vlan.j2' 2023-04-28 05:57:51,053 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/tests/inventory.yaml' 2023-04-28 05:57:51,053 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/tests/main.os6.yaml' 2023-04-28 05:57:51,053 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/tests/test.yaml' 2023-04-28 05:57:51,054 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vlan/vars/main.yml' 2023-04-28 05:57:51,054 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/LICENSE' 2023-04-28 05:57:51,054 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/README.md' 2023-04-28 05:57:51,055 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/defaults/main.yml' 2023-04-28 05:57:51,055 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/handlers/main.yml' 2023-04-28 05:57:51,055 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/meta/main.yml' 2023-04-28 05:57:51,055 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/tasks/main.yml' 2023-04-28 05:57:51,056 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/templates/os6_vrrp.j2' 2023-04-28 05:57:51,056 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/tests/inventory.yaml' 2023-04-28 05:57:51,056 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/tests/main.os6.yaml' 2023-04-28 05:57:51,056 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/tests/test.yaml' 2023-04-28 05:57:51,057 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_vrrp/vars/main.yml' 2023-04-28 05:57:51,057 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/LICENSE' 2023-04-28 05:57:51,057 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/README.md' 2023-04-28 05:57:51,058 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/defaults/main.yml' 2023-04-28 05:57:51,058 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/handlers/main.yml' 2023-04-28 05:57:51,059 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/meta/main.yml' 2023-04-28 05:57:51,059 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/tasks/main.yml' 2023-04-28 05:57:51,059 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/templates/os6_xstp.j2' 2023-04-28 05:57:51,059 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/tests/inventory.yaml' 2023-04-28 05:57:51,060 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/tests/main.os6.yaml' 2023-04-28 05:57:51,060 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/tests/test.yaml' 2023-04-28 05:57:51,060 wheel INFO adding 'ansible_collections/dellemc/os6/roles/os6_xstp/vars/main.yml' 2023-04-28 05:57:51,060 wheel INFO adding 'ansible_collections/dellemc/os9/COPYING' 2023-04-28 05:57:51,061 wheel INFO adding 'ansible_collections/dellemc/os9/FILES.json' 2023-04-28 05:57:51,062 wheel INFO adding 'ansible_collections/dellemc/os9/LICENSE' 2023-04-28 05:57:51,062 wheel INFO adding 'ansible_collections/dellemc/os9/MANIFEST.json' 2023-04-28 05:57:51,062 wheel INFO adding 'ansible_collections/dellemc/os9/README.md' 2023-04-28 05:57:51,063 wheel INFO adding 'ansible_collections/dellemc/os9/changelogs/CHANGELOG.rst' 2023-04-28 05:57:51,063 wheel INFO adding 'ansible_collections/dellemc/os9/changelogs/changelog.yaml' 2023-04-28 05:57:51,063 wheel INFO adding 'ansible_collections/dellemc/os9/changelogs/config.yaml' 2023-04-28 05:57:51,063 wheel INFO adding 'ansible_collections/dellemc/os9/meta/runtime.yml' 2023-04-28 05:57:51,064 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/README.md' 2023-04-28 05:57:51,064 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/datacenter.yaml' 2023-04-28 05:57:51,064 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/inventory.yaml' 2023-04-28 05:57:51,064 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars/all' 2023-04-28 05:57:51,065 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/group_vars/spine.yaml' 2023-04-28 05:57:51,065 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf1.yaml' 2023-04-28 05:57:51,065 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf2.yaml' 2023-04-28 05:57:51,065 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf3.yaml' 2023-04-28 05:57:51,066 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/leaf4.yaml' 2023-04-28 05:57:51,066 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/spine1.yaml' 2023-04-28 05:57:51,066 wheel INFO adding 'ansible_collections/dellemc/os9/playbooks/clos_fabric_ebgp/host_vars/spine2.yaml' 2023-04-28 05:57:51,066 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/action/__init__.py' 2023-04-28 05:57:51,067 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/action/os9.py' 2023-04-28 05:57:51,067 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/cliconf/__init__.py' 2023-04-28 05:57:51,067 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/cliconf/os9.py' 2023-04-28 05:57:51,067 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:51,067 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/doc_fragments/os9.py' 2023-04-28 05:57:51,068 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/module_utils/__init__.py' 2023-04-28 05:57:51,068 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:51,068 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/module_utils/network/os9.py' 2023-04-28 05:57:51,069 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/modules/__init__.py' 2023-04-28 05:57:51,069 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/modules/os9_command.py' 2023-04-28 05:57:51,069 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/modules/os9_config.py' 2023-04-28 05:57:51,069 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/modules/os9_facts.py' 2023-04-28 05:57:51,070 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/terminal/__init__.py' 2023-04-28 05:57:51,070 wheel INFO adding 'ansible_collections/dellemc/os9/plugins/terminal/os9.py' 2023-04-28 05:57:51,070 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/LICENSE' 2023-04-28 05:57:51,071 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/README.md' 2023-04-28 05:57:51,071 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/defaults/main.yml' 2023-04-28 05:57:51,071 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/handlers/main.yml' 2023-04-28 05:57:51,072 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/meta/main.yml' 2023-04-28 05:57:51,072 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/tasks/main.yml' 2023-04-28 05:57:51,072 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/templates/os9_aaa.j2' 2023-04-28 05:57:51,073 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/tests/inventory.yaml' 2023-04-28 05:57:51,073 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/tests/main.os6.yaml' 2023-04-28 05:57:51,073 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/tests/test.yaml' 2023-04-28 05:57:51,073 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_aaa/vars/main.yml' 2023-04-28 05:57:51,074 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/LICENSE' 2023-04-28 05:57:51,074 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/README.md' 2023-04-28 05:57:51,075 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/defaults/main.yml' 2023-04-28 05:57:51,075 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/handlers/main.yml' 2023-04-28 05:57:51,075 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/meta/main.yml' 2023-04-28 05:57:51,075 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/tasks/main.yml' 2023-04-28 05:57:51,076 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/templates/os9_acl.j2' 2023-04-28 05:57:51,076 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/tests/inventory.yaml' 2023-04-28 05:57:51,076 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/tests/main.os9.yaml' 2023-04-28 05:57:51,076 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/tests/test.yaml' 2023-04-28 05:57:51,077 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_acl/vars/main.yml' 2023-04-28 05:57:51,077 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/LICENSE' 2023-04-28 05:57:51,077 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/README.md' 2023-04-28 05:57:51,078 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/defaults/main.yml' 2023-04-28 05:57:51,078 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/handlers/main.yml' 2023-04-28 05:57:51,078 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/meta/main.yml' 2023-04-28 05:57:51,078 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/tasks/main.yml' 2023-04-28 05:57:51,079 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/templates/os9_bgp.j2' 2023-04-28 05:57:51,079 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/tests/inventory.yaml' 2023-04-28 05:57:51,079 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/tests/main.os9.yaml' 2023-04-28 05:57:51,079 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/tests/test.yaml' 2023-04-28 05:57:51,080 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_bgp/vars/main.yml' 2023-04-28 05:57:51,080 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/LICENSE' 2023-04-28 05:57:51,080 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/README.md' 2023-04-28 05:57:51,081 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/defaults/main.yml' 2023-04-28 05:57:51,081 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/handlers/main.yml' 2023-04-28 05:57:51,081 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/meta/main.yml' 2023-04-28 05:57:51,081 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/tasks/main.yml' 2023-04-28 05:57:51,082 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/templates/os9_copy_config.j2' 2023-04-28 05:57:51,082 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/tests/inventory.yaml' 2023-04-28 05:57:51,082 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/tests/main.os9.yaml' 2023-04-28 05:57:51,082 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/tests/test.yaml' 2023-04-28 05:57:51,083 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_copy_config/vars/main.yml' 2023-04-28 05:57:51,083 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/LICENSE' 2023-04-28 05:57:51,083 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/README.md' 2023-04-28 05:57:51,084 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/defaults/main.yml' 2023-04-28 05:57:51,084 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/handlers/main.yml' 2023-04-28 05:57:51,084 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/meta/main.yml' 2023-04-28 05:57:51,084 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/tasks/main.yml' 2023-04-28 05:57:51,085 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/templates/os9_dcb.j2' 2023-04-28 05:57:51,085 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/tests/inventory.yaml' 2023-04-28 05:57:51,085 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/tests/main.os9.yaml' 2023-04-28 05:57:51,085 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/tests/test.yaml' 2023-04-28 05:57:51,086 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dcb/vars/main.yml' 2023-04-28 05:57:51,086 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/LICENSE' 2023-04-28 05:57:51,086 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/README.md' 2023-04-28 05:57:51,087 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/defaults/main.yml' 2023-04-28 05:57:51,087 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/handlers/main.yml' 2023-04-28 05:57:51,087 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/meta/main.yml' 2023-04-28 05:57:51,087 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/tasks/main.yml' 2023-04-28 05:57:51,087 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/templates/os9_dns.j2' 2023-04-28 05:57:51,088 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/tests/inventory.yaml' 2023-04-28 05:57:51,088 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/tests/main.os9.yaml' 2023-04-28 05:57:51,088 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/tests/test.yaml' 2023-04-28 05:57:51,088 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_dns/vars/main.yml' 2023-04-28 05:57:51,089 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/LICENSE' 2023-04-28 05:57:51,089 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/README.md' 2023-04-28 05:57:51,089 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/defaults/main.yml' 2023-04-28 05:57:51,090 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/handlers/main.yml' 2023-04-28 05:57:51,090 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/meta/main.yml' 2023-04-28 05:57:51,090 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/tasks/main.yml' 2023-04-28 05:57:51,090 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/templates/os9_ecmp.j2' 2023-04-28 05:57:51,091 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/tests/inventory.yaml' 2023-04-28 05:57:51,091 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/tests/main.os9.yaml' 2023-04-28 05:57:51,091 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/tests/test.yaml' 2023-04-28 05:57:51,091 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ecmp/vars/main.yml' 2023-04-28 05:57:51,092 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/LICENSE' 2023-04-28 05:57:51,092 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/README.md' 2023-04-28 05:57:51,092 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/defaults/main.yml' 2023-04-28 05:57:51,093 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/handlers/main.yml' 2023-04-28 05:57:51,093 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/meta/main.yml' 2023-04-28 05:57:51,093 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/tasks/main.yml' 2023-04-28 05:57:51,094 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/templates/os9_interface.j2' 2023-04-28 05:57:51,094 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/tests/inventory.yaml' 2023-04-28 05:57:51,094 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/tests/main.os9.yaml' 2023-04-28 05:57:51,094 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/tests/test.yaml' 2023-04-28 05:57:51,094 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_interface/vars/main.yml' 2023-04-28 05:57:51,095 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/LICENSE' 2023-04-28 05:57:51,095 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/README.md' 2023-04-28 05:57:51,095 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/defaults/main.yml' 2023-04-28 05:57:51,096 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/handlers/main.yml' 2023-04-28 05:57:51,096 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/meta/main.yml' 2023-04-28 05:57:51,096 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/tasks/main.yml' 2023-04-28 05:57:51,096 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/templates/os9_lag.j2' 2023-04-28 05:57:51,097 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/tests/inventory.yaml' 2023-04-28 05:57:51,097 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/tests/main.os9.yaml' 2023-04-28 05:57:51,097 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/tests/test.yaml' 2023-04-28 05:57:51,097 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lag/vars/main.yml' 2023-04-28 05:57:51,098 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/LICENSE' 2023-04-28 05:57:51,098 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/README.md' 2023-04-28 05:57:51,098 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/defaults/main.yml' 2023-04-28 05:57:51,099 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/handlers/main.yml' 2023-04-28 05:57:51,099 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/meta/main.yml' 2023-04-28 05:57:51,099 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/tasks/main.yml' 2023-04-28 05:57:51,099 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/templates/os9_lldp.j2' 2023-04-28 05:57:51,100 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/tests/inventory.yaml' 2023-04-28 05:57:51,100 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/tests/main.os9.yaml' 2023-04-28 05:57:51,100 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/tests/test.yaml' 2023-04-28 05:57:51,100 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_lldp/vars/main.yml' 2023-04-28 05:57:51,101 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/LICENSE' 2023-04-28 05:57:51,101 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/README.md' 2023-04-28 05:57:51,101 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/defaults/main.yml' 2023-04-28 05:57:51,102 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/handlers/main.yml' 2023-04-28 05:57:51,102 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/meta/main.yml' 2023-04-28 05:57:51,102 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/tasks/main.yml' 2023-04-28 05:57:51,102 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/templates/os9_logging.j2' 2023-04-28 05:57:51,103 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/tests/inventory.yaml' 2023-04-28 05:57:51,103 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/tests/main.os9.yaml' 2023-04-28 05:57:51,103 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/tests/test.yaml' 2023-04-28 05:57:51,103 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_logging/vars/main.yml' 2023-04-28 05:57:51,104 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/LICENSE' 2023-04-28 05:57:51,104 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/README.md' 2023-04-28 05:57:51,104 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/defaults/main.yml' 2023-04-28 05:57:51,105 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/handlers/main.yml' 2023-04-28 05:57:51,105 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/meta/main.yml' 2023-04-28 05:57:51,105 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/tasks/main.yml' 2023-04-28 05:57:51,105 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/templates/os9_ntp.j2' 2023-04-28 05:57:51,106 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/tests/inventory.yaml' 2023-04-28 05:57:51,106 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/tests/main.os9.yaml' 2023-04-28 05:57:51,106 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/tests/test.yaml' 2023-04-28 05:57:51,106 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_ntp/vars/main.yml' 2023-04-28 05:57:51,107 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/LICENSE' 2023-04-28 05:57:51,107 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/README.md' 2023-04-28 05:57:51,107 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/defaults/main.yml' 2023-04-28 05:57:51,107 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/handlers/main.yml' 2023-04-28 05:57:51,108 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/meta/main.yml' 2023-04-28 05:57:51,108 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/tasks/main.yml' 2023-04-28 05:57:51,108 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/templates/os9_prefix_list.j2' 2023-04-28 05:57:51,108 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/inventory.yaml' 2023-04-28 05:57:51,109 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/main.os9.yaml' 2023-04-28 05:57:51,109 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/tests/test.yaml' 2023-04-28 05:57:51,109 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_prefix_list/vars/main.yml' 2023-04-28 05:57:51,109 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/LICENSE' 2023-04-28 05:57:51,110 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/README.md' 2023-04-28 05:57:51,110 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/defaults/main.yml' 2023-04-28 05:57:51,110 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/handlers/main.yml' 2023-04-28 05:57:51,111 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/meta/main.yml' 2023-04-28 05:57:51,111 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/tasks/main.yml' 2023-04-28 05:57:51,111 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/templates/os9_sflow.j2' 2023-04-28 05:57:51,111 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/tests/inventory.yaml' 2023-04-28 05:57:51,112 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/tests/main.os9.yaml' 2023-04-28 05:57:51,112 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/tests/test.yaml' 2023-04-28 05:57:51,112 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_sflow/vars/main.yml' 2023-04-28 05:57:51,112 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/LICENSE' 2023-04-28 05:57:51,113 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/README.md' 2023-04-28 05:57:51,113 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/defaults/main.yml' 2023-04-28 05:57:51,113 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/handlers/main.yml' 2023-04-28 05:57:51,114 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/meta/main.yml' 2023-04-28 05:57:51,114 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/tasks/main.yml' 2023-04-28 05:57:51,114 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/templates/os9_snmp.j2' 2023-04-28 05:57:51,115 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/tests/inventory.yaml' 2023-04-28 05:57:51,115 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/tests/main.os9.yaml' 2023-04-28 05:57:51,115 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/tests/test.yaml' 2023-04-28 05:57:51,115 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_snmp/vars/main.yml' 2023-04-28 05:57:51,116 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/LICENSE' 2023-04-28 05:57:51,116 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/README.md' 2023-04-28 05:57:51,116 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/defaults/main.yml' 2023-04-28 05:57:51,117 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/handlers/main.yml' 2023-04-28 05:57:51,117 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/meta/main.yml' 2023-04-28 05:57:51,117 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/tasks/main.yml' 2023-04-28 05:57:51,117 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/templates/os9_system.j2' 2023-04-28 05:57:51,118 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/tests/inventory.yaml' 2023-04-28 05:57:51,118 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/tests/main.os9.yaml' 2023-04-28 05:57:51,118 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/tests/test.yaml' 2023-04-28 05:57:51,118 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_system/vars/main.yml' 2023-04-28 05:57:51,119 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/LICENSE' 2023-04-28 05:57:51,119 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/README.md' 2023-04-28 05:57:51,119 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/defaults/main.yml' 2023-04-28 05:57:51,120 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/handlers/main.yml' 2023-04-28 05:57:51,120 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/meta/main.yml' 2023-04-28 05:57:51,120 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/tasks/main.yml' 2023-04-28 05:57:51,120 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/templates/os9_users.j2' 2023-04-28 05:57:51,121 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/tests/inventory.yaml' 2023-04-28 05:57:51,121 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/tests/main.os9.yaml' 2023-04-28 05:57:51,121 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/tests/test.yaml' 2023-04-28 05:57:51,121 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_users/vars/main.yml' 2023-04-28 05:57:51,122 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/LICENSE' 2023-04-28 05:57:51,122 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/README.md' 2023-04-28 05:57:51,122 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/defaults/main.yml' 2023-04-28 05:57:51,123 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/handlers/main.yml' 2023-04-28 05:57:51,123 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/meta/main.yml' 2023-04-28 05:57:51,123 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/tasks/main.yml' 2023-04-28 05:57:51,123 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/templates/os9_vlan.j2' 2023-04-28 05:57:51,124 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/tests/inventory.yaml' 2023-04-28 05:57:51,124 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/tests/main.os9.yaml' 2023-04-28 05:57:51,124 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/tests/test.yaml' 2023-04-28 05:57:51,124 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlan/vars/main.yml' 2023-04-28 05:57:51,125 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/LICENSE' 2023-04-28 05:57:51,125 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/README.md' 2023-04-28 05:57:51,125 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/defaults/main.yml' 2023-04-28 05:57:51,125 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/handlers/main.yml' 2023-04-28 05:57:51,126 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/meta/main.yml' 2023-04-28 05:57:51,126 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/tasks/main.yml' 2023-04-28 05:57:51,126 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/templates/os9_vlt.j2' 2023-04-28 05:57:51,126 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/tests/inventory.yaml' 2023-04-28 05:57:51,127 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/tests/main.os9.yaml' 2023-04-28 05:57:51,127 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/tests/test.yaml' 2023-04-28 05:57:51,127 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vlt/vars/main.yml' 2023-04-28 05:57:51,127 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/LICENSE' 2023-04-28 05:57:51,128 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/README.md' 2023-04-28 05:57:51,128 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/defaults/main.yml' 2023-04-28 05:57:51,128 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/handlers/main.yml' 2023-04-28 05:57:51,129 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/meta/main.yml' 2023-04-28 05:57:51,129 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/tasks/main.yml' 2023-04-28 05:57:51,129 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/templates/os9_vrf.j2' 2023-04-28 05:57:51,130 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/tests/inventory.yaml' 2023-04-28 05:57:51,130 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/tests/main.os9.yaml' 2023-04-28 05:57:51,130 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/tests/test.yaml' 2023-04-28 05:57:51,130 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrf/vars/main.yml' 2023-04-28 05:57:51,131 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/LICENSE' 2023-04-28 05:57:51,131 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/README.md' 2023-04-28 05:57:51,131 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/defaults/main.yml' 2023-04-28 05:57:51,132 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/handlers/main.yml' 2023-04-28 05:57:51,132 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/meta/main.yml' 2023-04-28 05:57:51,132 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/tasks/main.yml' 2023-04-28 05:57:51,132 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/templates/os9_vrrp.j2' 2023-04-28 05:57:51,133 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/tests/inventory.yaml' 2023-04-28 05:57:51,133 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/tests/main.os9.yaml' 2023-04-28 05:57:51,133 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/tests/test.yaml' 2023-04-28 05:57:51,133 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_vrrp/vars/main.yml' 2023-04-28 05:57:51,134 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/LICENSE' 2023-04-28 05:57:51,134 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/README.md' 2023-04-28 05:57:51,134 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/defaults/main.yml' 2023-04-28 05:57:51,135 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/handlers/main.yml' 2023-04-28 05:57:51,135 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/meta/main.yml' 2023-04-28 05:57:51,135 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/tasks/main.yml' 2023-04-28 05:57:51,135 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/templates/os9_xstp.j2' 2023-04-28 05:57:51,136 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/tests/inventory.yaml' 2023-04-28 05:57:51,136 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/tests/main.os9.yaml' 2023-04-28 05:57:51,136 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/tests/test.yaml' 2023-04-28 05:57:51,136 wheel INFO adding 'ansible_collections/dellemc/os9/roles/os9_xstp/vars/main.yml' 2023-04-28 05:57:51,137 wheel INFO adding 'ansible_collections/dellemc/powerflex/CHANGELOG.rst' 2023-04-28 05:57:51,137 wheel INFO adding 'ansible_collections/dellemc/powerflex/FILES.json' 2023-04-28 05:57:51,137 wheel INFO adding 'ansible_collections/dellemc/powerflex/LICENSE' 2023-04-28 05:57:51,138 wheel INFO adding 'ansible_collections/dellemc/powerflex/MANIFEST.json' 2023-04-28 05:57:51,138 wheel INFO adding 'ansible_collections/dellemc/powerflex/MODULE-LICENSE' 2023-04-28 05:57:51,138 wheel INFO adding 'ansible_collections/dellemc/powerflex/README.md' 2023-04-28 05:57:51,138 wheel INFO adding 'ansible_collections/dellemc/powerflex/ansible.cfg' 2023-04-28 05:57:51,139 wheel INFO adding 'ansible_collections/dellemc/powerflex/requirements.txt' 2023-04-28 05:57:51,139 wheel INFO adding 'ansible_collections/dellemc/powerflex/requirements.yml' 2023-04-28 05:57:51,139 wheel INFO adding 'ansible_collections/dellemc/powerflex/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:51,139 wheel INFO adding 'ansible_collections/dellemc/powerflex/changelogs/changelog.yaml' 2023-04-28 05:57:51,140 wheel INFO adding 'ansible_collections/dellemc/powerflex/changelogs/config.yaml' 2023-04-28 05:57:51,140 wheel INFO adding 'ansible_collections/dellemc/powerflex/meta/execution-environment.yml' 2023-04-28 05:57:51,140 wheel INFO adding 'ansible_collections/dellemc/powerflex/meta/runtime.yml' 2023-04-28 05:57:51,140 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/doc_fragments/powerflex.py' 2023-04-28 05:57:51,141 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/__init__.py' 2023-04-28 05:57:51,141 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/logging_handler.py' 2023-04-28 05:57:51,141 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/utils.py' 2023-04-28 05:57:51,141 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/device.py' 2023-04-28 05:57:51,142 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/info.py' 2023-04-28 05:57:51,143 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/mdm_cluster.py' 2023-04-28 05:57:51,143 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/protection_domain.py' 2023-04-28 05:57:51,144 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/replication_consistency_group.py' 2023-04-28 05:57:51,144 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/replication_pair.py' 2023-04-28 05:57:51,144 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/sdc.py' 2023-04-28 05:57:51,145 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/sds.py' 2023-04-28 05:57:51,145 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/snapshot.py' 2023-04-28 05:57:51,146 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/storagepool.py' 2023-04-28 05:57:51,146 wheel INFO adding 'ansible_collections/dellemc/powerflex/plugins/modules/volume.py' 2023-04-28 05:57:51,147 wheel INFO adding 'ansible_collections/dellemc/unity/CHANGELOG.rst' 2023-04-28 05:57:51,147 wheel INFO adding 'ansible_collections/dellemc/unity/FILES.json' 2023-04-28 05:57:51,147 wheel INFO adding 'ansible_collections/dellemc/unity/LICENSE' 2023-04-28 05:57:51,148 wheel INFO adding 'ansible_collections/dellemc/unity/MANIFEST.json' 2023-04-28 05:57:51,148 wheel INFO adding 'ansible_collections/dellemc/unity/MODULE-LICENSE' 2023-04-28 05:57:51,148 wheel INFO adding 'ansible_collections/dellemc/unity/README.md' 2023-04-28 05:57:51,149 wheel INFO adding 'ansible_collections/dellemc/unity/ansible.cfg' 2023-04-28 05:57:51,149 wheel INFO adding 'ansible_collections/dellemc/unity/requirements.txt' 2023-04-28 05:57:51,149 wheel INFO adding 'ansible_collections/dellemc/unity/requirements.yml' 2023-04-28 05:57:51,149 wheel INFO adding 'ansible_collections/dellemc/unity/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:51,150 wheel INFO adding 'ansible_collections/dellemc/unity/changelogs/changelog.yaml' 2023-04-28 05:57:51,150 wheel INFO adding 'ansible_collections/dellemc/unity/changelogs/config.yaml' 2023-04-28 05:57:51,150 wheel INFO adding 'ansible_collections/dellemc/unity/meta/execution-environment.yml' 2023-04-28 05:57:51,150 wheel INFO adding 'ansible_collections/dellemc/unity/meta/runtime.yml' 2023-04-28 05:57:51,151 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/doc_fragments/unity.py' 2023-04-28 05:57:51,151 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/__init__.py' 2023-04-28 05:57:51,151 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/logging_handler.py' 2023-04-28 05:57:51,151 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/utils.py' 2023-04-28 05:57:51,152 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/cifsserver.py' 2023-04-28 05:57:51,152 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/consistencygroup.py' 2023-04-28 05:57:51,153 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/filesystem.py' 2023-04-28 05:57:51,153 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/filesystem_snapshot.py' 2023-04-28 05:57:51,154 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/host.py' 2023-04-28 05:57:51,154 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/info.py' 2023-04-28 05:57:51,155 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/interface.py' 2023-04-28 05:57:51,155 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/nasserver.py' 2023-04-28 05:57:51,157 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/nfs.py' 2023-04-28 05:57:51,157 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/nfsserver.py' 2023-04-28 05:57:51,157 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/smbshare.py' 2023-04-28 05:57:51,158 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/snapshot.py' 2023-04-28 05:57:51,158 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/snapshotschedule.py' 2023-04-28 05:57:51,159 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/storagepool.py' 2023-04-28 05:57:51,159 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/tree_quota.py' 2023-04-28 05:57:51,160 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/user_quota.py' 2023-04-28 05:57:51,160 wheel INFO adding 'ansible_collections/dellemc/unity/plugins/modules/volume.py' 2023-04-28 05:57:51,161 wheel INFO adding 'ansible_collections/f5networks/f5_modules/CHANGELOG.rst' 2023-04-28 05:57:51,162 wheel INFO adding 'ansible_collections/f5networks/f5_modules/FILES.json' 2023-04-28 05:57:51,162 wheel INFO adding 'ansible_collections/f5networks/f5_modules/MANIFEST.json' 2023-04-28 05:57:51,163 wheel INFO adding 'ansible_collections/f5networks/f5_modules/README.md' 2023-04-28 05:57:51,163 wheel INFO adding 'ansible_collections/f5networks/f5_modules/requirements.txt' 2023-04-28 05:57:51,163 wheel INFO adding 'ansible_collections/f5networks/f5_modules/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:51,164 wheel INFO adding 'ansible_collections/f5networks/f5_modules/changelogs/changelog.yaml' 2023-04-28 05:57:51,164 wheel INFO adding 'ansible_collections/f5networks/f5_modules/changelogs/config.yaml' 2023-04-28 05:57:51,164 wheel INFO adding 'ansible_collections/f5networks/f5_modules/changelogs/fragments/.gitkeep' 2023-04-28 05:57:51,165 wheel INFO adding 'ansible_collections/f5networks/f5_modules/meta/runtime.yml' 2023-04-28 05:57:51,165 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/action/__init__.py' 2023-04-28 05:57:51,165 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/action/bigip.py' 2023-04-28 05:57:51,165 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/action/bigip_imish_config.py' 2023-04-28 05:57:51,166 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/action/bigiq.py' 2023-04-28 05:57:51,166 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5.py' 2023-04-28 05:57:51,166 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5_rest_cli.py' 2023-04-28 05:57:51,166 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/doc_fragments/f5ssh.py' 2023-04-28 05:57:51,167 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/filter/__init__.py' 2023-04-28 05:57:51,167 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/filter/abspath.py' 2023-04-28 05:57:51,167 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/filter/markdev.py' 2023-04-28 05:57:51,167 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/lookup/__init__.py' 2023-04-28 05:57:51,167 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/lookup/bigiq_license.py' 2023-04-28 05:57:51,168 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/lookup/license_hopper.py' 2023-04-28 05:57:51,168 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/__init__.py' 2023-04-28 05:57:51,168 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/bigip.py' 2023-04-28 05:57:51,168 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/bigiq.py' 2023-04-28 05:57:51,169 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/common.py' 2023-04-28 05:57:51,169 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/compare.py' 2023-04-28 05:57:51,169 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/constants.py' 2023-04-28 05:57:51,169 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/icontrol.py' 2023-04-28 05:57:51,170 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/ipaddress.py' 2023-04-28 05:57:51,170 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/teem.py' 2023-04-28 05:57:51,170 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/urls.py' 2023-04-28 05:57:51,170 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/module_utils/version.py' 2023-04-28 05:57:51,171 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/__init__.py' 2023-04-28 05:57:51,171 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_acl.py' 2023-04-28 05:57:51,172 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_network_access.py' 2023-04-28 05:57:51,172 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_policy_fetch.py' 2023-04-28 05:57:51,172 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_apm_policy_import.py' 2023-04-28 05:57:51,173 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_advanced_settings.py' 2023-04-28 05:57:51,173 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_dos_application.py' 2023-04-28 05:57:51,173 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_fetch.py' 2023-04-28 05:57:51,174 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_import.py' 2023-04-28 05:57:51,174 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_manage.py' 2023-04-28 05:57:51,175 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_server_technology.py' 2023-04-28 05:57:51,175 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_asm_policy_signature_set.py' 2023-04-28 05:57:51,175 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cgnat_lsn_pool.py' 2023-04-28 05:57:51,176 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cli_alias.py' 2023-04-28 05:57:51,176 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_cli_script.py' 2023-04-28 05:57:51,176 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_command.py' 2023-04-28 05:57:51,177 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_config.py' 2023-04-28 05:57:51,177 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_configsync_action.py' 2023-04-28 05:57:51,177 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_data_group.py' 2023-04-28 05:57:51,178 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth.py' 2023-04-28 05:57:51,178 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_ldap.py' 2023-04-28 05:57:51,179 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_radius.py' 2023-04-28 05:57:51,179 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_auth_radius_server.py' 2023-04-28 05:57:51,179 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_certificate.py' 2023-04-28 05:57:51,180 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_connectivity.py' 2023-04-28 05:57:51,180 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_dns.py' 2023-04-28 05:57:51,180 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_group.py' 2023-04-28 05:57:51,180 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_group_member.py' 2023-04-28 05:57:51,181 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_ha_group.py' 2023-04-28 05:57:51,181 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_httpd.py' 2023-04-28 05:57:51,183 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_info.py' 2023-04-28 05:57:51,185 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_license.py' 2023-04-28 05:57:51,186 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_ntp.py' 2023-04-28 05:57:51,186 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_sshd.py' 2023-04-28 05:57:51,186 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_syslog.py' 2023-04-28 05:57:51,187 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_traffic_group.py' 2023-04-28 05:57:51,187 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_device_trust.py' 2023-04-28 05:57:51,187 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_cache_resolver.py' 2023-04-28 05:57:51,188 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_nameserver.py' 2023-04-28 05:57:51,188 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_resolver.py' 2023-04-28 05:57:51,188 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_dns_zone.py' 2023-04-28 05:57:51,189 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_file_copy.py' 2023-04-28 05:57:51,189 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_address_list.py' 2023-04-28 05:57:51,189 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_dos_profile.py' 2023-04-28 05:57:51,190 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_dos_vector.py' 2023-04-28 05:57:51,190 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_global_rules.py' 2023-04-28 05:57:51,190 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_log_profile.py' 2023-04-28 05:57:51,191 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_log_profile_network.py' 2023-04-28 05:57:51,191 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_policy.py' 2023-04-28 05:57:51,192 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_port_list.py' 2023-04-28 05:57:51,192 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_rule.py' 2023-04-28 05:57:51,192 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_rule_list.py' 2023-04-28 05:57:51,193 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_firewall_schedule.py' 2023-04-28 05:57:51,193 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_datacenter.py' 2023-04-28 05:57:51,193 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_dns_listener.py' 2023-04-28 05:57:51,194 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_global.py' 2023-04-28 05:57:51,194 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_bigip.py' 2023-04-28 05:57:51,194 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_external.py' 2023-04-28 05:57:51,195 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_firepass.py' 2023-04-28 05:57:51,195 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_http.py' 2023-04-28 05:57:51,196 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_https.py' 2023-04-28 05:57:51,196 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_tcp.py' 2023-04-28 05:57:51,196 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_monitor_tcp_half_open.py' 2023-04-28 05:57:51,197 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_pool.py' 2023-04-28 05:57:51,197 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_pool_member.py' 2023-04-28 05:57:51,198 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_server.py' 2023-04-28 05:57:51,198 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_topology_record.py' 2023-04-28 05:57:51,199 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_topology_region.py' 2023-04-28 05:57:51,199 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_virtual_server.py' 2023-04-28 05:57:51,200 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_gtm_wide_ip.py' 2023-04-28 05:57:51,200 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_hostname.py' 2023-04-28 05:57:51,200 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_iapp_service.py' 2023-04-28 05:57:51,201 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_iapp_template.py' 2023-04-28 05:57:51,201 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ike_peer.py' 2023-04-28 05:57:51,201 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_imish_config.py' 2023-04-28 05:57:51,202 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_interface.py' 2023-04-28 05:57:51,202 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ipsec_policy.py' 2023-04-28 05:57:51,202 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_irule.py' 2023-04-28 05:57:51,203 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_log_destination.py' 2023-04-28 05:57:51,203 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_log_publisher.py' 2023-04-28 05:57:51,204 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ltm_global.py' 2023-04-28 05:57:51,204 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_lx_package.py' 2023-04-28 05:57:51,204 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_management_route.py' 2023-04-28 05:57:51,204 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_peer.py' 2023-04-28 05:57:51,205 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_protocol.py' 2023-04-28 05:57:51,205 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_route.py' 2023-04-28 05:57:51,205 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_router.py' 2023-04-28 05:57:51,206 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_message_routing_transport_config.py' 2023-04-28 05:57:51,206 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_dns.py' 2023-04-28 05:57:51,206 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_external.py' 2023-04-28 05:57:51,207 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_ftp.py' 2023-04-28 05:57:51,207 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_gateway_icmp.py' 2023-04-28 05:57:51,208 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_http.py' 2023-04-28 05:57:51,208 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_https.py' 2023-04-28 05:57:51,208 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_icmp.py' 2023-04-28 05:57:51,209 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_ldap.py' 2023-04-28 05:57:51,209 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_mysql.py' 2023-04-28 05:57:51,209 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_oracle.py' 2023-04-28 05:57:51,210 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_smtp.py' 2023-04-28 05:57:51,210 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_snmp_dca.py' 2023-04-28 05:57:51,210 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp.py' 2023-04-28 05:57:51,211 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp_echo.py' 2023-04-28 05:57:51,211 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_tcp_half_open.py' 2023-04-28 05:57:51,211 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_monitor_udp.py' 2023-04-28 05:57:51,212 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_network_globals.py' 2023-04-28 05:57:51,212 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_node.py' 2023-04-28 05:57:51,213 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_partition.py' 2023-04-28 05:57:51,213 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_password_policy.py' 2023-04-28 05:57:51,213 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_policy.py' 2023-04-28 05:57:51,214 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_policy_rule.py' 2023-04-28 05:57:51,215 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_pool.py' 2023-04-28 05:57:51,215 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_pool_member.py' 2023-04-28 05:57:51,216 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_analytics.py' 2023-04-28 05:57:51,216 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_client_ssl.py' 2023-04-28 05:57:51,217 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_dns.py' 2023-04-28 05:57:51,217 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_fastl4.py' 2023-04-28 05:57:51,218 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_ftp.py' 2023-04-28 05:57:51,218 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http.py' 2023-04-28 05:57:51,218 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http2.py' 2023-04-28 05:57:51,219 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_http_compression.py' 2023-04-28 05:57:51,219 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_oneconnect.py' 2023-04-28 05:57:51,219 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_cookie.py' 2023-04-28 05:57:51,220 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_src_addr.py' 2023-04-28 05:57:51,220 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_persistence_universal.py' 2023-04-28 05:57:51,221 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_server_ssl.py' 2023-04-28 05:57:51,221 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_sip.py' 2023-04-28 05:57:51,221 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_tcp.py' 2023-04-28 05:57:51,222 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_profile_udp.py' 2023-04-28 05:57:51,222 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_provision.py' 2023-04-28 05:57:51,222 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_qkview.py' 2023-04-28 05:57:51,223 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_role.py' 2023-04-28 05:57:51,223 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_syslog.py' 2023-04-28 05:57:51,223 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_remote_user.py' 2023-04-28 05:57:51,224 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_routedomain.py' 2023-04-28 05:57:51,224 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_selfip.py' 2023-04-28 05:57:51,224 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_service_policy.py' 2023-04-28 05:57:51,225 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_smtp.py' 2023-04-28 05:57:51,225 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snat_pool.py' 2023-04-28 05:57:51,225 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snat_translation.py' 2023-04-28 05:57:51,226 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp.py' 2023-04-28 05:57:51,226 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp_community.py' 2023-04-28 05:57:51,226 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_snmp_trap.py' 2023-04-28 05:57:51,227 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_image.py' 2023-04-28 05:57:51,227 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_install.py' 2023-04-28 05:57:51,227 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_software_update.py' 2023-04-28 05:57:51,228 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_certificate.py' 2023-04-28 05:57:51,228 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_csr.py' 2023-04-28 05:57:51,228 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_key.py' 2023-04-28 05:57:51,229 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_key_cert.py' 2023-04-28 05:57:51,229 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ssl_ocsp.py' 2023-04-28 05:57:51,229 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_static_route.py' 2023-04-28 05:57:51,230 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_daemon_log_tmm.py' 2023-04-28 05:57:51,230 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_db.py' 2023-04-28 05:57:51,230 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_sys_global.py' 2023-04-28 05:57:51,230 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_timer_policy.py' 2023-04-28 05:57:51,231 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_traffic_selector.py' 2023-04-28 05:57:51,231 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_trunk.py' 2023-04-28 05:57:51,231 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_tunnel.py' 2023-04-28 05:57:51,232 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ucs.py' 2023-04-28 05:57:51,232 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_ucs_fetch.py' 2023-04-28 05:57:51,233 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_user.py' 2023-04-28 05:57:51,233 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_vcmp_guest.py' 2023-04-28 05:57:51,233 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_virtual_address.py' 2023-04-28 05:57:51,234 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_virtual_server.py' 2023-04-28 05:57:51,235 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_vlan.py' 2023-04-28 05:57:51,235 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigip_wait.py' 2023-04-28 05:57:51,236 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fasthttp.py' 2023-04-28 05:57:51,236 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fastl4_tcp.py' 2023-04-28 05:57:51,236 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_fastl4_udp.py' 2023-04-28 05:57:51,237 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_http.py' 2023-04-28 05:57:51,237 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_https_offload.py' 2023-04-28 05:57:51,237 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_application_https_waf.py' 2023-04-28 05:57:51,238 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_device_discovery.py' 2023-04-28 05:57:51,238 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_device_info.py' 2023-04-28 05:57:51,239 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_license.py' 2023-04-28 05:57:51,239 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_license_assignment.py' 2023-04-28 05:57:51,240 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_regkey_pool.py' 2023-04-28 05:57:51,240 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_utility_license.py' 2023-04-28 05:57:51,240 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/modules/bigiq_utility_license_assignment.py' 2023-04-28 05:57:51,241 wheel INFO adding 'ansible_collections/f5networks/f5_modules/plugins/terminal/bigip.py' 2023-04-28 05:57:51,241 wheel INFO adding 'ansible_collections/fortinet/fortimanager/CHANGELOG.rst' 2023-04-28 05:57:51,242 wheel INFO adding 'ansible_collections/fortinet/fortimanager/FILES.json' 2023-04-28 05:57:51,243 wheel INFO adding 'ansible_collections/fortinet/fortimanager/MANIFEST.json' 2023-04-28 05:57:51,243 wheel INFO adding 'ansible_collections/fortinet/fortimanager/README.md' 2023-04-28 05:57:51,244 wheel INFO adding 'ansible_collections/fortinet/fortimanager/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:51,245 wheel INFO adding 'ansible_collections/fortinet/fortimanager/changelogs/changelog.yaml' 2023-04-28 05:57:51,245 wheel INFO adding 'ansible_collections/fortinet/fortimanager/changelogs/config.yaml' 2023-04-28 05:57:51,245 wheel INFO adding 'ansible_collections/fortinet/fortimanager/meta/runtime.yml' 2023-04-28 05:57:51,246 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/README.md' 2023-04-28 05:57:51,246 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/httpapi/fortimanager.py' 2023-04-28 05:57:51,246 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/module_utils/__init__.py' 2023-04-28 05:57:51,247 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/module_utils/common.py' 2023-04-28 05:57:51,267 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/module_utils/exported_schema.py' 2023-04-28 05:57:51,301 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/module_utils/fortimanager.py' 2023-04-28 05:57:51,302 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/module_utils/napi.py' 2023-04-28 05:57:51,304 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_adom_options.py' 2023-04-28 05:57:51,304 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_mmschecksum.py' 2023-04-28 05:57:51,304 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_mmschecksum_entries.py' 2023-04-28 05:57:51,304 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_notification.py' 2023-04-28 05:57:51,305 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_notification_entries.py' 2023-04-28 05:57:51,305 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile.py' 2023-04-28 05:57:51,306 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_cifs.py' 2023-04-28 05:57:51,306 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_contentdisarm.py' 2023-04-28 05:57:51,307 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_ftp.py' 2023-04-28 05:57:51,307 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_http.py' 2023-04-28 05:57:51,307 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_imap.py' 2023-04-28 05:57:51,308 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_mapi.py' 2023-04-28 05:57:51,308 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_nacquar.py' 2023-04-28 05:57:51,308 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_nntp.py' 2023-04-28 05:57:51,309 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_outbreakprevention.py' 2023-04-28 05:57:51,309 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_pop3.py' 2023-04-28 05:57:51,309 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_smb.py' 2023-04-28 05:57:51,310 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_smtp.py' 2023-04-28 05:57:51,310 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_antivirus_profile_ssh.py' 2023-04-28 05:57:51,310 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_apcfgprofile.py' 2023-04-28 05:57:51,311 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_apcfgprofile_commandlist.py' 2023-04-28 05:57:51,311 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_categories.py' 2023-04-28 05:57:51,311 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_custom.py' 2023-04-28 05:57:51,311 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_group.py' 2023-04-28 05:57:51,312 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list.py' 2023-04-28 05:57:51,312 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_defaultnetworkservices.py' 2023-04-28 05:57:51,313 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries.py' 2023-04-28 05:57:51,313 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries_parameters.py' 2023-04-28 05:57:51,313 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_application_list_entries_parameters_members.py' 2023-04-28 05:57:51,314 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_arrpprofile.py' 2023-04-28 05:57:51,314 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_authentication_scheme.py' 2023-04-28 05:57:51,314 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bleprofile.py' 2023-04-28 05:57:51,315 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bonjourprofile.py' 2023-04-28 05:57:51,315 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_bonjourprofile_policylist.py' 2023-04-28 05:57:51,315 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_certificate_template.py' 2023-04-28 05:57:51,315 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_domaincontroller.py' 2023-04-28 05:57:51,316 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile.py' 2023-04-28 05:57:51,316 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_filefilter.py' 2023-04-28 05:57:51,316 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_filefilter_entries.py' 2023-04-28 05:57:51,317 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_cifs_profile_serverkeytab.py' 2023-04-28 05:57:51,318 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_clone.py' 2023-04-28 05:57:51,320 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_credentialstore_domaincontroller.py' 2023-04-28 05:57:51,320 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_device_profile_fortianalyzer.py' 2023-04-28 05:57:51,320 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_device_profile_fortiguard.py' 2023-04-28 05:57:51,320 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_import.py' 2023-04-28 05:57:51,321 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_fortianalyzer_setting.py' 2023-04-28 05:57:51,321 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_fortianalyzercloud_setting.py' 2023-04-28 05:57:51,321 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_syslogd_filter.py' 2023-04-28 05:57:51,322 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_log_syslogd_setting.py' 2023-04-28 05:57:51,322 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_centralmanagement.py' 2023-04-28 05:57:51,322 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_centralmanagement_serverlist.py' 2023-04-28 05:57:51,323 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_dns.py' 2023-04-28 05:57:51,323 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_emailserver.py' 2023-04-28 05:57:51,323 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_global.py' 2023-04-28 05:57:51,324 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_ntp.py' 2023-04-28 05:57:51,324 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_ntp_ntpserver.py' 2023-04-28 05:57:51,324 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_admin.py' 2023-04-28 05:57:51,325 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_alertmail.py' 2023-04-28 05:57:51,325 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_auth.py' 2023-04-28 05:57:51,325 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_devicedetectionportal.py' 2023-04-28 05:57:51,325 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_ec.py' 2023-04-28 05:57:51,326 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_fortiguardwf.py' 2023-04-28 05:57:51,326 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_ftp.py' 2023-04-28 05:57:51,326 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_http.py' 2023-04-28 05:57:51,327 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_mail.py' 2023-04-28 05:57:51,327 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_mms.py' 2023-04-28 05:57:51,327 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_nacquar.py' 2023-04-28 05:57:51,327 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_nntp.py' 2023-04-28 05:57:51,328 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_spam.py' 2023-04-28 05:57:51,328 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_sslvpn.py' 2023-04-28 05:57:51,328 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_trafficquota.py' 2023-04-28 05:57:51,328 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_utm.py' 2023-04-28 05:57:51,329 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_replacemsg_webproxy.py' 2023-04-28 05:57:51,329 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community.py' 2023-04-28 05:57:51,330 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community_hosts.py' 2023-04-28 05:57:51,330 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_community_hosts6.py' 2023-04-28 05:57:51,330 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_sysinfo.py' 2023-04-28 05:57:51,330 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_devprof_system_snmp_user.py' 2023-04-28 05:57:51,331 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_datatype.py' 2023-04-28 05:57:51,331 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_dictionary.py' 2023-04-28 05:57:51,331 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_dictionary_entries.py' 2023-04-28 05:57:51,332 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_filepattern.py' 2023-04-28 05:57:51,332 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_filepattern_entries.py' 2023-04-28 05:57:51,332 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_fpsensitivity.py' 2023-04-28 05:57:51,333 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_profile.py' 2023-04-28 05:57:51,333 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_profile_rule.py' 2023-04-28 05:57:51,333 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensitivity.py' 2023-04-28 05:57:51,333 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor.py' 2023-04-28 05:57:51,334 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor_entries.py' 2023-04-28 05:57:51,334 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dlp_sensor_filter.py' 2023-04-28 05:57:51,335 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_domainfilter.py' 2023-04-28 05:57:51,335 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_domainfilter_entries.py' 2023-04-28 05:57:51,335 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile.py' 2023-04-28 05:57:51,336 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_dnstranslation.py' 2023-04-28 05:57:51,336 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_domainfilter.py' 2023-04-28 05:57:51,336 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_ftgddns.py' 2023-04-28 05:57:51,336 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dnsfilter_profile_ftgddns_filters.py' 2023-04-28 05:57:51,337 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_add_device.py' 2023-04-28 05:57:51,337 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_add_devlist.py' 2023-04-28 05:57:51,337 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_changehaseq.py' 2023-04-28 05:57:51,338 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_del_device.py' 2023-04-28 05:57:51,338 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_del_devlist.py' 2023-04-28 05:57:51,338 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_discover_device.py' 2023-04-28 05:57:51,339 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_import_devlist.py' 2023-04-28 05:57:51,340 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_reload_devlist.py' 2023-04-28 05:57:51,340 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_update_device.py' 2023-04-28 05:57:51,340 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvm_cmd_update_devlist.py' 2023-04-28 05:57:51,340 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_adom.py' 2023-04-28 05:57:51,341 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_adom_objectmember.py' 2023-04-28 05:57:51,341 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device.py' 2023-04-28 05:57:51,342 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device_replace_sn.py' 2023-04-28 05:57:51,342 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_device_vdom.py' 2023-04-28 05:57:51,342 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_folder.py' 2023-04-28 05:57:51,343 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_group.py' 2023-04-28 05:57:51,343 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_group_objectmember.py' 2023-04-28 05:57:51,343 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_adom.py' 2023-04-28 05:57:51,343 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_device.py' 2023-04-28 05:57:51,344 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_metafields_group.py' 2023-04-28 05:57:51,344 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_revision.py' 2023-04-28 05:57:51,344 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script.py' 2023-04-28 05:57:51,345 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_execute.py' 2023-04-28 05:57:51,345 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_objectmember.py' 2023-04-28 05:57:51,345 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_script_scriptschedule.py' 2023-04-28 05:57:51,346 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_approve.py' 2023-04-28 05:57:51,346 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_discard.py' 2023-04-28 05:57:51,346 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_drop.py' 2023-04-28 05:57:51,346 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_reject.py' 2023-04-28 05:57:51,347 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_repair.py' 2023-04-28 05:57:51,347 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_revert.py' 2023-04-28 05:57:51,347 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_review.py' 2023-04-28 05:57:51,347 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_save.py' 2023-04-28 05:57:51,348 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_start.py' 2023-04-28 05:57:51,348 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workflow_submit.py' 2023-04-28 05:57:51,348 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit.py' 2023-04-28 05:57:51,349 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_dev.py' 2023-04-28 05:57:51,349 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_obj.py' 2023-04-28 05:57:51,349 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_commit_pkg.py' 2023-04-28 05:57:51,349 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock.py' 2023-04-28 05:57:51,350 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_dev.py' 2023-04-28 05:57:51,350 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_obj.py' 2023-04-28 05:57:51,350 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_lock_pkg.py' 2023-04-28 05:57:51,351 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock.py' 2023-04-28 05:57:51,351 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_dev.py' 2023-04-28 05:57:51,351 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_obj.py' 2023-04-28 05:57:51,351 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dvmdb_workspace_unlock_pkg.py' 2023-04-28 05:57:51,352 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_address.py' 2023-04-28 05:57:51,352 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_address_dynamicaddrmapping.py' 2023-04-28 05:57:51,352 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_certificate_local.py' 2023-04-28 05:57:51,352 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_certificate_local_dynamicmapping.py' 2023-04-28 05:57:51,353 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_input_interface.py' 2023-04-28 05:57:51,353 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_input_interface_dynamicmapping.py' 2023-04-28 05:57:51,353 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface.py' 2023-04-28 05:57:51,354 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface_dynamicmapping.py' 2023-04-28 05:57:51,354 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_interface_platformmapping.py' 2023-04-28 05:57:51,354 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_ippool.py' 2023-04-28 05:57:51,355 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_multicast_interface.py' 2023-04-28 05:57:51,355 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_multicast_interface_dynamicmapping.py' 2023-04-28 05:57:51,355 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vip.py' 2023-04-28 05:57:51,356 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_members.py' 2023-04-28 05:57:51,356 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_members_dynamicmapping.py' 2023-04-28 05:57:51,356 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_neighbor.py' 2023-04-28 05:57:51,357 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_neighbor_dynamicmapping.py' 2023-04-28 05:57:51,357 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_server.py' 2023-04-28 05:57:51,357 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_virtualwanlink_server_dynamicmapping.py' 2023-04-28 05:57:51,358 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vpntunnel.py' 2023-04-28 05:57:51,358 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_dynamic_vpntunnel_dynamicmapping.py' 2023-04-28 05:57:51,358 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_blockallowlist.py' 2023-04-28 05:57:51,359 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_blockallowlist_entries.py' 2023-04-28 05:57:51,359 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bwl.py' 2023-04-28 05:57:51,359 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bwl_entries.py' 2023-04-28 05:57:51,359 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bword.py' 2023-04-28 05:57:51,360 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_bword_entries.py' 2023-04-28 05:57:51,360 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_dnsbl.py' 2023-04-28 05:57:51,360 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_dnsbl_entries.py' 2023-04-28 05:57:51,361 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_fortishield.py' 2023-04-28 05:57:51,361 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_iptrust.py' 2023-04-28 05:57:51,361 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_iptrust_entries.py' 2023-04-28 05:57:51,362 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_mheader.py' 2023-04-28 05:57:51,362 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_mheader_entries.py' 2023-04-28 05:57:51,362 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_options.py' 2023-04-28 05:57:51,362 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile.py' 2023-04-28 05:57:51,363 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_filefilter.py' 2023-04-28 05:57:51,363 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_filefilter_entries.py' 2023-04-28 05:57:51,364 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_gmail.py' 2023-04-28 05:57:51,364 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_imap.py' 2023-04-28 05:57:51,364 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_mapi.py' 2023-04-28 05:57:51,364 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_msnhotmail.py' 2023-04-28 05:57:51,365 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_otherwebmails.py' 2023-04-28 05:57:51,365 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_pop3.py' 2023-04-28 05:57:51,365 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_emailfilter_profile_smtp.py' 2023-04-28 05:57:51,365 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_endpointcontrol_fctems.py' 2023-04-28 05:57:51,366 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_exec_fgfm_reclaimdevtunnel.py' 2023-04-28 05:57:51,368 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_export_playbooks.py' 2023-04-28 05:57:51,370 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_dataplan.py' 2023-04-28 05:57:51,371 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile.py' 2023-04-28 05:57:51,371 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular.py' 2023-04-28 05:57:51,372 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_controllerreport.py' 2023-04-28 05:57:51,372 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem1.py' 2023-04-28 05:57:51,372 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem1_autoswitch.py' 2023-04-28 05:57:51,373 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem2.py' 2023-04-28 05:57:51,373 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_modem2_autoswitch.py' 2023-04-28 05:57:51,373 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification.py' 2023-04-28 05:57:51,374 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification_alert.py' 2023-04-28 05:57:51,374 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_cellular_smsnotification_receiver.py' 2023-04-28 05:57:51,374 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_lanextension.py' 2023-04-28 05:57:51,374 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_extenderprofile_lanextension_backhaul.py' 2023-04-28 05:57:51,375 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_simprofile.py' 2023-04-28 05:57:51,375 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_simprofile_autoswitchprofile.py' 2023-04-28 05:57:51,375 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_extendercontroller_template.py' 2023-04-28 05:57:51,377 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fact.py' 2023-04-28 05:57:51,380 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_filefilter_profile.py' 2023-04-28 05:57:51,381 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_filefilter_profile_rules.py' 2023-04-28 05:57:51,381 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy.py' 2023-04-28 05:57:51,382 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway.py' 2023-04-28 05:57:51,382 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6.py' 2023-04-28 05:57:51,383 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6_realservers.py' 2023-04-28 05:57:51,383 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway6_sslciphersuites.py' 2023-04-28 05:57:51,383 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway_realservers.py' 2023-04-28 05:57:51,384 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_apigateway_sslciphersuites.py' 2023-04-28 05:57:51,384 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_realservers.py' 2023-04-28 05:57:51,384 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_serverpubkeyauthsettings.py' 2023-04-28 05:57:51,385 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxy_serverpubkeyauthsettings_certextension.py' 2023-04-28 05:57:51,385 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_accessproxyvirtualhost.py' 2023-04-28 05:57:51,385 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address.py' 2023-04-28 05:57:51,386 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6.py' 2023-04-28 05:57:51,387 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_dynamicmapping.py' 2023-04-28 05:57:51,387 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_dynamicmapping_subnetsegment.py' 2023-04-28 05:57:51,387 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_list.py' 2023-04-28 05:57:51,388 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_subnetsegment.py' 2023-04-28 05:57:51,388 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6_tagging.py' 2023-04-28 05:57:51,388 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template.py' 2023-04-28 05:57:51,388 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template_subnetsegment.py' 2023-04-28 05:57:51,389 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address6template_subnetsegment_values.py' 2023-04-28 05:57:51,389 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_dynamicmapping.py' 2023-04-28 05:57:51,389 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_list.py' 2023-04-28 05:57:51,390 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_address_tagging.py' 2023-04-28 05:57:51,390 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp.py' 2023-04-28 05:57:51,391 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6.py' 2023-04-28 05:57:51,391 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6_dynamicmapping.py' 2023-04-28 05:57:51,391 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp6_tagging.py' 2023-04-28 05:57:51,392 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp_dynamicmapping.py' 2023-04-28 05:57:51,392 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_addrgrp_tagging.py' 2023-04-28 05:57:51,392 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_carrierendpointbwl.py' 2023-04-28 05:57:51,392 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_carrierendpointbwl_entries.py' 2023-04-28 05:57:51,393 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_decryptedtrafficmirror.py' 2023-04-28 05:57:51,393 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp.py' 2023-04-28 05:57:51,394 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_apn.py' 2023-04-28 05:57:51,395 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ieremovepolicy.py' 2023-04-28 05:57:51,395 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ievalidation.py' 2023-04-28 05:57:51,395 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_imsi.py' 2023-04-28 05:57:51,396 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_ippolicy.py' 2023-04-28 05:57:51,396 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimit.py' 2023-04-28 05:57:51,396 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv0.py' 2023-04-28 05:57:51,397 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv1.py' 2023-04-28 05:57:51,397 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_messageratelimitv2.py' 2023-04-28 05:57:51,397 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_noippolicy.py' 2023-04-28 05:57:51,397 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_perapnshaper.py' 2023-04-28 05:57:51,398 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_policy.py' 2023-04-28 05:57:51,398 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_gtp_policyv2.py' 2023-04-28 05:57:51,398 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_identitybasedroute.py' 2023-04-28 05:57:51,399 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_identitybasedroute_rule.py' 2023-04-28 05:57:51,399 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservice.py' 2023-04-28 05:57:51,399 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservice_entry.py' 2023-04-28 05:57:51,400 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition.py' 2023-04-28 05:57:51,400 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition_entry.py' 2023-04-28 05:57:51,400 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetserviceaddition_entry_portrange.py' 2023-04-28 05:57:51,401 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom.py' 2023-04-28 05:57:51,401 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_disableentry.py' 2023-04-28 05:57:51,401 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_disableentry_iprange.py' 2023-04-28 05:57:51,401 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_entry.py' 2023-04-28 05:57:51,402 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustom_entry_portrange.py' 2023-04-28 05:57:51,402 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicecustomgroup.py' 2023-04-28 05:57:51,402 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicegroup.py' 2023-04-28 05:57:51,403 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_internetservicename.py' 2023-04-28 05:57:51,403 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool.py' 2023-04-28 05:57:51,403 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool6.py' 2023-04-28 05:57:51,404 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool6_dynamicmapping.py' 2023-04-28 05:57:51,404 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ippool_dynamicmapping.py' 2023-04-28 05:57:51,404 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ldbmonitor.py' 2023-04-28 05:57:51,405 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile.py' 2023-04-28 05:57:51,405 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_dupe.py' 2023-04-28 05:57:51,406 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_flood.py' 2023-04-28 05:57:51,406 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_notification.py' 2023-04-28 05:57:51,406 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_notifmsisdn.py' 2023-04-28 05:57:51,407 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_mmsprofile_outbreakprevention.py' 2023-04-28 05:57:51,407 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress.py' 2023-04-28 05:57:51,407 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress6.py' 2023-04-28 05:57:51,408 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress6_tagging.py' 2023-04-28 05:57:51,408 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_multicastaddress_tagging.py' 2023-04-28 05:57:51,408 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profilegroup.py' 2023-04-28 05:57:51,409 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions.py' 2023-04-28 05:57:51,410 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs.py' 2023-04-28 05:57:51,410 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_filefilter.py' 2023-04-28 05:57:51,410 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_filefilter_entries.py' 2023-04-28 05:57:51,410 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_cifs_serverkeytab.py' 2023-04-28 05:57:51,411 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_dns.py' 2023-04-28 05:57:51,411 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_ftp.py' 2023-04-28 05:57:51,411 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_http.py' 2023-04-28 05:57:51,412 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_imap.py' 2023-04-28 05:57:51,412 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_mailsignature.py' 2023-04-28 05:57:51,412 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_mapi.py' 2023-04-28 05:57:51,413 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_nntp.py' 2023-04-28 05:57:51,413 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_pop3.py' 2023-04-28 05:57:51,413 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_smtp.py' 2023-04-28 05:57:51,414 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_profileprotocoloptions_ssh.py' 2023-04-28 05:57:51,414 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress.py' 2023-04-28 05:57:51,414 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress_headergroup.py' 2023-04-28 05:57:51,415 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddress_tagging.py' 2023-04-28 05:57:51,415 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddrgrp.py' 2023-04-28 05:57:51,415 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_proxyaddrgrp_tagging.py' 2023-04-28 05:57:51,416 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_group.py' 2023-04-28 05:57:51,416 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_onetime.py' 2023-04-28 05:57:51,416 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_schedule_recurring.py' 2023-04-28 05:57:51,416 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_category.py' 2023-04-28 05:57:51,417 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_custom.py' 2023-04-28 05:57:51,417 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_service_group.py' 2023-04-28 05:57:51,417 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shaper_peripshaper.py' 2023-04-28 05:57:51,418 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shaper_trafficshaper.py' 2023-04-28 05:57:51,418 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shapingprofile.py' 2023-04-28 05:57:51,418 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_shapingprofile_shapingentries.py' 2023-04-28 05:57:51,419 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_ssh_localca.py' 2023-04-28 05:57:51,419 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile.py' 2023-04-28 05:57:51,420 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_dot.py' 2023-04-28 05:57:51,420 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ftps.py' 2023-04-28 05:57:51,421 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_https.py' 2023-04-28 05:57:51,421 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_imaps.py' 2023-04-28 05:57:51,421 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_pop3s.py' 2023-04-28 05:57:51,422 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_smtps.py' 2023-04-28 05:57:51,422 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ssh.py' 2023-04-28 05:57:51,422 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_ssl.py' 2023-04-28 05:57:51,423 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_sslexempt.py' 2023-04-28 05:57:51,423 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_sslsshprofile_sslserver.py' 2023-04-28 05:57:51,423 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_trafficclass.py' 2023-04-28 05:57:51,424 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip.py' 2023-04-28 05:57:51,425 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46.py' 2023-04-28 05:57:51,426 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46_dynamicmapping.py' 2023-04-28 05:57:51,426 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip46_realservers.py' 2023-04-28 05:57:51,427 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6.py' 2023-04-28 05:57:51,428 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64.py' 2023-04-28 05:57:51,428 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64_dynamicmapping.py' 2023-04-28 05:57:51,429 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip64_realservers.py' 2023-04-28 05:57:51,429 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping.py' 2023-04-28 05:57:51,430 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping_realservers.py' 2023-04-28 05:57:51,430 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_dynamicmapping_sslciphersuites.py' 2023-04-28 05:57:51,430 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_realservers.py' 2023-04-28 05:57:51,431 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_sslciphersuites.py' 2023-04-28 05:57:51,431 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip6_sslserverciphersuites.py' 2023-04-28 05:57:51,432 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping.py' 2023-04-28 05:57:51,432 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping_realservers.py' 2023-04-28 05:57:51,433 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_dynamicmapping_sslciphersuites.py' 2023-04-28 05:57:51,433 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_realservers.py' 2023-04-28 05:57:51,433 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_sslciphersuites.py' 2023-04-28 05:57:51,434 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vip_sslserverciphersuites.py' 2023-04-28 05:57:51,434 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp.py' 2023-04-28 05:57:51,434 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp46.py' 2023-04-28 05:57:51,435 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp6.py' 2023-04-28 05:57:51,435 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp64.py' 2023-04-28 05:57:51,435 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_vipgrp_dynamicmapping.py' 2023-04-28 05:57:51,435 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_wildcardfqdn_custom.py' 2023-04-28 05:57:51,436 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_firewall_wildcardfqdn_group.py' 2023-04-28 05:57:51,436 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_device_blueprint.py' 2023-04-28 05:57:51,436 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_variable.py' 2023-04-28 05:57:51,437 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmg_variable_dynamicmapping.py' 2023-04-28 05:57:51,437 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_analyzer_virusreport.py' 2023-04-28 05:57:51,437 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_avips_advancedlog.py' 2023-04-28 05:57:51,437 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_avips_webproxy.py' 2023-04-28 05:57:51,438 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_customurllist.py' 2023-04-28 05:57:51,438 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_diskquota.py' 2023-04-28 05:57:51,438 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fctservices.py' 2023-04-28 05:57:51,439 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting.py' 2023-04-28 05:57:51,439 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverride.py' 2023-04-28 05:57:51,439 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverridetoclient.py' 2023-04-28 05:57:51,440 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_pushoverridetoclient_announceip.py' 2023-04-28 05:57:51,440 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_serveroverride.py' 2023-04-28 05:57:51,440 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_serveroverride_servlist.py' 2023-04-28 05:57:51,441 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fdssetting_updateschedule.py' 2023-04-28 05:57:51,441 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_fwmsetting.py' 2023-04-28 05:57:51,441 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_multilayer.py' 2023-04-28 05:57:51,441 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_publicnetwork.py' 2023-04-28 05:57:51,442 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveraccesspriorities.py' 2023-04-28 05:57:51,442 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveraccesspriorities_privateserver.py' 2023-04-28 05:57:51,442 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_serveroverridestatus.py' 2023-04-28 05:57:51,443 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_service.py' 2023-04-28 05:57:51,443 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting.py' 2023-04-28 05:57:51,443 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting_serveroverride.py' 2023-04-28 05:57:51,444 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_fgdsetting_serveroverride_servlist.py' 2023-04-28 05:57:51,444 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fmupdate_webspam_webproxy.py' 2023-04-28 05:57:51,445 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan.py' 2023-04-28 05:57:51,447 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver.py' 2023-04-28 05:57:51,447 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_excluderange.py' 2023-04-28 05:57:51,448 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_iprange.py' 2023-04-28 05:57:51,448 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_options.py' 2023-04-28 05:57:51,448 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dhcpserver_reservedaddress.py' 2023-04-28 05:57:51,449 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping.py' 2023-04-28 05:57:51,450 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver.py' 2023-04-28 05:57:51,450 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_excluderange.py' 2023-04-28 05:57:51,451 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_iprange.py' 2023-04-28 05:57:51,451 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_options.py' 2023-04-28 05:57:51,451 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_dhcpserver_reservedaddress.py' 2023-04-28 05:57:51,452 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface.py' 2023-04-28 05:57:51,452 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6.py' 2023-04-28 05:57:51,453 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6delegatedprefixlist.py' 2023-04-28 05:57:51,453 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6extraaddr.py' 2023-04-28 05:57:51,453 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_ip6prefixlist.py' 2023-04-28 05:57:51,454 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_ipv6_vrrp6.py' 2023-04-28 05:57:51,454 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_dynamicmapping_interface_secondaryip.py' 2023-04-28 05:57:51,455 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface.py' 2023-04-28 05:57:51,457 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6.py' 2023-04-28 05:57:51,457 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6delegatedprefixlist.py' 2023-04-28 05:57:51,458 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6extraaddr.py' 2023-04-28 05:57:51,458 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_ip6prefixlist.py' 2023-04-28 05:57:51,458 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_ipv6_vrrp6.py' 2023-04-28 05:57:51,458 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_secondaryip.py' 2023-04-28 05:57:51,459 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_fsp_vlan_interface_vrrp.py' 2023-04-28 05:57:51,459 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_generic.py' 2023-04-28 05:57:51,459 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_apn.py' 2023-04-28 05:57:51,460 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_apngrp.py' 2023-04-28 05:57:51,460 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_iewhitelist.py' 2023-04-28 05:57:51,460 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_iewhitelist_entries.py' 2023-04-28 05:57:51,461 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_messagefilterv0v1.py' 2023-04-28 05:57:51,461 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_messagefilterv2.py' 2023-04-28 05:57:51,461 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_gtp_tunnellimit.py' 2023-04-28 05:57:51,462 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqp3gppcellular.py' 2023-04-28 05:57:51,462 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqp3gppcellular_mccmnclist.py' 2023-04-28 05:57:51,462 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpipaddresstype.py' 2023-04-28 05:57:51,462 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm.py' 2023-04-28 05:57:51,463 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist.py' 2023-04-28 05:57:51,463 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist_eapmethod.py' 2023-04-28 05:57:51,463 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnairealm_nailist_eapmethod_authparam.py' 2023-04-28 05:57:51,464 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpnetworkauthtype.py' 2023-04-28 05:57:51,464 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqproamingconsortium.py' 2023-04-28 05:57:51,464 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqproamingconsortium_oilist.py' 2023-04-28 05:57:51,465 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenuename.py' 2023-04-28 05:57:51,465 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenuename_valuelist.py' 2023-04-28 05:57:51,465 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenueurl.py' 2023-04-28 05:57:51,465 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_anqpvenueurl_valuelist.py' 2023-04-28 05:57:51,466 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge.py' 2023-04-28 05:57:51,466 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge_aoclist.py' 2023-04-28 05:57:51,466 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpadviceofcharge_aoclist_planinfo.py' 2023-04-28 05:57:51,467 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpconncapability.py' 2023-04-28 05:57:51,467 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpoperatorname.py' 2023-04-28 05:57:51,467 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpoperatorname_valuelist.py' 2023-04-28 05:57:51,468 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider.py' 2023-04-28 05:57:51,468 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider_friendlyname.py' 2023-04-28 05:57:51,468 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovider_servicedescription.py' 2023-04-28 05:57:51,468 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovidernai.py' 2023-04-28 05:57:51,469 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qposuprovidernai_nailist.py' 2023-04-28 05:57:51,469 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qptermsandconditions.py' 2023-04-28 05:57:51,469 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_h2qpwanmetric.py' 2023-04-28 05:57:51,470 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_hsprofile.py' 2023-04-28 05:57:51,470 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_icon.py' 2023-04-28 05:57:51,470 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_icon_iconlist.py' 2023-04-28 05:57:51,471 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap.py' 2023-04-28 05:57:51,471 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap_dscpexcept.py' 2023-04-28 05:57:51,471 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_hotspot20_qosmap_dscprange.py' 2023-04-28 05:57:51,472 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile.py' 2023-04-28 05:57:51,472 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_icapheaders.py' 2023-04-28 05:57:51,472 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_respmodforwardrules.py' 2023-04-28 05:57:51,473 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_profile_respmodforwardrules_headergroup.py' 2023-04-28 05:57:51,473 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_icap_server.py' 2023-04-28 05:57:51,473 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_custom.py' 2023-04-28 05:57:51,474 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor.py' 2023-04-28 05:57:51,474 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor_entries.py' 2023-04-28 05:57:51,475 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_ips_sensor_entries_exemptip.py' 2023-04-28 05:57:51,475 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_log_customfield.py' 2023-04-28 05:57:51,475 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_metafields_system_admin_user.py' 2023-04-28 05:57:51,475 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_move.py' 2023-04-28 05:57:51,476 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile.py' 2023-04-28 05:57:51,476 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile_mpskgroup.py' 2023-04-28 05:57:51,477 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_mpskprofile_mpskgroup_mpskkey.py' 2023-04-28 05:57:51,477 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_nacprofile.py' 2023-04-28 05:57:51,477 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_authentication_rule.py' 2023-04-28 05:57:51,478 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_authentication_setting.py' 2023-04-28 05:57:51,478 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_central_dnat.py' 2023-04-28 05:57:51,478 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_central_dnat6.py' 2023-04-28 05:57:51,478 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_acl.py' 2023-04-28 05:57:51,479 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_acl6.py' 2023-04-28 05:57:51,479 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_centralsnatmap.py' 2023-04-28 05:57:51,479 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_consolidated_policy.py' 2023-04-28 05:57:51,480 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_consolidated_policy_sectionvalue.py' 2023-04-28 05:57:51,481 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy.py' 2023-04-28 05:57:51,481 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy6.py' 2023-04-28 05:57:51,481 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy6_anomaly.py' 2023-04-28 05:57:51,482 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_dospolicy_anomaly.py' 2023-04-28 05:57:51,482 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy.py' 2023-04-28 05:57:51,482 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy6.py' 2023-04-28 05:57:51,483 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy6_sectionvalue.py' 2023-04-28 05:57:51,483 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_interfacepolicy_sectionvalue.py' 2023-04-28 05:57:51,483 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_localinpolicy.py' 2023-04-28 05:57:51,484 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_localinpolicy6.py' 2023-04-28 05:57:51,484 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_multicastpolicy.py' 2023-04-28 05:57:51,484 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_multicastpolicy6.py' 2023-04-28 05:57:51,485 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy.py' 2023-04-28 05:57:51,486 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy46.py' 2023-04-28 05:57:51,486 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy6.py' 2023-04-28 05:57:51,487 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy64.py' 2023-04-28 05:57:51,487 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy6_sectionvalue.py' 2023-04-28 05:57:51,487 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_sectionvalue.py' 2023-04-28 05:57:51,488 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_vpndstnode.py' 2023-04-28 05:57:51,488 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_policy_vpnsrcnode.py' 2023-04-28 05:57:51,488 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_proxypolicy.py' 2023-04-28 05:57:51,489 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_proxypolicy_sectionvalue.py' 2023-04-28 05:57:51,489 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_securitypolicy.py' 2023-04-28 05:57:51,490 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_securitypolicy_sectionvalue.py' 2023-04-28 05:57:51,490 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_firewall_shapingpolicy.py' 2023-04-28 05:57:51,491 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_policy.py' 2023-04-28 05:57:51,493 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_policy6.py' 2023-04-28 05:57:51,493 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_footer_shapingpolicy.py' 2023-04-28 05:57:51,494 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_policy.py' 2023-04-28 05:57:51,496 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_policy6.py' 2023-04-28 05:57:51,496 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pkg_header_shapingpolicy.py' 2023-04-28 05:57:51,497 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_address.py' 2023-04-28 05:57:51,497 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_addrgrp.py' 2023-04-28 05:57:51,497 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_centralsnatmap.py' 2023-04-28 05:57:51,498 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_policy.py' 2023-04-28 05:57:51,498 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_service_custom.py' 2023-04-28 05:57:51,498 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_metafields_firewall_service_group.py' 2023-04-28 05:57:51,499 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_policy.py' 2023-04-28 05:57:51,499 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_policy_sectionvalue.py' 2023-04-28 05:57:51,499 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_securitypolicy.py' 2023-04-28 05:57:51,500 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_pblock_firewall_securitypolicy_sectionvalue.py' 2023-04-28 05:57:51,500 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_reset_database.py' 2023-04-28 05:57:51,500 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_upgrade.py' 2023-04-28 05:57:51,501 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_commit.py' 2023-04-28 05:57:51,501 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_lock.py' 2023-04-28 05:57:51,501 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_config_workspace_unlock.py' 2023-04-28 05:57:51,501 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_devprof_adom.py' 2023-04-28 05:57:51,502 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_devprof_pkg.py' 2023-04-28 05:57:51,502 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pblock_adom.py' 2023-04-28 05:57:51,502 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pblock_obj.py' 2023-04-28 05:57:51,503 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg.py' 2023-04-28 05:57:51,503 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg_adom.py' 2023-04-28 05:57:51,504 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_pkg_global.py' 2023-04-28 05:57:51,504 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_wanprof_adom.py' 2023-04-28 05:57:51,505 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_pm_wanprof_pkg.py' 2023-04-28 05:57:51,505 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_qosprofile.py' 2023-04-28 05:57:51,505 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_region.py' 2023-04-28 05:57:51,506 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_rename.py' 2023-04-28 05:57:51,508 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist.py' 2023-04-28 05:57:51,509 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist6.py' 2023-04-28 05:57:51,509 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist6_rule.py' 2023-04-28 05:57:51,509 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_accesslist_rule.py' 2023-04-28 05:57:51,509 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_aspathlist.py' 2023-04-28 05:57:51,510 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_aspathlist_rule.py' 2023-04-28 05:57:51,510 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_communitylist.py' 2023-04-28 05:57:51,510 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_communitylist_rule.py' 2023-04-28 05:57:51,510 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist.py' 2023-04-28 05:57:51,511 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist6.py' 2023-04-28 05:57:51,511 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist6_rule.py' 2023-04-28 05:57:51,511 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_prefixlist_rule.py' 2023-04-28 05:57:51,512 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_routemap.py' 2023-04-28 05:57:51,512 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_router_routemap_rule.py' 2023-04-28 05:57:51,512 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_abort.py' 2023-04-28 05:57:51,513 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_assign_package.py' 2023-04-28 05:57:51,513 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_cliprof_check.py' 2023-04-28 05:57:51,513 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_import_dev_objs.py' 2023-04-28 05:57:51,514 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_device.py' 2023-04-28 05:57:51,514 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_package.py' 2023-04-28 05:57:51,514 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_install_preview.py' 2023-04-28 05:57:51,514 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_cancel_install.py' 2023-04-28 05:57:51,515 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_clone.py' 2023-04-28 05:57:51,515 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_commit.py' 2023-04-28 05:57:51,515 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_package_move.py' 2023-04-28 05:57:51,516 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_pblock_clone.py' 2023-04-28 05:57:51,516 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_preview_result.py' 2023-04-28 05:57:51,516 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_reinstall_package.py' 2023-04-28 05:57:51,516 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_securityconsole_sign_certificate_template.py' 2023-04-28 05:57:51,517 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bwl.py' 2023-04-28 05:57:51,517 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bwl_entries.py' 2023-04-28 05:57:51,517 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bword.py' 2023-04-28 05:57:51,518 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_bword_entries.py' 2023-04-28 05:57:51,518 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_dnsbl.py' 2023-04-28 05:57:51,518 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_dnsbl_entries.py' 2023-04-28 05:57:51,518 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_iptrust.py' 2023-04-28 05:57:51,519 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_iptrust_entries.py' 2023-04-28 05:57:51,519 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_mheader.py' 2023-04-28 05:57:51,519 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_mheader_entries.py' 2023-04-28 05:57:51,520 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile.py' 2023-04-28 05:57:51,520 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_gmail.py' 2023-04-28 05:57:51,520 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_imap.py' 2023-04-28 05:57:51,521 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_mapi.py' 2023-04-28 05:57:51,521 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_msnhotmail.py' 2023-04-28 05:57:51,521 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_pop3.py' 2023-04-28 05:57:51,521 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_smtp.py' 2023-04-28 05:57:51,522 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_spamfilter_profile_yahoomail.py' 2023-04-28 05:57:51,522 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile.py' 2023-04-28 05:57:51,522 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_filefilter.py' 2023-04-28 05:57:51,523 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_filefilter_entries.py' 2023-04-28 05:57:51,523 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sshfilter_profile_shellcommands.py' 2023-04-28 05:57:51,523 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_customcommand.py' 2023-04-28 05:57:51,523 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_dsl_policy.py' 2023-04-28 05:57:51,524 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile.py' 2023-04-28 05:57:51,524 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_customtlvs.py' 2023-04-28 05:57:51,524 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_medlocationservice.py' 2023-04-28 05:57:51,525 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_lldpprofile_mednetworkpolicy.py' 2023-04-28 05:57:51,525 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch.py' 2023-04-28 05:57:51,526 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_8021xsettings.py' 2023-04-28 05:57:51,526 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_customcommand.py' 2023-04-28 05:57:51,527 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_igmpsnooping.py' 2023-04-28 05:57:51,527 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ipsourceguard.py' 2023-04-28 05:57:51,527 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ipsourceguard_bindingentry.py' 2023-04-28 05:57:51,527 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_mirror.py' 2023-04-28 05:57:51,528 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_ports.py' 2023-04-28 05:57:51,528 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_remotelog.py' 2023-04-28 05:57:51,529 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpcommunity.py' 2023-04-28 05:57:51,529 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpcommunity_hosts.py' 2023-04-28 05:57:51,529 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpsysinfo.py' 2023-04-28 05:57:51,530 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmptrapthreshold.py' 2023-04-28 05:57:51,530 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_snmpuser.py' 2023-04-28 05:57:51,530 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_stormcontrol.py' 2023-04-28 05:57:51,530 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_stpsettings.py' 2023-04-28 05:57:51,531 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_switchlog.py' 2023-04-28 05:57:51,531 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_managedswitch_switchstpsettings.py' 2023-04-28 05:57:51,531 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_dot1pmap.py' 2023-04-28 05:57:51,531 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_ipdscpmap.py' 2023-04-28 05:57:51,532 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_ipdscpmap_map.py' 2023-04-28 05:57:51,532 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_qospolicy.py' 2023-04-28 05:57:51,532 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_queuepolicy.py' 2023-04-28 05:57:51,533 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_qos_queuepolicy_cosqueue.py' 2023-04-28 05:57:51,533 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_securitypolicy_8021x.py' 2023-04-28 05:57:51,533 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_switchcontroller_securitypolicy_captiveportal.py' 2023-04-28 05:57:51,534 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_api_sdnconnector.py' 2023-04-28 05:57:51,534 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_generate_wsdl.py' 2023-04-28 05:57:51,534 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_hitcount.py' 2023-04-28 05:57:51,534 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_login_challenge.py' 2023-04-28 05:57:51,535 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_login_user.py' 2023-04-28 05:57:51,535 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_logout.py' 2023-04-28 05:57:51,535 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_proxy_json.py' 2023-04-28 05:57:51,535 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_reboot.py' 2023-04-28 05:57:51,536 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_sys_task_result.py' 2023-04-28 05:57:51,536 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_group.py' 2023-04-28 05:57:51,536 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_group_member.py' 2023-04-28 05:57:51,537 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_ldap.py' 2023-04-28 05:57:51,537 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_ldap_adom.py' 2023-04-28 05:57:51,537 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_profile.py' 2023-04-28 05:57:51,538 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_profile_datamaskcustomfields.py' 2023-04-28 05:57:51,538 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_radius.py' 2023-04-28 05:57:51,539 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_setting.py' 2023-04-28 05:57:51,539 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_tacacs.py' 2023-04-28 05:57:51,540 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user.py' 2023-04-28 05:57:51,540 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_adom.py' 2023-04-28 05:57:51,540 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_adomexclude.py' 2023-04-28 05:57:51,541 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_appfilter.py' 2023-04-28 05:57:51,541 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_dashboard.py' 2023-04-28 05:57:51,541 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_dashboardtabs.py' 2023-04-28 05:57:51,542 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_ipsfilter.py' 2023-04-28 05:57:51,542 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_metadata.py' 2023-04-28 05:57:51,542 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_policypackage.py' 2023-04-28 05:57:51,542 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_restrictdevvdom.py' 2023-04-28 05:57:51,543 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_admin_user_webfilter.py' 2023-04-28 05:57:51,543 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertconsole.py' 2023-04-28 05:57:51,543 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertemail.py' 2023-04-28 05:57:51,544 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertevent.py' 2023-04-28 05:57:51,544 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_alertevent_alertdestination.py' 2023-04-28 05:57:51,544 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete.py' 2023-04-28 05:57:51,545 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_dlpfilesautodeletion.py' 2023-04-28 05:57:51,545 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_logautodeletion.py' 2023-04-28 05:57:51,545 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_quarantinefilesautodeletion.py' 2023-04-28 05:57:51,545 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_autodelete_reportautodeletion.py' 2023-04-28 05:57:51,546 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_backup_allsettings.py' 2023-04-28 05:57:51,546 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_ca.py' 2023-04-28 05:57:51,546 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_crl.py' 2023-04-28 05:57:51,547 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_local.py' 2023-04-28 05:57:51,547 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_oftp.py' 2023-04-28 05:57:51,547 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_remote.py' 2023-04-28 05:57:51,547 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_certificate_ssh.py' 2023-04-28 05:57:51,548 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_connector.py' 2023-04-28 05:57:51,548 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_customlanguage.py' 2023-04-28 05:57:51,548 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server.py' 2023-04-28 05:57:51,549 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_excluderange.py' 2023-04-28 05:57:51,549 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_iprange.py' 2023-04-28 05:57:51,550 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_options.py' 2023-04-28 05:57:51,550 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dhcp_server_reservedaddress.py' 2023-04-28 05:57:51,550 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dm.py' 2023-04-28 05:57:51,551 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_dns.py' 2023-04-28 05:57:51,551 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_docker.py' 2023-04-28 05:57:51,551 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_externalresource.py' 2023-04-28 05:57:51,552 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fips.py' 2023-04-28 05:57:51,552 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiguard.py' 2023-04-28 05:57:51,552 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiview_autocache.py' 2023-04-28 05:57:51,553 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_fortiview_setting.py' 2023-04-28 05:57:51,553 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipcountry.py' 2023-04-28 05:57:51,553 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride.py' 2023-04-28 05:57:51,554 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride_ip6range.py' 2023-04-28 05:57:51,554 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_geoipoverride_iprange.py' 2023-04-28 05:57:51,554 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_global.py' 2023-04-28 05:57:51,555 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_guiact.py' 2023-04-28 05:57:51,555 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha.py' 2023-04-28 05:57:51,556 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_monitoredinterfaces.py' 2023-04-28 05:57:51,556 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_monitoredips.py' 2023-04-28 05:57:51,556 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ha_peer.py' 2023-04-28 05:57:51,556 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_hascheduledcheck.py' 2023-04-28 05:57:51,557 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface.py' 2023-04-28 05:57:51,557 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface_ipv6.py' 2023-04-28 05:57:51,557 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_interface_member.py' 2023-04-28 05:57:51,558 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_localinpolicy.py' 2023-04-28 05:57:51,558 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_localinpolicy6.py' 2023-04-28 05:57:51,558 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_disk_filter.py' 2023-04-28 05:57:51,559 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_disk_setting.py' 2023-04-28 05:57:51,559 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer2_filter.py' 2023-04-28 05:57:51,560 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer2_setting.py' 2023-04-28 05:57:51,560 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer3_filter.py' 2023-04-28 05:57:51,560 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer3_setting.py' 2023-04-28 05:57:51,561 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer_filter.py' 2023-04-28 05:57:51,561 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_fortianalyzer_setting.py' 2023-04-28 05:57:51,562 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_memory_filter.py' 2023-04-28 05:57:51,562 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_memory_setting.py' 2023-04-28 05:57:51,562 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_setting.py' 2023-04-28 05:57:51,563 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd2_filter.py' 2023-04-28 05:57:51,563 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd2_setting.py' 2023-04-28 05:57:51,564 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd3_filter.py' 2023-04-28 05:57:51,564 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd3_setting.py' 2023-04-28 05:57:51,565 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd_filter.py' 2023-04-28 05:57:51,565 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_locallog_syslogd_setting.py' 2023-04-28 05:57:51,565 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_alert.py' 2023-04-28 05:57:51,566 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_devicedisable.py' 2023-04-28 05:57:51,566 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_fospolicystats.py' 2023-04-28 05:57:51,566 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_interfacestats.py' 2023-04-28 05:57:51,566 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ioc.py' 2023-04-28 05:57:51,567 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_maildomain.py' 2023-04-28 05:57:51,567 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit.py' 2023-04-28 05:57:51,567 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit_device.py' 2023-04-28 05:57:51,567 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_ratelimit_ratelimits.py' 2023-04-28 05:57:51,568 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings.py' 2023-04-28 05:57:51,569 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollinganalyzer.py' 2023-04-28 05:57:51,569 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollinglocal.py' 2023-04-28 05:57:51,570 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_settings_rollingregular.py' 2023-04-28 05:57:51,570 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_log_topology.py' 2023-04-28 05:57:51,570 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile.py' 2023-04-28 05:57:51,571 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile_devicefilter.py' 2023-04-28 05:57:51,571 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_clientprofile_logfilter.py' 2023-04-28 05:57:51,571 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_logfetch_serversettings.py' 2023-04-28 05:57:51,571 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_mail.py' 2023-04-28 05:57:51,572 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_mcpolicydisabledadoms.py' 2023-04-28 05:57:51,572 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_meta.py' 2023-04-28 05:57:51,572 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_meta_sysmetafields.py' 2023-04-28 05:57:51,573 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_metadata_admins.py' 2023-04-28 05:57:51,573 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu.py' 2023-04-28 05:57:51,574 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_fpanomaly.py' 2023-04-28 05:57:51,574 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_isfnpqueues.py' 2023-04-28 05:57:51,574 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_portcpumap.py' 2023-04-28 05:57:51,574 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_portnpumap.py' 2023-04-28 05:57:51,575 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_priorityprotocol.py' 2023-04-28 05:57:51,575 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_npu_swehhash.py' 2023-04-28 05:57:51,575 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ntp.py' 2023-04-28 05:57:51,576 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_ntp_ntpserver.py' 2023-04-28 05:57:51,576 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_objecttagging.py' 2023-04-28 05:57:51,576 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_passwordpolicy.py' 2023-04-28 05:57:51,577 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup.py' 2023-04-28 05:57:51,578 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_admin.py' 2023-04-28 05:57:51,578 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_alertmail.py' 2023-04-28 05:57:51,578 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_auth.py' 2023-04-28 05:57:51,579 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_automation.py' 2023-04-28 05:57:51,579 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_custommessage.py' 2023-04-28 05:57:51,579 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_devicedetectionportal.py' 2023-04-28 05:57:51,579 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_ec.py' 2023-04-28 05:57:51,580 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_fortiguardwf.py' 2023-04-28 05:57:51,580 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_ftp.py' 2023-04-28 05:57:51,580 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_http.py' 2023-04-28 05:57:51,581 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_icap.py' 2023-04-28 05:57:51,581 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mail.py' 2023-04-28 05:57:51,581 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm1.py' 2023-04-28 05:57:51,581 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm3.py' 2023-04-28 05:57:51,582 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm4.py' 2023-04-28 05:57:51,582 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mm7.py' 2023-04-28 05:57:51,582 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_mms.py' 2023-04-28 05:57:51,583 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_nacquar.py' 2023-04-28 05:57:51,583 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_nntp.py' 2023-04-28 05:57:51,583 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_spam.py' 2023-04-28 05:57:51,584 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_sslvpn.py' 2023-04-28 05:57:51,584 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_trafficquota.py' 2023-04-28 05:57:51,584 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_utm.py' 2023-04-28 05:57:51,585 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsggroup_webproxy.py' 2023-04-28 05:57:51,585 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_replacemsgimage.py' 2023-04-28 05:57:51,585 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_autocache.py' 2023-04-28 05:57:51,585 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_estbrowsetime.py' 2023-04-28 05:57:51,586 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group.py' 2023-04-28 05:57:51,586 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group_chartalternative.py' 2023-04-28 05:57:51,586 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_group_groupby.py' 2023-04-28 05:57:51,587 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_report_setting.py' 2023-04-28 05:57:51,587 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_route.py' 2023-04-28 05:57:51,587 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_route6.py' 2023-04-28 05:57:51,587 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_saml.py' 2023-04-28 05:57:51,588 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_saml_fabricidp.py' 2023-04-28 05:57:51,588 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector.py' 2023-04-28 05:57:51,589 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_externalaccountlist.py' 2023-04-28 05:57:51,589 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_externalip.py' 2023-04-28 05:57:51,589 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_forwardingrule.py' 2023-04-28 05:57:51,590 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_gcpprojectlist.py' 2023-04-28 05:57:51,590 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_nic.py' 2023-04-28 05:57:51,590 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_nic_ip.py' 2023-04-28 05:57:51,590 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_route.py' 2023-04-28 05:57:51,591 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_routetable.py' 2023-04-28 05:57:51,591 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sdnconnector_routetable_route.py' 2023-04-28 05:57:51,591 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_smsserver.py' 2023-04-28 05:57:51,592 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sniffer.py' 2023-04-28 05:57:51,592 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community.py' 2023-04-28 05:57:51,592 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community_hosts.py' 2023-04-28 05:57:51,592 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_community_hosts6.py' 2023-04-28 05:57:51,593 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_sysinfo.py' 2023-04-28 05:57:51,593 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_snmp_user.py' 2023-04-28 05:57:51,593 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_socfabric.py' 2023-04-28 05:57:51,594 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql.py' 2023-04-28 05:57:51,594 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_customindex.py' 2023-04-28 05:57:51,594 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_customskipidx.py' 2023-04-28 05:57:51,595 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sql_tsindexfield.py' 2023-04-28 05:57:51,595 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_sslciphersuites.py' 2023-04-28 05:57:51,595 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_syslog.py' 2023-04-28 05:57:51,596 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_virtualwirepair.py' 2023-04-28 05:57:51,596 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_webproxy.py' 2023-04-28 05:57:51,596 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_workflow_approvalmatrix.py' 2023-04-28 05:57:51,596 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_system_workflow_approvalmatrix_approver.py' 2023-04-28 05:57:51,597 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_template.py' 2023-04-28 05:57:51,597 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_templategroup.py' 2023-04-28 05:57:51,597 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_adgrp.py' 2023-04-28 05:57:51,598 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_clearpass.py' 2023-04-28 05:57:51,598 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_connector.py' 2023-04-28 05:57:51,598 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device.py' 2023-04-28 05:57:51,599 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device_dynamicmapping.py' 2023-04-28 05:57:51,599 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_device_tagging.py' 2023-04-28 05:57:51,599 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicecategory.py' 2023-04-28 05:57:51,599 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup.py' 2023-04-28 05:57:51,600 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup_dynamicmapping.py' 2023-04-28 05:57:51,600 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_devicegroup_tagging.py' 2023-04-28 05:57:51,600 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_domaincontroller.py' 2023-04-28 05:57:51,601 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_domaincontroller_extraserver.py' 2023-04-28 05:57:51,601 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_exchange.py' 2023-04-28 05:57:51,601 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fortitoken.py' 2023-04-28 05:57:51,602 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fsso.py' 2023-04-28 05:57:51,602 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fsso_dynamicmapping.py' 2023-04-28 05:57:51,603 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fssopolling.py' 2023-04-28 05:57:51,603 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_fssopolling_adgrp.py' 2023-04-28 05:57:51,603 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group.py' 2023-04-28 05:57:51,604 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping.py' 2023-04-28 05:57:51,605 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_guest.py' 2023-04-28 05:57:51,605 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_match.py' 2023-04-28 05:57:51,605 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_dynamicmapping_sslvpnoschecklist.py' 2023-04-28 05:57:51,605 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_guest.py' 2023-04-28 05:57:51,606 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_group_match.py' 2023-04-28 05:57:51,606 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_krbkeytab.py' 2023-04-28 05:57:51,606 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_ldap.py' 2023-04-28 05:57:51,607 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_ldap_dynamicmapping.py' 2023-04-28 05:57:51,608 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_local.py' 2023-04-28 05:57:51,608 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_nsx.py' 2023-04-28 05:57:51,608 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_nsx_service.py' 2023-04-28 05:57:51,608 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_passwordpolicy.py' 2023-04-28 05:57:51,609 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_peer.py' 2023-04-28 05:57:51,609 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_peergrp.py' 2023-04-28 05:57:51,609 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_pop3.py' 2023-04-28 05:57:51,610 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_pxgrid.py' 2023-04-28 05:57:51,610 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius.py' 2023-04-28 05:57:51,611 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_accountingserver.py' 2023-04-28 05:57:51,612 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_dynamicmapping.py' 2023-04-28 05:57:51,612 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_radius_dynamicmapping_accountingserver.py' 2023-04-28 05:57:51,613 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_saml.py' 2023-04-28 05:57:51,613 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_securityexemptlist.py' 2023-04-28 05:57:51,613 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_securityexemptlist_rule.py' 2023-04-28 05:57:51,614 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_tacacs.py' 2023-04-28 05:57:51,614 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_tacacs_dynamicmapping.py' 2023-04-28 05:57:51,614 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_vcenter.py' 2023-04-28 05:57:51,615 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_user_vcenter_rule.py' 2023-04-28 05:57:51,615 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_utmprofile.py' 2023-04-28 05:57:51,616 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap.py' 2023-04-28 05:57:51,618 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_dynamicmapping.py' 2023-04-28 05:57:51,619 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_macfilterlist.py' 2023-04-28 05:57:51,619 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_mpskkey.py' 2023-04-28 05:57:51,620 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_portalmessageoverrides.py' 2023-04-28 05:57:51,620 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_vlanname.py' 2023-04-28 05:57:51,620 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vap_vlanpool.py' 2023-04-28 05:57:51,620 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vapgroup.py' 2023-04-28 05:57:51,621 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile.py' 2023-04-28 05:57:51,621 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile_fortiguardcategory.py' 2023-04-28 05:57:51,621 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_profile_fortiguardcategory_filters.py' 2023-04-28 05:57:51,622 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_youtubechannelfilter.py' 2023-04-28 05:57:51,622 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_videofilter_youtubechannelfilter_entries.py' 2023-04-28 05:57:51,622 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile.py' 2023-04-28 05:57:51,623 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_msrp.py' 2023-04-28 05:57:51,623 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_sccp.py' 2023-04-28 05:57:51,624 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_voip_profile_sip.py' 2023-04-28 05:57:51,624 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_ca.py' 2023-04-28 05:57:51,625 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_ocspserver.py' 2023-04-28 05:57:51,625 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_certificate_remote.py' 2023-04-28 05:57:51,625 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ipsec_fec.py' 2023-04-28 05:57:51,626 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ipsec_fec_mappings.py' 2023-04-28 05:57:51,626 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ssl_settings.py' 2023-04-28 05:57:51,627 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpn_ssl_settings_authenticationrule.py' 2023-04-28 05:57:51,627 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node.py' 2023-04-28 05:57:51,628 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_iprange.py' 2023-04-28 05:57:51,628 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_ipv4excluderange.py' 2023-04-28 05:57:51,628 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_protectedsubnet.py' 2023-04-28 05:57:51,628 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_node_summaryaddr.py' 2023-04-28 05:57:51,629 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnmgr_vpntable.py' 2023-04-28 05:57:51,630 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_hostchecksoftware.py' 2023-04-28 05:57:51,630 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_hostchecksoftware_checkitemlist.py' 2023-04-28 05:57:51,630 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal.py' 2023-04-28 05:57:51,631 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup.py' 2023-04-28 05:57:51,632 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup_bookmarks.py' 2023-04-28 05:57:51,632 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_bookmarkgroup_bookmarks_formdata.py' 2023-04-28 05:57:51,632 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_macaddrcheckrule.py' 2023-04-28 05:57:51,633 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_oschecklist.py' 2023-04-28 05:57:51,633 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_portal_splitdns.py' 2023-04-28 05:57:51,633 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_vpnsslweb_realm.py' 2023-04-28 05:57:51,634 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_mainclass.py' 2023-04-28 05:57:51,634 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile.py' 2023-04-28 05:57:51,635 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_addresslist.py' 2023-04-28 05:57:51,635 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint.py' 2023-04-28 05:57:51,636 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_contentlength.py' 2023-04-28 05:57:51,636 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_exception.py' 2023-04-28 05:57:51,637 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_headerlength.py' 2023-04-28 05:57:51,637 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_hostname.py' 2023-04-28 05:57:51,637 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_linelength.py' 2023-04-28 05:57:51,638 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_malformed.py' 2023-04-28 05:57:51,638 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxcookie.py' 2023-04-28 05:57:51,638 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxheaderline.py' 2023-04-28 05:57:51,638 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxrangesegment.py' 2023-04-28 05:57:51,639 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_maxurlparam.py' 2023-04-28 05:57:51,639 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_method.py' 2023-04-28 05:57:51,639 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_paramlength.py' 2023-04-28 05:57:51,640 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_urlparamlength.py' 2023-04-28 05:57:51,640 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_constraint_version.py' 2023-04-28 05:57:51,640 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_method.py' 2023-04-28 05:57:51,641 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_method_methodpolicy.py' 2023-04-28 05:57:51,641 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature.py' 2023-04-28 05:57:51,641 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature_customsignature.py' 2023-04-28 05:57:51,642 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_signature_mainclass.py' 2023-04-28 05:57:51,642 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_urlaccess.py' 2023-04-28 05:57:51,642 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_profile_urlaccess_accesspattern.py' 2023-04-28 05:57:51,642 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_signature.py' 2023-04-28 05:57:51,643 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_waf_subclass.py' 2023-04-28 05:57:51,643 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wagprofile.py' 2023-04-28 05:57:51,643 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_authgroup.py' 2023-04-28 05:57:51,644 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_peer.py' 2023-04-28 05:57:51,644 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile.py' 2023-04-28 05:57:51,644 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_cifs.py' 2023-04-28 05:57:51,645 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_ftp.py' 2023-04-28 05:57:51,645 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_http.py' 2023-04-28 05:57:51,645 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_mapi.py' 2023-04-28 05:57:51,646 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanopt_profile_tcp.py' 2023-04-28 05:57:51,646 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan.py' 2023-04-28 05:57:51,647 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_duplication.py' 2023-04-28 05:57:51,647 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_healthcheck.py' 2023-04-28 05:57:51,648 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_healthcheck_sla.py' 2023-04-28 05:57:51,648 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_members.py' 2023-04-28 05:57:51,648 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_neighbor.py' 2023-04-28 05:57:51,649 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_service.py' 2023-04-28 05:57:51,649 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_service_sla.py' 2023-04-28 05:57:51,649 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_sdwan_zone.py' 2023-04-28 05:57:51,650 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink.py' 2023-04-28 05:57:51,651 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_healthcheck.py' 2023-04-28 05:57:51,651 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_healthcheck_sla.py' 2023-04-28 05:57:51,651 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_members.py' 2023-04-28 05:57:51,652 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_neighbor.py' 2023-04-28 05:57:51,652 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_service.py' 2023-04-28 05:57:51,652 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wanprof_system_virtualwanlink_service_sla.py' 2023-04-28 05:57:51,653 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_categories.py' 2023-04-28 05:57:51,653 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_content.py' 2023-04-28 05:57:51,653 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_content_entries.py' 2023-04-28 05:57:51,654 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_contentheader.py' 2023-04-28 05:57:51,654 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_contentheader_entries.py' 2023-04-28 05:57:51,654 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_ftgdlocalcat.py' 2023-04-28 05:57:51,654 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_ftgdlocalrating.py' 2023-04-28 05:57:51,655 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile.py' 2023-04-28 05:57:51,656 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish.py' 2023-04-28 05:57:51,656 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish_custompatterns.py' 2023-04-28 05:57:51,656 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_antiphish_inspectionentries.py' 2023-04-28 05:57:51,657 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_filefilter.py' 2023-04-28 05:57:51,657 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_filefilter_entries.py' 2023-04-28 05:57:51,657 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf.py' 2023-04-28 05:57:51,658 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf_filters.py' 2023-04-28 05:57:51,658 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_ftgdwf_quota.py' 2023-04-28 05:57:51,658 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_override.py' 2023-04-28 05:57:51,659 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_urlextraction.py' 2023-04-28 05:57:51,659 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_web.py' 2023-04-28 05:57:51,659 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_profile_youtubechannelfilter.py' 2023-04-28 05:57:51,659 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_urlfilter.py' 2023-04-28 05:57:51,660 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webfilter_urlfilter_entries.py' 2023-04-28 05:57:51,660 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardserver.py' 2023-04-28 05:57:51,660 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardservergroup.py' 2023-04-28 05:57:51,661 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_forwardservergroup_serverlist.py' 2023-04-28 05:57:51,661 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_profile.py' 2023-04-28 05:57:51,661 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_profile_headers.py' 2023-04-28 05:57:51,662 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_webproxy_wisp.py' 2023-04-28 05:57:51,662 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_widsprofile.py' 2023-04-28 05:57:51,663 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile.py' 2023-04-28 05:57:51,665 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_denymaclist.py' 2023-04-28 05:57:51,665 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_eslsesdongle.py' 2023-04-28 05:57:51,665 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_lan.py' 2023-04-28 05:57:51,666 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_lbs.py' 2023-04-28 05:57:51,666 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_platform.py' 2023-04-28 05:57:51,666 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio1.py' 2023-04-28 05:57:51,667 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio2.py' 2023-04-28 05:57:51,668 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio3.py' 2023-04-28 05:57:51,668 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_radio4.py' 2023-04-28 05:57:51,669 wheel INFO adding 'ansible_collections/fortinet/fortimanager/plugins/modules/fmgr_wtpprofile_splittunnelingacl.py' 2023-04-28 05:57:51,669 wheel INFO adding 'ansible_collections/fortinet/fortios/CHANGELOG.rst' 2023-04-28 05:57:51,670 wheel INFO adding 'ansible_collections/fortinet/fortios/FILES.json' 2023-04-28 05:57:51,671 wheel INFO adding 'ansible_collections/fortinet/fortios/LICENSE' 2023-04-28 05:57:51,671 wheel INFO adding 'ansible_collections/fortinet/fortios/MANIFEST.json' 2023-04-28 05:57:51,671 wheel INFO adding 'ansible_collections/fortinet/fortios/README.md' 2023-04-28 05:57:51,672 wheel INFO adding 'ansible_collections/fortinet/fortios/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:51,672 wheel INFO adding 'ansible_collections/fortinet/fortios/changelogs/changelog.yaml' 2023-04-28 05:57:51,673 wheel INFO adding 'ansible_collections/fortinet/fortios/changelogs/config.yaml' 2023-04-28 05:57:51,673 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_firewall_address.yml' 2023-04-28 05:57:51,673 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_firewall_address_group.yml' 2023-04-28 05:57:51,673 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_firewall_vip.yml' 2023-04-28 05:57:51,673 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_system_alias.yml' 2023-04-28 05:57:51,674 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_system_dns.yml' 2023-04-28 05:57:51,674 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_system_global.yml' 2023-04-28 05:57:51,674 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_system_ha.yml' 2023-04-28 05:57:51,674 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_system_ha_monitor.yml' 2023-04-28 05:57:51,674 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_system_ntp.yml' 2023-04-28 05:57:51,675 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/set_system_zone.yml' 2023-04-28 05:57:51,675 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/httpapi/readme' 2023-04-28 05:57:51,675 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/httpapi/set_system_global.yml' 2023-04-28 05:57:51,675 wheel INFO adding 'ansible_collections/fortinet/fortios/examples/httpapi/inventory/hosts' 2023-04-28 05:57:51,676 wheel INFO adding 'ansible_collections/fortinet/fortios/meta/runtime.yml' 2023-04-28 05:57:51,676 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/doc_fragments/fortios.py' 2023-04-28 05:57:51,676 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/httpapi/fortios.py' 2023-04-28 05:57:51,676 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/common/__init__.py' 2023-04-28 05:57:51,677 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/common/type_utils.py' 2023-04-28 05:57:51,677 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/__init__.py' 2023-04-28 05:57:51,677 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/common.py' 2023-04-28 05:57:51,677 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/fortimanager.py' 2023-04-28 05:57:51,678 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/__init__.py' 2023-04-28 05:57:51,678 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/comparison.py' 2023-04-28 05:57:51,678 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/data_post_processor.py' 2023-04-28 05:57:51,679 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/fortios.py' 2023-04-28 05:57:51,679 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/secret_field.py' 2023-04-28 05:57:51,679 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/__init__.py' 2023-04-28 05:57:51,679 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/__init__.py' 2023-04-28 05:57:51,680 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/facts.py' 2023-04-28 05:57:51,680 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/__init__.py' 2023-04-28 05:57:51,680 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/system.py' 2023-04-28 05:57:51,680 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/__init__.py' 2023-04-28 05:57:51,681 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/facts.py' 2023-04-28 05:57:51,681 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/__init__.py' 2023-04-28 05:57:51,681 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/system.py' 2023-04-28 05:57:51,682 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/__init__.py' 2023-04-28 05:57:51,683 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_alertemail_setting.py' 2023-04-28 05:57:51,683 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_heuristic.py' 2023-04-28 05:57:51,684 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_mms_checksum.py' 2023-04-28 05:57:51,684 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_notification.py' 2023-04-28 05:57:51,686 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_profile.py' 2023-04-28 05:57:51,689 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_quarantine.py' 2023-04-28 05:57:51,690 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_antivirus_settings.py' 2023-04-28 05:57:51,691 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_application_custom.py' 2023-04-28 05:57:51,691 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_application_group.py' 2023-04-28 05:57:51,692 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_application_list.py' 2023-04-28 05:57:51,693 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_application_name.py' 2023-04-28 05:57:51,693 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_application_rule_settings.py' 2023-04-28 05:57:51,693 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_rule.py' 2023-04-28 05:57:51,694 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_scheme.py' 2023-04-28 05:57:51,694 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_authentication_setting.py' 2023-04-28 05:57:51,695 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_automation_setting.py' 2023-04-28 05:57:51,695 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_ca.py' 2023-04-28 05:57:51,696 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_crl.py' 2023-04-28 05:57:51,696 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_local.py' 2023-04-28 05:57:51,697 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_certificate_remote.py' 2023-04-28 05:57:51,697 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_cifs_domain_controller.py' 2023-04-28 05:57:51,697 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_cifs_profile.py' 2023-04-28 05:57:51,698 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_configuration_fact.py' 2023-04-28 05:57:51,699 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_credential_store_domain_controller.py' 2023-04-28 05:57:51,700 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_data_type.py' 2023-04-28 05:57:51,700 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_dictionary.py' 2023-04-28 05:57:51,700 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_filepattern.py' 2023-04-28 05:57:51,701 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_fp_doc_source.py' 2023-04-28 05:57:51,702 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_fp_sensitivity.py' 2023-04-28 05:57:51,702 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_profile.py' 2023-04-28 05:57:51,702 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_sensitivity.py' 2023-04-28 05:57:51,703 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_sensor.py' 2023-04-28 05:57:51,704 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dlp_settings.py' 2023-04-28 05:57:51,704 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dnsfilter_domain_filter.py' 2023-04-28 05:57:51,705 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dnsfilter_profile.py' 2023-04-28 05:57:51,705 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dpdk_cpus.py' 2023-04-28 05:57:51,706 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_dpdk_global.py' 2023-04-28 05:57:51,706 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_block_allow_list.py' 2023-04-28 05:57:51,706 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_bwl.py' 2023-04-28 05:57:51,707 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_bword.py' 2023-04-28 05:57:51,707 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_dnsbl.py' 2023-04-28 05:57:51,708 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_fortishield.py' 2023-04-28 05:57:51,708 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_iptrust.py' 2023-04-28 05:57:51,708 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_mheader.py' 2023-04-28 05:57:51,709 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_options.py' 2023-04-28 05:57:51,709 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_emailfilter_profile.py' 2023-04-28 05:57:51,710 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_client.py' 2023-04-28 05:57:51,711 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_fctems.py' 2023-04-28 05:57:51,711 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_forticlient_ems.py' 2023-04-28 05:57:51,712 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_forticlient_registration_sync.py' 2023-04-28 05:57:51,712 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_profile.py' 2023-04-28 05:57:51,713 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_registered_forticlient.py' 2023-04-28 05:57:51,713 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_endpoint_control_settings.py' 2023-04-28 05:57:51,714 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_export_config_playbook.py' 2023-04-28 05:57:51,715 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_dataplan.py' 2023-04-28 05:57:51,716 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_extender.py' 2023-04-28 05:57:51,717 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_controller_extender_profile.py' 2023-04-28 05:57:51,718 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_extender_info.py' 2023-04-28 05:57:51,718 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_lte_carrier_by_mcc_mnc.py' 2023-04-28 05:57:51,718 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_lte_carrier_list.py' 2023-04-28 05:57:51,719 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_modem_status.py' 2023-04-28 05:57:51,719 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extender_sys_info.py' 2023-04-28 05:57:51,719 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_dataplan.py' 2023-04-28 05:57:51,719 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_extender.py' 2023-04-28 05:57:51,720 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_extender_profile.py' 2023-04-28 05:57:51,720 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_fortigate.py' 2023-04-28 05:57:51,721 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_extension_controller_fortigate_profile.py' 2023-04-28 05:57:51,721 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_file_filter_profile.py' 2023-04-28 05:57:51,722 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy.py' 2023-04-28 05:57:51,725 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy6.py' 2023-04-28 05:57:51,728 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy_ssh_client_cert.py' 2023-04-28 05:57:51,729 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_access_proxy_virtual_host.py' 2023-04-28 05:57:51,729 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_acl.py' 2023-04-28 05:57:51,730 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_acl6.py' 2023-04-28 05:57:51,730 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address.py' 2023-04-28 05:57:51,731 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address6.py' 2023-04-28 05:57:51,731 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_address6_template.py' 2023-04-28 05:57:51,732 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_addrgrp.py' 2023-04-28 05:57:51,732 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_addrgrp6.py' 2023-04-28 05:57:51,733 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_auth_portal.py' 2023-04-28 05:57:51,733 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_carrier_endpoint_bwl.py' 2023-04-28 05:57:51,734 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_central_snat_map.py' 2023-04-28 05:57:51,734 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_city.py' 2023-04-28 05:57:51,735 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_consolidated_policy.py' 2023-04-28 05:57:51,735 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_country.py' 2023-04-28 05:57:51,735 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_decrypted_traffic_mirror.py' 2023-04-28 05:57:51,736 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dnstranslation.py' 2023-04-28 05:57:51,736 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dos_policy.py' 2023-04-28 05:57:51,737 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_dos_policy6.py' 2023-04-28 05:57:51,737 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_global.py' 2023-04-28 05:57:51,739 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_gtp.py' 2023-04-28 05:57:51,740 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_identity_based_route.py' 2023-04-28 05:57:51,741 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_interface_policy.py' 2023-04-28 05:57:51,742 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_interface_policy6.py' 2023-04-28 05:57:51,742 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service.py' 2023-04-28 05:57:51,743 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_addition.py' 2023-04-28 05:57:51,743 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_append.py' 2023-04-28 05:57:51,743 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_botnet.py' 2023-04-28 05:57:51,744 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_custom.py' 2023-04-28 05:57:51,744 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_custom_group.py' 2023-04-28 05:57:51,744 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_definition.py' 2023-04-28 05:57:51,745 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_extension.py' 2023-04-28 05:57:51,745 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_group.py' 2023-04-28 05:57:51,746 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_ipbl_reason.py' 2023-04-28 05:57:51,746 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_ipbl_vendor.py' 2023-04-28 05:57:51,746 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_list.py' 2023-04-28 05:57:51,747 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_name.py' 2023-04-28 05:57:51,747 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_owner.py' 2023-04-28 05:57:51,747 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_reputation.py' 2023-04-28 05:57:51,747 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_internet_service_sld.py' 2023-04-28 05:57:51,748 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ip_translation.py' 2023-04-28 05:57:51,748 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipmacbinding_setting.py' 2023-04-28 05:57:51,748 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipmacbinding_table.py' 2023-04-28 05:57:51,749 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ippool.py' 2023-04-28 05:57:51,749 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ippool6.py' 2023-04-28 05:57:51,750 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_iprope_list.py' 2023-04-28 05:57:51,750 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ipv6_eh_filter.py' 2023-04-28 05:57:51,750 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ldb_monitor.py' 2023-04-28 05:57:51,751 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_local_in_policy.py' 2023-04-28 05:57:51,751 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_local_in_policy6.py' 2023-04-28 05:57:51,752 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_mms_profile.py' 2023-04-28 05:57:51,753 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_address.py' 2023-04-28 05:57:51,754 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_address6.py' 2023-04-28 05:57:51,755 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_policy.py' 2023-04-28 05:57:51,755 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_multicast_policy6.py' 2023-04-28 05:57:51,755 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_network_service_dynamic.py' 2023-04-28 05:57:51,756 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_pfcp.py' 2023-04-28 05:57:51,757 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy.py' 2023-04-28 05:57:51,759 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy46.py' 2023-04-28 05:57:51,760 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy6.py' 2023-04-28 05:57:51,760 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_policy64.py' 2023-04-28 05:57:51,761 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_profile_group.py' 2023-04-28 05:57:51,762 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_profile_protocol_options.py' 2023-04-28 05:57:51,764 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proute.py' 2023-04-28 05:57:51,764 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_address.py' 2023-04-28 05:57:51,765 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_addrgrp.py' 2023-04-28 05:57:51,766 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_proxy_policy.py' 2023-04-28 05:57:51,767 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_region.py' 2023-04-28 05:57:51,767 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_group.py' 2023-04-28 05:57:51,767 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_onetime.py' 2023-04-28 05:57:51,768 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_schedule_recurring.py' 2023-04-28 05:57:51,768 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_security_policy.py' 2023-04-28 05:57:51,769 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_category.py' 2023-04-28 05:57:51,770 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_custom.py' 2023-04-28 05:57:51,770 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_service_group.py' 2023-04-28 05:57:51,771 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaper_per_ip_shaper.py' 2023-04-28 05:57:51,771 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaper_traffic_shaper.py' 2023-04-28 05:57:51,772 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaping_policy.py' 2023-04-28 05:57:51,772 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_shaping_profile.py' 2023-04-28 05:57:51,773 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_sniffer.py' 2023-04-28 05:57:51,774 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_host_key.py' 2023-04-28 05:57:51,774 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_local_ca.py' 2023-04-28 05:57:51,775 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_local_key.py' 2023-04-28 05:57:51,775 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssh_setting.py' 2023-04-28 05:57:51,775 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_server.py' 2023-04-28 05:57:51,776 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_setting.py' 2023-04-28 05:57:51,778 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ssl_ssh_profile.py' 2023-04-28 05:57:51,780 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_traffic_class.py' 2023-04-28 05:57:51,780 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_ttl_policy.py' 2023-04-28 05:57:51,781 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vendor_mac.py' 2023-04-28 05:57:51,782 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip.py' 2023-04-28 05:57:51,784 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip46.py' 2023-04-28 05:57:51,786 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip6.py' 2023-04-28 05:57:51,788 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vip64.py' 2023-04-28 05:57:51,788 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp.py' 2023-04-28 05:57:51,789 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp46.py' 2023-04-28 05:57:51,789 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp6.py' 2023-04-28 05:57:51,789 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_vipgrp64.py' 2023-04-28 05:57:51,790 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_wildcard_fqdn_custom.py' 2023-04-28 05:57:51,790 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_firewall_wildcard_fqdn_group.py' 2023-04-28 05:57:51,791 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ftp_proxy_explicit.py' 2023-04-28 05:57:51,791 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apn.py' 2023-04-28 05:57:51,791 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apn_shaper.py' 2023-04-28 05:57:51,792 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_apngrp.py' 2023-04-28 05:57:51,792 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_ie_allow_list.py' 2023-04-28 05:57:51,792 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_ie_white_list.py' 2023-04-28 05:57:51,793 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_message_filter_v0v1.py' 2023-04-28 05:57:51,794 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_message_filter_v2.py' 2023-04-28 05:57:51,794 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_rat_timeout_profile.py' 2023-04-28 05:57:51,794 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_gtp_tunnel_limit.py' 2023-04-28 05:57:51,795 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_nic.py' 2023-04-28 05:57:51,795 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_dce.py' 2023-04-28 05:57:51,795 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_session_stats.py' 2023-04-28 05:57:51,796 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_hardware_npu_np6_sse_stats.py' 2023-04-28 05:57:51,796 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_profile.py' 2023-04-28 05:57:51,797 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_server.py' 2023-04-28 05:57:51,797 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_icap_server_group.py' 2023-04-28 05:57:51,797 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_custom.py' 2023-04-28 05:57:51,798 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_decoder.py' 2023-04-28 05:57:51,798 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_global.py' 2023-04-28 05:57:51,799 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_rule.py' 2023-04-28 05:57:51,799 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_rule_settings.py' 2023-04-28 05:57:51,800 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_sensor.py' 2023-04-28 05:57:51,801 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_settings.py' 2023-04-28 05:57:51,801 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ips_view_map.py' 2023-04-28 05:57:51,801 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_json_generic.py' 2023-04-28 05:57:51,802 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_custom_field.py' 2023-04-28 05:57:51,802 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_disk_filter.py' 2023-04-28 05:57:51,803 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_disk_setting.py' 2023-04-28 05:57:51,804 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_eventfilter.py' 2023-04-28 05:57:51,804 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fact.py' 2023-04-28 05:57:51,805 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_filter.py' 2023-04-28 05:57:51,806 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_override_filter.py' 2023-04-28 05:57:51,807 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_override_setting.py' 2023-04-28 05:57:51,807 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer2_setting.py' 2023-04-28 05:57:51,808 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_filter.py' 2023-04-28 05:57:51,809 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_override_filter.py' 2023-04-28 05:57:51,809 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_override_setting.py' 2023-04-28 05:57:51,810 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer3_setting.py' 2023-04-28 05:57:51,811 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_filter.py' 2023-04-28 05:57:51,811 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_override_filter.py' 2023-04-28 05:57:51,812 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_override_setting.py' 2023-04-28 05:57:51,812 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_cloud_setting.py' 2023-04-28 05:57:51,813 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_filter.py' 2023-04-28 05:57:51,814 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_override_filter.py' 2023-04-28 05:57:51,814 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_override_setting.py' 2023-04-28 05:57:51,815 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortianalyzer_setting.py' 2023-04-28 05:57:51,816 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_filter.py' 2023-04-28 05:57:51,817 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_override_filter.py' 2023-04-28 05:57:51,817 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_override_setting.py' 2023-04-28 05:57:51,818 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_fortiguard_setting.py' 2023-04-28 05:57:51,818 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_gui_display.py' 2023-04-28 05:57:51,819 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_filter.py' 2023-04-28 05:57:51,819 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_global_setting.py' 2023-04-28 05:57:51,820 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_memory_setting.py' 2023-04-28 05:57:51,820 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_null_device_filter.py' 2023-04-28 05:57:51,821 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_null_device_setting.py' 2023-04-28 05:57:51,821 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_setting.py' 2023-04-28 05:57:51,822 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_filter.py' 2023-04-28 05:57:51,822 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_override_filter.py' 2023-04-28 05:57:51,823 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_override_setting.py' 2023-04-28 05:57:51,824 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd2_setting.py' 2023-04-28 05:57:51,825 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_filter.py' 2023-04-28 05:57:51,825 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_override_filter.py' 2023-04-28 05:57:51,826 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_override_setting.py' 2023-04-28 05:57:51,827 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd3_setting.py' 2023-04-28 05:57:51,827 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_filter.py' 2023-04-28 05:57:51,828 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_override_filter.py' 2023-04-28 05:57:51,829 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_override_setting.py' 2023-04-28 05:57:51,829 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd4_setting.py' 2023-04-28 05:57:51,830 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_filter.py' 2023-04-28 05:57:51,831 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_override_filter.py' 2023-04-28 05:57:51,831 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_override_setting.py' 2023-04-28 05:57:51,832 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_syslogd_setting.py' 2023-04-28 05:57:51,833 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting2_filter.py' 2023-04-28 05:57:51,833 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting2_setting.py' 2023-04-28 05:57:51,833 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting3_filter.py' 2023-04-28 05:57:51,834 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting3_setting.py' 2023-04-28 05:57:51,834 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting_filter.py' 2023-04-28 05:57:51,834 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_tacacsplusaccounting_setting.py' 2023-04-28 05:57:51,835 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_threat_weight.py' 2023-04-28 05:57:51,836 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_webtrends_filter.py' 2023-04-28 05:57:51,837 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_log_webtrends_setting.py' 2023-04-28 05:57:51,837 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_monitor.py' 2023-04-28 05:57:51,838 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_monitor_fact.py' 2023-04-28 05:57:51,839 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_monitoring_np6_ipsec_engine.py' 2023-04-28 05:57:51,839 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_monitoring_npu_hpe.py' 2023-04-28 05:57:51,840 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_nsxt_service_chain.py' 2023-04-28 05:57:51,840 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_nsxt_setting.py' 2023-04-28 05:57:51,840 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_pfcp_message_filter.py' 2023-04-28 05:57:51,841 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_report_chart.py' 2023-04-28 05:57:51,842 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_report_dataset.py' 2023-04-28 05:57:51,842 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_report_layout.py' 2023-04-28 05:57:51,843 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_report_setting.py' 2023-04-28 05:57:51,844 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_report_style.py' 2023-04-28 05:57:51,844 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_report_theme.py' 2023-04-28 05:57:51,845 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_access_list.py' 2023-04-28 05:57:51,845 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_access_list6.py' 2023-04-28 05:57:51,845 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_aspath_list.py' 2023-04-28 05:57:51,846 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_auth_path.py' 2023-04-28 05:57:51,846 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bfd.py' 2023-04-28 05:57:51,846 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bfd6.py' 2023-04-28 05:57:51,848 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_bgp.py' 2023-04-28 05:57:51,852 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_community_list.py' 2023-04-28 05:57:51,853 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_isis.py' 2023-04-28 05:57:51,854 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_key_chain.py' 2023-04-28 05:57:51,855 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast.py' 2023-04-28 05:57:51,855 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast6.py' 2023-04-28 05:57:51,856 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_multicast_flow.py' 2023-04-28 05:57:51,857 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ospf.py' 2023-04-28 05:57:51,858 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ospf6.py' 2023-04-28 05:57:51,860 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_policy.py' 2023-04-28 05:57:51,860 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_policy6.py' 2023-04-28 05:57:51,861 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_prefix_list.py' 2023-04-28 05:57:51,861 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_prefix_list6.py' 2023-04-28 05:57:51,862 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_rip.py' 2023-04-28 05:57:51,863 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_ripng.py' 2023-04-28 05:57:51,863 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_route_map.py' 2023-04-28 05:57:51,864 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_setting.py' 2023-04-28 05:57:51,865 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py' 2023-04-28 05:57:51,865 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static6.py' 2023-04-28 05:57:51,865 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_sctp_filter_profile.py' 2023-04-28 05:57:51,866 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_bwl.py' 2023-04-28 05:57:51,866 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_bword.py' 2023-04-28 05:57:51,867 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_dnsbl.py' 2023-04-28 05:57:51,867 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_fortishield.py' 2023-04-28 05:57:51,867 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_iptrust.py' 2023-04-28 05:57:51,867 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_mheader.py' 2023-04-28 05:57:51,868 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_options.py' 2023-04-28 05:57:51,868 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_spamfilter_profile.py' 2023-04-28 05:57:51,869 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_ssh_filter_profile.py' 2023-04-28 05:57:51,869 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_802_1x_settings.py' 2023-04-28 05:57:51,870 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_custom.py' 2023-04-28 05:57:51,870 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_default.py' 2023-04-28 05:57:51,870 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_auto_config_policy.py' 2023-04-28 05:57:51,871 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_custom_command.py' 2023-04-28 05:57:51,871 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_dynamic_port_policy.py' 2023-04-28 05:57:51,872 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_flow_tracking.py' 2023-04-28 05:57:51,872 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_fortilink_settings.py' 2023-04-28 05:57:51,872 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_global.py' 2023-04-28 05:57:51,873 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_igmp_snooping.py' 2023-04-28 05:57:51,873 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_initial_config_template.py' 2023-04-28 05:57:51,874 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_initial_config_vlans.py' 2023-04-28 05:57:51,874 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_lldp_profile.py' 2023-04-28 05:57:51,875 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_lldp_settings.py' 2023-04-28 05:57:51,875 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_location.py' 2023-04-28 05:57:51,876 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_mac_policy.py' 2023-04-28 05:57:51,876 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_mac_sync_settings.py' 2023-04-28 05:57:51,878 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_managed_switch.py' 2023-04-28 05:57:51,881 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_nac_device.py' 2023-04-28 05:57:51,881 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_nac_settings.py' 2023-04-28 05:57:51,881 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_network_monitor_settings.py' 2023-04-28 05:57:51,882 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_poe.py' 2023-04-28 05:57:51,882 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_port_policy.py' 2023-04-28 05:57:51,882 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_ptp_policy.py' 2023-04-28 05:57:51,883 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_ptp_settings.py' 2023-04-28 05:57:51,883 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_dot1p_map.py' 2023-04-28 05:57:51,884 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_ip_dscp_map.py' 2023-04-28 05:57:51,884 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_qos_policy.py' 2023-04-28 05:57:51,885 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_qos_queue_policy.py' 2023-04-28 05:57:51,885 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_quarantine.py' 2023-04-28 05:57:51,886 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_remote_log.py' 2023-04-28 05:57:51,886 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_802_1x.py' 2023-04-28 05:57:51,887 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_captive_portal.py' 2023-04-28 05:57:51,887 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_security_policy_local_access.py' 2023-04-28 05:57:51,888 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_sflow.py' 2023-04-28 05:57:51,888 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_community.py' 2023-04-28 05:57:51,888 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_sysinfo.py' 2023-04-28 05:57:51,889 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_trap_threshold.py' 2023-04-28 05:57:51,889 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_snmp_user.py' 2023-04-28 05:57:51,889 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_storm_control.py' 2023-04-28 05:57:51,890 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_storm_control_policy.py' 2023-04-28 05:57:51,890 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_stp_instance.py' 2023-04-28 05:57:51,891 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_stp_settings.py' 2023-04-28 05:57:51,891 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_group.py' 2023-04-28 05:57:51,891 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_interface_tag.py' 2023-04-28 05:57:51,892 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_log.py' 2023-04-28 05:57:51,892 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_switch_profile.py' 2023-04-28 05:57:51,892 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_system.py' 2023-04-28 05:57:51,893 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_traffic_policy.py' 2023-04-28 05:57:51,893 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_traffic_sniffer.py' 2023-04-28 05:57:51,893 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_virtual_port_pool.py' 2023-04-28 05:57:51,894 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_vlan.py' 2023-04-28 05:57:51,894 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_switch_controller_vlan_policy.py' 2023-04-28 05:57:51,894 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_3g_modem_custom.py' 2023-04-28 05:57:51,895 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_accprofile.py' 2023-04-28 05:57:51,896 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_acme.py' 2023-04-28 05:57:51,897 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_admin.py' 2023-04-28 05:57:51,898 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_affinity_interrupt.py' 2023-04-28 05:57:51,898 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_affinity_packet_redistribution.py' 2023-04-28 05:57:51,899 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_alarm.py' 2023-04-28 05:57:51,899 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_alias.py' 2023-04-28 05:57:51,899 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_api_user.py' 2023-04-28 05:57:51,900 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_arp_table.py' 2023-04-28 05:57:51,900 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_auto_install.py' 2023-04-28 05:57:51,900 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_auto_script.py' 2023-04-28 05:57:51,901 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_action.py' 2023-04-28 05:57:51,902 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_destination.py' 2023-04-28 05:57:51,902 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_stitch.py' 2023-04-28 05:57:51,903 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_automation_trigger.py' 2023-04-28 05:57:51,903 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_push_update.py' 2023-04-28 05:57:51,904 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_schedule.py' 2023-04-28 05:57:51,904 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_autoupdate_tunneling.py' 2023-04-28 05:57:51,904 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_central_management.py' 2023-04-28 05:57:51,905 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_cluster_sync.py' 2023-04-28 05:57:51,906 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_console.py' 2023-04-28 05:57:51,906 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_csf.py' 2023-04-28 05:57:51,907 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_custom_language.py' 2023-04-28 05:57:51,907 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ddns.py' 2023-04-28 05:57:51,908 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dedicated_mgmt.py' 2023-04-28 05:57:51,908 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dhcp6_server.py' 2023-04-28 05:57:51,909 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dhcp_server.py' 2023-04-28 05:57:51,910 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns.py' 2023-04-28 05:57:51,911 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns64.py' 2023-04-28 05:57:51,911 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns_database.py' 2023-04-28 05:57:51,912 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dns_server.py' 2023-04-28 05:57:51,912 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_dscp_based_priority.py' 2023-04-28 05:57:51,913 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_email_server.py' 2023-04-28 05:57:51,913 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_external_resource.py' 2023-04-28 05:57:51,914 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_federated_upgrade.py' 2023-04-28 05:57:51,914 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fips_cc.py' 2023-04-28 05:57:51,914 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fm.py' 2023-04-28 05:57:51,915 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortiai.py' 2023-04-28 05:57:51,915 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortiguard.py' 2023-04-28 05:57:51,916 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortimanager.py' 2023-04-28 05:57:51,916 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortindr.py' 2023-04-28 05:57:51,917 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fortisandbox.py' 2023-04-28 05:57:51,917 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_fsso_polling.py' 2023-04-28 05:57:51,917 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ftm_push.py' 2023-04-28 05:57:51,918 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geneve.py' 2023-04-28 05:57:51,918 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geoip_country.py' 2023-04-28 05:57:51,918 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_geoip_override.py' 2023-04-28 05:57:51,919 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_gi_gk.py' 2023-04-28 05:57:51,920 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_global.py' 2023-04-28 05:57:51,923 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_gre_tunnel.py' 2023-04-28 05:57:51,924 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ha.py' 2023-04-28 05:57:51,925 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ha_monitor.py' 2023-04-28 05:57:51,926 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ike.py' 2023-04-28 05:57:51,928 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_interface.py' 2023-04-28 05:57:51,932 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipam.py' 2023-04-28 05:57:51,932 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipip_tunnel.py' 2023-04-28 05:57:51,933 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips.py' 2023-04-28 05:57:51,933 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips_urlfilter_dns.py' 2023-04-28 05:57:51,933 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ips_urlfilter_dns6.py' 2023-04-28 05:57:51,934 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipsec_aggregate.py' 2023-04-28 05:57:51,934 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipv6_neighbor_cache.py' 2023-04-28 05:57:51,934 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ipv6_tunnel.py' 2023-04-28 05:57:51,935 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_isf_queue_profile.py' 2023-04-28 05:57:51,935 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_link_monitor.py' 2023-04-28 05:57:51,936 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_lldp_network_policy.py' 2023-04-28 05:57:51,937 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_lte_modem.py' 2023-04-28 05:57:51,937 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mac_address_table.py' 2023-04-28 05:57:51,937 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_management_tunnel.py' 2023-04-28 05:57:51,938 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mem_mgr.py' 2023-04-28 05:57:51,938 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_mobile_tunnel.py' 2023-04-28 05:57:51,939 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_modem.py' 2023-04-28 05:57:51,939 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_nat64.py' 2023-04-28 05:57:51,940 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_nd_proxy.py' 2023-04-28 05:57:51,940 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_netflow.py' 2023-04-28 05:57:51,940 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_network_visibility.py' 2023-04-28 05:57:51,941 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_np6.py' 2023-04-28 05:57:51,942 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_npu.py' 2023-04-28 05:57:51,943 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ntp.py' 2023-04-28 05:57:51,943 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_object_tagging.py' 2023-04-28 05:57:51,944 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_password_policy.py' 2023-04-28 05:57:51,944 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_password_policy_guest_admin.py' 2023-04-28 05:57:51,945 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_performance_top.py' 2023-04-28 05:57:51,945 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_physical_switch.py' 2023-04-28 05:57:51,946 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_pppoe_interface.py' 2023-04-28 05:57:51,946 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_probe_response.py' 2023-04-28 05:57:51,946 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_proxy_arp.py' 2023-04-28 05:57:51,947 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_ptp.py' 2023-04-28 05:57:51,947 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_admin.py' 2023-04-28 05:57:51,947 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_alertmail.py' 2023-04-28 05:57:51,948 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_auth.py' 2023-04-28 05:57:51,948 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_automation.py' 2023-04-28 05:57:51,948 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_device_detection_portal.py' 2023-04-28 05:57:51,949 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_ec.py' 2023-04-28 05:57:51,949 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_fortiguard_wf.py' 2023-04-28 05:57:51,949 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_ftp.py' 2023-04-28 05:57:51,951 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_group.py' 2023-04-28 05:57:51,952 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_http.py' 2023-04-28 05:57:51,953 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_icap.py' 2023-04-28 05:57:51,953 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_image.py' 2023-04-28 05:57:51,953 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mail.py' 2023-04-28 05:57:51,954 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm1.py' 2023-04-28 05:57:51,954 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm3.py' 2023-04-28 05:57:51,955 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm4.py' 2023-04-28 05:57:51,955 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mm7.py' 2023-04-28 05:57:51,956 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_mms.py' 2023-04-28 05:57:51,956 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_nac_quar.py' 2023-04-28 05:57:51,956 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_nntp.py' 2023-04-28 05:57:51,957 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_spam.py' 2023-04-28 05:57:51,957 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_sslvpn.py' 2023-04-28 05:57:51,957 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_traffic_quota.py' 2023-04-28 05:57:51,958 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_utm.py' 2023-04-28 05:57:51,958 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_replacemsg_webproxy.py' 2023-04-28 05:57:51,959 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_resource_limits.py' 2023-04-28 05:57:51,959 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_saml.py' 2023-04-28 05:57:51,960 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sdn_connector.py' 2023-04-28 05:57:51,961 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sdwan.py' 2023-04-28 05:57:51,963 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_session_helper.py' 2023-04-28 05:57:51,963 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_session_ttl.py' 2023-04-28 05:57:51,964 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_settings.py' 2023-04-28 05:57:51,966 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sflow.py' 2023-04-28 05:57:51,966 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sit_tunnel.py' 2023-04-28 05:57:51,967 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_smc_ntp.py' 2023-04-28 05:57:51,967 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sms_server.py' 2023-04-28 05:57:51,968 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_community.py' 2023-04-28 05:57:51,968 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_mib_view.py' 2023-04-28 05:57:51,969 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_sysinfo.py' 2023-04-28 05:57:51,969 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_snmp_user.py' 2023-04-28 05:57:51,970 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_speed_test_schedule.py' 2023-04-28 05:57:51,970 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_speed_test_server.py' 2023-04-28 05:57:51,971 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sso_admin.py' 2023-04-28 05:57:51,971 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_sso_forticloud_admin.py' 2023-04-28 05:57:51,971 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_standalone_cluster.py' 2023-04-28 05:57:51,972 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_storage.py' 2023-04-28 05:57:51,972 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_stp.py' 2023-04-28 05:57:51,973 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_switch_interface.py' 2023-04-28 05:57:51,973 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_tos_based_priority.py' 2023-04-28 05:57:51,974 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom.py' 2023-04-28 05:57:51,974 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_dns.py' 2023-04-28 05:57:51,974 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_exception.py' 2023-04-28 05:57:51,975 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_link.py' 2023-04-28 05:57:51,975 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_netflow.py' 2023-04-28 05:57:51,976 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_property.py' 2023-04-28 05:57:51,976 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_radius_server.py' 2023-04-28 05:57:51,976 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vdom_sflow.py' 2023-04-28 05:57:51,977 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_switch.py' 2023-04-28 05:57:51,978 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_wan_link.py' 2023-04-28 05:57:51,978 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_virtual_wire_pair.py' 2023-04-28 05:57:51,979 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vne_tunnel.py' 2023-04-28 05:57:51,979 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_vxlan.py' 2023-04-28 05:57:51,980 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_wccp.py' 2023-04-28 05:57:51,980 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_system_zone.py' 2023-04-28 05:57:51,981 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_adgrp.py' 2023-04-28 05:57:51,981 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_certificate.py' 2023-04-28 05:57:51,981 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device.py' 2023-04-28 05:57:51,982 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_access_list.py' 2023-04-28 05:57:51,982 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_category.py' 2023-04-28 05:57:51,982 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_device_group.py' 2023-04-28 05:57:51,983 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_domain_controller.py' 2023-04-28 05:57:51,983 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_exchange.py' 2023-04-28 05:57:51,984 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fortitoken.py' 2023-04-28 05:57:51,984 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fsso.py' 2023-04-28 05:57:51,985 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_fsso_polling.py' 2023-04-28 05:57:51,985 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_group.py' 2023-04-28 05:57:51,986 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_krb_keytab.py' 2023-04-28 05:57:51,986 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_ldap.py' 2023-04-28 05:57:51,987 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_local.py' 2023-04-28 05:57:51,988 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_nac_policy.py' 2023-04-28 05:57:51,988 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_password_policy.py' 2023-04-28 05:57:51,988 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_peer.py' 2023-04-28 05:57:51,989 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_peergrp.py' 2023-04-28 05:57:51,989 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_pop3.py' 2023-04-28 05:57:51,990 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_quarantine.py' 2023-04-28 05:57:51,990 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_radius.py' 2023-04-28 05:57:51,992 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_saml.py' 2023-04-28 05:57:51,992 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_security_exempt_list.py' 2023-04-28 05:57:51,993 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_setting.py' 2023-04-28 05:57:51,993 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_user_tacacsplus.py' 2023-04-28 05:57:51,994 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_profile.py' 2023-04-28 05:57:51,994 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_youtube_channel_filter.py' 2023-04-28 05:57:51,995 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_videofilter_youtube_key.py' 2023-04-28 05:57:51,996 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_voip_profile.py' 2023-04-28 05:57:51,998 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_ca.py' 2023-04-28 05:57:51,999 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_crl.py' 2023-04-28 05:57:51,999 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_local.py' 2023-04-28 05:57:52,000 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_ocsp_server.py' 2023-04-28 05:57:52,000 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_remote.py' 2023-04-28 05:57:52,000 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_certificate_setting.py' 2023-04-28 05:57:52,001 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ike_gateway.py' 2023-04-28 05:57:52,001 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_concentrator.py' 2023-04-28 05:57:52,002 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_fec.py' 2023-04-28 05:57:52,002 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_forticlient.py' 2023-04-28 05:57:52,002 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_manualkey.py' 2023-04-28 05:57:52,003 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_manualkey_interface.py' 2023-04-28 05:57:52,005 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase1.py' 2023-04-28 05:57:52,007 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase1_interface.py' 2023-04-28 05:57:52,010 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase2.py' 2023-04-28 05:57:52,011 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ipsec_phase2_interface.py' 2023-04-28 05:57:52,012 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_l2tp.py' 2023-04-28 05:57:52,013 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ocvpn.py' 2023-04-28 05:57:52,013 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_pptp.py' 2023-04-28 05:57:52,013 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_client.py' 2023-04-28 05:57:52,014 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_settings.py' 2023-04-28 05:57:52,016 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_host_check_software.py' 2023-04-28 05:57:52,017 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_portal.py' 2023-04-28 05:57:52,019 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_realm.py' 2023-04-28 05:57:52,019 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_user_bookmark.py' 2023-04-28 05:57:52,020 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_vpn_ssl_web_user_group_bookmark.py' 2023-04-28 05:57:52,021 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_main_class.py' 2023-04-28 05:57:52,023 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_profile.py' 2023-04-28 05:57:52,025 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_signature.py' 2023-04-28 05:57:52,026 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_waf_sub_class.py' 2023-04-28 05:57:52,026 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_auth_group.py' 2023-04-28 05:57:52,026 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_cache_service.py' 2023-04-28 05:57:52,027 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_content_delivery_network_rule.py' 2023-04-28 05:57:52,028 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_peer.py' 2023-04-28 05:57:52,028 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_profile.py' 2023-04-28 05:57:52,029 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_remote_storage.py' 2023-04-28 05:57:52,030 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_settings.py' 2023-04-28 05:57:52,030 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wanopt_webcache.py' 2023-04-28 05:57:52,032 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_debug_url.py' 2023-04-28 05:57:52,034 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_explicit.py' 2023-04-28 05:57:52,036 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_forward_server.py' 2023-04-28 05:57:52,037 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_forward_server_group.py' 2023-04-28 05:57:52,037 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_global.py' 2023-04-28 05:57:52,038 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_profile.py' 2023-04-28 05:57:52,038 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_url_match.py' 2023-04-28 05:57:52,039 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_web_proxy_wisp.py' 2023-04-28 05:57:52,039 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_content.py' 2023-04-28 05:57:52,040 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_content_header.py' 2023-04-28 05:57:52,040 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_fortiguard.py' 2023-04-28 05:57:52,040 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ftgd_local_cat.py' 2023-04-28 05:57:52,041 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ftgd_local_rating.py' 2023-04-28 05:57:52,041 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_cache_setting.py' 2023-04-28 05:57:52,041 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_setting.py' 2023-04-28 05:57:52,042 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_ips_urlfilter_setting6.py' 2023-04-28 05:57:52,042 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_override.py' 2023-04-28 05:57:52,043 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_profile.py' 2023-04-28 05:57:52,045 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_search_engine.py' 2023-04-28 05:57:52,045 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_status.py' 2023-04-28 05:57:52,046 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_webfilter_urlfilter.py' 2023-04-28 05:57:52,046 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_access_control_list.py' 2023-04-28 05:57:52,047 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_address.py' 2023-04-28 05:57:52,047 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_addrgrp.py' 2023-04-28 05:57:52,047 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ap_status.py' 2023-04-28 05:57:52,048 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_apcfg_profile.py' 2023-04-28 05:57:52,048 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_arrp_profile.py' 2023-04-28 05:57:52,049 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ble_profile.py' 2023-04-28 05:57:52,049 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_bonjour_profile.py' 2023-04-28 05:57:52,050 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_client_info.py' 2023-04-28 05:57:52,050 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_global.py' 2023-04-28 05:57:52,050 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_3gpp_cellular.py' 2023-04-28 05:57:52,051 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_ip_address_type.py' 2023-04-28 05:57:52,051 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_nai_realm.py' 2023-04-28 05:57:52,052 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_network_auth_type.py' 2023-04-28 05:57:52,052 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_roaming_consortium.py' 2023-04-28 05:57:52,053 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_venue_name.py' 2023-04-28 05:57:52,053 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_anqp_venue_url.py' 2023-04-28 05:57:52,053 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_advice_of_charge.py' 2023-04-28 05:57:52,054 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_conn_capability.py' 2023-04-28 05:57:52,054 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_operator_name.py' 2023-04-28 05:57:52,055 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_osu_provider.py' 2023-04-28 05:57:52,055 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_osu_provider_nai.py' 2023-04-28 05:57:52,056 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_terms_and_conditions.py' 2023-04-28 05:57:52,056 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_h2qp_wan_metric.py' 2023-04-28 05:57:52,057 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_hs_profile.py' 2023-04-28 05:57:52,058 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_icon.py' 2023-04-28 05:57:52,058 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_hotspot20_qos_map.py' 2023-04-28 05:57:52,058 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_inter_controller.py' 2023-04-28 05:57:52,059 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_log.py' 2023-04-28 05:57:52,060 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_mpsk_profile.py' 2023-04-28 05:57:52,060 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_nac_profile.py' 2023-04-28 05:57:52,060 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_qos_profile.py' 2023-04-28 05:57:52,061 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_region.py' 2023-04-28 05:57:52,061 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_rf_analysis.py' 2023-04-28 05:57:52,062 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_setting.py' 2023-04-28 05:57:52,063 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_snmp.py' 2023-04-28 05:57:52,064 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_spectral_info.py' 2023-04-28 05:57:52,064 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_ssid_policy.py' 2023-04-28 05:57:52,065 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_status.py' 2023-04-28 05:57:52,065 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_syslog_profile.py' 2023-04-28 05:57:52,065 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_timers.py' 2023-04-28 05:57:52,066 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_utm_profile.py' 2023-04-28 05:57:52,067 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap.py' 2023-04-28 05:57:52,070 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap_group.py' 2023-04-28 05:57:52,070 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_vap_status.py' 2023-04-28 05:57:52,071 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wag_profile.py' 2023-04-28 05:57:52,071 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wids_profile.py' 2023-04-28 05:57:52,073 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp.py' 2023-04-28 05:57:52,075 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_group.py' 2023-04-28 05:57:52,079 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_profile.py' 2023-04-28 05:57:52,085 wheel INFO adding 'ansible_collections/fortinet/fortios/plugins/modules/fortios_wireless_controller_wtp_status.py' 2023-04-28 05:57:52,085 wheel INFO adding 'ansible_collections/frr/frr/CHANGELOG.rst' 2023-04-28 05:57:52,086 wheel INFO adding 'ansible_collections/frr/frr/FILES.json' 2023-04-28 05:57:52,086 wheel INFO adding 'ansible_collections/frr/frr/LICENSE' 2023-04-28 05:57:52,087 wheel INFO adding 'ansible_collections/frr/frr/MANIFEST.json' 2023-04-28 05:57:52,087 wheel INFO adding 'ansible_collections/frr/frr/README.md' 2023-04-28 05:57:52,087 wheel INFO adding 'ansible_collections/frr/frr/bindep.txt' 2023-04-28 05:57:52,087 wheel INFO adding 'ansible_collections/frr/frr/codecov.yml' 2023-04-28 05:57:52,087 wheel INFO adding 'ansible_collections/frr/frr/pyproject.toml' 2023-04-28 05:57:52,088 wheel INFO adding 'ansible_collections/frr/frr/requirements.txt' 2023-04-28 05:57:52,088 wheel INFO adding 'ansible_collections/frr/frr/test-requirements.txt' 2023-04-28 05:57:52,088 wheel INFO adding 'ansible_collections/frr/frr/tox.ini' 2023-04-28 05:57:52,088 wheel INFO adding 'ansible_collections/frr/frr/changelogs/changelog.yaml' 2023-04-28 05:57:52,088 wheel INFO adding 'ansible_collections/frr/frr/changelogs/config.yaml' 2023-04-28 05:57:52,089 wheel INFO adding 'ansible_collections/frr/frr/meta/runtime.yml' 2023-04-28 05:57:52,089 wheel INFO adding 'ansible_collections/frr/frr/plugins/cliconf/__init__.py' 2023-04-28 05:57:52,089 wheel INFO adding 'ansible_collections/frr/frr/plugins/cliconf/frr.py' 2023-04-28 05:57:52,090 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,090 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/__init__.py' 2023-04-28 05:57:52,090 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/frr.py' 2023-04-28 05:57:52,090 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/__init__.py' 2023-04-28 05:57:52,091 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/module.py' 2023-04-28 05:57:52,091 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/providers.py' 2023-04-28 05:57:52,091 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/__init__.py' 2023-04-28 05:57:52,091 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/__init__.py' 2023-04-28 05:57:52,091 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/base.py' 2023-04-28 05:57:52,092 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/__init__.py' 2023-04-28 05:57:52,092 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/address_family.py' 2023-04-28 05:57:52,092 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/neighbors.py' 2023-04-28 05:57:52,093 wheel INFO adding 'ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/process.py' 2023-04-28 05:57:52,093 wheel INFO adding 'ansible_collections/frr/frr/plugins/modules/__init__.py' 2023-04-28 05:57:52,093 wheel INFO adding 'ansible_collections/frr/frr/plugins/modules/frr_bgp.py' 2023-04-28 05:57:52,093 wheel INFO adding 'ansible_collections/frr/frr/plugins/modules/frr_facts.py' 2023-04-28 05:57:52,094 wheel INFO adding 'ansible_collections/frr/frr/plugins/terminal/__init__.py' 2023-04-28 05:57:52,094 wheel INFO adding 'ansible_collections/frr/frr/plugins/terminal/frr.py' 2023-04-28 05:57:52,094 wheel INFO adding 'ansible_collections/gluster/gluster/CHANGELOG.rst' 2023-04-28 05:57:52,094 wheel INFO adding 'ansible_collections/gluster/gluster/FILES.json' 2023-04-28 05:57:52,095 wheel INFO adding 'ansible_collections/gluster/gluster/LICENSE' 2023-04-28 05:57:52,095 wheel INFO adding 'ansible_collections/gluster/gluster/MANIFEST.json' 2023-04-28 05:57:52,095 wheel INFO adding 'ansible_collections/gluster/gluster/README.md' 2023-04-28 05:57:52,095 wheel INFO adding 'ansible_collections/gluster/gluster/changelogs/changelog.yaml' 2023-04-28 05:57:52,096 wheel INFO adding 'ansible_collections/gluster/gluster/changelogs/config.yaml' 2023-04-28 05:57:52,096 wheel INFO adding 'ansible_collections/gluster/gluster/meta/runtime.yml' 2023-04-28 05:57:52,096 wheel INFO adding 'ansible_collections/gluster/gluster/plugins/modules/geo_rep.py' 2023-04-28 05:57:52,096 wheel INFO adding 'ansible_collections/gluster/gluster/plugins/modules/gluster_heal_info.py' 2023-04-28 05:57:52,097 wheel INFO adding 'ansible_collections/gluster/gluster/plugins/modules/gluster_peer.py' 2023-04-28 05:57:52,097 wheel INFO adding 'ansible_collections/gluster/gluster/plugins/modules/gluster_volume.py' 2023-04-28 05:57:52,097 wheel INFO adding 'ansible_collections/google/cloud/CHANGELOG.rst' 2023-04-28 05:57:52,098 wheel INFO adding 'ansible_collections/google/cloud/CONTRIBUTING.md' 2023-04-28 05:57:52,098 wheel INFO adding 'ansible_collections/google/cloud/FILES.json' 2023-04-28 05:57:52,099 wheel INFO adding 'ansible_collections/google/cloud/LICENSE' 2023-04-28 05:57:52,100 wheel INFO adding 'ansible_collections/google/cloud/MAINTAINING.md' 2023-04-28 05:57:52,100 wheel INFO adding 'ansible_collections/google/cloud/MANIFEST.json' 2023-04-28 05:57:52,100 wheel INFO adding 'ansible_collections/google/cloud/README.md' 2023-04-28 05:57:52,100 wheel INFO adding 'ansible_collections/google/cloud/requirements-test.txt' 2023-04-28 05:57:52,101 wheel INFO adding 'ansible_collections/google/cloud/requirements.txt' 2023-04-28 05:57:52,101 wheel INFO adding 'ansible_collections/google/cloud/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,101 wheel INFO adding 'ansible_collections/google/cloud/changelogs/changelog.yaml' 2023-04-28 05:57:52,102 wheel INFO adding 'ansible_collections/google/cloud/changelogs/config.yaml' 2023-04-28 05:57:52,102 wheel INFO adding 'ansible_collections/google/cloud/meta/runtime.yml' 2023-04-28 05:57:52,102 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/Dockerfile.j2' 2023-04-28 05:57:52,102 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/archive_playbook.yml' 2023-04-28 05:57:52,103 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/converge.yml' 2023-04-28 05:57:52,103 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/molecule.yml' 2023-04-28 05:57:52,103 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/package_playbook.yml' 2023-04-28 05:57:52,103 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/verify.yml' 2023-04-28 05:57:52,103 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/files/override.conf' 2023-04-28 05:57:52,104 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcloud/tests/test_default.py' 2023-04-28 05:57:52,104 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcsfuse/Dockerfile.j2' 2023-04-28 05:57:52,104 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcsfuse/converge.yml' 2023-04-28 05:57:52,104 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcsfuse/molecule.yml' 2023-04-28 05:57:52,105 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcsfuse/verify.yml' 2023-04-28 05:57:52,105 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcsfuse/files/override.conf' 2023-04-28 05:57:52,105 wheel INFO adding 'ansible_collections/google/cloud/molecule/gcsfuse/tests/test_default.py' 2023-04-28 05:57:52,105 wheel INFO adding 'ansible_collections/google/cloud/plugins/README.md' 2023-04-28 05:57:52,106 wheel INFO adding 'ansible_collections/google/cloud/plugins/doc_fragments/gcp.py' 2023-04-28 05:57:52,106 wheel INFO adding 'ansible_collections/google/cloud/plugins/filter/gcp_kms_filters.py' 2023-04-28 05:57:52,106 wheel INFO adding 'ansible_collections/google/cloud/plugins/inventory/gcp_compute.py' 2023-04-28 05:57:52,106 wheel INFO adding 'ansible_collections/google/cloud/plugins/module_utils/gcp_utils.py' 2023-04-28 05:57:52,107 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_appengine_firewall_rule.py' 2023-04-28 05:57:52,107 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_appengine_firewall_rule_info.py' 2023-04-28 05:57:52,108 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_bigquery_dataset.py' 2023-04-28 05:57:52,108 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_bigquery_dataset_info.py' 2023-04-28 05:57:52,108 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_bigquery_table.py' 2023-04-28 05:57:52,109 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_bigquery_table_info.py' 2023-04-28 05:57:52,109 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_bigtable_instance.py' 2023-04-28 05:57:52,110 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_bigtable_instance_info.py' 2023-04-28 05:57:52,110 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudbuild_trigger.py' 2023-04-28 05:57:52,111 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudbuild_trigger_info.py' 2023-04-28 05:57:52,111 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudfunctions_cloud_function.py' 2023-04-28 05:57:52,111 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudfunctions_cloud_function_info.py' 2023-04-28 05:57:52,112 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudscheduler_job.py' 2023-04-28 05:57:52,112 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudscheduler_job_info.py' 2023-04-28 05:57:52,112 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudtasks_queue.py' 2023-04-28 05:57:52,113 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_cloudtasks_queue_info.py' 2023-04-28 05:57:52,113 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_address.py' 2023-04-28 05:57:52,113 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_address_info.py' 2023-04-28 05:57:52,114 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_autoscaler.py' 2023-04-28 05:57:52,114 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_autoscaler_info.py' 2023-04-28 05:57:52,114 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_bucket.py' 2023-04-28 05:57:52,115 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_bucket_info.py' 2023-04-28 05:57:52,115 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_service.py' 2023-04-28 05:57:52,116 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_backend_service_info.py' 2023-04-28 05:57:52,116 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_disk.py' 2023-04-28 05:57:52,117 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_disk_info.py' 2023-04-28 05:57:52,117 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_external_vpn_gateway.py' 2023-04-28 05:57:52,117 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_external_vpn_gateway_info.py' 2023-04-28 05:57:52,118 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_firewall.py' 2023-04-28 05:57:52,118 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_firewall_info.py' 2023-04-28 05:57:52,118 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_forwarding_rule.py' 2023-04-28 05:57:52,119 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_forwarding_rule_info.py' 2023-04-28 05:57:52,119 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_global_address.py' 2023-04-28 05:57:52,119 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_global_address_info.py' 2023-04-28 05:57:52,120 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_global_forwarding_rule.py' 2023-04-28 05:57:52,120 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_global_forwarding_rule_info.py' 2023-04-28 05:57:52,120 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_health_check.py' 2023-04-28 05:57:52,121 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_health_check_info.py' 2023-04-28 05:57:52,121 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_http_health_check.py' 2023-04-28 05:57:52,122 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_http_health_check_info.py' 2023-04-28 05:57:52,122 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_https_health_check.py' 2023-04-28 05:57:52,122 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_https_health_check_info.py' 2023-04-28 05:57:52,123 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_image.py' 2023-04-28 05:57:52,123 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_image_info.py' 2023-04-28 05:57:52,123 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance.py' 2023-04-28 05:57:52,124 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group.py' 2023-04-28 05:57:52,124 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_info.py' 2023-04-28 05:57:52,124 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_manager.py' 2023-04-28 05:57:52,125 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_group_manager_info.py' 2023-04-28 05:57:52,125 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_info.py' 2023-04-28 05:57:52,126 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_template.py' 2023-04-28 05:57:52,126 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_instance_template_info.py' 2023-04-28 05:57:52,127 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_interconnect_attachment.py' 2023-04-28 05:57:52,127 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_interconnect_attachment_info.py' 2023-04-28 05:57:52,127 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_network.py' 2023-04-28 05:57:52,127 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_network_endpoint_group.py' 2023-04-28 05:57:52,128 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_network_endpoint_group_info.py' 2023-04-28 05:57:52,128 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_network_info.py' 2023-04-28 05:57:52,128 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_node_group.py' 2023-04-28 05:57:52,129 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_node_group_info.py' 2023-04-28 05:57:52,129 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_node_template.py' 2023-04-28 05:57:52,130 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_node_template_info.py' 2023-04-28 05:57:52,130 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_autoscaler.py' 2023-04-28 05:57:52,130 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_autoscaler_info.py' 2023-04-28 05:57:52,131 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_backend_service.py' 2023-04-28 05:57:52,131 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_backend_service_info.py' 2023-04-28 05:57:52,132 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_disk.py' 2023-04-28 05:57:52,132 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_disk_info.py' 2023-04-28 05:57:52,133 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_health_check.py' 2023-04-28 05:57:52,133 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_health_check_info.py' 2023-04-28 05:57:52,134 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_instance_group_manager.py' 2023-04-28 05:57:52,134 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_instance_group_manager_info.py' 2023-04-28 05:57:52,134 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_http_proxy.py' 2023-04-28 05:57:52,134 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_http_proxy_info.py' 2023-04-28 05:57:52,135 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_https_proxy.py' 2023-04-28 05:57:52,135 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_target_https_proxy_info.py' 2023-04-28 05:57:52,136 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_url_map.py' 2023-04-28 05:57:52,137 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_region_url_map_info.py' 2023-04-28 05:57:52,138 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_reservation.py' 2023-04-28 05:57:52,138 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_reservation_info.py' 2023-04-28 05:57:52,138 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_resource_policy.py' 2023-04-28 05:57:52,139 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_resource_policy_info.py' 2023-04-28 05:57:52,139 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_route.py' 2023-04-28 05:57:52,139 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_route_info.py' 2023-04-28 05:57:52,140 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_router.py' 2023-04-28 05:57:52,140 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_router_info.py' 2023-04-28 05:57:52,140 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_snapshot.py' 2023-04-28 05:57:52,141 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_snapshot_info.py' 2023-04-28 05:57:52,141 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_certificate.py' 2023-04-28 05:57:52,141 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_certificate_info.py' 2023-04-28 05:57:52,142 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_policy.py' 2023-04-28 05:57:52,142 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_ssl_policy_info.py' 2023-04-28 05:57:52,142 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_subnetwork.py' 2023-04-28 05:57:52,142 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_subnetwork_info.py' 2023-04-28 05:57:52,143 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_http_proxy.py' 2023-04-28 05:57:52,143 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_http_proxy_info.py' 2023-04-28 05:57:52,143 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_https_proxy.py' 2023-04-28 05:57:52,144 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_https_proxy_info.py' 2023-04-28 05:57:52,144 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_instance.py' 2023-04-28 05:57:52,144 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_instance_info.py' 2023-04-28 05:57:52,144 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_pool.py' 2023-04-28 05:57:52,145 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_pool_info.py' 2023-04-28 05:57:52,145 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_ssl_proxy.py' 2023-04-28 05:57:52,145 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_ssl_proxy_info.py' 2023-04-28 05:57:52,146 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_tcp_proxy.py' 2023-04-28 05:57:52,146 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_tcp_proxy_info.py' 2023-04-28 05:57:52,146 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_vpn_gateway.py' 2023-04-28 05:57:52,147 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_target_vpn_gateway_info.py' 2023-04-28 05:57:52,148 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_url_map.py' 2023-04-28 05:57:52,150 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_url_map_info.py' 2023-04-28 05:57:52,150 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_vpn_tunnel.py' 2023-04-28 05:57:52,151 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_compute_vpn_tunnel_info.py' 2023-04-28 05:57:52,151 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_container_cluster.py' 2023-04-28 05:57:52,152 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_container_cluster_info.py' 2023-04-28 05:57:52,152 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_container_node_pool.py' 2023-04-28 05:57:52,153 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_container_node_pool_info.py' 2023-04-28 05:57:52,153 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_dns_managed_zone.py' 2023-04-28 05:57:52,153 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_dns_managed_zone_info.py' 2023-04-28 05:57:52,154 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_dns_resource_record_set.py' 2023-04-28 05:57:52,154 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_dns_resource_record_set_info.py' 2023-04-28 05:57:52,154 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_filestore_instance.py' 2023-04-28 05:57:52,155 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_filestore_instance_info.py' 2023-04-28 05:57:52,155 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_iam_role.py' 2023-04-28 05:57:52,155 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_iam_role_info.py' 2023-04-28 05:57:52,155 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account.py' 2023-04-28 05:57:52,156 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account_info.py' 2023-04-28 05:57:52,156 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_iam_service_account_key.py' 2023-04-28 05:57:52,156 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_kms_crypto_key.py' 2023-04-28 05:57:52,156 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_kms_crypto_key_info.py' 2023-04-28 05:57:52,157 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_kms_key_ring.py' 2023-04-28 05:57:52,157 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_kms_key_ring_info.py' 2023-04-28 05:57:52,157 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_logging_metric.py' 2023-04-28 05:57:52,158 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_logging_metric_info.py' 2023-04-28 05:57:52,158 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_mlengine_model.py' 2023-04-28 05:57:52,158 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_mlengine_model_info.py' 2023-04-28 05:57:52,159 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_mlengine_version.py' 2023-04-28 05:57:52,159 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_mlengine_version_info.py' 2023-04-28 05:57:52,159 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_pubsub_subscription.py' 2023-04-28 05:57:52,160 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_pubsub_subscription_info.py' 2023-04-28 05:57:52,160 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_pubsub_topic.py' 2023-04-28 05:57:52,160 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_pubsub_topic_info.py' 2023-04-28 05:57:52,160 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_redis_instance.py' 2023-04-28 05:57:52,161 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_redis_instance_info.py' 2023-04-28 05:57:52,161 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_resourcemanager_project.py' 2023-04-28 05:57:52,161 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_resourcemanager_project_info.py' 2023-04-28 05:57:52,162 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_config.py' 2023-04-28 05:57:52,162 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_config_info.py' 2023-04-28 05:57:52,162 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_variable.py' 2023-04-28 05:57:52,162 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_runtimeconfig_variable_info.py' 2023-04-28 05:57:52,163 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_serviceusage_service.py' 2023-04-28 05:57:52,163 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_serviceusage_service_info.py' 2023-04-28 05:57:52,163 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sourcerepo_repository.py' 2023-04-28 05:57:52,163 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sourcerepo_repository_info.py' 2023-04-28 05:57:52,164 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_spanner_database.py' 2023-04-28 05:57:52,164 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_spanner_database_info.py' 2023-04-28 05:57:52,164 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_spanner_instance.py' 2023-04-28 05:57:52,165 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_spanner_instance_info.py' 2023-04-28 05:57:52,165 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sql_database.py' 2023-04-28 05:57:52,165 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sql_database_info.py' 2023-04-28 05:57:52,165 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sql_instance.py' 2023-04-28 05:57:52,166 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sql_instance_info.py' 2023-04-28 05:57:52,166 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sql_ssl_cert.py' 2023-04-28 05:57:52,167 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sql_user.py' 2023-04-28 05:57:52,167 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_sql_user_info.py' 2023-04-28 05:57:52,167 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_storage_bucket.py' 2023-04-28 05:57:52,168 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_storage_bucket_access_control.py' 2023-04-28 05:57:52,168 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_storage_default_object_acl.py' 2023-04-28 05:57:52,168 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_storage_object.py' 2023-04-28 05:57:52,168 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_tpu_node.py' 2023-04-28 05:57:52,169 wheel INFO adding 'ansible_collections/google/cloud/plugins/modules/gcp_tpu_node_info.py' 2023-04-28 05:57:52,169 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/README.md' 2023-04-28 05:57:52,169 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/defaults/main.yml' 2023-04-28 05:57:52,170 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/meta/main.yml' 2023-04-28 05:57:52,170 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/tasks/main.yml' 2023-04-28 05:57:52,170 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/tasks/archive/archive_install.yml' 2023-04-28 05:57:52,170 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/tasks/archive/command_completion.yml' 2023-04-28 05:57:52,171 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/tasks/archive/main.yml' 2023-04-28 05:57:52,171 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/tasks/package/debian.yml' 2023-04-28 05:57:52,171 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/tasks/package/main.yml' 2023-04-28 05:57:52,171 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/tasks/package/redhat.yml' 2023-04-28 05:57:52,172 wheel INFO adding 'ansible_collections/google/cloud/roles/gcloud/vars/main.yml' 2023-04-28 05:57:52,172 wheel INFO adding 'ansible_collections/google/cloud/roles/gcp_http_lb/README.md' 2023-04-28 05:57:52,172 wheel INFO adding 'ansible_collections/google/cloud/roles/gcp_http_lb/defaults/main.yml' 2023-04-28 05:57:52,172 wheel INFO adding 'ansible_collections/google/cloud/roles/gcp_http_lb/meta/main.yml' 2023-04-28 05:57:52,173 wheel INFO adding 'ansible_collections/google/cloud/roles/gcp_http_lb/tasks/main.yml' 2023-04-28 05:57:52,173 wheel INFO adding 'ansible_collections/google/cloud/roles/gcp_http_lb/tests/inventory' 2023-04-28 05:57:52,173 wheel INFO adding 'ansible_collections/google/cloud/roles/gcp_http_lb/tests/test.yml' 2023-04-28 05:57:52,173 wheel INFO adding 'ansible_collections/google/cloud/roles/gcp_http_lb/vars/main.yml' 2023-04-28 05:57:52,174 wheel INFO adding 'ansible_collections/google/cloud/roles/gcsfuse/README.md' 2023-04-28 05:57:52,174 wheel INFO adding 'ansible_collections/google/cloud/roles/gcsfuse/defaults/main.yml' 2023-04-28 05:57:52,174 wheel INFO adding 'ansible_collections/google/cloud/roles/gcsfuse/handlers/main.yml' 2023-04-28 05:57:52,174 wheel INFO adding 'ansible_collections/google/cloud/roles/gcsfuse/meta/main.yml' 2023-04-28 05:57:52,174 wheel INFO adding 'ansible_collections/google/cloud/roles/gcsfuse/tasks/debian.yml' 2023-04-28 05:57:52,175 wheel INFO adding 'ansible_collections/google/cloud/roles/gcsfuse/tasks/main.yml' 2023-04-28 05:57:52,175 wheel INFO adding 'ansible_collections/google/cloud/roles/gcsfuse/vars/main.yml' 2023-04-28 05:57:52,175 wheel INFO adding 'ansible_collections/google/cloud/scripts/bootstrap-project.sh' 2023-04-28 05:57:52,175 wheel INFO adding 'ansible_collections/google/cloud/scripts/cleanup-project.sh' 2023-04-28 05:57:52,176 wheel INFO adding 'ansible_collections/google/cloud/test-fixtures/cloud-function.zip' 2023-04-28 05:57:52,176 wheel INFO adding 'ansible_collections/google/cloud/test-fixtures/cloud-function-source/build-function-zip.sh' 2023-04-28 05:57:52,176 wheel INFO adding 'ansible_collections/google/cloud/test-fixtures/cloud-function-source/main.py' 2023-04-28 05:57:52,176 wheel INFO adding 'ansible_collections/google/cloud/test-fixtures/cloud-function-source/requirements.txt' 2023-04-28 05:57:52,177 wheel INFO adding 'ansible_collections/grafana/grafana/CHANGELOG.rst' 2023-04-28 05:57:52,177 wheel INFO adding 'ansible_collections/grafana/grafana/FILES.json' 2023-04-28 05:57:52,177 wheel INFO adding 'ansible_collections/grafana/grafana/LICENSE' 2023-04-28 05:57:52,178 wheel INFO adding 'ansible_collections/grafana/grafana/MANIFEST.json' 2023-04-28 05:57:52,178 wheel INFO adding 'ansible_collections/grafana/grafana/README.md' 2023-04-28 05:57:52,178 wheel INFO adding 'ansible_collections/grafana/grafana/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,178 wheel INFO adding 'ansible_collections/grafana/grafana/changelogs/changelog.yaml' 2023-04-28 05:57:52,179 wheel INFO adding 'ansible_collections/grafana/grafana/changelogs/config.yaml' 2023-04-28 05:57:52,179 wheel INFO adding 'ansible_collections/grafana/grafana/meta/runtime.yml' 2023-04-28 05:57:52,179 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/alert_contact_point.py' 2023-04-28 05:57:52,179 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/alert_notification_policy.py' 2023-04-28 05:57:52,180 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/cloud_api_key.py' 2023-04-28 05:57:52,180 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/cloud_plugin.py' 2023-04-28 05:57:52,180 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/cloud_stack.py' 2023-04-28 05:57:52,180 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/dashboard.py' 2023-04-28 05:57:52,181 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/datasource.py' 2023-04-28 05:57:52,181 wheel INFO adding 'ansible_collections/grafana/grafana/plugins/modules/folder.py' 2023-04-28 05:57:52,181 wheel INFO adding 'ansible_collections/grafana/grafana/roles/grafana_agent/README.md' 2023-04-28 05:57:52,181 wheel INFO adding 'ansible_collections/grafana/grafana/roles/grafana_agent/defaults/main.yml' 2023-04-28 05:57:52,182 wheel INFO adding 'ansible_collections/grafana/grafana/roles/grafana_agent/meta/main.yml' 2023-04-28 05:57:52,182 wheel INFO adding 'ansible_collections/grafana/grafana/roles/grafana_agent/tasks/main.yml' 2023-04-28 05:57:52,182 wheel INFO adding 'ansible_collections/hetzner/hcloud/CHANGELOG.rst' 2023-04-28 05:57:52,183 wheel INFO adding 'ansible_collections/hetzner/hcloud/COPYING' 2023-04-28 05:57:52,183 wheel INFO adding 'ansible_collections/hetzner/hcloud/FILES.json' 2023-04-28 05:57:52,184 wheel INFO adding 'ansible_collections/hetzner/hcloud/MANIFEST.json' 2023-04-28 05:57:52,184 wheel INFO adding 'ansible_collections/hetzner/hcloud/README.md' 2023-04-28 05:57:52,184 wheel INFO adding 'ansible_collections/hetzner/hcloud/changelogs/.gitignore' 2023-04-28 05:57:52,184 wheel INFO adding 'ansible_collections/hetzner/hcloud/changelogs/changelog.yaml' 2023-04-28 05:57:52,185 wheel INFO adding 'ansible_collections/hetzner/hcloud/changelogs/config.yaml' 2023-04-28 05:57:52,185 wheel INFO adding 'ansible_collections/hetzner/hcloud/changelogs/fragments/.keep' 2023-04-28 05:57:52,185 wheel INFO adding 'ansible_collections/hetzner/hcloud/meta/runtime.yml' 2023-04-28 05:57:52,185 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,186 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/doc_fragments/hcloud.py' 2023-04-28 05:57:52,186 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/inventory/__init__.py' 2023-04-28 05:57:52,186 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/inventory/hcloud.py' 2023-04-28 05:57:52,186 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,187 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/module_utils/hcloud.py' 2023-04-28 05:57:52,187 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/__init__.py' 2023-04-28 05:57:52,187 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_certificate.py' 2023-04-28 05:57:52,187 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_certificate_info.py' 2023-04-28 05:57:52,188 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_datacenter_facts.py' 2023-04-28 05:57:52,188 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_datacenter_info.py' 2023-04-28 05:57:52,188 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_firewall.py' 2023-04-28 05:57:52,188 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip.py' 2023-04-28 05:57:52,189 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip_facts.py' 2023-04-28 05:57:52,189 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_floating_ip_info.py' 2023-04-28 05:57:52,189 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_image_facts.py' 2023-04-28 05:57:52,189 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_image_info.py' 2023-04-28 05:57:52,190 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer.py' 2023-04-28 05:57:52,190 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_info.py' 2023-04-28 05:57:52,190 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_network.py' 2023-04-28 05:57:52,191 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_service.py' 2023-04-28 05:57:52,191 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_target.py' 2023-04-28 05:57:52,191 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_load_balancer_type_info.py' 2023-04-28 05:57:52,191 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_location_facts.py' 2023-04-28 05:57:52,192 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_location_info.py' 2023-04-28 05:57:52,192 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_network.py' 2023-04-28 05:57:52,192 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_network_info.py' 2023-04-28 05:57:52,192 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_placement_group.py' 2023-04-28 05:57:52,193 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_primary_ip.py' 2023-04-28 05:57:52,193 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_rdns.py' 2023-04-28 05:57:52,193 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_route.py' 2023-04-28 05:57:52,194 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server.py' 2023-04-28 05:57:52,194 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_facts.py' 2023-04-28 05:57:52,194 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_info.py' 2023-04-28 05:57:52,194 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_network.py' 2023-04-28 05:57:52,195 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_type_facts.py' 2023-04-28 05:57:52,195 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_server_type_info.py' 2023-04-28 05:57:52,195 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key.py' 2023-04-28 05:57:52,195 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key_facts.py' 2023-04-28 05:57:52,196 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_ssh_key_info.py' 2023-04-28 05:57:52,196 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_subnetwork.py' 2023-04-28 05:57:52,196 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume.py' 2023-04-28 05:57:52,196 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume_facts.py' 2023-04-28 05:57:52,197 wheel INFO adding 'ansible_collections/hetzner/hcloud/plugins/modules/hcloud_volume_info.py' 2023-04-28 05:57:52,197 wheel INFO adding 'ansible_collections/hpe/nimble/CHANGELOG.rst' 2023-04-28 05:57:52,197 wheel INFO adding 'ansible_collections/hpe/nimble/FILES.json' 2023-04-28 05:57:52,198 wheel INFO adding 'ansible_collections/hpe/nimble/MANIFEST.json' 2023-04-28 05:57:52,198 wheel INFO adding 'ansible_collections/hpe/nimble/README.md' 2023-04-28 05:57:52,198 wheel INFO adding 'ansible_collections/hpe/nimble/bindep.txt' 2023-04-28 05:57:52,198 wheel INFO adding 'ansible_collections/hpe/nimble/requirements.txt' 2023-04-28 05:57:52,198 wheel INFO adding 'ansible_collections/hpe/nimble/changelogs/changelog.yaml' 2023-04-28 05:57:52,199 wheel INFO adding 'ansible_collections/hpe/nimble/changelogs/config.yaml' 2023-04-28 05:57:52,199 wheel INFO adding 'ansible_collections/hpe/nimble/meta/runtime.yml' 2023-04-28 05:57:52,199 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/doc_fragments/hpe_nimble.py' 2023-04-28 05:57:52,199 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/module_utils/hpe_nimble.py' 2023-04-28 05:57:52,200 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_access_control_record.py' 2023-04-28 05:57:52,200 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_array.py' 2023-04-28 05:57:52,200 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_chap_user.py' 2023-04-28 05:57:52,201 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_disk.py' 2023-04-28 05:57:52,201 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_encryption.py' 2023-04-28 05:57:52,201 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_fc.py' 2023-04-28 05:57:52,202 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_group.py' 2023-04-28 05:57:52,202 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_info.py' 2023-04-28 05:57:52,202 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_initiator_group.py' 2023-04-28 05:57:52,203 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_network.py' 2023-04-28 05:57:52,203 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_partner.py' 2023-04-28 05:57:52,203 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_performance_policy.py' 2023-04-28 05:57:52,204 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_pool.py' 2023-04-28 05:57:52,204 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_protection_schedule.py' 2023-04-28 05:57:52,204 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_protection_template.py' 2023-04-28 05:57:52,205 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_shelf.py' 2023-04-28 05:57:52,205 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_snapshot.py' 2023-04-28 05:57:52,205 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_snapshot_collection.py' 2023-04-28 05:57:52,206 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_user.py' 2023-04-28 05:57:52,206 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_user_policy.py' 2023-04-28 05:57:52,206 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_volume.py' 2023-04-28 05:57:52,207 wheel INFO adding 'ansible_collections/hpe/nimble/plugins/modules/hpe_nimble_volume_collection.py' 2023-04-28 05:57:52,207 wheel INFO adding 'ansible_collections/ibm/qradar/CHANGELOG.rst' 2023-04-28 05:57:52,207 wheel INFO adding 'ansible_collections/ibm/qradar/FILES.json' 2023-04-28 05:57:52,208 wheel INFO adding 'ansible_collections/ibm/qradar/LICENSE' 2023-04-28 05:57:52,208 wheel INFO adding 'ansible_collections/ibm/qradar/MANIFEST.json' 2023-04-28 05:57:52,208 wheel INFO adding 'ansible_collections/ibm/qradar/README.md' 2023-04-28 05:57:52,209 wheel INFO adding 'ansible_collections/ibm/qradar/bindep.txt' 2023-04-28 05:57:52,209 wheel INFO adding 'ansible_collections/ibm/qradar/pyproject.toml' 2023-04-28 05:57:52,209 wheel INFO adding 'ansible_collections/ibm/qradar/requirements.txt' 2023-04-28 05:57:52,209 wheel INFO adding 'ansible_collections/ibm/qradar/test-requirements.txt' 2023-04-28 05:57:52,209 wheel INFO adding 'ansible_collections/ibm/qradar/tox.ini' 2023-04-28 05:57:52,210 wheel INFO adding 'ansible_collections/ibm/qradar/changelogs/changelog.yaml' 2023-04-28 05:57:52,210 wheel INFO adding 'ansible_collections/ibm/qradar/changelogs/config.yaml' 2023-04-28 05:57:52,210 wheel INFO adding 'ansible_collections/ibm/qradar/meta/runtime.yml' 2023-04-28 05:57:52,210 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/action/__init__.py' 2023-04-28 05:57:52,211 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/action/qradar_analytics_rules.py' 2023-04-28 05:57:52,211 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/action/qradar_log_sources_management.py' 2023-04-28 05:57:52,211 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/httpapi/qradar.py' 2023-04-28 05:57:52,211 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/module_utils/qradar.py' 2023-04-28 05:57:52,212 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/deploy.py' 2023-04-28 05:57:52,212 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/log_source_management.py' 2023-04-28 05:57:52,212 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/offense_action.py' 2023-04-28 05:57:52,212 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/offense_info.py' 2023-04-28 05:57:52,213 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/offense_note.py' 2023-04-28 05:57:52,213 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_analytics_rules.py' 2023-04-28 05:57:52,213 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_deploy.py' 2023-04-28 05:57:52,213 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_log_source_management.py' 2023-04-28 05:57:52,214 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_log_sources_management.py' 2023-04-28 05:57:52,214 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_offense_action.py' 2023-04-28 05:57:52,214 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_offense_info.py' 2023-04-28 05:57:52,215 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_offense_note.py' 2023-04-28 05:57:52,215 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_rule.py' 2023-04-28 05:57:52,215 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/qradar_rule_info.py' 2023-04-28 05:57:52,215 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/rule.py' 2023-04-28 05:57:52,216 wheel INFO adding 'ansible_collections/ibm/qradar/plugins/modules/rule_info.py' 2023-04-28 05:57:52,216 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/FILES.json' 2023-04-28 05:57:52,216 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/LICENSE' 2023-04-28 05:57:52,217 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/MANIFEST.json' 2023-04-28 05:57:52,217 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/README.md' 2023-04-28 05:57:52,217 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/requirements.txt' 2023-04-28 05:57:52,217 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/requirements.yml' 2023-04-28 05:57:52,218 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/changelogs/changelog.yaml' 2023-04-28 05:57:52,218 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/meta/execution-environment.yml' 2023-04-28 05:57:52,218 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/meta/runtime.yml' 2023-04-28 05:57:52,218 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/playbooks/create_GMCV_in_CG.yml' 2023-04-28 05:57:52,219 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/playbooks/generic_ansible_sample.yaml' 2023-04-28 05:57:52,219 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/playbooks/generic_info.yml' 2023-04-28 05:57:52,219 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/playbooks/initial_setup_system_complete.yml' 2023-04-28 05:57:52,219 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/playbooks/map_volume_to_host.yml' 2023-04-28 05:57:52,219 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/playbooks/volume_migrate.yml' 2023-04-28 05:57:52,220 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/playbooks/volumegrp_create.yml' 2023-04-28 05:57:52,220 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/README.md' 2023-04-28 05:57:52,220 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/ibm_svc_ssh.py' 2023-04-28 05:57:52,220 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/ibm_svc_utils.py' 2023-04-28 05:57:52,221 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/__init__.py' 2023-04-28 05:57:52,221 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_awss3_cloudaccount.py' 2023-04-28 05:57:52,221 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_cloud_backups.py' 2023-04-28 05:57:52,222 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_ip_partnership.py' 2023-04-28 05:57:52,222 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_provisioning_policy.py' 2023-04-28 05:57:52,222 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_replication_policy.py' 2023-04-28 05:57:52,223 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_snapshot.py' 2023-04-28 05:57:52,223 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_snapshotpolicy.py' 2023-04-28 05:57:52,223 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_ssl_certificate.py' 2023-04-28 05:57:52,223 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_manage_truststore_for_replication.py' 2023-04-28 05:57:52,224 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_restore_cloud_backup.py' 2023-04-28 05:57:52,224 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_sv_switch_replication_direction.py' 2023-04-28 05:57:52,224 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_auth.py' 2023-04-28 05:57:52,224 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_complete_initial_setup.py' 2023-04-28 05:57:52,225 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_host.py' 2023-04-28 05:57:52,225 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_hostcluster.py' 2023-04-28 05:57:52,225 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_info.py' 2023-04-28 05:57:52,226 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_initial_setup.py' 2023-04-28 05:57:52,226 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_callhome.py' 2023-04-28 05:57:52,226 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_consistgrp_flashcopy.py' 2023-04-28 05:57:52,227 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_cv.py' 2023-04-28 05:57:52,227 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_flashcopy.py' 2023-04-28 05:57:52,227 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_ip.py' 2023-04-28 05:57:52,228 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_migration.py' 2023-04-28 05:57:52,228 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_mirrored_volume.py' 2023-04-28 05:57:52,229 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_ownershipgroup.py' 2023-04-28 05:57:52,229 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_portset.py' 2023-04-28 05:57:52,229 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_replication.py' 2023-04-28 05:57:52,229 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_replicationgroup.py' 2023-04-28 05:57:52,230 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_safeguarded_policy.py' 2023-04-28 05:57:52,230 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_sra.py' 2023-04-28 05:57:52,230 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_user.py' 2023-04-28 05:57:52,231 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_usergroup.py' 2023-04-28 05:57:52,231 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_volume.py' 2023-04-28 05:57:52,231 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_manage_volumegroup.py' 2023-04-28 05:57:52,232 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_mdisk.py' 2023-04-28 05:57:52,232 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_mdiskgrp.py' 2023-04-28 05:57:52,232 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_start_stop_flashcopy.py' 2023-04-28 05:57:52,233 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_start_stop_replication.py' 2023-04-28 05:57:52,233 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_vdisk.py' 2023-04-28 05:57:52,233 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svc_vol_map.py' 2023-04-28 05:57:52,233 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svcinfo_command.py' 2023-04-28 05:57:52,234 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/plugins/modules/ibm_svctask_command.py' 2023-04-28 05:57:52,234 wheel INFO adding 'ansible_collections/ibm/spectrum_virtualize/roles/place_holder' 2023-04-28 05:57:52,234 wheel INFO adding 'ansible_collections/infinidat/infinibox/CHANGELOG.rst' 2023-04-28 05:57:52,235 wheel INFO adding 'ansible_collections/infinidat/infinibox/FILES.json' 2023-04-28 05:57:52,235 wheel INFO adding 'ansible_collections/infinidat/infinibox/LICENSE' 2023-04-28 05:57:52,235 wheel INFO adding 'ansible_collections/infinidat/infinibox/MANIFEST.json' 2023-04-28 05:57:52,236 wheel INFO adding 'ansible_collections/infinidat/infinibox/Makefile' 2023-04-28 05:57:52,236 wheel INFO adding 'ansible_collections/infinidat/infinibox/Makefile-help' 2023-04-28 05:57:52,236 wheel INFO adding 'ansible_collections/infinidat/infinibox/README.md' 2023-04-28 05:57:52,236 wheel INFO adding 'ansible_collections/infinidat/infinibox/requirements-dev.txt' 2023-04-28 05:57:52,236 wheel INFO adding 'ansible_collections/infinidat/infinibox/requirements.txt' 2023-04-28 05:57:52,237 wheel INFO adding 'ansible_collections/infinidat/infinibox/ibox_vars/iboxCICD.yaml' 2023-04-28 05:57:52,237 wheel INFO adding 'ansible_collections/infinidat/infinibox/ibox_vars/iboxNNNN_example.yaml' 2023-04-28 05:57:52,237 wheel INFO adding 'ansible_collections/infinidat/infinibox/meta/execution-environment.yml' 2023-04-28 05:57:52,237 wheel INFO adding 'ansible_collections/infinidat/infinibox/meta/runtime.yml' 2023-04-28 05:57:52,238 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/ansible.cfg' 2023-04-28 05:57:52,238 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_runtest.yml' 2023-04-28 05:57:52,238 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_setup.yml' 2023-04-28 05:57:52,238 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/infinisafe_demo_teardown.yml' 2023-04-28 05:57:52,238 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/inventory' 2023-04-28 05:57:52,239 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_create_map_cluster.yml' 2023-04-28 05:57:52,239 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_create_network_spaces.yml' 2023-04-28 05:57:52,239 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_create_resources.yml' 2023-04-28 05:57:52,240 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_create_snapshots.yml' 2023-04-28 05:57:52,240 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_remove_map_cluster.yml' 2023-04-28 05:57:52,240 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_remove_network_spaces.yml' 2023-04-28 05:57:52,240 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_remove_resources.yml' 2023-04-28 05:57:52,240 wheel INFO adding 'ansible_collections/infinidat/infinibox/playbooks/test_remove_snapshots.yml' 2023-04-28 05:57:52,241 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/doc_fragments/infinibox.py' 2023-04-28 05:57:52,241 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/filter/delta_time.yml' 2023-04-28 05:57:52,241 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/filter/psus_filters.py' 2023-04-28 05:57:52,241 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/module_utils/infinibox.py' 2023-04-28 05:57:52,242 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/__init__.py' 2023-04-28 05:57:52,242 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_cluster.py' 2023-04-28 05:57:52,242 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_export.py' 2023-04-28 05:57:52,242 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_export_client.py' 2023-04-28 05:57:52,243 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_fs.py' 2023-04-28 05:57:52,243 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_host.py' 2023-04-28 05:57:52,243 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_map.py' 2023-04-28 05:57:52,244 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_network_space.py' 2023-04-28 05:57:52,244 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_pool.py' 2023-04-28 05:57:52,244 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_port.py' 2023-04-28 05:57:52,244 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_user.py' 2023-04-28 05:57:52,245 wheel INFO adding 'ansible_collections/infinidat/infinibox/plugins/modules/infini_vol.py' 2023-04-28 05:57:52,245 wheel INFO adding 'ansible_collections/infoblox/nios_modules/CHANGELOG.rst' 2023-04-28 05:57:52,245 wheel INFO adding 'ansible_collections/infoblox/nios_modules/CONTRIBUTING.md' 2023-04-28 05:57:52,246 wheel INFO adding 'ansible_collections/infoblox/nios_modules/COPYING' 2023-04-28 05:57:52,246 wheel INFO adding 'ansible_collections/infoblox/nios_modules/FILES.json' 2023-04-28 05:57:52,247 wheel INFO adding 'ansible_collections/infoblox/nios_modules/MANIFEST.json' 2023-04-28 05:57:52,247 wheel INFO adding 'ansible_collections/infoblox/nios_modules/README.md' 2023-04-28 05:57:52,247 wheel INFO adding 'ansible_collections/infoblox/nios_modules/requirements.txt' 2023-04-28 05:57:52,247 wheel INFO adding 'ansible_collections/infoblox/nios_modules/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,248 wheel INFO adding 'ansible_collections/infoblox/nios_modules/changelogs/changelog.yaml' 2023-04-28 05:57:52,248 wheel INFO adding 'ansible_collections/infoblox/nios_modules/changelogs/config.yaml' 2023-04-28 05:57:52,248 wheel INFO adding 'ansible_collections/infoblox/nios_modules/meta/runtime.yml' 2023-04-28 05:57:52,248 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_a_record.yaml' 2023-04-28 05:57:52,249 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_cname_record.yaml' 2023-04-28 05:57:52,249 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_dns_view.yml' 2023-04-28 05:57:52,249 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_dtc_lbdn.yml' 2023-04-28 05:57:52,249 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_dtc_pool.yml' 2023-04-28 05:57:52,249 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_dtc_server.yml' 2023-04-28 05:57:52,250 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_mx_record.yaml' 2023-04-28 05:57:52,250 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_network.yml' 2023-04-28 05:57:52,250 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_network_view.yml' 2023-04-28 05:57:52,250 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_txt_record.yaml' 2023-04-28 05:57:52,250 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/create_zone.yml' 2023-04-28 05:57:52,251 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/delete_cname_record.yaml' 2023-04-28 05:57:52,251 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/delete_dnsview.yml' 2023-04-28 05:57:52,251 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/delete_mx_record.yaml' 2023-04-28 05:57:52,251 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/delete_network.yml' 2023-04-28 05:57:52,251 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/delete_network_view.yml' 2023-04-28 05:57:52,252 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/delete_txt_record.yaml' 2023-04-28 05:57:52,252 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/delete_zone.yml' 2023-04-28 05:57:52,252 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/restart_services.yml' 2023-04-28 05:57:52,252 wheel INFO adding 'ansible_collections/infoblox/nios_modules/playbooks/update_a_record.yml' 2023-04-28 05:57:52,252 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/README.md' 2023-04-28 05:57:52,253 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/doc_fragments/nios.py' 2023-04-28 05:57:52,253 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/inventory/nios_inventory.py' 2023-04-28 05:57:52,253 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/lookup/nios_lookup.py' 2023-04-28 05:57:52,254 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/lookup/nios_next_ip.py' 2023-04-28 05:57:52,254 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/lookup/nios_next_network.py' 2023-04-28 05:57:52,255 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/module_utils/api.py' 2023-04-28 05:57:52,255 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/module_utils/network.py' 2023-04-28 05:57:52,255 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_a_record.py' 2023-04-28 05:57:52,255 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_aaaa_record.py' 2023-04-28 05:57:52,256 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_cname_record.py' 2023-04-28 05:57:52,256 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_dns_view.py' 2023-04-28 05:57:52,256 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_lbdn.py' 2023-04-28 05:57:52,256 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_pool.py' 2023-04-28 05:57:52,257 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_dtc_server.py' 2023-04-28 05:57:52,257 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_fixed_address.py' 2023-04-28 05:57:52,257 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_host_record.py' 2023-04-28 05:57:52,257 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_member.py' 2023-04-28 05:57:52,258 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_mx_record.py' 2023-04-28 05:57:52,258 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_naptr_record.py' 2023-04-28 05:57:52,258 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_network.py' 2023-04-28 05:57:52,259 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_network_view.py' 2023-04-28 05:57:52,259 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_nsgroup.py' 2023-04-28 05:57:52,259 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_ptr_record.py' 2023-04-28 05:57:52,259 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_restartservices.py' 2023-04-28 05:57:52,260 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_srv_record.py' 2023-04-28 05:57:52,260 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_txt_record.py' 2023-04-28 05:57:52,260 wheel INFO adding 'ansible_collections/infoblox/nios_modules/plugins/modules/nios_zone.py' 2023-04-28 05:57:52,260 wheel INFO adding 'ansible_collections/inspur/ispim/CHANGELOG.rst' 2023-04-28 05:57:52,261 wheel INFO adding 'ansible_collections/inspur/ispim/CODE_OF_CONDUCT.md' 2023-04-28 05:57:52,261 wheel INFO adding 'ansible_collections/inspur/ispim/FILES.json' 2023-04-28 05:57:52,262 wheel INFO adding 'ansible_collections/inspur/ispim/LICENSE' 2023-04-28 05:57:52,262 wheel INFO adding 'ansible_collections/inspur/ispim/MANIFEST.json' 2023-04-28 05:57:52,262 wheel INFO adding 'ansible_collections/inspur/ispim/README.md' 2023-04-28 05:57:52,262 wheel INFO adding 'ansible_collections/inspur/ispim/__init__.py' 2023-04-28 05:57:52,262 wheel INFO adding 'ansible_collections/inspur/ispim/requirements.txt' 2023-04-28 05:57:52,263 wheel INFO adding 'ansible_collections/inspur/ispim/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,263 wheel INFO adding 'ansible_collections/inspur/ispim/changelogs/changelog.yaml' 2023-04-28 05:57:52,263 wheel INFO adding 'ansible_collections/inspur/ispim/changelogs/config.yaml' 2023-04-28 05:57:52,264 wheel INFO adding 'ansible_collections/inspur/ispim/changelogs/fragments/.keep' 2023-04-28 05:57:52,264 wheel INFO adding 'ansible_collections/inspur/ispim/meta/runtime.yml' 2023-04-28 05:57:52,264 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/doc_fragments/ism.py' 2023-04-28 05:57:52,264 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,265 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/module_utils/ism.py' 2023-04-28 05:57:52,265 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/__init__.py' 2023-04-28 05:57:52,265 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ad_group.py' 2023-04-28 05:57:52,265 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ad_group_info.py' 2023-04-28 05:57:52,266 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ad_info.py' 2023-04-28 05:57:52,266 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/adapter_info.py' 2023-04-28 05:57:52,266 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/add_ldisk.py' 2023-04-28 05:57:52,266 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/alert_policy_info.py' 2023-04-28 05:57:52,267 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/audit_log_info.py' 2023-04-28 05:57:52,267 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/auto_capture_info.py' 2023-04-28 05:57:52,267 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/backplane_info.py' 2023-04-28 05:57:52,267 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/backup.py' 2023-04-28 05:57:52,268 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/bios_export.py' 2023-04-28 05:57:52,268 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/bios_import.py' 2023-04-28 05:57:52,268 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/bios_info.py' 2023-04-28 05:57:52,268 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/bmc_info.py' 2023-04-28 05:57:52,268 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/boot_image_info.py' 2023-04-28 05:57:52,269 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/boot_option_info.py' 2023-04-28 05:57:52,269 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/clear_audit_log.py' 2023-04-28 05:57:52,269 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/clear_event_log.py' 2023-04-28 05:57:52,269 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/clear_system_log.py' 2023-04-28 05:57:52,269 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/collect_blackbox.py' 2023-04-28 05:57:52,270 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/collect_log.py' 2023-04-28 05:57:52,270 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/connect_media_info.py' 2023-04-28 05:57:52,270 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/cpu_info.py' 2023-04-28 05:57:52,270 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/del_session.py' 2023-04-28 05:57:52,271 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/dns_info.py' 2023-04-28 05:57:52,271 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/download_auto_screenshot.py' 2023-04-28 05:57:52,271 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/download_manual_screenshot.py' 2023-04-28 05:57:52,271 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_ad.py' 2023-04-28 05:57:52,271 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_alert_policy.py' 2023-04-28 05:57:52,272 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_auto_capture.py' 2023-04-28 05:57:52,272 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_bios.py' 2023-04-28 05:57:52,272 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_boot_image.py' 2023-04-28 05:57:52,272 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_boot_option.py' 2023-04-28 05:57:52,273 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_connect_media.py' 2023-04-28 05:57:52,273 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_dns.py' 2023-04-28 05:57:52,273 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_event_log_policy.py' 2023-04-28 05:57:52,273 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_fan.py' 2023-04-28 05:57:52,274 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_fru.py' 2023-04-28 05:57:52,274 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_ipv4.py' 2023-04-28 05:57:52,274 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_ipv6.py' 2023-04-28 05:57:52,274 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_kvm.py' 2023-04-28 05:57:52,274 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_ldap.py' 2023-04-28 05:57:52,275 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_ldisk.py' 2023-04-28 05:57:52,275 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_log_setting.py' 2023-04-28 05:57:52,275 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_m6_log_setting.py' 2023-04-28 05:57:52,275 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_manual_capture.py' 2023-04-28 05:57:52,276 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_media_instance.py' 2023-04-28 05:57:52,276 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_ncsi.py' 2023-04-28 05:57:52,276 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_network.py' 2023-04-28 05:57:52,276 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_network_bond.py' 2023-04-28 05:57:52,277 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_network_link.py' 2023-04-28 05:57:52,277 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_ntp.py' 2023-04-28 05:57:52,277 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_pdisk.py' 2023-04-28 05:57:52,277 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_power_budget.py' 2023-04-28 05:57:52,277 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_power_restore.py' 2023-04-28 05:57:52,278 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_power_status.py' 2023-04-28 05:57:52,278 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_preserve_config.py' 2023-04-28 05:57:52,278 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_psu_config.py' 2023-04-28 05:57:52,278 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_psu_peak.py' 2023-04-28 05:57:52,279 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_restore_factory_default.py' 2023-04-28 05:57:52,279 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_service.py' 2023-04-28 05:57:52,279 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_smtp.py' 2023-04-28 05:57:52,279 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_smtp_com.py' 2023-04-28 05:57:52,280 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_smtp_dest.py' 2023-04-28 05:57:52,280 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_snmp.py' 2023-04-28 05:57:52,280 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_snmp_trap.py' 2023-04-28 05:57:52,280 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_threshold.py' 2023-04-28 05:57:52,280 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_uid.py' 2023-04-28 05:57:52,281 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_virtual_media.py' 2023-04-28 05:57:52,281 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/edit_vlan.py' 2023-04-28 05:57:52,281 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/event_log_info.py' 2023-04-28 05:57:52,281 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/event_log_policy_info.py' 2023-04-28 05:57:52,282 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/fan_info.py' 2023-04-28 05:57:52,282 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/fru_info.py' 2023-04-28 05:57:52,282 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/fw_version_info.py' 2023-04-28 05:57:52,282 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/gpu_info.py' 2023-04-28 05:57:52,282 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/hard_disk_info.py' 2023-04-28 05:57:52,283 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/kvm_info.py' 2023-04-28 05:57:52,283 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ldap_group.py' 2023-04-28 05:57:52,283 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ldap_group_info.py' 2023-04-28 05:57:52,283 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ldap_info.py' 2023-04-28 05:57:52,284 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ldisk_info.py' 2023-04-28 05:57:52,284 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/log_setting_info.py' 2023-04-28 05:57:52,284 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/media_instance_info.py' 2023-04-28 05:57:52,284 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/mem_info.py' 2023-04-28 05:57:52,284 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ncsi_info.py' 2023-04-28 05:57:52,285 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/network_bond_info.py' 2023-04-28 05:57:52,285 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/network_info.py' 2023-04-28 05:57:52,285 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/network_link_info.py' 2023-04-28 05:57:52,285 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/ntp_info.py' 2023-04-28 05:57:52,285 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/onboard_disk_info.py' 2023-04-28 05:57:52,286 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/pcie_info.py' 2023-04-28 05:57:52,286 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/pdisk_info.py' 2023-04-28 05:57:52,286 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/power_budget_info.py' 2023-04-28 05:57:52,286 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/power_consumption_info.py' 2023-04-28 05:57:52,287 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/power_restore_info.py' 2023-04-28 05:57:52,287 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/power_status_info.py' 2023-04-28 05:57:52,287 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/preserve_config_info.py' 2023-04-28 05:57:52,287 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/psu_config_info.py' 2023-04-28 05:57:52,287 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/psu_info.py' 2023-04-28 05:57:52,288 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/psu_peak_info.py' 2023-04-28 05:57:52,288 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/raid_info.py' 2023-04-28 05:57:52,288 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/reset_bmc.py' 2023-04-28 05:57:52,288 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/reset_kvm.py' 2023-04-28 05:57:52,288 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/restore.py' 2023-04-28 05:57:52,289 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/self_test_info.py' 2023-04-28 05:57:52,289 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/sensor_info.py' 2023-04-28 05:57:52,289 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/server_info.py' 2023-04-28 05:57:52,289 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/service_info.py' 2023-04-28 05:57:52,290 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/session_info.py' 2023-04-28 05:57:52,290 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/smtp_info.py' 2023-04-28 05:57:52,290 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/snmp_info.py' 2023-04-28 05:57:52,290 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/snmp_trap_info.py' 2023-04-28 05:57:52,290 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/support_info.py' 2023-04-28 05:57:52,291 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/system_log_info.py' 2023-04-28 05:57:52,291 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/temp_info.py' 2023-04-28 05:57:52,291 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/threshold_info.py' 2023-04-28 05:57:52,291 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/uid_info.py' 2023-04-28 05:57:52,292 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/update_cpld.py' 2023-04-28 05:57:52,292 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/update_fw.py' 2023-04-28 05:57:52,292 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/user.py' 2023-04-28 05:57:52,292 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/user_group.py' 2023-04-28 05:57:52,292 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/user_group_info.py' 2023-04-28 05:57:52,293 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/user_info.py' 2023-04-28 05:57:52,293 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/virtual_media_info.py' 2023-04-28 05:57:52,293 wheel INFO adding 'ansible_collections/inspur/ispim/plugins/modules/volt_info.py' 2023-04-28 05:57:52,293 wheel INFO adding 'ansible_collections/inspur/sm/CHANGELOG.rst' 2023-04-28 05:57:52,294 wheel INFO adding 'ansible_collections/inspur/sm/CODE_OF_CONDUCT.md' 2023-04-28 05:57:52,294 wheel INFO adding 'ansible_collections/inspur/sm/FILES.json' 2023-04-28 05:57:52,295 wheel INFO adding 'ansible_collections/inspur/sm/LICENSE' 2023-04-28 05:57:52,295 wheel INFO adding 'ansible_collections/inspur/sm/MANIFEST.json' 2023-04-28 05:57:52,295 wheel INFO adding 'ansible_collections/inspur/sm/README.md' 2023-04-28 05:57:52,296 wheel INFO adding 'ansible_collections/inspur/sm/__init__.py' 2023-04-28 05:57:52,296 wheel INFO adding 'ansible_collections/inspur/sm/bindep.txt' 2023-04-28 05:57:52,296 wheel INFO adding 'ansible_collections/inspur/sm/requirements.txt' 2023-04-28 05:57:52,296 wheel INFO adding 'ansible_collections/inspur/sm/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,297 wheel INFO adding 'ansible_collections/inspur/sm/changelogs/changelog.yaml' 2023-04-28 05:57:52,297 wheel INFO adding 'ansible_collections/inspur/sm/changelogs/config.yaml' 2023-04-28 05:57:52,297 wheel INFO adding 'ansible_collections/inspur/sm/meta/runtime.yml' 2023-04-28 05:57:52,297 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ad_group.yml' 2023-04-28 05:57:52,298 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ad_group_info.yml' 2023-04-28 05:57:52,298 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ad_info.yml' 2023-04-28 05:57:52,298 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-adapter_info.yml' 2023-04-28 05:57:52,298 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-add_ad_group.yml' 2023-04-28 05:57:52,298 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-add_ldap_group.yml' 2023-04-28 05:57:52,299 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-add_ldisk.yml' 2023-04-28 05:57:52,299 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-add_user.yml' 2023-04-28 05:57:52,299 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-add_user_group.yml' 2023-04-28 05:57:52,299 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-alert_policy_info.yml' 2023-04-28 05:57:52,300 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-audit_log_info.yml' 2023-04-28 05:57:52,300 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-auto_capture_info.yml' 2023-04-28 05:57:52,300 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-backplane_info.yml' 2023-04-28 05:57:52,300 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-backup.yml' 2023-04-28 05:57:52,300 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-bios_export.yml' 2023-04-28 05:57:52,301 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-bios_import.yml' 2023-04-28 05:57:52,301 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-bios_info.yml' 2023-04-28 05:57:52,301 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-bmc_info.yml' 2023-04-28 05:57:52,301 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-boot_image_info.yml' 2023-04-28 05:57:52,301 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-boot_option_info.yml' 2023-04-28 05:57:52,302 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-clear_audit_log.yml' 2023-04-28 05:57:52,302 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-clear_event_log.yml' 2023-04-28 05:57:52,302 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-clear_system_log.yml' 2023-04-28 05:57:52,302 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-collect_blackbox.yml' 2023-04-28 05:57:52,302 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-collect_log.yml' 2023-04-28 05:57:52,303 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-connect_media_info.yml' 2023-04-28 05:57:52,303 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-cpu_info.yml' 2023-04-28 05:57:52,303 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-del_ad_group.yml' 2023-04-28 05:57:52,303 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-del_ldap_group.yml' 2023-04-28 05:57:52,303 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-del_session.yml' 2023-04-28 05:57:52,304 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-del_user.yml' 2023-04-28 05:57:52,304 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-del_user_group.yml' 2023-04-28 05:57:52,304 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-dns_info.yml' 2023-04-28 05:57:52,304 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-download_auto_screenshot.yml' 2023-04-28 05:57:52,304 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-download_manual_screenshot.yml' 2023-04-28 05:57:52,305 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ad.yml' 2023-04-28 05:57:52,305 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ad_group.yml' 2023-04-28 05:57:52,305 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_alert_policy.yml' 2023-04-28 05:57:52,305 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_auto_capture.yml' 2023-04-28 05:57:52,305 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_bios.yml' 2023-04-28 05:57:52,306 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_boot_image.yml' 2023-04-28 05:57:52,306 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_boot_option.yml' 2023-04-28 05:57:52,306 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_connect_media.yml' 2023-04-28 05:57:52,306 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_dns.yml' 2023-04-28 05:57:52,306 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_event_log_policy.yml' 2023-04-28 05:57:52,307 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_fan.yml' 2023-04-28 05:57:52,307 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_fru.yml' 2023-04-28 05:57:52,307 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ipv4.yml' 2023-04-28 05:57:52,307 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ipv6.yml' 2023-04-28 05:57:52,308 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_kvm.yml' 2023-04-28 05:57:52,308 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldap.yml' 2023-04-28 05:57:52,308 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldap_group.yml' 2023-04-28 05:57:52,308 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ldisk.yml' 2023-04-28 05:57:52,308 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_log_setting.yml' 2023-04-28 05:57:52,309 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_manual_capture.yml' 2023-04-28 05:57:52,309 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_media_instance.yml' 2023-04-28 05:57:52,309 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ncsi.yml' 2023-04-28 05:57:52,309 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_network.yml' 2023-04-28 05:57:52,309 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_network_bond.yml' 2023-04-28 05:57:52,310 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_network_link.yml' 2023-04-28 05:57:52,310 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_ntp.yml' 2023-04-28 05:57:52,310 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_pass_user.yml' 2023-04-28 05:57:52,310 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_pdisk.yml' 2023-04-28 05:57:52,310 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_budget.yml' 2023-04-28 05:57:52,311 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_restore.yml' 2023-04-28 05:57:52,311 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_power_status.yml' 2023-04-28 05:57:52,311 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_preserve_config.yml' 2023-04-28 05:57:52,311 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_priv_user.yml' 2023-04-28 05:57:52,311 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_psu_config.yml' 2023-04-28 05:57:52,312 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_psu_peak.yml' 2023-04-28 05:57:52,312 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_restore_factory_default.yml' 2023-04-28 05:57:52,312 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_service.yml' 2023-04-28 05:57:52,312 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp.yml' 2023-04-28 05:57:52,312 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp_com.yml' 2023-04-28 05:57:52,313 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_smtp_dest.yml' 2023-04-28 05:57:52,313 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_snmp.yml' 2023-04-28 05:57:52,313 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_snmp_trap.yml' 2023-04-28 05:57:52,313 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_threshold.yml' 2023-04-28 05:57:52,313 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_uid.yml' 2023-04-28 05:57:52,314 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_user_group.yml' 2023-04-28 05:57:52,314 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_virtual_media.yml' 2023-04-28 05:57:52,314 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-edit_vlan.yml' 2023-04-28 05:57:52,314 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-event_log_info.yml' 2023-04-28 05:57:52,314 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-event_log_policy_info.yml' 2023-04-28 05:57:52,315 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-fan_info.yml' 2023-04-28 05:57:52,315 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-fru_info.yml' 2023-04-28 05:57:52,315 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-fw_verison_info.yml' 2023-04-28 05:57:52,315 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-gpu_info.yml' 2023-04-28 05:57:52,315 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-hard_disk_info.yml' 2023-04-28 05:57:52,316 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-kvm_info.yml' 2023-04-28 05:57:52,316 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ldap_group.yml' 2023-04-28 05:57:52,316 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ldap_group_info.yml' 2023-04-28 05:57:52,316 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ldap_info.yml' 2023-04-28 05:57:52,316 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ldisk_info.yml' 2023-04-28 05:57:52,317 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-log_setting_info.yml' 2023-04-28 05:57:52,317 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-media_instance_info.yml' 2023-04-28 05:57:52,317 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-mem_info.yml' 2023-04-28 05:57:52,318 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ncsi_info.yml' 2023-04-28 05:57:52,318 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-network_bond_info.yml' 2023-04-28 05:57:52,318 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-network_info.yml' 2023-04-28 05:57:52,319 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-network_link_info.yml' 2023-04-28 05:57:52,319 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-ntp_info.yml' 2023-04-28 05:57:52,319 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-onboard_disk_info.yml' 2023-04-28 05:57:52,319 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-pcie_info.yml' 2023-04-28 05:57:52,319 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-pdisk_info.yml' 2023-04-28 05:57:52,320 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-power_budget_info.yml' 2023-04-28 05:57:52,320 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-power_consumption_info.yml' 2023-04-28 05:57:52,320 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-power_restore_info.yml' 2023-04-28 05:57:52,320 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-power_status_info.yml' 2023-04-28 05:57:52,320 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-preserver_config_info.yml' 2023-04-28 05:57:52,321 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-psu_config_info.yml' 2023-04-28 05:57:52,321 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-psu_info.yml' 2023-04-28 05:57:52,321 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-psu_peak_info.yml' 2023-04-28 05:57:52,321 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-raid_info.yml' 2023-04-28 05:57:52,321 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-reset_bmc.yml' 2023-04-28 05:57:52,322 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-reset_kvm.yml' 2023-04-28 05:57:52,322 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-restore.yml' 2023-04-28 05:57:52,322 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-self_test_info.yml' 2023-04-28 05:57:52,322 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-sensor_info.yml' 2023-04-28 05:57:52,322 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-server_info.yml' 2023-04-28 05:57:52,323 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-service_info.yml' 2023-04-28 05:57:52,323 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-session_info.yml' 2023-04-28 05:57:52,323 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-smtp_info.yml' 2023-04-28 05:57:52,323 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-snmp_info.yml' 2023-04-28 05:57:52,324 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-snmp_trap_info.yml' 2023-04-28 05:57:52,324 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-system_log_info.yml' 2023-04-28 05:57:52,324 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-temp_info.yml' 2023-04-28 05:57:52,324 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-threshold_info.yml' 2023-04-28 05:57:52,324 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-uid_info.yml' 2023-04-28 05:57:52,325 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-update_cpld.yml' 2023-04-28 05:57:52,325 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-update_fw.yml' 2023-04-28 05:57:52,325 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-user.yml' 2023-04-28 05:57:52,325 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-user_group.yml' 2023-04-28 05:57:52,325 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-user_group_info.yml' 2023-04-28 05:57:52,326 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-user_info.yml' 2023-04-28 05:57:52,326 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-virtual_media_info.yml' 2023-04-28 05:57:52,326 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/examples-volt_info.yml' 2023-04-28 05:57:52,326 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/overall/examples-ad_overall.yml' 2023-04-28 05:57:52,326 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/overall/examples-ldap_overall.yml' 2023-04-28 05:57:52,327 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/overall/examples-system_info_overall.yml' 2023-04-28 05:57:52,327 wheel INFO adding 'ansible_collections/inspur/sm/playbooks/modules/overall/examples-user_overall.yml' 2023-04-28 05:57:52,327 wheel INFO adding 'ansible_collections/inspur/sm/plugins/doc_fragments/ism.py' 2023-04-28 05:57:52,327 wheel INFO adding 'ansible_collections/inspur/sm/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,328 wheel INFO adding 'ansible_collections/inspur/sm/plugins/module_utils/ism.py' 2023-04-28 05:57:52,328 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/__init__.py' 2023-04-28 05:57:52,328 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ad_group.py' 2023-04-28 05:57:52,328 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ad_group_info.py' 2023-04-28 05:57:52,329 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ad_info.py' 2023-04-28 05:57:52,329 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/adapter_info.py' 2023-04-28 05:57:52,329 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/add_ad_group.py' 2023-04-28 05:57:52,329 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/add_ldap_group.py' 2023-04-28 05:57:52,330 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/add_ldisk.py' 2023-04-28 05:57:52,330 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/add_user.py' 2023-04-28 05:57:52,330 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/add_user_group.py' 2023-04-28 05:57:52,330 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/alert_policy_info.py' 2023-04-28 05:57:52,331 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/audit_log_info.py' 2023-04-28 05:57:52,331 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/auto_capture_info.py' 2023-04-28 05:57:52,331 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/backplane_info.py' 2023-04-28 05:57:52,331 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/backup.py' 2023-04-28 05:57:52,331 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/bios_export.py' 2023-04-28 05:57:52,332 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/bios_import.py' 2023-04-28 05:57:52,332 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/bios_info.py' 2023-04-28 05:57:52,332 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/bmc_info.py' 2023-04-28 05:57:52,332 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/boot_image_info.py' 2023-04-28 05:57:52,333 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/boot_option_info.py' 2023-04-28 05:57:52,333 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/clear_audit_log.py' 2023-04-28 05:57:52,333 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/clear_event_log.py' 2023-04-28 05:57:52,333 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/clear_system_log.py' 2023-04-28 05:57:52,333 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/collect_blackbox.py' 2023-04-28 05:57:52,334 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/collect_log.py' 2023-04-28 05:57:52,334 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/connect_media_info.py' 2023-04-28 05:57:52,334 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/cpu_info.py' 2023-04-28 05:57:52,334 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/del_ad_group.py' 2023-04-28 05:57:52,335 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/del_ldap_group.py' 2023-04-28 05:57:52,335 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/del_session.py' 2023-04-28 05:57:52,335 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/del_user.py' 2023-04-28 05:57:52,335 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/del_user_group.py' 2023-04-28 05:57:52,335 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/dns_info.py' 2023-04-28 05:57:52,336 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/download_auto_screenshot.py' 2023-04-28 05:57:52,336 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/download_manual_screenshot.py' 2023-04-28 05:57:52,336 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ad.py' 2023-04-28 05:57:52,336 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ad_group.py' 2023-04-28 05:57:52,337 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_alert_policy.py' 2023-04-28 05:57:52,337 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_auto_capture.py' 2023-04-28 05:57:52,337 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_bios.py' 2023-04-28 05:57:52,337 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_boot_image.py' 2023-04-28 05:57:52,337 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_boot_option.py' 2023-04-28 05:57:52,338 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_connect_media.py' 2023-04-28 05:57:52,338 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_dns.py' 2023-04-28 05:57:52,338 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_event_log_policy.py' 2023-04-28 05:57:52,338 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_fan.py' 2023-04-28 05:57:52,339 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_fru.py' 2023-04-28 05:57:52,339 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ipv4.py' 2023-04-28 05:57:52,339 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ipv6.py' 2023-04-28 05:57:52,339 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_kvm.py' 2023-04-28 05:57:52,340 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ldap.py' 2023-04-28 05:57:52,340 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ldap_group.py' 2023-04-28 05:57:52,340 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ldisk.py' 2023-04-28 05:57:52,340 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_log_setting.py' 2023-04-28 05:57:52,340 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_manual_capture.py' 2023-04-28 05:57:52,341 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_media_instance.py' 2023-04-28 05:57:52,341 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ncsi.py' 2023-04-28 05:57:52,341 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_network.py' 2023-04-28 05:57:52,341 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_network_bond.py' 2023-04-28 05:57:52,342 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_network_link.py' 2023-04-28 05:57:52,342 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_ntp.py' 2023-04-28 05:57:52,342 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_pass_user.py' 2023-04-28 05:57:52,342 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_pdisk.py' 2023-04-28 05:57:52,343 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_power_budget.py' 2023-04-28 05:57:52,343 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_power_restore.py' 2023-04-28 05:57:52,343 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_power_status.py' 2023-04-28 05:57:52,343 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_preserve_config.py' 2023-04-28 05:57:52,343 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_priv_user.py' 2023-04-28 05:57:52,344 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_psu_config.py' 2023-04-28 05:57:52,344 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_psu_peak.py' 2023-04-28 05:57:52,344 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_restore_factory_default.py' 2023-04-28 05:57:52,344 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_service.py' 2023-04-28 05:57:52,345 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_smtp.py' 2023-04-28 05:57:52,345 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_smtp_com.py' 2023-04-28 05:57:52,345 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_smtp_dest.py' 2023-04-28 05:57:52,345 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_snmp.py' 2023-04-28 05:57:52,346 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_snmp_trap.py' 2023-04-28 05:57:52,346 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_threshold.py' 2023-04-28 05:57:52,346 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_uid.py' 2023-04-28 05:57:52,346 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_user_group.py' 2023-04-28 05:57:52,347 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_virtual_media.py' 2023-04-28 05:57:52,347 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/edit_vlan.py' 2023-04-28 05:57:52,347 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/event_log_info.py' 2023-04-28 05:57:52,347 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/event_log_policy_info.py' 2023-04-28 05:57:52,347 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/fan_info.py' 2023-04-28 05:57:52,348 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/fru_info.py' 2023-04-28 05:57:52,348 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/fw_version_info.py' 2023-04-28 05:57:52,348 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/gpu_info.py' 2023-04-28 05:57:52,348 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/hard_disk_info.py' 2023-04-28 05:57:52,348 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/kvm_info.py' 2023-04-28 05:57:52,349 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ldap_group.py' 2023-04-28 05:57:52,349 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ldap_group_info.py' 2023-04-28 05:57:52,349 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ldap_info.py' 2023-04-28 05:57:52,349 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ldisk_info.py' 2023-04-28 05:57:52,350 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/log_setting_info.py' 2023-04-28 05:57:52,350 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/media_instance_info.py' 2023-04-28 05:57:52,350 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/mem_info.py' 2023-04-28 05:57:52,350 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ncsi_info.py' 2023-04-28 05:57:52,351 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/network_bond_info.py' 2023-04-28 05:57:52,351 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/network_info.py' 2023-04-28 05:57:52,351 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/network_link_info.py' 2023-04-28 05:57:52,351 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/ntp_info.py' 2023-04-28 05:57:52,351 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/onboard_disk_info.py' 2023-04-28 05:57:52,352 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/pcie_info.py' 2023-04-28 05:57:52,352 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/pdisk_info.py' 2023-04-28 05:57:52,352 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/power_budget_info.py' 2023-04-28 05:57:52,352 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/power_consumption_info.py' 2023-04-28 05:57:52,352 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/power_restore_info.py' 2023-04-28 05:57:52,353 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/power_status_info.py' 2023-04-28 05:57:52,353 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/preserve_config_info.py' 2023-04-28 05:57:52,353 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/psu_config_info.py' 2023-04-28 05:57:52,353 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/psu_info.py' 2023-04-28 05:57:52,354 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/psu_peak_info.py' 2023-04-28 05:57:52,354 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/raid_info.py' 2023-04-28 05:57:52,354 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/reset_bmc.py' 2023-04-28 05:57:52,354 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/reset_kvm.py' 2023-04-28 05:57:52,354 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/restore.py' 2023-04-28 05:57:52,355 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/self_test_info.py' 2023-04-28 05:57:52,355 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/sensor_info.py' 2023-04-28 05:57:52,355 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/server_info.py' 2023-04-28 05:57:52,355 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/service_info.py' 2023-04-28 05:57:52,356 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/session_info.py' 2023-04-28 05:57:52,356 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/smtp_info.py' 2023-04-28 05:57:52,356 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/snmp_info.py' 2023-04-28 05:57:52,356 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/snmp_trap_info.py' 2023-04-28 05:57:52,356 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/system_log_info.py' 2023-04-28 05:57:52,357 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/temp_info.py' 2023-04-28 05:57:52,357 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/threshold_info.py' 2023-04-28 05:57:52,357 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/uid_info.py' 2023-04-28 05:57:52,357 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/update_cpld.py' 2023-04-28 05:57:52,358 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/update_fw.py' 2023-04-28 05:57:52,358 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/user.py' 2023-04-28 05:57:52,358 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/user_group.py' 2023-04-28 05:57:52,358 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/user_group_info.py' 2023-04-28 05:57:52,358 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/user_info.py' 2023-04-28 05:57:52,359 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/virtual_media_info.py' 2023-04-28 05:57:52,359 wheel INFO adding 'ansible_collections/inspur/sm/plugins/modules/volt_info.py' 2023-04-28 05:57:52,359 wheel INFO adding 'ansible_collections/junipernetworks/junos/CHANGELOG.rst' 2023-04-28 05:57:52,360 wheel INFO adding 'ansible_collections/junipernetworks/junos/FILES.json' 2023-04-28 05:57:52,362 wheel INFO adding 'ansible_collections/junipernetworks/junos/LICENSE' 2023-04-28 05:57:52,362 wheel INFO adding 'ansible_collections/junipernetworks/junos/MANIFEST.json' 2023-04-28 05:57:52,362 wheel INFO adding 'ansible_collections/junipernetworks/junos/README.md' 2023-04-28 05:57:52,362 wheel INFO adding 'ansible_collections/junipernetworks/junos/bindep.txt' 2023-04-28 05:57:52,363 wheel INFO adding 'ansible_collections/junipernetworks/junos/pyproject.toml' 2023-04-28 05:57:52,363 wheel INFO adding 'ansible_collections/junipernetworks/junos/requirements.txt' 2023-04-28 05:57:52,363 wheel INFO adding 'ansible_collections/junipernetworks/junos/test-requirements.txt' 2023-04-28 05:57:52,363 wheel INFO adding 'ansible_collections/junipernetworks/junos/tox.ini' 2023-04-28 05:57:52,364 wheel INFO adding 'ansible_collections/junipernetworks/junos/changelogs/changelog.yaml' 2023-04-28 05:57:52,364 wheel INFO adding 'ansible_collections/junipernetworks/junos/changelogs/config.yaml' 2023-04-28 05:57:52,364 wheel INFO adding 'ansible_collections/junipernetworks/junos/changelogs/fragments/.keep' 2023-04-28 05:57:52,364 wheel INFO adding 'ansible_collections/junipernetworks/junos/meta/runtime.yml' 2023-04-28 05:57:52,365 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/action/__init__.py' 2023-04-28 05:57:52,365 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/action/junos.py' 2023-04-28 05:57:52,365 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/cliconf/__init__.py' 2023-04-28 05:57:52,365 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/cliconf/junos.py' 2023-04-28 05:57:52,366 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,366 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/doc_fragments/junos.py' 2023-04-28 05:57:52,366 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,366 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:52,367 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/__init__.py' 2023-04-28 05:57:52,367 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/junos.py' 2023-04-28 05:57:52,367 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/__init__.py' 2023-04-28 05:57:52,367 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/__init__.py' 2023-04-28 05:57:52,368 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:52,368 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/__init__.py' 2023-04-28 05:57:52,368 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/acls.py' 2023-04-28 05:57:52,368 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/__init__.py' 2023-04-28 05:57:52,369 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:52,369 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/__init__.py' 2023-04-28 05:57:52,370 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/bgp_global.py' 2023-04-28 05:57:52,370 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/__init__.py' 2023-04-28 05:57:52,370 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/facts.py' 2023-04-28 05:57:52,371 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/__init__.py' 2023-04-28 05:57:52,371 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/hostname.py' 2023-04-28 05:57:52,371 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/__init__.py' 2023-04-28 05:57:52,371 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/interfaces.py' 2023-04-28 05:57:52,372 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/__init__.py' 2023-04-28 05:57:52,372 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:52,372 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/__init__.py' 2023-04-28 05:57:52,372 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:52,373 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/__init__.py' 2023-04-28 05:57:52,373 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/lacp.py' 2023-04-28 05:57:52,373 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/__init__.py' 2023-04-28 05:57:52,373 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:52,374 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/__init__.py' 2023-04-28 05:57:52,374 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:52,374 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/__init__.py' 2023-04-28 05:57:52,374 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/lldp_global.py' 2023-04-28 05:57:52,375 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/__init__.py' 2023-04-28 05:57:52,375 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:52,375 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/__init__.py' 2023-04-28 05:57:52,375 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/logging_global.py' 2023-04-28 05:57:52,376 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/__init__.py' 2023-04-28 05:57:52,376 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/ntp_global.py' 2023-04-28 05:57:52,376 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/__init__.py' 2023-04-28 05:57:52,377 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:52,377 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/__init__.py' 2023-04-28 05:57:52,377 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/ospfv2.py' 2023-04-28 05:57:52,377 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/__init__.py' 2023-04-28 05:57:52,378 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/ospfv3.py' 2023-04-28 05:57:52,378 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/__init__.py' 2023-04-28 05:57:52,378 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/prefix_lists.py' 2023-04-28 05:57:52,378 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/__init__.py' 2023-04-28 05:57:52,379 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/routing_instances.py' 2023-04-28 05:57:52,379 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/__init__.py' 2023-04-28 05:57:52,379 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/routing_options.py' 2023-04-28 05:57:52,380 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/__init__.py' 2023-04-28 05:57:52,380 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/security_policies.py' 2023-04-28 05:57:52,381 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/__init__.py' 2023-04-28 05:57:52,381 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/security_policies_global.py' 2023-04-28 05:57:52,381 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/__init__.py' 2023-04-28 05:57:52,381 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/security_zones.py' 2023-04-28 05:57:52,382 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/__init__.py' 2023-04-28 05:57:52,382 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/snmp_server.py' 2023-04-28 05:57:52,382 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/__init__.py' 2023-04-28 05:57:52,382 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/static_routes.py' 2023-04-28 05:57:52,383 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/__init__.py' 2023-04-28 05:57:52,383 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/vlans.py' 2023-04-28 05:57:52,383 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/__init__.py' 2023-04-28 05:57:52,383 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/__init__.py' 2023-04-28 05:57:52,384 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:52,384 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/__init__.py' 2023-04-28 05:57:52,384 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/acls.py' 2023-04-28 05:57:52,385 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/__init__.py' 2023-04-28 05:57:52,385 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:52,385 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/__init__.py' 2023-04-28 05:57:52,386 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/bgp_global.py' 2023-04-28 05:57:52,386 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/__init__.py' 2023-04-28 05:57:52,386 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/hostname.py' 2023-04-28 05:57:52,387 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/__init__.py' 2023-04-28 05:57:52,387 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/interfaces.py' 2023-04-28 05:57:52,387 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/__init__.py' 2023-04-28 05:57:52,387 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:52,388 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/__init__.py' 2023-04-28 05:57:52,388 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:52,388 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/__init__.py' 2023-04-28 05:57:52,388 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/lacp.py' 2023-04-28 05:57:52,389 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/__init__.py' 2023-04-28 05:57:52,389 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:52,389 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/__init__.py' 2023-04-28 05:57:52,389 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:52,390 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/__init__.py' 2023-04-28 05:57:52,390 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/lldp_global.py' 2023-04-28 05:57:52,390 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/__init__.py' 2023-04-28 05:57:52,391 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:52,391 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/__init__.py' 2023-04-28 05:57:52,391 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/logging_global.py' 2023-04-28 05:57:52,391 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/__init__.py' 2023-04-28 05:57:52,392 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/ntp_global.py' 2023-04-28 05:57:52,392 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/__init__.py' 2023-04-28 05:57:52,392 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:52,393 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/__init__.py' 2023-04-28 05:57:52,393 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/ospfv2.py' 2023-04-28 05:57:52,393 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/__init__.py' 2023-04-28 05:57:52,393 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/ospfv3.py' 2023-04-28 05:57:52,394 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/__init__.py' 2023-04-28 05:57:52,394 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/prefix_lists.py' 2023-04-28 05:57:52,394 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/__init__.py' 2023-04-28 05:57:52,394 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/routing_instances.py' 2023-04-28 05:57:52,395 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/__init__.py' 2023-04-28 05:57:52,395 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/routing_options.py' 2023-04-28 05:57:52,395 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/__init__.py' 2023-04-28 05:57:52,396 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/security_policies.py' 2023-04-28 05:57:52,396 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/__init__.py' 2023-04-28 05:57:52,396 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/security_policies_global.py' 2023-04-28 05:57:52,397 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/__init__.py' 2023-04-28 05:57:52,397 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/security_zones.py' 2023-04-28 05:57:52,397 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/__init__.py' 2023-04-28 05:57:52,398 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/snmp_server.py' 2023-04-28 05:57:52,398 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/__init__.py' 2023-04-28 05:57:52,398 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/static_routes.py' 2023-04-28 05:57:52,398 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/__init__.py' 2023-04-28 05:57:52,399 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/vlans.py' 2023-04-28 05:57:52,399 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/__init__.py' 2023-04-28 05:57:52,399 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/facts.py' 2023-04-28 05:57:52,400 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/__init__.py' 2023-04-28 05:57:52,400 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/acl_interfaces.py' 2023-04-28 05:57:52,400 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/__init__.py' 2023-04-28 05:57:52,400 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/acls.py' 2023-04-28 05:57:52,401 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/__init__.py' 2023-04-28 05:57:52,401 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:52,401 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/__init__.py' 2023-04-28 05:57:52,402 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/bgp_global.py' 2023-04-28 05:57:52,402 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/__init__.py' 2023-04-28 05:57:52,402 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/hostname.py' 2023-04-28 05:57:52,403 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/__init__.py' 2023-04-28 05:57:52,403 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/interfaces.py' 2023-04-28 05:57:52,403 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/__init__.py' 2023-04-28 05:57:52,403 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/l2_interfaces.py' 2023-04-28 05:57:52,404 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/__init__.py' 2023-04-28 05:57:52,404 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:52,404 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/__init__.py' 2023-04-28 05:57:52,404 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/lacp.py' 2023-04-28 05:57:52,405 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/__init__.py' 2023-04-28 05:57:52,405 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/lacp_interfaces.py' 2023-04-28 05:57:52,405 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/__init__.py' 2023-04-28 05:57:52,405 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:52,406 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/__init__.py' 2023-04-28 05:57:52,406 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/base.py' 2023-04-28 05:57:52,406 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/__init__.py' 2023-04-28 05:57:52,406 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/lldp_global.py' 2023-04-28 05:57:52,407 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/__init__.py' 2023-04-28 05:57:52,407 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:52,407 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/__init__.py' 2023-04-28 05:57:52,407 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/logging_global.py' 2023-04-28 05:57:52,408 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/__init__.py' 2023-04-28 05:57:52,408 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/ntp_global.py' 2023-04-28 05:57:52,408 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/__init__.py' 2023-04-28 05:57:52,408 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:52,409 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/__init__.py' 2023-04-28 05:57:52,409 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/ospfv2.py' 2023-04-28 05:57:52,409 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/__init__.py' 2023-04-28 05:57:52,409 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/ospfv3.py' 2023-04-28 05:57:52,410 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/__init__.py' 2023-04-28 05:57:52,410 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/prefix_lists.py' 2023-04-28 05:57:52,410 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/__init__.py' 2023-04-28 05:57:52,410 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/routing_instances.py' 2023-04-28 05:57:52,411 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/__init__.py' 2023-04-28 05:57:52,411 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/routing_options.py' 2023-04-28 05:57:52,411 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/__init__.py' 2023-04-28 05:57:52,412 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/security_policies.py' 2023-04-28 05:57:52,412 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/__init__.py' 2023-04-28 05:57:52,412 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/security_policies_global.py' 2023-04-28 05:57:52,412 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/__init__.py' 2023-04-28 05:57:52,413 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/security_zones.py' 2023-04-28 05:57:52,413 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/__init__.py' 2023-04-28 05:57:52,413 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/snmp_server.py' 2023-04-28 05:57:52,414 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/__init__.py' 2023-04-28 05:57:52,414 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/static_routes.py' 2023-04-28 05:57:52,414 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/__init__.py' 2023-04-28 05:57:52,414 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/vlans.py' 2023-04-28 05:57:52,415 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/__init__.py' 2023-04-28 05:57:52,415 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/utils.py' 2023-04-28 05:57:52,415 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/__init__.py' 2023-04-28 05:57:52,415 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_acl_interfaces.py' 2023-04-28 05:57:52,416 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_acls.py' 2023-04-28 05:57:52,416 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_banner.py' 2023-04-28 05:57:52,416 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_bgp_address_family.py' 2023-04-28 05:57:52,417 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_bgp_global.py' 2023-04-28 05:57:52,417 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_command.py' 2023-04-28 05:57:52,418 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_config.py' 2023-04-28 05:57:52,418 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_facts.py' 2023-04-28 05:57:52,418 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_hostname.py' 2023-04-28 05:57:52,419 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_interfaces.py' 2023-04-28 05:57:52,419 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_l2_interfaces.py' 2023-04-28 05:57:52,419 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_l3_interfaces.py' 2023-04-28 05:57:52,419 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_lacp.py' 2023-04-28 05:57:52,420 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_lacp_interfaces.py' 2023-04-28 05:57:52,420 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_lag_interfaces.py' 2023-04-28 05:57:52,420 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_lldp_global.py' 2023-04-28 05:57:52,421 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_lldp_interfaces.py' 2023-04-28 05:57:52,421 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_logging.py' 2023-04-28 05:57:52,421 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_logging_global.py' 2023-04-28 05:57:52,422 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_netconf.py' 2023-04-28 05:57:52,422 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_ntp_global.py' 2023-04-28 05:57:52,423 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_ospf_interfaces.py' 2023-04-28 05:57:52,423 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_ospfv2.py' 2023-04-28 05:57:52,423 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_ospfv3.py' 2023-04-28 05:57:52,423 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_package.py' 2023-04-28 05:57:52,424 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_ping.py' 2023-04-28 05:57:52,424 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_prefix_lists.py' 2023-04-28 05:57:52,424 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_routing_instances.py' 2023-04-28 05:57:52,425 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_routing_options.py' 2023-04-28 05:57:52,425 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_rpc.py' 2023-04-28 05:57:52,425 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_scp.py' 2023-04-28 05:57:52,426 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_security_policies.py' 2023-04-28 05:57:52,426 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_security_policies_global.py' 2023-04-28 05:57:52,427 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_security_zones.py' 2023-04-28 05:57:52,427 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_snmp_server.py' 2023-04-28 05:57:52,428 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_static_routes.py' 2023-04-28 05:57:52,428 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_system.py' 2023-04-28 05:57:52,428 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_user.py' 2023-04-28 05:57:52,429 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_vlans.py' 2023-04-28 05:57:52,429 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/modules/junos_vrf.py' 2023-04-28 05:57:52,429 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/netconf/__init__.py' 2023-04-28 05:57:52,430 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/netconf/junos.py' 2023-04-28 05:57:52,430 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/terminal/__init__.py' 2023-04-28 05:57:52,430 wheel INFO adding 'ansible_collections/junipernetworks/junos/plugins/terminal/junos.py' 2023-04-28 05:57:52,430 wheel INFO adding 'ansible_collections/kubernetes/core/CHANGELOG.rst' 2023-04-28 05:57:52,431 wheel INFO adding 'ansible_collections/kubernetes/core/CONTRIBUTING.md' 2023-04-28 05:57:52,431 wheel INFO adding 'ansible_collections/kubernetes/core/FILES.json' 2023-04-28 05:57:52,432 wheel INFO adding 'ansible_collections/kubernetes/core/LICENSE' 2023-04-28 05:57:52,432 wheel INFO adding 'ansible_collections/kubernetes/core/MANIFEST.json' 2023-04-28 05:57:52,433 wheel INFO adding 'ansible_collections/kubernetes/core/Makefile' 2023-04-28 05:57:52,433 wheel INFO adding 'ansible_collections/kubernetes/core/PSF-license.txt' 2023-04-28 05:57:52,433 wheel INFO adding 'ansible_collections/kubernetes/core/README.md' 2023-04-28 05:57:52,433 wheel INFO adding 'ansible_collections/kubernetes/core/bindep.txt' 2023-04-28 05:57:52,434 wheel INFO adding 'ansible_collections/kubernetes/core/codecov.yml' 2023-04-28 05:57:52,434 wheel INFO adding 'ansible_collections/kubernetes/core/requirements.txt' 2023-04-28 05:57:52,434 wheel INFO adding 'ansible_collections/kubernetes/core/setup.cfg' 2023-04-28 05:57:52,434 wheel INFO adding 'ansible_collections/kubernetes/core/test-requirements.txt' 2023-04-28 05:57:52,434 wheel INFO adding 'ansible_collections/kubernetes/core/tox.ini' 2023-04-28 05:57:52,435 wheel INFO adding 'ansible_collections/kubernetes/core/changelogs/changelog.yaml' 2023-04-28 05:57:52,435 wheel INFO adding 'ansible_collections/kubernetes/core/changelogs/config.yaml' 2023-04-28 05:57:52,435 wheel INFO adding 'ansible_collections/kubernetes/core/meta/runtime.yml' 2023-04-28 05:57:52,436 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/helm.py' 2023-04-28 05:57:52,436 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/helm_info.py' 2023-04-28 05:57:52,436 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/helm_plugin.py' 2023-04-28 05:57:52,437 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/helm_plugin_info.py' 2023-04-28 05:57:52,437 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/helm_repository.py' 2023-04-28 05:57:52,437 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s.py' 2023-04-28 05:57:52,438 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_cluster_info.py' 2023-04-28 05:57:52,438 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_cp.py' 2023-04-28 05:57:52,438 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_drain.py' 2023-04-28 05:57:52,439 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_exec.py' 2023-04-28 05:57:52,439 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_info.py' 2023-04-28 05:57:52,439 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_log.py' 2023-04-28 05:57:52,439 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_rollback.py' 2023-04-28 05:57:52,440 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_scale.py' 2023-04-28 05:57:52,440 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/k8s_service.py' 2023-04-28 05:57:52,440 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/action/ks8_json_patch.py' 2023-04-28 05:57:52,441 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/connection/kubectl.py' 2023-04-28 05:57:52,441 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,441 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/helm_common_options.py' 2023-04-28 05:57:52,442 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_auth_options.py' 2023-04-28 05:57:52,442 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_delete_options.py' 2023-04-28 05:57:52,442 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_name_options.py' 2023-04-28 05:57:52,442 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_resource_options.py' 2023-04-28 05:57:52,442 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_scale_options.py' 2023-04-28 05:57:52,443 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_state_options.py' 2023-04-28 05:57:52,443 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/doc_fragments/k8s_wait_options.py' 2023-04-28 05:57:52,443 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/filter/k8s.py' 2023-04-28 05:57:52,443 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/filter/k8s_config_resource_name.yml' 2023-04-28 05:57:52,444 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/inventory/k8s.py' 2023-04-28 05:57:52,444 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/lookup/k8s.py' 2023-04-28 05:57:52,444 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/lookup/kustomize.py' 2023-04-28 05:57:52,445 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,445 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/_version.py' 2023-04-28 05:57:52,445 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/ansiblemodule.py' 2023-04-28 05:57:52,445 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/apply.py' 2023-04-28 05:57:52,446 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/args_common.py' 2023-04-28 05:57:52,446 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/common.py' 2023-04-28 05:57:52,447 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/copy.py' 2023-04-28 05:57:52,447 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/exceptions.py' 2023-04-28 05:57:52,447 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/hashes.py' 2023-04-28 05:57:52,447 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/helm.py' 2023-04-28 05:57:52,447 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/helm_args_common.py' 2023-04-28 05:57:52,448 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8sdynamicclient.py' 2023-04-28 05:57:52,448 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/selector.py' 2023-04-28 05:57:52,448 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/version.py' 2023-04-28 05:57:52,448 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/client/discovery.py' 2023-04-28 05:57:52,449 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/client/resource.py' 2023-04-28 05:57:52,449 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8s/client.py' 2023-04-28 05:57:52,449 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8s/core.py' 2023-04-28 05:57:52,449 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8s/exceptions.py' 2023-04-28 05:57:52,450 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8s/resource.py' 2023-04-28 05:57:52,450 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8s/runner.py' 2023-04-28 05:57:52,450 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8s/service.py' 2023-04-28 05:57:52,451 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/module_utils/k8s/waiter.py' 2023-04-28 05:57:52,451 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/__init__.py' 2023-04-28 05:57:52,451 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/helm.py' 2023-04-28 05:57:52,451 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/helm_info.py' 2023-04-28 05:57:52,452 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/helm_plugin.py' 2023-04-28 05:57:52,452 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/helm_plugin_info.py' 2023-04-28 05:57:52,452 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/helm_pull.py' 2023-04-28 05:57:52,452 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/helm_repository.py' 2023-04-28 05:57:52,453 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/helm_template.py' 2023-04-28 05:57:52,453 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s.py' 2023-04-28 05:57:52,453 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_cluster_info.py' 2023-04-28 05:57:52,454 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_cp.py' 2023-04-28 05:57:52,454 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_drain.py' 2023-04-28 05:57:52,454 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_exec.py' 2023-04-28 05:57:52,454 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_info.py' 2023-04-28 05:57:52,455 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_json_patch.py' 2023-04-28 05:57:52,455 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_log.py' 2023-04-28 05:57:52,455 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_rollback.py' 2023-04-28 05:57:52,455 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_scale.py' 2023-04-28 05:57:52,456 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_service.py' 2023-04-28 05:57:52,456 wheel INFO adding 'ansible_collections/kubernetes/core/plugins/modules/k8s_taint.py' 2023-04-28 05:57:52,456 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/CHANGELOG.rst' 2023-04-28 05:57:52,457 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/CODE_OF_CONDUCT.md' 2023-04-28 05:57:52,457 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/CONTRIBUTING.md' 2023-04-28 05:57:52,457 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/FILES.json' 2023-04-28 05:57:52,458 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/LICENSE' 2023-04-28 05:57:52,458 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/MAINTAINERS' 2023-04-28 05:57:52,458 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/MANIFEST.json' 2023-04-28 05:57:52,459 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/README.md' 2023-04-28 05:57:52,459 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/changelogs/changelog.yaml' 2023-04-28 05:57:52,459 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/changelogs/config.yaml' 2023-04-28 05:57:52,459 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/changelogs/fragments/.keep' 2023-04-28 05:57:52,460 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/meta/runtime.yml' 2023-04-28 05:57:52,460 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/attributes.py' 2023-04-28 05:57:52,460 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/sql_credentials.py' 2023-04-28 05:57:52,460 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/state.py' 2023-04-28 05:57:52,461 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/module_utils/_SqlServerUtils.psm1' 2023-04-28 05:57:52,461 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/ag_listener.ps1' 2023-04-28 05:57:52,461 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/ag_listener.py' 2023-04-28 05:57:52,461 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/ag_replica.ps1' 2023-04-28 05:57:52,462 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/ag_replica.py' 2023-04-28 05:57:52,462 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job.ps1' 2023-04-28 05:57:52,462 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job.py' 2023-04-28 05:57:52,462 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_category.ps1' 2023-04-28 05:57:52,463 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_category.py' 2023-04-28 05:57:52,463 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_schedule.ps1' 2023-04-28 05:57:52,463 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_schedule.py' 2023-04-28 05:57:52,463 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_step.ps1' 2023-04-28 05:57:52,464 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/agent_job_step.py' 2023-04-28 05:57:52,464 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/availability_group.ps1' 2023-04-28 05:57:52,464 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/availability_group.py' 2023-04-28 05:57:52,464 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/backup.ps1' 2023-04-28 05:57:52,465 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/backup.py' 2023-04-28 05:57:52,465 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/credential.ps1' 2023-04-28 05:57:52,465 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/credential.py' 2023-04-28 05:57:52,465 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/database.ps1' 2023-04-28 05:57:52,466 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/database.py' 2023-04-28 05:57:52,466 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/dba_multitool.ps1' 2023-04-28 05:57:52,466 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/dba_multitool.py' 2023-04-28 05:57:52,466 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/first_responder_kit.ps1' 2023-04-28 05:57:52,466 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/first_responder_kit.py' 2023-04-28 05:57:52,467 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/hadr.ps1' 2023-04-28 05:57:52,467 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/hadr.py' 2023-04-28 05:57:52,467 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/install_script.ps1' 2023-04-28 05:57:52,467 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/install_script.py' 2023-04-28 05:57:52,468 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/instance_info.ps1' 2023-04-28 05:57:52,468 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/instance_info.py' 2023-04-28 05:57:52,468 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/login.ps1' 2023-04-28 05:57:52,468 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/login.py' 2023-04-28 05:57:52,468 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/maintenance_solution.ps1' 2023-04-28 05:57:52,469 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/maintenance_solution.py' 2023-04-28 05:57:52,469 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/memory.ps1' 2023-04-28 05:57:52,469 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/memory.py' 2023-04-28 05:57:52,469 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/nonquery.ps1' 2023-04-28 05:57:52,469 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/nonquery.py' 2023-04-28 05:57:52,470 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/resource_governor.ps1' 2023-04-28 05:57:52,470 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/resource_governor.py' 2023-04-28 05:57:52,470 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/restore.ps1' 2023-04-28 05:57:52,470 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/restore.py' 2023-04-28 05:57:52,471 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/rg_resource_pool.ps1' 2023-04-28 05:57:52,471 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/rg_resource_pool.py' 2023-04-28 05:57:52,471 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/rg_workload_group.ps1' 2023-04-28 05:57:52,471 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/rg_workload_group.py' 2023-04-28 05:57:52,472 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/sa.ps1' 2023-04-28 05:57:52,472 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/sa.py' 2023-04-28 05:57:52,472 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/sp_configure.ps1' 2023-04-28 05:57:52,472 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/sp_configure.py' 2023-04-28 05:57:52,472 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/sp_whoisactive.ps1' 2023-04-28 05:57:52,473 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/sp_whoisactive.py' 2023-04-28 05:57:52,473 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/spn.ps1' 2023-04-28 05:57:52,473 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/spn.py' 2023-04-28 05:57:52,473 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/tcp_port.ps1' 2023-04-28 05:57:52,473 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/tcp_port.py' 2023-04-28 05:57:52,474 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/traceflag.ps1' 2023-04-28 05:57:52,474 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/traceflag.py' 2023-04-28 05:57:52,474 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/user.ps1' 2023-04-28 05:57:52,474 wheel INFO adding 'ansible_collections/lowlydba/sqlserver/plugins/modules/user.py' 2023-04-28 05:57:52,475 wheel INFO adding 'ansible_collections/mellanox/onyx/FILES.json' 2023-04-28 05:57:52,475 wheel INFO adding 'ansible_collections/mellanox/onyx/LICENSE' 2023-04-28 05:57:52,476 wheel INFO adding 'ansible_collections/mellanox/onyx/MANIFEST.json' 2023-04-28 05:57:52,476 wheel INFO adding 'ansible_collections/mellanox/onyx/README.md' 2023-04-28 05:57:52,476 wheel INFO adding 'ansible_collections/mellanox/onyx/changelogs/CHANGELOG.rst' 2023-04-28 05:57:52,476 wheel INFO adding 'ansible_collections/mellanox/onyx/changelogs/changelog.yaml' 2023-04-28 05:57:52,476 wheel INFO adding 'ansible_collections/mellanox/onyx/changelogs/config.yaml' 2023-04-28 05:57:52,477 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/action/__init__.py' 2023-04-28 05:57:52,477 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/action/onyx_config.py' 2023-04-28 05:57:52,477 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/cliconf/__init__.py' 2023-04-28 05:57:52,477 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/cliconf/onyx.py' 2023-04-28 05:57:52,478 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,478 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/doc_fragments/onyx.py' 2023-04-28 05:57:52,478 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,478 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/__init__.py' 2023-04-28 05:57:52,479 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/onyx.py' 2023-04-28 05:57:52,479 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/__init__.py' 2023-04-28 05:57:52,479 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_aaa.py' 2023-04-28 05:57:52,479 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_bfd.py' 2023-04-28 05:57:52,480 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_bgp.py' 2023-04-28 05:57:52,480 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_buffer_pool.py' 2023-04-28 05:57:52,480 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_command.py' 2023-04-28 05:57:52,481 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_config.py' 2023-04-28 05:57:52,481 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_facts.py' 2023-04-28 05:57:52,481 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp.py' 2023-04-28 05:57:52,481 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp_interface.py' 2023-04-28 05:57:52,482 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_igmp_vlan.py' 2023-04-28 05:57:52,482 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_interface.py' 2023-04-28 05:57:52,482 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_l2_interface.py' 2023-04-28 05:57:52,483 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_l3_interface.py' 2023-04-28 05:57:52,483 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_linkagg.py' 2023-04-28 05:57:52,483 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_lldp.py' 2023-04-28 05:57:52,483 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_lldp_interface.py' 2023-04-28 05:57:52,484 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_magp.py' 2023-04-28 05:57:52,484 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_mlag_ipl.py' 2023-04-28 05:57:52,484 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_mlag_vip.py' 2023-04-28 05:57:52,484 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_ntp.py' 2023-04-28 05:57:52,485 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_ntp_servers_peers.py' 2023-04-28 05:57:52,485 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_ospf.py' 2023-04-28 05:57:52,485 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_pfc_interface.py' 2023-04-28 05:57:52,485 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_protocol.py' 2023-04-28 05:57:52,486 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_ptp_global.py' 2023-04-28 05:57:52,486 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_ptp_interface.py' 2023-04-28 05:57:52,486 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_qos.py' 2023-04-28 05:57:52,486 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp.py' 2023-04-28 05:57:52,487 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp_hosts.py' 2023-04-28 05:57:52,487 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_snmp_users.py' 2023-04-28 05:57:52,487 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_syslog_files.py' 2023-04-28 05:57:52,488 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_syslog_remote.py' 2023-04-28 05:57:52,488 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_traffic_class.py' 2023-04-28 05:57:52,488 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_username.py' 2023-04-28 05:57:52,488 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_vlan.py' 2023-04-28 05:57:52,489 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_vxlan.py' 2023-04-28 05:57:52,489 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/modules/onyx_wjh.py' 2023-04-28 05:57:52,489 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/terminal/__init__.py' 2023-04-28 05:57:52,489 wheel INFO adding 'ansible_collections/mellanox/onyx/plugins/terminal/onyx.py' 2023-04-28 05:57:52,490 wheel INFO adding 'ansible_collections/microsoft/ad/CHANGELOG.rst' 2023-04-28 05:57:52,490 wheel INFO adding 'ansible_collections/microsoft/ad/CODE_OF_CONDUCT.md' 2023-04-28 05:57:52,490 wheel INFO adding 'ansible_collections/microsoft/ad/COPYING' 2023-04-28 05:57:52,491 wheel INFO adding 'ansible_collections/microsoft/ad/FILES.json' 2023-04-28 05:57:52,491 wheel INFO adding 'ansible_collections/microsoft/ad/MANIFEST.json' 2023-04-28 05:57:52,491 wheel INFO adding 'ansible_collections/microsoft/ad/README.md' 2023-04-28 05:57:52,492 wheel INFO adding 'ansible_collections/microsoft/ad/codecov.yml' 2023-04-28 05:57:52,492 wheel INFO adding 'ansible_collections/microsoft/ad/changelogs/changelog.yaml' 2023-04-28 05:57:52,492 wheel INFO adding 'ansible_collections/microsoft/ad/changelogs/config.yaml' 2023-04-28 05:57:52,492 wheel INFO adding 'ansible_collections/microsoft/ad/changelogs/fragments/.keep' 2023-04-28 05:57:52,493 wheel INFO adding 'ansible_collections/microsoft/ad/meta/runtime.yml' 2023-04-28 05:57:52,493 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/action/__init__.py' 2023-04-28 05:57:52,493 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/action/domain.py' 2023-04-28 05:57:52,493 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/action/domain_controller.py' 2023-04-28 05:57:52,493 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/action/membership.py' 2023-04-28 05:57:52,494 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/doc_fragments/ad_object.py' 2023-04-28 05:57:52,494 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/module_utils/_ADObject.psm1' 2023-04-28 05:57:52,495 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/computer.ps1' 2023-04-28 05:57:52,495 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/computer.py' 2023-04-28 05:57:52,495 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/domain.ps1' 2023-04-28 05:57:52,495 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/domain.py' 2023-04-28 05:57:52,496 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/domain_controller.ps1' 2023-04-28 05:57:52,496 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/domain_controller.py' 2023-04-28 05:57:52,496 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/group.ps1' 2023-04-28 05:57:52,496 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/group.py' 2023-04-28 05:57:52,497 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/membership.ps1' 2023-04-28 05:57:52,497 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/membership.py' 2023-04-28 05:57:52,497 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/object.ps1' 2023-04-28 05:57:52,497 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/object.py' 2023-04-28 05:57:52,498 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/object_info.ps1' 2023-04-28 05:57:52,498 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/object_info.py' 2023-04-28 05:57:52,498 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/offline_join.ps1' 2023-04-28 05:57:52,498 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/offline_join.py' 2023-04-28 05:57:52,499 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/ou.ps1' 2023-04-28 05:57:52,499 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/ou.py' 2023-04-28 05:57:52,499 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/user.ps1' 2023-04-28 05:57:52,499 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/modules/user.py' 2023-04-28 05:57:52,500 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/plugin_utils/__init__.py' 2023-04-28 05:57:52,500 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/plugin_utils/_module_with_reboot.py' 2023-04-28 05:57:52,500 wheel INFO adding 'ansible_collections/microsoft/ad/plugins/plugin_utils/_reboot.py' 2023-04-28 05:57:52,501 wheel INFO adding 'ansible_collections/netapp/aws/CHANGELOG.rst' 2023-04-28 05:57:52,501 wheel INFO adding 'ansible_collections/netapp/aws/COPYING' 2023-04-28 05:57:52,501 wheel INFO adding 'ansible_collections/netapp/aws/FILES.json' 2023-04-28 05:57:52,502 wheel INFO adding 'ansible_collections/netapp/aws/MANIFEST.json' 2023-04-28 05:57:52,502 wheel INFO adding 'ansible_collections/netapp/aws/README.md' 2023-04-28 05:57:52,502 wheel INFO adding 'ansible_collections/netapp/aws/requirements.txt' 2023-04-28 05:57:52,502 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/changelog.yaml' 2023-04-28 05:57:52,502 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/config.yaml' 2023-04-28 05:57:52,503 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/20.2.0.yaml' 2023-04-28 05:57:52,503 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/20.6.0.yaml' 2023-04-28 05:57:52,503 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/20.8.0.yaml' 2023-04-28 05:57:52,503 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/20.9.0.yaml' 2023-04-28 05:57:52,504 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/2019.10.0.yaml' 2023-04-28 05:57:52,504 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-3569.yaml' 2023-04-28 05:57:52,504 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-3644.yaml' 2023-04-28 05:57:52,505 wheel INFO adding 'ansible_collections/netapp/aws/changelogs/fragments/DEVOPS-4416.yaml' 2023-04-28 05:57:52,505 wheel INFO adding 'ansible_collections/netapp/aws/meta/runtime.yml' 2023-04-28 05:57:52,505 wheel INFO adding 'ansible_collections/netapp/aws/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,505 wheel INFO adding 'ansible_collections/netapp/aws/plugins/module_utils/netapp.py' 2023-04-28 05:57:52,506 wheel INFO adding 'ansible_collections/netapp/aws/plugins/module_utils/netapp_module.py' 2023-04-28 05:57:52,506 wheel INFO adding 'ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_active_directory.py' 2023-04-28 05:57:52,506 wheel INFO adding 'ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_filesystems.py' 2023-04-28 05:57:52,506 wheel INFO adding 'ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_pool.py' 2023-04-28 05:57:52,507 wheel INFO adding 'ansible_collections/netapp/aws/plugins/modules/aws_netapp_cvs_snapshots.py' 2023-04-28 05:57:52,507 wheel INFO adding 'ansible_collections/netapp/azure/CHANGELOG.rst' 2023-04-28 05:57:52,507 wheel INFO adding 'ansible_collections/netapp/azure/COPYING' 2023-04-28 05:57:52,508 wheel INFO adding 'ansible_collections/netapp/azure/FILES.json' 2023-04-28 05:57:52,508 wheel INFO adding 'ansible_collections/netapp/azure/HACK.md' 2023-04-28 05:57:52,508 wheel INFO adding 'ansible_collections/netapp/azure/MANIFEST.json' 2023-04-28 05:57:52,508 wheel INFO adding 'ansible_collections/netapp/azure/README.md' 2023-04-28 05:57:52,509 wheel INFO adding 'ansible_collections/netapp/azure/requirements.txt' 2023-04-28 05:57:52,509 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,509 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/changelog.yaml' 2023-04-28 05:57:52,509 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/config.yaml' 2023-04-28 05:57:52,510 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/20.2.0.yaml' 2023-04-28 05:57:52,510 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/20.4.0.yaml' 2023-04-28 05:57:52,510 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/20.5.0.yaml' 2023-04-28 05:57:52,510 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/20.6.0.yaml' 2023-04-28 05:57:52,510 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/20.7.0.yaml' 2023-04-28 05:57:52,511 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/20.8.0.yaml' 2023-04-28 05:57:52,511 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3505.yaml' 2023-04-28 05:57:52,511 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3526.yaml' 2023-04-28 05:57:52,511 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3663.yaml' 2023-04-28 05:57:52,511 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3704.yaml' 2023-04-28 05:57:52,512 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3849.yaml' 2023-04-28 05:57:52,512 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3935.yaml' 2023-04-28 05:57:52,512 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-3949.yaml' 2023-04-28 05:57:52,512 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4001.yaml' 2023-04-28 05:57:52,512 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4070.yaml' 2023-04-28 05:57:52,513 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4135.yaml' 2023-04-28 05:57:52,513 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4246.yaml' 2023-04-28 05:57:52,513 wheel INFO adding 'ansible_collections/netapp/azure/changelogs/fragments/DEVOPS-4416.yaml' 2023-04-28 05:57:52,513 wheel INFO adding 'ansible_collections/netapp/azure/meta/runtime.yml' 2023-04-28 05:57:52,514 wheel INFO adding 'ansible_collections/netapp/azure/plugins/doc_fragments/azure.py' 2023-04-28 05:57:52,514 wheel INFO adding 'ansible_collections/netapp/azure/plugins/doc_fragments/azure_tags.py' 2023-04-28 05:57:52,514 wheel INFO adding 'ansible_collections/netapp/azure/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,514 wheel INFO adding 'ansible_collections/netapp/azure/plugins/module_utils/azure_rm_netapp_common.py' 2023-04-28 05:57:52,515 wheel INFO adding 'ansible_collections/netapp/azure/plugins/module_utils/netapp_module.py' 2023-04-28 05:57:52,515 wheel INFO adding 'ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_account.py' 2023-04-28 05:57:52,515 wheel INFO adding 'ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_capacity_pool.py' 2023-04-28 05:57:52,516 wheel INFO adding 'ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_snapshot.py' 2023-04-28 05:57:52,516 wheel INFO adding 'ansible_collections/netapp/azure/plugins/modules/azure_rm_netapp_volume.py' 2023-04-28 05:57:52,516 wheel INFO adding 'ansible_collections/netapp/cloudmanager/CHANGELOG.rst' 2023-04-28 05:57:52,517 wheel INFO adding 'ansible_collections/netapp/cloudmanager/COPYING' 2023-04-28 05:57:52,517 wheel INFO adding 'ansible_collections/netapp/cloudmanager/FILES.json' 2023-04-28 05:57:52,517 wheel INFO adding 'ansible_collections/netapp/cloudmanager/MANIFEST.json' 2023-04-28 05:57:52,518 wheel INFO adding 'ansible_collections/netapp/cloudmanager/README.md' 2023-04-28 05:57:52,518 wheel INFO adding 'ansible_collections/netapp/cloudmanager/kubectl.sha256' 2023-04-28 05:57:52,518 wheel INFO adding 'ansible_collections/netapp/cloudmanager/requirements.txt' 2023-04-28 05:57:52,518 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,519 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/changelog.yaml' 2023-04-28 05:57:52,519 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/config.yaml' 2023-04-28 05:57:52,519 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3803.yaml' 2023-04-28 05:57:52,519 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3844.yaml' 2023-04-28 05:57:52,520 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3909.yaml' 2023-04-28 05:57:52,520 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3910.yaml' 2023-04-28 05:57:52,520 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3911.yaml' 2023-04-28 05:57:52,520 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3912.yaml' 2023-04-28 05:57:52,520 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3913.yaml' 2023-04-28 05:57:52,521 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3922.yaml' 2023-04-28 05:57:52,521 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3946.yaml' 2023-04-28 05:57:52,521 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3947.yaml' 2023-04-28 05:57:52,521 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3948.yaml' 2023-04-28 05:57:52,521 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3965.yaml' 2023-04-28 05:57:52,522 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3967.yaml' 2023-04-28 05:57:52,522 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3975.yaml' 2023-04-28 05:57:52,522 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3984.yaml' 2023-04-28 05:57:52,522 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3985.yaml' 2023-04-28 05:57:52,522 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-3995.yaml' 2023-04-28 05:57:52,523 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4021.yaml' 2023-04-28 05:57:52,523 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4065.yaml' 2023-04-28 05:57:52,523 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4105.yaml' 2023-04-28 05:57:52,523 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4118.yaml' 2023-04-28 05:57:52,523 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4136.yaml' 2023-04-28 05:57:52,524 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4164.yaml' 2023-04-28 05:57:52,524 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4200.yaml' 2023-04-28 05:57:52,524 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4201.yaml' 2023-04-28 05:57:52,524 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4205.yaml' 2023-04-28 05:57:52,524 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4223.yaml' 2023-04-28 05:57:52,525 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4264.yaml' 2023-04-28 05:57:52,525 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4267.yaml' 2023-04-28 05:57:52,525 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4271.yaml' 2023-04-28 05:57:52,525 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4281.yaml' 2023-04-28 05:57:52,525 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4292.yaml' 2023-04-28 05:57:52,526 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4298.yaml' 2023-04-28 05:57:52,526 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4303.yaml' 2023-04-28 05:57:52,526 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4321.yaml' 2023-04-28 05:57:52,526 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4327.yaml' 2023-04-28 05:57:52,526 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4328.yaml' 2023-04-28 05:57:52,527 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4358.yaml' 2023-04-28 05:57:52,527 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4386.yaml' 2023-04-28 05:57:52,527 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4416.yaml' 2023-04-28 05:57:52,527 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4458.yaml' 2023-04-28 05:57:52,527 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4492.yaml' 2023-04-28 05:57:52,528 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4500.yaml' 2023-04-28 05:57:52,528 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4513.yaml' 2023-04-28 05:57:52,528 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4516.yaml' 2023-04-28 05:57:52,528 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4542.yaml' 2023-04-28 05:57:52,528 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4563.yaml' 2023-04-28 05:57:52,529 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4567.yaml' 2023-04-28 05:57:52,529 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4647.yaml' 2023-04-28 05:57:52,529 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4703.yaml' 2023-04-28 05:57:52,529 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4758.yaml' 2023-04-28 05:57:52,529 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-4820.yaml' 2023-04-28 05:57:52,530 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5002.yaml' 2023-04-28 05:57:52,530 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5151.yaml' 2023-04-28 05:57:52,530 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5252.yaml' 2023-04-28 05:57:52,530 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5307.yaml' 2023-04-28 05:57:52,530 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5342.yaml' 2023-04-28 05:57:52,531 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5366.yaml' 2023-04-28 05:57:52,531 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5437.yaml' 2023-04-28 05:57:52,531 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5452.yaml' 2023-04-28 05:57:52,531 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5472.yaml' 2023-04-28 05:57:52,531 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5527.yaml' 2023-04-28 05:57:52,532 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5540.yaml' 2023-04-28 05:57:52,532 wheel INFO adding 'ansible_collections/netapp/cloudmanager/changelogs/fragments/DEVOPS-5562.yaml' 2023-04-28 05:57:52,532 wheel INFO adding 'ansible_collections/netapp/cloudmanager/execution_environments/README.md' 2023-04-28 05:57:52,532 wheel INFO adding 'ansible_collections/netapp/cloudmanager/execution_environments/requirements.txt' 2023-04-28 05:57:52,533 wheel INFO adding 'ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy/execution-environment.yml' 2023-04-28 05:57:52,533 wheel INFO adding 'ansible_collections/netapp/cloudmanager/execution_environments/from_galaxy/requirements.yml' 2023-04-28 05:57:52,533 wheel INFO adding 'ansible_collections/netapp/cloudmanager/execution_environments/from_github/execution-environment.yml' 2023-04-28 05:57:52,533 wheel INFO adding 'ansible_collections/netapp/cloudmanager/execution_environments/from_github/requirements.yml' 2023-04-28 05:57:52,533 wheel INFO adding 'ansible_collections/netapp/cloudmanager/meta/execution-environment.yml' 2023-04-28 05:57:52,534 wheel INFO adding 'ansible_collections/netapp/cloudmanager/meta/runtime.yml' 2023-04-28 05:57:52,534 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/README.md' 2023-04-28 05:57:52,534 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,534 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/module_utils/netapp.py' 2023-04-28 05:57:52,535 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/module_utils/netapp_module.py' 2023-04-28 05:57:52,535 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_aggregate.py' 2023-04-28 05:57:52,536 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_aws_fsx.py' 2023-04-28 05:57:52,536 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cifs_server.py' 2023-04-28 05:57:52,536 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_aws.py' 2023-04-28 05:57:52,537 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_azure.py' 2023-04-28 05:57:52,537 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_connector_gcp.py' 2023-04-28 05:57:52,537 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_aws.py' 2023-04-28 05:57:52,538 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_azure.py' 2023-04-28 05:57:52,538 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_cvo_gcp.py' 2023-04-28 05:57:52,539 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_info.py' 2023-04-28 05:57:52,539 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_nss_account.py' 2023-04-28 05:57:52,539 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_snapmirror.py' 2023-04-28 05:57:52,540 wheel INFO adding 'ansible_collections/netapp/cloudmanager/plugins/modules/na_cloudmanager_volume.py' 2023-04-28 05:57:52,540 wheel INFO adding 'ansible_collections/netapp/elementsw/CHANGELOG.rst' 2023-04-28 05:57:52,540 wheel INFO adding 'ansible_collections/netapp/elementsw/FILES.json' 2023-04-28 05:57:52,541 wheel INFO adding 'ansible_collections/netapp/elementsw/MANIFEST.json' 2023-04-28 05:57:52,541 wheel INFO adding 'ansible_collections/netapp/elementsw/README.md' 2023-04-28 05:57:52,541 wheel INFO adding 'ansible_collections/netapp/elementsw/requirements.txt' 2023-04-28 05:57:52,541 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/changelog.yaml' 2023-04-28 05:57:52,542 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/config.yaml' 2023-04-28 05:57:52,542 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/20.2.0.yaml' 2023-04-28 05:57:52,542 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/20.6.0.yaml' 2023-04-28 05:57:52,542 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/20.8.0.yaml' 2023-04-28 05:57:52,542 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/20.9.0.yaml' 2023-04-28 05:57:52,543 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/2019.10.0.yaml' 2023-04-28 05:57:52,543 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3117.yaml' 2023-04-28 05:57:52,543 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3174.yaml' 2023-04-28 05:57:52,543 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3188.yaml' 2023-04-28 05:57:52,543 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3196.yaml' 2023-04-28 05:57:52,544 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3235.yaml' 2023-04-28 05:57:52,544 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3310.yml' 2023-04-28 05:57:52,544 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3324.yaml' 2023-04-28 05:57:52,544 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3731.yaml' 2023-04-28 05:57:52,544 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3733.yaml' 2023-04-28 05:57:52,545 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3734.yaml' 2023-04-28 05:57:52,545 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-3800.yaml' 2023-04-28 05:57:52,545 wheel INFO adding 'ansible_collections/netapp/elementsw/changelogs/fragments/DEVOPS-4416.yaml' 2023-04-28 05:57:52,545 wheel INFO adding 'ansible_collections/netapp/elementsw/meta/runtime.yml' 2023-04-28 05:57:52,546 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,546 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/module_utils/netapp.py' 2023-04-28 05:57:52,546 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/module_utils/netapp_elementsw_module.py' 2023-04-28 05:57:52,546 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/module_utils/netapp_module.py' 2023-04-28 05:57:52,547 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_access_group.py' 2023-04-28 05:57:52,547 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_access_group_volumes.py' 2023-04-28 05:57:52,547 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_account.py' 2023-04-28 05:57:52,548 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_admin_users.py' 2023-04-28 05:57:52,548 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_backup.py' 2023-04-28 05:57:52,548 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_check_connections.py' 2023-04-28 05:57:52,548 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster.py' 2023-04-28 05:57:52,549 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_config.py' 2023-04-28 05:57:52,549 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_pair.py' 2023-04-28 05:57:52,549 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_cluster_snmp.py' 2023-04-28 05:57:52,550 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_drive.py' 2023-04-28 05:57:52,550 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_info.py' 2023-04-28 05:57:52,550 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_initiators.py' 2023-04-28 05:57:52,550 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_ldap.py' 2023-04-28 05:57:52,551 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_network_interfaces.py' 2023-04-28 05:57:52,551 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_node.py' 2023-04-28 05:57:52,551 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_qos_policy.py' 2023-04-28 05:57:52,552 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot.py' 2023-04-28 05:57:52,552 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot_restore.py' 2023-04-28 05:57:52,552 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_snapshot_schedule.py' 2023-04-28 05:57:52,552 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_vlan.py' 2023-04-28 05:57:52,553 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume.py' 2023-04-28 05:57:52,553 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume_clone.py' 2023-04-28 05:57:52,553 wheel INFO adding 'ansible_collections/netapp/elementsw/plugins/modules/na_elementsw_volume_pair.py' 2023-04-28 05:57:52,554 wheel INFO adding 'ansible_collections/netapp/ontap/CHANGELOG.rst' 2023-04-28 05:57:52,555 wheel INFO adding 'ansible_collections/netapp/ontap/COPYING' 2023-04-28 05:57:52,555 wheel INFO adding 'ansible_collections/netapp/ontap/FILES.json' 2023-04-28 05:57:52,557 wheel INFO adding 'ansible_collections/netapp/ontap/MANIFEST.json' 2023-04-28 05:57:52,557 wheel INFO adding 'ansible_collections/netapp/ontap/README.md' 2023-04-28 05:57:52,558 wheel INFO adding 'ansible_collections/netapp/ontap/requirements.txt' 2023-04-28 05:57:52,558 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/.DS_Store' 2023-04-28 05:57:52,558 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,559 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/changelog.yaml' 2023-04-28 05:57:52,560 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/config.yaml' 2023-04-28 05:57:52,561 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/0-copy_ignore_txt.yml' 2023-04-28 05:57:52,561 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/19.10.0.yaml' 2023-04-28 05:57:52,561 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/19.11.0.yaml' 2023-04-28 05:57:52,561 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.1.0.yaml' 2023-04-28 05:57:52,561 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.2.0.yaml' 2023-04-28 05:57:52,562 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.3.0.yaml' 2023-04-28 05:57:52,562 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.4.0.yaml' 2023-04-28 05:57:52,562 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.4.1.yaml' 2023-04-28 05:57:52,562 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.5.0.yaml' 2023-04-28 05:57:52,563 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.6.0.yaml' 2023-04-28 05:57:52,563 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.6.1.yaml' 2023-04-28 05:57:52,563 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.7.0.yaml' 2023-04-28 05:57:52,563 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.8.0.yaml' 2023-04-28 05:57:52,563 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/20.9.0.yaml' 2023-04-28 05:57:52,564 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1661.yaml' 2023-04-28 05:57:52,564 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1665.yaml' 2023-04-28 05:57:52,564 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-1926.yaml' 2023-04-28 05:57:52,564 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2353.yaml' 2023-04-28 05:57:52,565 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2422.yaml' 2023-04-28 05:57:52,565 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2426.yaml' 2023-04-28 05:57:52,565 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2459.yaml' 2023-04-28 05:57:52,565 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2459b.yaml' 2023-04-28 05:57:52,565 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2491.yaml' 2023-04-28 05:57:52,566 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2668.yaml' 2023-04-28 05:57:52,566 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2928.yaml' 2023-04-28 05:57:52,566 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2964.yaml' 2023-04-28 05:57:52,566 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2965.yaml' 2023-04-28 05:57:52,566 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-2972.yaml' 2023-04-28 05:57:52,567 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3113.yaml' 2023-04-28 05:57:52,567 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3137.yaml' 2023-04-28 05:57:52,567 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3139.yaml' 2023-04-28 05:57:52,567 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3148.yaml' 2023-04-28 05:57:52,567 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3149.yaml' 2023-04-28 05:57:52,568 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3167.yaml' 2023-04-28 05:57:52,568 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3175.yaml' 2023-04-28 05:57:52,568 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3178.yaml' 2023-04-28 05:57:52,568 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3181.yaml' 2023-04-28 05:57:52,568 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3194.yaml' 2023-04-28 05:57:52,569 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3230.yaml' 2023-04-28 05:57:52,569 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3241.yaml' 2023-04-28 05:57:52,569 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3242.yaml' 2023-04-28 05:57:52,569 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3251.yaml' 2023-04-28 05:57:52,569 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3262.yaml' 2023-04-28 05:57:52,570 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3304.yaml' 2023-04-28 05:57:52,570 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3310.yml' 2023-04-28 05:57:52,570 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3312.yaml' 2023-04-28 05:57:52,570 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3329.yaml' 2023-04-28 05:57:52,570 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3346.yaml' 2023-04-28 05:57:52,571 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3354.yaml' 2023-04-28 05:57:52,571 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3358.yaml' 2023-04-28 05:57:52,571 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3366.yaml' 2023-04-28 05:57:52,571 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3367.yaml' 2023-04-28 05:57:52,571 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3368.yaml' 2023-04-28 05:57:52,572 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3369.yaml' 2023-04-28 05:57:52,572 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3370.yaml' 2023-04-28 05:57:52,572 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3371.yaml' 2023-04-28 05:57:52,572 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3385.yaml' 2023-04-28 05:57:52,572 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3386.yaml' 2023-04-28 05:57:52,573 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3390.yaml' 2023-04-28 05:57:52,573 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3392.yaml' 2023-04-28 05:57:52,573 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3399.yaml' 2023-04-28 05:57:52,573 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3400.yaml' 2023-04-28 05:57:52,573 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3401.yaml' 2023-04-28 05:57:52,574 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3439.yaml' 2023-04-28 05:57:52,574 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3442.yaml' 2023-04-28 05:57:52,574 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3443.yaml' 2023-04-28 05:57:52,574 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3454.yaml' 2023-04-28 05:57:52,574 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3479.yaml' 2023-04-28 05:57:52,575 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3480.yaml' 2023-04-28 05:57:52,575 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3483.yaml' 2023-04-28 05:57:52,575 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3490.yaml' 2023-04-28 05:57:52,575 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3494.yaml' 2023-04-28 05:57:52,575 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3497.yaml' 2023-04-28 05:57:52,576 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3501.yaml' 2023-04-28 05:57:52,576 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3510.yaml' 2023-04-28 05:57:52,576 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3515.yaml' 2023-04-28 05:57:52,576 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3534.yaml' 2023-04-28 05:57:52,576 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3535.yaml' 2023-04-28 05:57:52,577 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3536.yaml' 2023-04-28 05:57:52,577 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3540.yaml' 2023-04-28 05:57:52,577 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3542.yaml' 2023-04-28 05:57:52,577 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3543.yaml' 2023-04-28 05:57:52,577 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3571.yaml' 2023-04-28 05:57:52,577 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3579.yaml' 2023-04-28 05:57:52,578 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3580.yaml' 2023-04-28 05:57:52,578 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3595.yaml' 2023-04-28 05:57:52,578 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3615.yaml' 2023-04-28 05:57:52,578 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3623.yaml' 2023-04-28 05:57:52,578 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3625.yaml' 2023-04-28 05:57:52,579 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3626.yaml' 2023-04-28 05:57:52,579 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3628.yaml' 2023-04-28 05:57:52,579 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3632.yaml' 2023-04-28 05:57:52,579 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3633.yaml' 2023-04-28 05:57:52,579 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3649.yaml' 2023-04-28 05:57:52,580 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3654.yaml' 2023-04-28 05:57:52,580 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3655.yaml' 2023-04-28 05:57:52,580 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3662.yaml' 2023-04-28 05:57:52,580 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3667.yaml' 2023-04-28 05:57:52,580 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3668.yaml' 2023-04-28 05:57:52,581 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3671.yaml' 2023-04-28 05:57:52,581 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3677.yaml' 2023-04-28 05:57:52,581 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3685.yaml' 2023-04-28 05:57:52,581 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3716.yaml' 2023-04-28 05:57:52,581 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3718.yaml' 2023-04-28 05:57:52,582 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3754.yaml' 2023-04-28 05:57:52,582 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3757.yaml' 2023-04-28 05:57:52,582 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3767.yaml' 2023-04-28 05:57:52,582 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3772.yaml' 2023-04-28 05:57:52,582 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3801.yaml' 2023-04-28 05:57:52,583 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3807.yaml' 2023-04-28 05:57:52,583 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3811.yaml' 2023-04-28 05:57:52,583 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3812.yml' 2023-04-28 05:57:52,583 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3830.yaml' 2023-04-28 05:57:52,583 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3850.yaml' 2023-04-28 05:57:52,584 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3870.yaml' 2023-04-28 05:57:52,584 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3883.yaml' 2023-04-28 05:57:52,584 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3900.yaml' 2023-04-28 05:57:52,584 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3926.yaml' 2023-04-28 05:57:52,584 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3939.yaml' 2023-04-28 05:57:52,585 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3950.yaml' 2023-04-28 05:57:52,585 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3952.yaml' 2023-04-28 05:57:52,585 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3969.yaml' 2023-04-28 05:57:52,585 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3971.yaml' 2023-04-28 05:57:52,585 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3973.yaml' 2023-04-28 05:57:52,586 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3983.yaml' 2023-04-28 05:57:52,586 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-3994.yaml' 2023-04-28 05:57:52,586 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4005.yaml' 2023-04-28 05:57:52,586 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4010.yaml' 2023-04-28 05:57:52,586 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4022.yaml' 2023-04-28 05:57:52,587 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4026.yaml' 2023-04-28 05:57:52,587 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4031.yaml' 2023-04-28 05:57:52,587 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4039.yaml' 2023-04-28 05:57:52,587 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4048.yaml' 2023-04-28 05:57:52,587 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4049.yaml' 2023-04-28 05:57:52,588 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4060.yaml' 2023-04-28 05:57:52,588 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4079.yaml' 2023-04-28 05:57:52,588 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4113.yaml' 2023-04-28 05:57:52,588 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4114.yml' 2023-04-28 05:57:52,588 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4116.yaml' 2023-04-28 05:57:52,589 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4119.yaml' 2023-04-28 05:57:52,589 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4121.yaml' 2023-04-28 05:57:52,589 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4122.yaml' 2023-04-28 05:57:52,589 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4123.yaml' 2023-04-28 05:57:52,589 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4140.yaml' 2023-04-28 05:57:52,590 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4150.yaml' 2023-04-28 05:57:52,590 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4157.yaml' 2023-04-28 05:57:52,590 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4159.yaml' 2023-04-28 05:57:52,590 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4161.yaml' 2023-04-28 05:57:52,590 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4175.yaml' 2023-04-28 05:57:52,591 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4177.yaml' 2023-04-28 05:57:52,591 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4179.yml' 2023-04-28 05:57:52,591 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4190.yaml' 2023-04-28 05:57:52,591 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4191.yaml' 2023-04-28 05:57:52,591 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4196.yaml' 2023-04-28 05:57:52,592 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4197.yaml' 2023-04-28 05:57:52,592 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4206.yaml' 2023-04-28 05:57:52,592 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4218.yaml' 2023-04-28 05:57:52,592 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4227.yaml' 2023-04-28 05:57:52,592 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4228.yaml' 2023-04-28 05:57:52,593 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4231.yaml' 2023-04-28 05:57:52,593 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4235.yaml' 2023-04-28 05:57:52,593 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4243.yaml' 2023-04-28 05:57:52,593 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4255.yaml' 2023-04-28 05:57:52,593 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4256.yaml' 2023-04-28 05:57:52,594 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4270.yaml' 2023-04-28 05:57:52,594 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4288.yaml' 2023-04-28 05:57:52,594 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4289.yaml' 2023-04-28 05:57:52,594 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4300.yaml' 2023-04-28 05:57:52,594 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4312.yml' 2023-04-28 05:57:52,595 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4319.yaml' 2023-04-28 05:57:52,595 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4320.yaml' 2023-04-28 05:57:52,595 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4325.yml' 2023-04-28 05:57:52,595 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4329.yaml' 2023-04-28 05:57:52,595 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4331.yaml' 2023-04-28 05:57:52,596 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4332.yaml' 2023-04-28 05:57:52,596 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4333.yaml' 2023-04-28 05:57:52,596 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4334.yaml' 2023-04-28 05:57:52,596 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4335.yaml' 2023-04-28 05:57:52,596 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4336.yaml' 2023-04-28 05:57:52,597 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4337.yaml' 2023-04-28 05:57:52,597 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4338.yml' 2023-04-28 05:57:52,597 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4339.yaml' 2023-04-28 05:57:52,597 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4340.yaml' 2023-04-28 05:57:52,597 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4341.yaml' 2023-04-28 05:57:52,598 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4342.yml' 2023-04-28 05:57:52,598 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4343.yaml' 2023-04-28 05:57:52,598 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4344.yaml' 2023-04-28 05:57:52,598 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4345.yaml' 2023-04-28 05:57:52,598 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4347.yaml' 2023-04-28 05:57:52,599 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4348.yaml' 2023-04-28 05:57:52,599 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4349.yaml' 2023-04-28 05:57:52,599 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4350.yaml' 2023-04-28 05:57:52,599 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4367.yaml' 2023-04-28 05:57:52,599 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4391.yaml' 2023-04-28 05:57:52,600 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4392.yaml' 2023-04-28 05:57:52,600 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4393.yaml' 2023-04-28 05:57:52,600 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4394.yaml' 2023-04-28 05:57:52,600 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4399.yaml' 2023-04-28 05:57:52,600 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4401.yaml' 2023-04-28 05:57:52,600 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4404.yaml' 2023-04-28 05:57:52,601 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4415.yaml' 2023-04-28 05:57:52,601 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4417.yaml' 2023-04-28 05:57:52,601 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4435.yml' 2023-04-28 05:57:52,601 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4439.yaml' 2023-04-28 05:57:52,601 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4449.yaml' 2023-04-28 05:57:52,602 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4457.yaml' 2023-04-28 05:57:52,602 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4459.yaml' 2023-04-28 05:57:52,602 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4460.yaml' 2023-04-28 05:57:52,602 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4465.yml' 2023-04-28 05:57:52,602 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4479.yaml' 2023-04-28 05:57:52,603 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4487.yaml' 2023-04-28 05:57:52,603 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4501.yaml' 2023-04-28 05:57:52,603 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4508.yaml' 2023-04-28 05:57:52,603 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4526.yaml' 2023-04-28 05:57:52,603 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4527.yaml' 2023-04-28 05:57:52,604 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4540.yaml' 2023-04-28 05:57:52,604 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4554.yaml' 2023-04-28 05:57:52,604 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4565.yaml' 2023-04-28 05:57:52,604 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4566.yaml' 2023-04-28 05:57:52,604 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4568.yaml' 2023-04-28 05:57:52,605 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4573.yaml' 2023-04-28 05:57:52,605 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4577.yaml' 2023-04-28 05:57:52,605 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4588.yaml' 2023-04-28 05:57:52,605 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4604.yaml' 2023-04-28 05:57:52,605 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4605.yaml' 2023-04-28 05:57:52,606 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4606.yaml' 2023-04-28 05:57:52,606 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4609.yaml' 2023-04-28 05:57:52,606 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4612.yaml' 2023-04-28 05:57:52,606 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4621.yaml' 2023-04-28 05:57:52,606 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4623.yaml' 2023-04-28 05:57:52,607 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4644.yaml' 2023-04-28 05:57:52,607 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4645.yaml' 2023-04-28 05:57:52,607 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4648.yaml' 2023-04-28 05:57:52,607 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4676.yaml' 2023-04-28 05:57:52,608 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4679.yaml' 2023-04-28 05:57:52,608 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4691.yaml' 2023-04-28 05:57:52,608 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4711.yaml' 2023-04-28 05:57:52,608 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4716.yaml' 2023-04-28 05:57:52,608 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4719.yml' 2023-04-28 05:57:52,609 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4729.yml' 2023-04-28 05:57:52,609 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4731.yaml' 2023-04-28 05:57:52,609 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4735.yaml' 2023-04-28 05:57:52,609 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4736.yaml' 2023-04-28 05:57:52,609 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4737.yaml' 2023-04-28 05:57:52,610 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4743.yaml' 2023-04-28 05:57:52,610 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4745.yaml' 2023-04-28 05:57:52,610 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4747.yaml' 2023-04-28 05:57:52,610 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4762.yaml' 2023-04-28 05:57:52,610 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4763.yaml' 2023-04-28 05:57:52,611 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4764.yaml' 2023-04-28 05:57:52,611 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4767.yaml' 2023-04-28 05:57:52,611 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4769.yaml' 2023-04-28 05:57:52,611 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4770.yaml' 2023-04-28 05:57:52,611 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4771.yaml' 2023-04-28 05:57:52,612 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4773.yaml' 2023-04-28 05:57:52,612 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4774.yaml' 2023-04-28 05:57:52,612 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4775.yaml' 2023-04-28 05:57:52,612 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4776.yaml' 2023-04-28 05:57:52,612 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4779.yaml' 2023-04-28 05:57:52,613 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4780.yaml' 2023-04-28 05:57:52,613 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4781.yaml' 2023-04-28 05:57:52,613 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4784.yaml' 2023-04-28 05:57:52,613 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4785.yaml' 2023-04-28 05:57:52,613 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4786.yaml' 2023-04-28 05:57:52,614 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4788.yaml' 2023-04-28 05:57:52,614 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4789.yaml' 2023-04-28 05:57:52,614 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4790.yaml' 2023-04-28 05:57:52,614 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4794.yaml' 2023-04-28 05:57:52,614 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4798.yaml' 2023-04-28 05:57:52,615 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4799.yaml' 2023-04-28 05:57:52,615 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4800.yaml' 2023-04-28 05:57:52,615 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4801.yaml' 2023-04-28 05:57:52,615 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4802.yaml' 2023-04-28 05:57:52,615 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4803.yaml' 2023-04-28 05:57:52,616 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4804.yaml' 2023-04-28 05:57:52,616 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4807.yaml' 2023-04-28 05:57:52,616 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4808.yaml' 2023-04-28 05:57:52,616 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4809.yaml' 2023-04-28 05:57:52,616 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4813.yaml' 2023-04-28 05:57:52,617 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4818.yaml' 2023-04-28 05:57:52,617 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4830.yaml' 2023-04-28 05:57:52,617 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4832.yml' 2023-04-28 05:57:52,617 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4834.yaml' 2023-04-28 05:57:52,617 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4857.yaml' 2023-04-28 05:57:52,618 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4862.yaml' 2023-04-28 05:57:52,618 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4863.yaml' 2023-04-28 05:57:52,618 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4864.yaml' 2023-04-28 05:57:52,618 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4872.yaml' 2023-04-28 05:57:52,618 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4879.yaml' 2023-04-28 05:57:52,619 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4882.yaml' 2023-04-28 05:57:52,619 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4898.yaml' 2023-04-28 05:57:52,619 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4975.yaml' 2023-04-28 05:57:52,619 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4981.yaml' 2023-04-28 05:57:52,619 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4984.yaml' 2023-04-28 05:57:52,620 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4985.yaml' 2023-04-28 05:57:52,620 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-4998.yaml' 2023-04-28 05:57:52,620 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5015.yml' 2023-04-28 05:57:52,620 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5016.yaml' 2023-04-28 05:57:52,620 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5017.yaml' 2023-04-28 05:57:52,621 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5019.yaml' 2023-04-28 05:57:52,621 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5026.yaml' 2023-04-28 05:57:52,621 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5034.yaml' 2023-04-28 05:57:52,621 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5047.yaml' 2023-04-28 05:57:52,621 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5062.yaml' 2023-04-28 05:57:52,622 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5063.yaml' 2023-04-28 05:57:52,622 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5065.yaml' 2023-04-28 05:57:52,622 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5068.yaml' 2023-04-28 05:57:52,622 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5079.yml' 2023-04-28 05:57:52,622 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5082.yaml' 2023-04-28 05:57:52,623 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5084.yaml' 2023-04-28 05:57:52,623 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5085.yaml' 2023-04-28 05:57:52,623 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5090.yaml' 2023-04-28 05:57:52,623 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5092.yaml' 2023-04-28 05:57:52,623 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5109.yaml' 2023-04-28 05:57:52,624 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5121.yaml' 2023-04-28 05:57:52,624 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5127.yaml' 2023-04-28 05:57:52,624 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5136.yaml' 2023-04-28 05:57:52,624 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5137.yaml' 2023-04-28 05:57:52,624 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5138.yaml' 2023-04-28 05:57:52,625 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5152.yaml' 2023-04-28 05:57:52,625 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5161.yaml' 2023-04-28 05:57:52,625 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5168.yaml' 2023-04-28 05:57:52,625 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5174.yaml' 2023-04-28 05:57:52,625 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5179.yaml' 2023-04-28 05:57:52,625 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5188.yaml' 2023-04-28 05:57:52,626 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5189.yaml' 2023-04-28 05:57:52,626 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5190.yaml' 2023-04-28 05:57:52,626 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5195.yaml' 2023-04-28 05:57:52,626 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5215.yaml' 2023-04-28 05:57:52,626 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5216.yaml' 2023-04-28 05:57:52,627 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5220.yaml' 2023-04-28 05:57:52,627 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5223.yaml' 2023-04-28 05:57:52,627 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5228.yaml' 2023-04-28 05:57:52,627 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5229.yaml' 2023-04-28 05:57:52,627 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5241.yaml' 2023-04-28 05:57:52,628 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5243.yaml' 2023-04-28 05:57:52,628 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5246.yaml' 2023-04-28 05:57:52,628 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5251.yaml' 2023-04-28 05:57:52,628 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5263.yaml' 2023-04-28 05:57:52,628 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5268.yaml' 2023-04-28 05:57:52,629 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5270.yaml' 2023-04-28 05:57:52,629 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5271.yaml' 2023-04-28 05:57:52,629 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5275.yaml' 2023-04-28 05:57:52,630 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5285.yaml' 2023-04-28 05:57:52,630 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5287.yaml' 2023-04-28 05:57:52,630 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5297.yaml' 2023-04-28 05:57:52,630 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5299.yaml' 2023-04-28 05:57:52,630 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5304.yaml' 2023-04-28 05:57:52,631 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5310.yaml' 2023-04-28 05:57:52,631 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5312.yaml' 2023-04-28 05:57:52,631 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5338.yaml' 2023-04-28 05:57:52,631 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5344.yaml' 2023-04-28 05:57:52,631 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5354.yaml' 2023-04-28 05:57:52,632 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5367.yaml' 2023-04-28 05:57:52,632 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5380.yaml' 2023-04-28 05:57:52,632 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5409.yaml' 2023-04-28 05:57:52,632 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5412.yaml' 2023-04-28 05:57:52,632 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5413.yaml' 2023-04-28 05:57:52,633 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5414.yaml' 2023-04-28 05:57:52,633 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5415.yaml' 2023-04-28 05:57:52,633 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5426.yaml' 2023-04-28 05:57:52,633 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5427.yaml' 2023-04-28 05:57:52,633 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5430.yaml' 2023-04-28 05:57:52,634 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5431.yaml' 2023-04-28 05:57:52,634 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5453.yaml' 2023-04-28 05:57:52,634 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5457.yaml' 2023-04-28 05:57:52,634 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5479.yaml' 2023-04-28 05:57:52,634 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5481.yaml' 2023-04-28 05:57:52,635 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5484.yaml' 2023-04-28 05:57:52,635 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5485.yaml' 2023-04-28 05:57:52,635 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5487.yaml' 2023-04-28 05:57:52,635 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5503.yaml' 2023-04-28 05:57:52,635 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5504.yaml' 2023-04-28 05:57:52,636 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5505.yaml' 2023-04-28 05:57:52,636 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5506.yaml' 2023-04-28 05:57:52,636 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5507.yaml' 2023-04-28 05:57:52,636 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5531.yaml' 2023-04-28 05:57:52,636 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5532.yaml' 2023-04-28 05:57:52,637 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5536.yaml' 2023-04-28 05:57:52,637 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5537.yaml' 2023-04-28 05:57:52,637 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5540.yaml' 2023-04-28 05:57:52,637 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5548.yaml' 2023-04-28 05:57:52,637 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5589.yaml' 2023-04-28 05:57:52,638 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5591.yaml' 2023-04-28 05:57:52,638 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5592.yaml' 2023-04-28 05:57:52,638 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5594.yaml' 2023-04-28 05:57:52,638 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5595.yaml' 2023-04-28 05:57:52,638 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5596.yaml' 2023-04-28 05:57:52,639 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5604.yaml' 2023-04-28 05:57:52,639 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5606.yaml' 2023-04-28 05:57:52,639 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5611.yaml' 2023-04-28 05:57:52,639 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5626.yaml' 2023-04-28 05:57:52,639 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5628.yaml' 2023-04-28 05:57:52,640 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5629.yaml' 2023-04-28 05:57:52,640 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5659.yaml' 2023-04-28 05:57:52,640 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5662.yaml' 2023-04-28 05:57:52,640 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5665.yaml' 2023-04-28 05:57:52,640 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5666.yaml' 2023-04-28 05:57:52,641 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5671.yaml' 2023-04-28 05:57:52,641 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5677.yaml' 2023-04-28 05:57:52,641 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5678.yaml' 2023-04-28 05:57:52,641 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5696.yaml' 2023-04-28 05:57:52,641 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5711.yaml' 2023-04-28 05:57:52,642 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5713.yaml' 2023-04-28 05:57:52,642 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5725.yaml' 2023-04-28 05:57:52,642 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5733.yaml' 2023-04-28 05:57:52,642 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5734.yaml' 2023-04-28 05:57:52,642 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5735.yaml' 2023-04-28 05:57:52,642 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5737.yaml' 2023-04-28 05:57:52,643 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5738.yaml' 2023-04-28 05:57:52,643 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5757.yaml' 2023-04-28 05:57:52,643 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5760.yaml' 2023-04-28 05:57:52,643 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5761.yaml' 2023-04-28 05:57:52,643 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5774.yaml' 2023-04-28 05:57:52,644 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5784.yaml' 2023-04-28 05:57:52,644 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5788.yaml' 2023-04-28 05:57:52,644 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5790.yaml' 2023-04-28 05:57:52,644 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5807.yaml' 2023-04-28 05:57:52,644 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5808.yaml' 2023-04-28 05:57:52,645 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5809.yml' 2023-04-28 05:57:52,645 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5812.yaml' 2023-04-28 05:57:52,645 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5816.yaml' 2023-04-28 05:57:52,645 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5819.yaml' 2023-04-28 05:57:52,645 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5820.yaml' 2023-04-28 05:57:52,646 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5844.yaml' 2023-04-28 05:57:52,646 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5845.yaml' 2023-04-28 05:57:52,646 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5859.yaml' 2023-04-28 05:57:52,646 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5892.yaml' 2023-04-28 05:57:52,646 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5894.yaml' 2023-04-28 05:57:52,647 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5899.yaml' 2023-04-28 05:57:52,647 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5910.yaml' 2023-04-28 05:57:52,647 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5913.yaml' 2023-04-28 05:57:52,647 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5917.yaml' 2023-04-28 05:57:52,647 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5919.yaml' 2023-04-28 05:57:52,648 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5926.yaml' 2023-04-28 05:57:52,648 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5938.yaml' 2023-04-28 05:57:52,648 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5948.yaml' 2023-04-28 05:57:52,648 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5952.yaml' 2023-04-28 05:57:52,648 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5960.yaml' 2023-04-28 05:57:52,649 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5972.yaml' 2023-04-28 05:57:52,649 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5983.yaml' 2023-04-28 05:57:52,649 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-5986.yaml' 2023-04-28 05:57:52,649 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/DEVOPS-6005.yaml' 2023-04-28 05:57:52,649 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/github-110.yaml' 2023-04-28 05:57:52,650 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/github-56.yaml' 2023-04-28 05:57:52,650 wheel INFO adding 'ansible_collections/netapp/ontap/changelogs/fragments/no-story-1.yaml' 2023-04-28 05:57:52,650 wheel INFO adding 'ansible_collections/netapp/ontap/execution_environments/README.md' 2023-04-28 05:57:52,650 wheel INFO adding 'ansible_collections/netapp/ontap/execution_environments/requirements.txt' 2023-04-28 05:57:52,651 wheel INFO adding 'ansible_collections/netapp/ontap/execution_environments/from_galaxy/execution-environment.yml' 2023-04-28 05:57:52,651 wheel INFO adding 'ansible_collections/netapp/ontap/execution_environments/from_galaxy/requirements.yml' 2023-04-28 05:57:52,651 wheel INFO adding 'ansible_collections/netapp/ontap/execution_environments/from_github/execution-environment.yml' 2023-04-28 05:57:52,651 wheel INFO adding 'ansible_collections/netapp/ontap/execution_environments/from_github/requirements.yml' 2023-04-28 05:57:52,651 wheel INFO adding 'ansible_collections/netapp/ontap/meta/execution-environment.yml' 2023-04-28 05:57:52,652 wheel INFO adding 'ansible_collections/netapp/ontap/meta/runtime.yml' 2023-04-28 05:57:52,652 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/README.md' 2023-04-28 05:57:52,652 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_install_SSL_certificate.yml' 2023-04-28 05:57:52,652 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_install_SSL_certificate_REST.yml' 2023-04-28 05:57:52,653 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware.yml' 2023-04-28 05:57:52,653 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware_with_extra_vars.yml' 2023-04-28 05:57:52,653 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/na_ontap_pb_upgrade_firmware_with_vars_file.yml' 2023-04-28 05:57:52,653 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/ontap_vars_file.yml' 2023-04-28 05:57:52,654 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/filter/test_na_filter_iso8601.yaml' 2023-04-28 05:57:52,654 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/json_query/README.md' 2023-04-28 05:57:52,654 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/json_query/na_ontap_pb_get_online_volumes.yml' 2023-04-28 05:57:52,654 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/json_query/na_ontap_pb_get_online_volumes_loop.yml' 2023-04-28 05:57:52,655 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/rest_apis/clusters.yaml' 2023-04-28 05:57:52,655 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/rest_apis/list_aggregates.yaml' 2023-04-28 05:57:52,655 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/rest_apis/volumes.yml' 2023-04-28 05:57:52,655 wheel INFO adding 'ansible_collections/netapp/ontap/playbooks/examples/support/debug_connectivity.yaml' 2023-04-28 05:57:52,656 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,656 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/filter/iso8601_duration_from_seconds.yml' 2023-04-28 05:57:52,656 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/filter/iso8601_duration_to_seconds.yml' 2023-04-28 05:57:52,656 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/filter/na_filter_iso8601.py' 2023-04-28 05:57:52,657 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/netapp.py' 2023-04-28 05:57:52,657 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/netapp_elementsw_module.py' 2023-04-28 05:57:52,657 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/netapp_ipaddress.py' 2023-04-28 05:57:52,658 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/netapp_module.py' 2023-04-28 05:57:52,658 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/rest_application.py' 2023-04-28 05:57:52,658 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/rest_generic.py' 2023-04-28 05:57:52,659 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/rest_owning_resource.py' 2023-04-28 05:57:52,659 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/rest_response_helpers.py' 2023-04-28 05:57:52,659 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/rest_user.py' 2023-04-28 05:57:52,659 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/rest_volume.py' 2023-04-28 05:57:52,659 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/rest_vserver.py' 2023-04-28 05:57:52,660 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/module_utils/zapis_svm.py' 2023-04-28 05:57:52,660 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_active_directory.py' 2023-04-28 05:57:52,661 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_aggregate.py' 2023-04-28 05:57:52,661 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_autosupport.py' 2023-04-28 05:57:52,661 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_autosupport_invoke.py' 2023-04-28 05:57:52,662 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_bgp_peer_group.py' 2023-04-28 05:57:52,662 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_broadcast_domain.py' 2023-04-28 05:57:52,662 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_broadcast_domain_ports.py' 2023-04-28 05:57:52,663 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cg_snapshot.py' 2023-04-28 05:57:52,663 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs.py' 2023-04-28 05:57:52,663 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_acl.py' 2023-04-28 05:57:52,664 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_group.py' 2023-04-28 05:57:52,664 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_group_member.py' 2023-04-28 05:57:52,664 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user.py' 2023-04-28 05:57:52,664 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user_modify.py' 2023-04-28 05:57:52,665 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_local_user_set_password.py' 2023-04-28 05:57:52,665 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cifs_server.py' 2023-04-28 05:57:52,665 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster.py' 2023-04-28 05:57:52,666 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster_ha.py' 2023-04-28 05:57:52,666 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_cluster_peer.py' 2023-04-28 05:57:52,666 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_command.py' 2023-04-28 05:57:52,667 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_debug.py' 2023-04-28 05:57:52,667 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_disk_options.py' 2023-04-28 05:57:52,667 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_disks.py' 2023-04-28 05:57:52,668 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_dns.py' 2023-04-28 05:57:52,668 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_domain_tunnel.py' 2023-04-28 05:57:52,668 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_efficiency_policy.py' 2023-04-28 05:57:52,668 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ems_destination.py' 2023-04-28 05:57:52,669 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ems_filter.py' 2023-04-28 05:57:52,669 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_export_policy.py' 2023-04-28 05:57:52,669 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_export_policy_rule.py' 2023-04-28 05:57:52,670 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fcp.py' 2023-04-28 05:57:52,670 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdsd.py' 2023-04-28 05:57:52,670 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdsp.py' 2023-04-28 05:57:52,670 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdspt.py' 2023-04-28 05:57:52,671 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fdss.py' 2023-04-28 05:57:52,671 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_directory_policy.py' 2023-04-28 05:57:52,671 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_security_permissions.py' 2023-04-28 05:57:52,672 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_file_security_permissions_acl.py' 2023-04-28 05:57:52,672 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_firewall_policy.py' 2023-04-28 05:57:52,672 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_firmware_upgrade.py' 2023-04-28 05:57:52,673 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_flexcache.py' 2023-04-28 05:57:52,673 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_event.py' 2023-04-28 05:57:52,674 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_ext_engine.py' 2023-04-28 05:57:52,674 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_policy.py' 2023-04-28 05:57:52,674 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_scope.py' 2023-04-28 05:57:52,675 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_fpolicy_status.py' 2023-04-28 05:57:52,675 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_igroup.py' 2023-04-28 05:57:52,675 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_igroup_initiator.py' 2023-04-28 05:57:52,676 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_info.py' 2023-04-28 05:57:52,676 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_interface.py' 2023-04-28 05:57:52,677 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ipspace.py' 2023-04-28 05:57:52,677 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_iscsi.py' 2023-04-28 05:57:52,677 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_iscsi_security.py' 2023-04-28 05:57:52,678 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_job_schedule.py' 2023-04-28 05:57:52,678 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_kerberos_realm.py' 2023-04-28 05:57:52,678 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ldap.py' 2023-04-28 05:57:52,679 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ldap_client.py' 2023-04-28 05:57:52,679 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_license.py' 2023-04-28 05:57:52,679 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_local_hosts.py' 2023-04-28 05:57:52,680 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_log_forward.py' 2023-04-28 05:57:52,680 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_login_messages.py' 2023-04-28 05:57:52,680 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun.py' 2023-04-28 05:57:52,681 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_copy.py' 2023-04-28 05:57:52,681 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_map.py' 2023-04-28 05:57:52,681 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_lun_map_reporting_nodes.py' 2023-04-28 05:57:52,682 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_mcc_mediator.py' 2023-04-28 05:57:52,682 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_metrocluster.py' 2023-04-28 05:57:52,682 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_metrocluster_dr_group.py' 2023-04-28 05:57:52,682 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_motd.py' 2023-04-28 05:57:52,683 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_name_mappings.py' 2023-04-28 05:57:52,683 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_name_service_switch.py' 2023-04-28 05:57:52,683 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ndmp.py' 2023-04-28 05:57:52,684 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_ifgrp.py' 2023-04-28 05:57:52,684 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_port.py' 2023-04-28 05:57:52,684 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_routes.py' 2023-04-28 05:57:52,685 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_subnet.py' 2023-04-28 05:57:52,685 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_net_vlan.py' 2023-04-28 05:57:52,685 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_nfs.py' 2023-04-28 05:57:52,686 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_node.py' 2023-04-28 05:57:52,686 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntfs_dacl.py' 2023-04-28 05:57:52,686 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntfs_sd.py' 2023-04-28 05:57:52,686 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntp.py' 2023-04-28 05:57:52,687 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ntp_key.py' 2023-04-28 05:57:52,687 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme.py' 2023-04-28 05:57:52,687 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme_namespace.py' 2023-04-28 05:57:52,688 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_nvme_subsystem.py' 2023-04-28 05:57:52,688 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_object_store.py' 2023-04-28 05:57:52,688 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_partitions.py' 2023-04-28 05:57:52,688 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ports.py' 2023-04-28 05:57:52,689 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_portset.py' 2023-04-28 05:57:52,689 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_publickey.py' 2023-04-28 05:57:52,689 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_qos_adaptive_policy_group.py' 2023-04-28 05:57:52,690 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_qos_policy_group.py' 2023-04-28 05:57:52,690 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_qtree.py' 2023-04-28 05:57:52,690 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_quota_policy.py' 2023-04-28 05:57:52,691 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_quotas.py' 2023-04-28 05:57:52,691 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_rest_cli.py' 2023-04-28 05:57:52,692 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_rest_info.py' 2023-04-28 05:57:52,692 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_restit.py' 2023-04-28 05:57:52,692 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_buckets.py' 2023-04-28 05:57:52,693 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_groups.py' 2023-04-28 05:57:52,693 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_policies.py' 2023-04-28 05:57:52,693 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_services.py' 2023-04-28 05:57:52,693 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_s3_users.py' 2023-04-28 05:57:52,694 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_certificates.py' 2023-04-28 05:57:52,694 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_config.py' 2023-04-28 05:57:52,694 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_ca_certificate.py' 2023-04-28 05:57:52,695 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_config.py' 2023-04-28 05:57:52,695 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ipsec_policy.py' 2023-04-28 05:57:52,695 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_key_manager.py' 2023-04-28 05:57:52,696 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_security_ssh.py' 2023-04-28 05:57:52,696 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_service_policy.py' 2023-04-28 05:57:52,696 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_service_processor_network.py' 2023-04-28 05:57:52,696 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_snaplock_clock.py' 2023-04-28 05:57:52,697 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapmirror.py' 2023-04-28 05:57:52,698 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapmirror_policy.py' 2023-04-28 05:57:52,698 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapshot.py' 2023-04-28 05:57:52,698 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_snapshot_policy.py' 2023-04-28 05:57:52,699 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_snmp.py' 2023-04-28 05:57:52,699 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_snmp_traphosts.py' 2023-04-28 05:57:52,699 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_software_update.py' 2023-04-28 05:57:52,700 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ssh_command.py' 2023-04-28 05:57:52,700 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_storage_auto_giveback.py' 2023-04-28 05:57:52,700 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_storage_failover.py' 2023-04-28 05:57:52,701 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_svm.py' 2023-04-28 05:57:52,701 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_svm_options.py' 2023-04-28 05:57:52,701 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_ucadapter.py' 2023-04-28 05:57:52,702 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_unix_group.py' 2023-04-28 05:57:52,702 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_unix_user.py' 2023-04-28 05:57:52,702 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_user.py' 2023-04-28 05:57:52,703 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_user_role.py' 2023-04-28 05:57:52,703 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume.py' 2023-04-28 05:57:52,704 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_autosize.py' 2023-04-28 05:57:52,704 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_clone.py' 2023-04-28 05:57:52,705 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_efficiency.py' 2023-04-28 05:57:52,705 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_volume_snaplock.py' 2023-04-28 05:57:52,705 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan.py' 2023-04-28 05:57:52,706 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_on_access_policy.py' 2023-04-28 05:57:52,706 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_on_demand_task.py' 2023-04-28 05:57:52,706 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vscan_scanner_pool.py' 2023-04-28 05:57:52,707 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_audit.py' 2023-04-28 05:57:52,707 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_cifs_security.py' 2023-04-28 05:57:52,707 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_peer.py' 2023-04-28 05:57:52,708 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_vserver_peer_permissions.py' 2023-04-28 05:57:52,708 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_wait_for_condition.py' 2023-04-28 05:57:52,708 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_wwpn_alias.py' 2023-04-28 05:57:52,708 wheel INFO adding 'ansible_collections/netapp/ontap/plugins/modules/na_ontap_zapit.py' 2023-04-28 05:57:52,709 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/LICENSE' 2023-04-28 05:57:52,709 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/README.md' 2023-04-28 05:57:52,709 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/defaults/main.yml' 2023-04-28 05:57:52,710 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/handlers/main.yml' 2023-04-28 05:57:52,710 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/meta/main.yml' 2023-04-28 05:57:52,710 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tasks/main.yml' 2023-04-28 05:57:52,711 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests/inventory' 2023-04-28 05:57:52,711 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/tests/test.yml' 2023-04-28 05:57:52,711 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_cluster_config/vars/main.yml' 2023-04-28 05:57:52,711 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/LICENSE' 2023-04-28 05:57:52,712 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/README.md' 2023-04-28 05:57:52,712 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/defaults/main.yml' 2023-04-28 05:57:52,712 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/handlers/main.yml' 2023-04-28 05:57:52,712 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/meta/main.yml' 2023-04-28 05:57:52,713 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tasks/main.yml' 2023-04-28 05:57:52,713 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests/inventory' 2023-04-28 05:57:52,713 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/tests/test.yml' 2023-04-28 05:57:52,713 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_nas_create/vars/main.yml' 2023-04-28 05:57:52,714 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/LICENSE' 2023-04-28 05:57:52,714 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/README.md' 2023-04-28 05:57:52,714 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/defaults/main.yml' 2023-04-28 05:57:52,715 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/handlers/main.yml' 2023-04-28 05:57:52,715 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/meta/main.yml' 2023-04-28 05:57:52,715 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/tasks/main.yml' 2023-04-28 05:57:52,715 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests/inventory' 2023-04-28 05:57:52,716 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/tests/test.yml' 2023-04-28 05:57:52,716 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_san_create/vars/main.yml' 2023-04-28 05:57:52,716 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/README.md' 2023-04-28 05:57:52,716 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/defaults/main.yml' 2023-04-28 05:57:52,717 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/handlers/main.yml' 2023-04-28 05:57:52,717 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/meta/main.yml' 2023-04-28 05:57:52,717 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tasks/main.yml' 2023-04-28 05:57:52,717 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests/inventory' 2023-04-28 05:57:52,717 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/tests/test.yml' 2023-04-28 05:57:52,718 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_snapmirror_create/vars/main.yml' 2023-04-28 05:57:52,718 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/LICENSE' 2023-04-28 05:57:52,718 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/README.md' 2023-04-28 05:57:52,719 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/defaults/main.yml' 2023-04-28 05:57:52,719 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/handlers/main.yml' 2023-04-28 05:57:52,719 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/meta/main.yml' 2023-04-28 05:57:52,719 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tasks/main.yml' 2023-04-28 05:57:52,720 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests/inventory' 2023-04-28 05:57:52,720 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/tests/test.yml' 2023-04-28 05:57:52,720 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_create/vars/main.yml' 2023-04-28 05:57:52,720 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/.travis.yml' 2023-04-28 05:57:52,721 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/README.md' 2023-04-28 05:57:52,721 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/defaults/main.yml' 2023-04-28 05:57:52,721 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/handlers/main.yml' 2023-04-28 05:57:52,721 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/meta/main.yml' 2023-04-28 05:57:52,722 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/assert_prereqs_and_vserver_exists.yml' 2023-04-28 05:57:52,722 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/delete_volumes.yml' 2023-04-28 05:57:52,722 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/find_and_delete_volumes.yml' 2023-04-28 05:57:52,722 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/find_and_delete_volumes_retries.yml' 2023-04-28 05:57:52,722 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_cifs_server.yml' 2023-04-28 05:57:52,723 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_igroups.yml' 2023-04-28 05:57:52,723 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_interfaces.yml' 2023-04-28 05:57:52,723 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/get_volumes.yml' 2023-04-28 05:57:52,723 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tasks/main.yml' 2023-04-28 05:57:52,724 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests/inventory' 2023-04-28 05:57:52,724 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/tests/test.yml' 2023-04-28 05:57:52,724 wheel INFO adding 'ansible_collections/netapp/ontap/roles/na_ontap_vserver_delete/vars/main.yml' 2023-04-28 05:57:52,724 wheel INFO adding 'ansible_collections/netapp/storagegrid/CHANGELOG.rst' 2023-04-28 05:57:52,725 wheel INFO adding 'ansible_collections/netapp/storagegrid/COPYING' 2023-04-28 05:57:52,725 wheel INFO adding 'ansible_collections/netapp/storagegrid/FILES.json' 2023-04-28 05:57:52,725 wheel INFO adding 'ansible_collections/netapp/storagegrid/MANIFEST.json' 2023-04-28 05:57:52,726 wheel INFO adding 'ansible_collections/netapp/storagegrid/README.md' 2023-04-28 05:57:52,726 wheel INFO adding 'ansible_collections/netapp/storagegrid/requirements.txt' 2023-04-28 05:57:52,726 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/changelog.yaml' 2023-04-28 05:57:52,726 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/config.yaml' 2023-04-28 05:57:52,727 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/20.10.0.yaml' 2023-04-28 05:57:52,727 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/20.6.1.yaml' 2023-04-28 05:57:52,727 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/20.7.0.yaml' 2023-04-28 05:57:52,727 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/21.11.0.yaml' 2023-04-28 05:57:52,727 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/21.11.1.yaml' 2023-04-28 05:57:52,728 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/21.6.0.yaml' 2023-04-28 05:57:52,728 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/21.9.0.yaml' 2023-04-28 05:57:52,728 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/DEVOPS-4416.yaml' 2023-04-28 05:57:52,728 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/github-10.yaml' 2023-04-28 05:57:52,728 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/github-66.yaml' 2023-04-28 05:57:52,729 wheel INFO adding 'ansible_collections/netapp/storagegrid/changelogs/fragments/github-8.yaml' 2023-04-28 05:57:52,729 wheel INFO adding 'ansible_collections/netapp/storagegrid/meta/runtime.yml' 2023-04-28 05:57:52,729 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,729 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/module_utils/netapp.py' 2023-04-28 05:57:52,730 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/module_utils/netapp_module.py' 2023-04-28 05:57:52,730 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_account.py' 2023-04-28 05:57:52,730 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_certificate.py' 2023-04-28 05:57:52,731 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_client_certificate.py' 2023-04-28 05:57:52,731 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_dns.py' 2023-04-28 05:57:52,731 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_gateway.py' 2023-04-28 05:57:52,732 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_group.py' 2023-04-28 05:57:52,732 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_ha_group.py' 2023-04-28 05:57:52,732 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_identity_federation.py' 2023-04-28 05:57:52,732 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_info.py' 2023-04-28 05:57:52,733 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_ntp.py' 2023-04-28 05:57:52,733 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_regions.py' 2023-04-28 05:57:52,733 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_traffic_classes.py' 2023-04-28 05:57:52,733 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_grid_user.py' 2023-04-28 05:57:52,734 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_container.py' 2023-04-28 05:57:52,734 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_group.py' 2023-04-28 05:57:52,734 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_identity_federation.py' 2023-04-28 05:57:52,735 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_info.py' 2023-04-28 05:57:52,735 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_user.py' 2023-04-28 05:57:52,735 wheel INFO adding 'ansible_collections/netapp/storagegrid/plugins/modules/na_sg_org_user_s3_key.py' 2023-04-28 05:57:52,735 wheel INFO adding 'ansible_collections/netapp/um_info/CHANGELOG.rst' 2023-04-28 05:57:52,736 wheel INFO adding 'ansible_collections/netapp/um_info/COPYING' 2023-04-28 05:57:52,736 wheel INFO adding 'ansible_collections/netapp/um_info/FILES.json' 2023-04-28 05:57:52,736 wheel INFO adding 'ansible_collections/netapp/um_info/MANIFEST.json' 2023-04-28 05:57:52,737 wheel INFO adding 'ansible_collections/netapp/um_info/README.md' 2023-04-28 05:57:52,737 wheel INFO adding 'ansible_collections/netapp/um_info/requirements.txt' 2023-04-28 05:57:52,737 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/changelog.yaml' 2023-04-28 05:57:52,737 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/config.yaml' 2023-04-28 05:57:52,738 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/fragments/20.7.0.yaml' 2023-04-28 05:57:52,738 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-2952.yaml' 2023-04-28 05:57:52,738 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-3920.yaml' 2023-04-28 05:57:52,738 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-3962.yaml' 2023-04-28 05:57:52,738 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4059.yaml' 2023-04-28 05:57:52,739 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4087.yaml' 2023-04-28 05:57:52,739 wheel INFO adding 'ansible_collections/netapp/um_info/changelogs/fragments/DEVOPS-4416.yaml' 2023-04-28 05:57:52,739 wheel INFO adding 'ansible_collections/netapp/um_info/meta/runtime.yml' 2023-04-28 05:57:52,739 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,740 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/module_utils/netapp.py' 2023-04-28 05:57:52,740 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/module_utils/netapp_module.py' 2023-04-28 05:57:52,740 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_aggregates_info.py' 2023-04-28 05:57:52,740 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_clusters_info.py' 2023-04-28 05:57:52,741 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_list_aggregates.py' 2023-04-28 05:57:52,741 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_list_clusters.py' 2023-04-28 05:57:52,741 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_list_nodes.py' 2023-04-28 05:57:52,741 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_list_svms.py' 2023-04-28 05:57:52,742 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_list_volumes.py' 2023-04-28 05:57:52,742 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_nodes_info.py' 2023-04-28 05:57:52,742 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_svms_info.py' 2023-04-28 05:57:52,742 wheel INFO adding 'ansible_collections/netapp/um_info/plugins/modules/na_um_volumes_info.py' 2023-04-28 05:57:52,743 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/CHANGELOG.rst' 2023-04-28 05:57:52,743 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/CONTRIBUTING.md' 2023-04-28 05:57:52,743 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/COPYING' 2023-04-28 05:57:52,744 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/FILES.json' 2023-04-28 05:57:52,744 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/Jenkinsfile.blackduck' 2023-04-28 05:57:52,744 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/MANIFEST.json' 2023-04-28 05:57:52,745 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/README.md' 2023-04-28 05:57:52,745 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/ansible.cfg' 2023-04-28 05:57:52,746 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/eseries-ansible-collections-diagram.png' 2023-04-28 05:57:52,746 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,747 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/changelogs/changelog.yaml' 2023-04-28 05:57:52,747 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/changelogs/config.yaml' 2023-04-28 05:57:52,747 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/meta/runtime.yml' 2023-04-28 05:57:52,747 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/netapp.py' 2023-04-28 05:57:52,748 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/santricity.py' 2023-04-28 05:57:52,748 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_host.py' 2023-04-28 05:57:52,748 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_host_detail.py' 2023-04-28 05:57:52,748 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_lun_mapping.py' 2023-04-28 05:57:52,749 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_storage_pool.py' 2023-04-28 05:57:52,749 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/lookup/santricity_volume.py' 2023-04-28 05:57:52,749 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/module_utils/netapp.py' 2023-04-28 05:57:52,750 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/module_utils/santricity.py' 2023-04-28 05:57:52,750 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_alerts.py' 2023-04-28 05:57:52,750 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_alerts_syslog.py' 2023-04-28 05:57:52,751 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_asup.py' 2023-04-28 05:57:52,751 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_auditlog.py' 2023-04-28 05:57:52,751 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_auth.py' 2023-04-28 05:57:52,751 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_client_certificate.py' 2023-04-28 05:57:52,752 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_discover.py' 2023-04-28 05:57:52,752 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_drive_firmware.py' 2023-04-28 05:57:52,753 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_facts.py' 2023-04-28 05:57:52,753 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_firmware.py' 2023-04-28 05:57:52,754 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_global.py' 2023-04-28 05:57:52,754 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_host.py' 2023-04-28 05:57:52,755 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_hostgroup.py' 2023-04-28 05:57:52,755 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_ib_iser_interface.py' 2023-04-28 05:57:52,755 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_iscsi_interface.py' 2023-04-28 05:57:52,755 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_iscsi_target.py' 2023-04-28 05:57:52,756 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_ldap.py' 2023-04-28 05:57:52,756 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_lun_mapping.py' 2023-04-28 05:57:52,756 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_mgmt_interface.py' 2023-04-28 05:57:52,757 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_nvme_interface.py' 2023-04-28 05:57:52,757 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_drive_firmware_upload.py' 2023-04-28 05:57:52,757 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_firmware_upload.py' 2023-04-28 05:57:52,758 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_proxy_systems.py' 2023-04-28 05:57:52,758 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_server_certificate.py' 2023-04-28 05:57:52,759 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_snapshot.py' 2023-04-28 05:57:52,759 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_storagepool.py' 2023-04-28 05:57:52,760 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_syslog.py' 2023-04-28 05:57:52,760 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/na_santricity_volume.py' 2023-04-28 05:57:52,761 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_alerts.py' 2023-04-28 05:57:52,761 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg.py' 2023-04-28 05:57:52,761 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg_role.py' 2023-04-28 05:57:52,761 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_amg_sync.py' 2023-04-28 05:57:52,762 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_asup.py' 2023-04-28 05:57:52,762 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_auditlog.py' 2023-04-28 05:57:52,762 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_auth.py' 2023-04-28 05:57:52,762 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_drive_firmware.py' 2023-04-28 05:57:52,763 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_facts.py' 2023-04-28 05:57:52,763 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_firmware.py' 2023-04-28 05:57:52,764 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_flashcache.py' 2023-04-28 05:57:52,764 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_global.py' 2023-04-28 05:57:52,764 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_host.py' 2023-04-28 05:57:52,764 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_hostgroup.py' 2023-04-28 05:57:52,765 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_iscsi_interface.py' 2023-04-28 05:57:52,765 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_iscsi_target.py' 2023-04-28 05:57:52,765 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_ldap.py' 2023-04-28 05:57:52,766 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_lun_mapping.py' 2023-04-28 05:57:52,766 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_mgmt_interface.py' 2023-04-28 05:57:52,766 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_group.py' 2023-04-28 05:57:52,767 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_images.py' 2023-04-28 05:57:52,767 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_snapshot_volume.py' 2023-04-28 05:57:52,767 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_storage_system.py' 2023-04-28 05:57:52,767 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_storagepool.py' 2023-04-28 05:57:52,768 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_syslog.py' 2023-04-28 05:57:52,768 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_volume.py' 2023-04-28 05:57:52,769 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/plugins/modules/netapp_e_volume_copy.py' 2023-04-28 05:57:52,769 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/.travis.yml' 2023-04-28 05:57:52,769 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/README.md' 2023-04-28 05:57:52,770 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/defaults/main.yml' 2023-04-28 05:57:52,770 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/meta/main.yml' 2023-04-28 05:57:52,770 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/build_info.yml' 2023-04-28 05:57:52,770 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/main.yml' 2023-04-28 05:57:52,771 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/proxy.yml' 2023-04-28 05:57:52,771 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/proxy_security.yml' 2023-04-28 05:57:52,771 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/discovery.yml' 2023-04-28 05:57:52,771 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/prefer_embedded.yml' 2023-04-28 05:57:52,772 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/prefer_proxy.yml' 2023-04-28 05:57:52,772 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_common/tasks/collect_facts/validate_system_api_url.yml' 2023-04-28 05:57:52,772 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/README.md' 2023-04-28 05:57:52,773 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/defaults/main.yml' 2023-04-28 05:57:52,773 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/meta/main.yml' 2023-04-28 05:57:52,773 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/initiator.yml' 2023-04-28 05:57:52,774 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface.yml' 2023-04-28 05:57:52,774 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/lun_mapping.yml' 2023-04-28 05:57:52,774 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/main.yml' 2023-04-28 05:57:52,774 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot.yml' 2023-04-28 05:57:52,775 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/storage_pool_absent.yml' 2023-04-28 05:57:52,775 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/storage_pool_present.yml' 2023-04-28 05:57:52,775 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/volume.yml' 2023-04-28 05:57:52,775 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/ib_iser.yml' 2023-04-28 05:57:52,776 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/iscsi.yml' 2023-04-28 05:57:52,776 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/nvme_ib.yml' 2023-04-28 05:57:52,776 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/interface/nvme_roce.yml' 2023-04-28 05:57:52,776 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/group.yml' 2023-04-28 05:57:52,777 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/rollback.yml' 2023-04-28 05:57:52,777 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/tasks/snapshot/view.yml' 2023-04-28 05:57:52,777 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates/hostnqn.j2' 2023-04-28 05:57:52,777 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_host/templates/initiatorname_iscsi.j2' 2023-04-28 05:57:52,777 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/.travis.yml' 2023-04-28 05:57:52,778 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/README.md' 2023-04-28 05:57:52,778 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/defaults/main.yml' 2023-04-28 05:57:52,778 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/meta/main.yml' 2023-04-28 05:57:52,779 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/firmware.yml' 2023-04-28 05:57:52,779 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/interface.yml' 2023-04-28 05:57:52,779 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/logging.yml' 2023-04-28 05:57:52,779 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/main.yml' 2023-04-28 05:57:52,780 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/security.yml' 2023-04-28 05:57:52,780 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/roles/nar_santricity_management/tasks/system.yml' 2023-04-28 05:57:52,780 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/vars/hubPreCheck.groovy' 2023-04-28 05:57:52,780 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/vars/hubScan.groovy' 2023-04-28 05:57:52,781 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/vars/hubScanDocker.groovy' 2023-04-28 05:57:52,781 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/vars/hubScanProject.groovy' 2023-04-28 05:57:52,781 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/vars/setupBlackduckBuildParameters.groovy' 2023-04-28 05:57:52,781 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/vars/setupBuildParameters.groovy' 2023-04-28 05:57:52,782 wheel INFO adding 'ansible_collections/netapp_eseries/santricity/vars/setupSynopsysDetect.groovy' 2023-04-28 05:57:52,782 wheel INFO adding 'ansible_collections/netbox/netbox/CHANGELOG.rst' 2023-04-28 05:57:52,782 wheel INFO adding 'ansible_collections/netbox/netbox/CONTRIBUTING.md' 2023-04-28 05:57:52,783 wheel INFO adding 'ansible_collections/netbox/netbox/FILES.json' 2023-04-28 05:57:52,784 wheel INFO adding 'ansible_collections/netbox/netbox/LICENSE' 2023-04-28 05:57:52,784 wheel INFO adding 'ansible_collections/netbox/netbox/MANIFEST.json' 2023-04-28 05:57:52,785 wheel INFO adding 'ansible_collections/netbox/netbox/README.md' 2023-04-28 05:57:52,785 wheel INFO adding 'ansible_collections/netbox/netbox/ansible.cfg' 2023-04-28 05:57:52,785 wheel INFO adding 'ansible_collections/netbox/netbox/poetry.lock' 2023-04-28 05:57:52,786 wheel INFO adding 'ansible_collections/netbox/netbox/pyproject.toml' 2023-04-28 05:57:52,786 wheel INFO adding 'ansible_collections/netbox/netbox/requirements.txt' 2023-04-28 05:57:52,787 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/changelog.yaml' 2023-04-28 05:57:52,787 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/config.yaml' 2023-04-28 05:57:52,787 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/fragments/.gitkeep' 2023-04-28 05:57:52,788 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/fragments/619-v3.0-ci-fixes.yml' 2023-04-28 05:57:52,788 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/fragments/allow-jinja2.yml' 2023-04-28 05:57:52,788 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/fragments/issue-558.yml' 2023-04-28 05:57:52,788 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/fragments/issue-951.yml' 2023-04-28 05:57:52,788 wheel INFO adding 'ansible_collections/netbox/netbox/changelogs/fragments/serial_and_asset.yml' 2023-04-28 05:57:52,789 wheel INFO adding 'ansible_collections/netbox/netbox/hacking/black.sh' 2023-04-28 05:57:52,789 wheel INFO adding 'ansible_collections/netbox/netbox/hacking/build.sh' 2023-04-28 05:57:52,789 wheel INFO adding 'ansible_collections/netbox/netbox/hacking/local-test.sh' 2023-04-28 05:57:52,789 wheel INFO adding 'ansible_collections/netbox/netbox/hacking/make-docs.sh' 2023-04-28 05:57:52,789 wheel INFO adding 'ansible_collections/netbox/netbox/hacking/update_test_inventories.sh' 2023-04-28 05:57:52,790 wheel INFO adding 'ansible_collections/netbox/netbox/meta/execution-environment.yml' 2023-04-28 05:57:52,790 wheel INFO adding 'ansible_collections/netbox/netbox/meta/runtime.yml' 2023-04-28 05:57:52,790 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/doc_fragments/common.py' 2023-04-28 05:57:52,791 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/inventory/nb_inventory.py' 2023-04-28 05:57:52,791 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/lookup/nb_lookup.py' 2023-04-28 05:57:52,792 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,792 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_circuits.py' 2023-04-28 05:57:52,792 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_dcim.py' 2023-04-28 05:57:52,792 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_extras.py' 2023-04-28 05:57:52,793 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_ipam.py' 2023-04-28 05:57:52,793 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_secrets.py' 2023-04-28 05:57:52,793 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_tenancy.py' 2023-04-28 05:57:52,793 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_utils.py' 2023-04-28 05:57:52,794 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_virtualization.py' 2023-04-28 05:57:52,794 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/module_utils/netbox_wireless.py' 2023-04-28 05:57:52,795 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/__init__.py' 2023-04-28 05:57:52,795 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_aggregate.py' 2023-04-28 05:57:52,795 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_asn.py' 2023-04-28 05:57:52,795 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_cable.py' 2023-04-28 05:57:52,795 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_circuit.py' 2023-04-28 05:57:52,796 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_circuit_termination.py' 2023-04-28 05:57:52,796 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_circuit_type.py' 2023-04-28 05:57:52,796 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_cluster.py' 2023-04-28 05:57:52,796 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_cluster_group.py' 2023-04-28 05:57:52,797 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_cluster_type.py' 2023-04-28 05:57:52,797 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_config_context.py' 2023-04-28 05:57:52,797 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_console_port.py' 2023-04-28 05:57:52,797 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_console_port_template.py' 2023-04-28 05:57:52,798 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_console_server_port.py' 2023-04-28 05:57:52,798 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_console_server_port_template.py' 2023-04-28 05:57:52,798 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_contact.py' 2023-04-28 05:57:52,798 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_contact_group.py' 2023-04-28 05:57:52,799 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_contact_role.py' 2023-04-28 05:57:52,799 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_custom_field.py' 2023-04-28 05:57:52,799 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_custom_link.py' 2023-04-28 05:57:52,799 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_device.py' 2023-04-28 05:57:52,800 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_device_bay.py' 2023-04-28 05:57:52,800 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_device_bay_template.py' 2023-04-28 05:57:52,800 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_device_interface.py' 2023-04-28 05:57:52,800 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_device_interface_template.py' 2023-04-28 05:57:52,801 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_device_role.py' 2023-04-28 05:57:52,801 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_device_type.py' 2023-04-28 05:57:52,801 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_export_template.py' 2023-04-28 05:57:52,801 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_fhrp_group.py' 2023-04-28 05:57:52,802 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_front_port.py' 2023-04-28 05:57:52,802 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_front_port_template.py' 2023-04-28 05:57:52,802 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_inventory_item.py' 2023-04-28 05:57:52,802 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_inventory_item_role.py' 2023-04-28 05:57:52,803 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_ip_address.py' 2023-04-28 05:57:52,803 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_ipam_role.py' 2023-04-28 05:57:52,803 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_journal_entry.py' 2023-04-28 05:57:52,803 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_l2vpn.py' 2023-04-28 05:57:52,804 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_location.py' 2023-04-28 05:57:52,804 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_manufacturer.py' 2023-04-28 05:57:52,804 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_module_type.py' 2023-04-28 05:57:52,804 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_platform.py' 2023-04-28 05:57:52,804 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_power_feed.py' 2023-04-28 05:57:52,805 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_power_outlet.py' 2023-04-28 05:57:52,805 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_power_outlet_template.py' 2023-04-28 05:57:52,805 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_power_panel.py' 2023-04-28 05:57:52,805 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_power_port.py' 2023-04-28 05:57:52,806 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_power_port_template.py' 2023-04-28 05:57:52,806 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_prefix.py' 2023-04-28 05:57:52,806 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_provider.py' 2023-04-28 05:57:52,806 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_provider_network.py' 2023-04-28 05:57:52,807 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_rack.py' 2023-04-28 05:57:52,807 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_rack_group.py' 2023-04-28 05:57:52,807 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_rack_role.py' 2023-04-28 05:57:52,807 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_rear_port.py' 2023-04-28 05:57:52,808 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_rear_port_template.py' 2023-04-28 05:57:52,808 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_region.py' 2023-04-28 05:57:52,808 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_rir.py' 2023-04-28 05:57:52,808 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_route_target.py' 2023-04-28 05:57:52,809 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_service.py' 2023-04-28 05:57:52,809 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_service_template.py' 2023-04-28 05:57:52,809 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_site.py' 2023-04-28 05:57:52,809 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_site_group.py' 2023-04-28 05:57:52,810 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_tag.py' 2023-04-28 05:57:52,810 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_tenant.py' 2023-04-28 05:57:52,810 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_tenant_group.py' 2023-04-28 05:57:52,810 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_virtual_chassis.py' 2023-04-28 05:57:52,811 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_virtual_machine.py' 2023-04-28 05:57:52,811 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_vlan.py' 2023-04-28 05:57:52,811 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_vlan_group.py' 2023-04-28 05:57:52,811 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_vm_interface.py' 2023-04-28 05:57:52,812 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_vrf.py' 2023-04-28 05:57:52,812 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_webhook.py' 2023-04-28 05:57:52,812 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_lan.py' 2023-04-28 05:57:52,812 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_lan_group.py' 2023-04-28 05:57:52,813 wheel INFO adding 'ansible_collections/netbox/netbox/plugins/modules/netbox_wireless_link.py' 2023-04-28 05:57:52,813 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/CHANGELOG.rst' 2023-04-28 05:57:52,813 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/CONTRIBUTING.md' 2023-04-28 05:57:52,813 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/COPYING' 2023-04-28 05:57:52,814 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/FILES.json' 2023-04-28 05:57:52,815 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/MANIFEST.json' 2023-04-28 05:57:52,815 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/README.md' 2023-04-28 05:57:52,815 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/codecov.yml' 2023-04-28 05:57:52,815 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/requirements.txt' 2023-04-28 05:57:52,815 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/changelogs/.gitignore' 2023-04-28 05:57:52,816 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/changelogs/changelog.yaml' 2023-04-28 05:57:52,816 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/changelogs/config.yaml' 2023-04-28 05:57:52,816 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/changelogs/fragments/.keep' 2023-04-28 05:57:52,816 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/meta/runtime.yml' 2023-04-28 05:57:52,817 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,817 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/cloudstack.py' 2023-04-28 05:57:52,817 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/cloudstack_environment.py' 2023-04-28 05:57:52,817 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/inventory/__init__.py' 2023-04-28 05:57:52,818 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/inventory/instance.py' 2023-04-28 05:57:52,818 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/module_utils/cloudstack.py' 2023-04-28 05:57:52,818 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/__init__.py' 2023-04-28 05:57:52,819 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_account.py' 2023-04-28 05:57:52,819 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_affinitygroup.py' 2023-04-28 05:57:52,819 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_cluster.py' 2023-04-28 05:57:52,819 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_configuration.py' 2023-04-28 05:57:52,820 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_disk_offering.py' 2023-04-28 05:57:52,820 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_domain.py' 2023-04-28 05:57:52,820 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_facts.py' 2023-04-28 05:57:52,820 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_firewall.py' 2023-04-28 05:57:52,821 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_host.py' 2023-04-28 05:57:52,821 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_image_store.py' 2023-04-28 05:57:52,821 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance.py' 2023-04-28 05:57:52,822 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_info.py' 2023-04-28 05:57:52,822 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_nic.py' 2023-04-28 05:57:52,822 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_nic_secondaryip.py' 2023-04-28 05:57:52,823 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instance_password_reset.py' 2023-04-28 05:57:52,823 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_instancegroup.py' 2023-04-28 05:57:52,823 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_ip_address.py' 2023-04-28 05:57:52,823 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_iso.py' 2023-04-28 05:57:52,824 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_loadbalancer_rule.py' 2023-04-28 05:57:52,824 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_loadbalancer_rule_member.py' 2023-04-28 05:57:52,824 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network.py' 2023-04-28 05:57:52,824 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_acl.py' 2023-04-28 05:57:52,825 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_acl_rule.py' 2023-04-28 05:57:52,825 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_network_offering.py' 2023-04-28 05:57:52,825 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_physical_network.py' 2023-04-28 05:57:52,826 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_pod.py' 2023-04-28 05:57:52,826 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_portforward.py' 2023-04-28 05:57:52,826 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_project.py' 2023-04-28 05:57:52,826 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_region.py' 2023-04-28 05:57:52,827 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_resourcelimit.py' 2023-04-28 05:57:52,827 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_role.py' 2023-04-28 05:57:52,827 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_role_permission.py' 2023-04-28 05:57:52,827 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_router.py' 2023-04-28 05:57:52,828 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_securitygroup.py' 2023-04-28 05:57:52,828 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_securitygroup_rule.py' 2023-04-28 05:57:52,828 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_service_offering.py' 2023-04-28 05:57:52,829 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_snapshot_policy.py' 2023-04-28 05:57:52,829 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_sshkeypair.py' 2023-04-28 05:57:52,829 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_staticnat.py' 2023-04-28 05:57:52,829 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_storage_pool.py' 2023-04-28 05:57:52,830 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_template.py' 2023-04-28 05:57:52,830 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_traffic_type.py' 2023-04-28 05:57:52,830 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_user.py' 2023-04-28 05:57:52,831 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vlan_ip_range.py' 2023-04-28 05:57:52,831 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vmsnapshot.py' 2023-04-28 05:57:52,831 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_volume.py' 2023-04-28 05:57:52,831 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpc.py' 2023-04-28 05:57:52,832 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpc_offering.py' 2023-04-28 05:57:52,832 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_connection.py' 2023-04-28 05:57:52,832 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_customer_gateway.py' 2023-04-28 05:57:52,832 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_vpn_gateway.py' 2023-04-28 05:57:52,833 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_zone.py' 2023-04-28 05:57:52,833 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/plugins/modules/cs_zone_info.py' 2023-04-28 05:57:52,833 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/scripts/inventory/cloudstack.ini' 2023-04-28 05:57:52,834 wheel INFO adding 'ansible_collections/ngine_io/cloudstack/scripts/inventory/cloudstack.py' 2023-04-28 05:57:52,834 wheel INFO adding 'ansible_collections/ngine_io/exoscale/CHANGELOG.rst' 2023-04-28 05:57:52,834 wheel INFO adding 'ansible_collections/ngine_io/exoscale/CONTRIBUTING.md' 2023-04-28 05:57:52,834 wheel INFO adding 'ansible_collections/ngine_io/exoscale/FILES.json' 2023-04-28 05:57:52,834 wheel INFO adding 'ansible_collections/ngine_io/exoscale/MANIFEST.json' 2023-04-28 05:57:52,835 wheel INFO adding 'ansible_collections/ngine_io/exoscale/README.md' 2023-04-28 05:57:52,835 wheel INFO adding 'ansible_collections/ngine_io/exoscale/changelogs/.gitignore' 2023-04-28 05:57:52,835 wheel INFO adding 'ansible_collections/ngine_io/exoscale/changelogs/changelog.yaml' 2023-04-28 05:57:52,835 wheel INFO adding 'ansible_collections/ngine_io/exoscale/changelogs/config.yaml' 2023-04-28 05:57:52,836 wheel INFO adding 'ansible_collections/ngine_io/exoscale/changelogs/fragments/.keep' 2023-04-28 05:57:52,836 wheel INFO adding 'ansible_collections/ngine_io/exoscale/meta/runtime.yml' 2023-04-28 05:57:52,836 wheel INFO adding 'ansible_collections/ngine_io/exoscale/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,836 wheel INFO adding 'ansible_collections/ngine_io/exoscale/plugins/doc_fragments/exoscale.py' 2023-04-28 05:57:52,837 wheel INFO adding 'ansible_collections/ngine_io/exoscale/plugins/module_utils/exoscale.py' 2023-04-28 05:57:52,837 wheel INFO adding 'ansible_collections/ngine_io/exoscale/plugins/modules/__init__.py' 2023-04-28 05:57:52,837 wheel INFO adding 'ansible_collections/ngine_io/exoscale/plugins/modules/exo_dns_domain.py' 2023-04-28 05:57:52,837 wheel INFO adding 'ansible_collections/ngine_io/exoscale/plugins/modules/exo_dns_record.py' 2023-04-28 05:57:52,838 wheel INFO adding 'ansible_collections/ngine_io/vultr/CHANGELOG.rst' 2023-04-28 05:57:52,838 wheel INFO adding 'ansible_collections/ngine_io/vultr/CONTRIBUTING.md' 2023-04-28 05:57:52,838 wheel INFO adding 'ansible_collections/ngine_io/vultr/COPYING' 2023-04-28 05:57:52,839 wheel INFO adding 'ansible_collections/ngine_io/vultr/FILES.json' 2023-04-28 05:57:52,839 wheel INFO adding 'ansible_collections/ngine_io/vultr/MANIFEST.json' 2023-04-28 05:57:52,839 wheel INFO adding 'ansible_collections/ngine_io/vultr/README.md' 2023-04-28 05:57:52,839 wheel INFO adding 'ansible_collections/ngine_io/vultr/codecov.yml' 2023-04-28 05:57:52,840 wheel INFO adding 'ansible_collections/ngine_io/vultr/changelogs/.gitignore' 2023-04-28 05:57:52,840 wheel INFO adding 'ansible_collections/ngine_io/vultr/changelogs/changelog.yaml' 2023-04-28 05:57:52,840 wheel INFO adding 'ansible_collections/ngine_io/vultr/changelogs/config.yaml' 2023-04-28 05:57:52,840 wheel INFO adding 'ansible_collections/ngine_io/vultr/changelogs/fragments/.keep' 2023-04-28 05:57:52,841 wheel INFO adding 'ansible_collections/ngine_io/vultr/meta/runtime.yml' 2023-04-28 05:57:52,841 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,841 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/doc_fragments/vultr.py' 2023-04-28 05:57:52,841 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/inventory/__init__.py' 2023-04-28 05:57:52,842 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/inventory/vultr.py' 2023-04-28 05:57:52,842 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/module_utils/vultr.py' 2023-04-28 05:57:52,842 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/__init__.py' 2023-04-28 05:57:52,842 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_account_info.py' 2023-04-28 05:57:52,843 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_block_storage.py' 2023-04-28 05:57:52,843 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_block_storage_info.py' 2023-04-28 05:57:52,843 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_domain.py' 2023-04-28 05:57:52,843 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_domain_info.py' 2023-04-28 05:57:52,844 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_dns_record.py' 2023-04-28 05:57:52,844 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_group.py' 2023-04-28 05:57:52,844 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_group_info.py' 2023-04-28 05:57:52,844 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_firewall_rule.py' 2023-04-28 05:57:52,845 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_network.py' 2023-04-28 05:57:52,845 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_network_info.py' 2023-04-28 05:57:52,845 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_os_info.py' 2023-04-28 05:57:52,845 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_plan_baremetal_info.py' 2023-04-28 05:57:52,846 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_plan_info.py' 2023-04-28 05:57:52,846 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_region_info.py' 2023-04-28 05:57:52,846 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_server.py' 2023-04-28 05:57:52,847 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_server_baremetal.py' 2023-04-28 05:57:52,847 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_server_info.py' 2023-04-28 05:57:52,847 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_ssh_key.py' 2023-04-28 05:57:52,847 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_ssh_key_info.py' 2023-04-28 05:57:52,848 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_startup_script.py' 2023-04-28 05:57:52,848 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_startup_script_info.py' 2023-04-28 05:57:52,848 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_user.py' 2023-04-28 05:57:52,848 wheel INFO adding 'ansible_collections/ngine_io/vultr/plugins/modules/vultr_user_info.py' 2023-04-28 05:57:52,849 wheel INFO adding 'ansible_collections/openstack/cloud/CHANGELOG.rst' 2023-04-28 05:57:52,849 wheel INFO adding 'ansible_collections/openstack/cloud/CONTRIBUTING.rst' 2023-04-28 05:57:52,849 wheel INFO adding 'ansible_collections/openstack/cloud/COPYING' 2023-04-28 05:57:52,850 wheel INFO adding 'ansible_collections/openstack/cloud/FILES.json' 2023-04-28 05:57:52,850 wheel INFO adding 'ansible_collections/openstack/cloud/MANIFEST.json' 2023-04-28 05:57:52,850 wheel INFO adding 'ansible_collections/openstack/cloud/README.md' 2023-04-28 05:57:52,851 wheel INFO adding 'ansible_collections/openstack/cloud/bindep.txt' 2023-04-28 05:57:52,851 wheel INFO adding 'ansible_collections/openstack/cloud/requirements.txt' 2023-04-28 05:57:52,851 wheel INFO adding 'ansible_collections/openstack/cloud/setup.py' 2023-04-28 05:57:52,851 wheel INFO adding 'ansible_collections/openstack/cloud/meta/runtime.yml' 2023-04-28 05:57:52,852 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:52,852 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/doc_fragments/openstack.py' 2023-04-28 05:57:52,852 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/inventory/__init__.py' 2023-04-28 05:57:52,852 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/inventory/openstack.py' 2023-04-28 05:57:52,853 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,853 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/module_utils/ironic.py' 2023-04-28 05:57:52,853 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/module_utils/openstack.py' 2023-04-28 05:57:52,854 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/__init__.py' 2023-04-28 05:57:52,854 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/address_scope.py' 2023-04-28 05:57:52,854 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/auth.py' 2023-04-28 05:57:52,854 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/baremetal_inspect.py' 2023-04-28 05:57:52,855 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/baremetal_node.py' 2023-04-28 05:57:52,855 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/baremetal_node_action.py' 2023-04-28 05:57:52,855 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/baremetal_node_info.py' 2023-04-28 05:57:52,856 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/baremetal_port.py' 2023-04-28 05:57:52,856 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/baremetal_port_info.py' 2023-04-28 05:57:52,856 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/catalog_service.py' 2023-04-28 05:57:52,856 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/coe_cluster.py' 2023-04-28 05:57:52,857 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/coe_cluster_template.py' 2023-04-28 05:57:52,857 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/compute_flavor.py' 2023-04-28 05:57:52,857 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/compute_flavor_info.py' 2023-04-28 05:57:52,857 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/compute_service_info.py' 2023-04-28 05:57:52,858 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/config.py' 2023-04-28 05:57:52,858 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/container.py' 2023-04-28 05:57:52,858 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/dns_zone.py' 2023-04-28 05:57:52,858 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/dns_zone_info.py' 2023-04-28 05:57:52,859 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/endpoint.py' 2023-04-28 05:57:52,859 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/federation_idp.py' 2023-04-28 05:57:52,859 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/federation_idp_info.py' 2023-04-28 05:57:52,859 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/federation_mapping.py' 2023-04-28 05:57:52,860 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/federation_mapping_info.py' 2023-04-28 05:57:52,860 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/floating_ip.py' 2023-04-28 05:57:52,860 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/floating_ip_info.py' 2023-04-28 05:57:52,860 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/group_assignment.py' 2023-04-28 05:57:52,861 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/host_aggregate.py' 2023-04-28 05:57:52,861 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_domain.py' 2023-04-28 05:57:52,861 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_domain_info.py' 2023-04-28 05:57:52,861 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_group.py' 2023-04-28 05:57:52,862 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_group_info.py' 2023-04-28 05:57:52,862 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_role.py' 2023-04-28 05:57:52,862 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_role_info.py' 2023-04-28 05:57:52,862 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_user.py' 2023-04-28 05:57:52,862 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/identity_user_info.py' 2023-04-28 05:57:52,863 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/image.py' 2023-04-28 05:57:52,863 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/image_info.py' 2023-04-28 05:57:52,863 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/keypair.py' 2023-04-28 05:57:52,864 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/keypair_info.py' 2023-04-28 05:57:52,864 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/keystone_federation_protocol.py' 2023-04-28 05:57:52,864 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/keystone_federation_protocol_info.py' 2023-04-28 05:57:52,864 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/lb_health_monitor.py' 2023-04-28 05:57:52,865 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/lb_listener.py' 2023-04-28 05:57:52,865 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/lb_member.py' 2023-04-28 05:57:52,865 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/lb_pool.py' 2023-04-28 05:57:52,865 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/loadbalancer.py' 2023-04-28 05:57:52,866 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/network.py' 2023-04-28 05:57:52,866 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/networks_info.py' 2023-04-28 05:57:52,866 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/neutron_rbac_policies_info.py' 2023-04-28 05:57:52,866 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/neutron_rbac_policy.py' 2023-04-28 05:57:52,867 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/object.py' 2023-04-28 05:57:52,867 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/object_container.py' 2023-04-28 05:57:52,867 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_auth.py' 2023-04-28 05:57:52,867 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_client_config.py' 2023-04-28 05:57:52,868 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_coe_cluster.py' 2023-04-28 05:57:52,868 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_coe_cluster_template.py' 2023-04-28 05:57:52,868 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_flavor_info.py' 2023-04-28 05:57:52,868 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_floating_ip.py' 2023-04-28 05:57:52,869 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_group.py' 2023-04-28 05:57:52,869 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_group_info.py' 2023-04-28 05:57:52,869 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_image.py' 2023-04-28 05:57:52,869 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_image_info.py' 2023-04-28 05:57:52,870 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_ironic.py' 2023-04-28 05:57:52,870 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_ironic_inspect.py' 2023-04-28 05:57:52,870 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_ironic_node.py' 2023-04-28 05:57:52,871 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keypair.py' 2023-04-28 05:57:52,871 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_domain.py' 2023-04-28 05:57:52,871 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_domain_info.py' 2023-04-28 05:57:52,871 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_endpoint.py' 2023-04-28 05:57:52,872 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_federation_protocol.py' 2023-04-28 05:57:52,872 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_federation_protocol_info.py' 2023-04-28 05:57:52,872 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_identity_provider.py' 2023-04-28 05:57:52,872 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_identity_provider_info.py' 2023-04-28 05:57:52,872 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_mapping.py' 2023-04-28 05:57:52,873 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_mapping_info.py' 2023-04-28 05:57:52,873 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_role.py' 2023-04-28 05:57:52,873 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_keystone_service.py' 2023-04-28 05:57:52,873 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_listener.py' 2023-04-28 05:57:52,874 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_loadbalancer.py' 2023-04-28 05:57:52,874 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_member.py' 2023-04-28 05:57:52,874 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_network.py' 2023-04-28 05:57:52,875 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_networks_info.py' 2023-04-28 05:57:52,875 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_nova_flavor.py' 2023-04-28 05:57:52,875 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_nova_host_aggregate.py' 2023-04-28 05:57:52,875 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_object.py' 2023-04-28 05:57:52,875 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_pool.py' 2023-04-28 05:57:52,876 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_port.py' 2023-04-28 05:57:52,876 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_port_info.py' 2023-04-28 05:57:52,876 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_project.py' 2023-04-28 05:57:52,877 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_project_access.py' 2023-04-28 05:57:52,877 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_project_info.py' 2023-04-28 05:57:52,877 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_quota.py' 2023-04-28 05:57:52,877 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_recordset.py' 2023-04-28 05:57:52,878 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_router.py' 2023-04-28 05:57:52,878 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_routers_info.py' 2023-04-28 05:57:52,878 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_security_group.py' 2023-04-28 05:57:52,878 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_security_group_rule.py' 2023-04-28 05:57:52,879 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_server.py' 2023-04-28 05:57:52,880 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_server_action.py' 2023-04-28 05:57:52,880 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_server_group.py' 2023-04-28 05:57:52,880 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_server_info.py' 2023-04-28 05:57:52,880 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_server_metadata.py' 2023-04-28 05:57:52,880 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_server_volume.py' 2023-04-28 05:57:52,881 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_stack.py' 2023-04-28 05:57:52,881 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_subnet.py' 2023-04-28 05:57:52,881 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_subnets_info.py' 2023-04-28 05:57:52,881 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_user.py' 2023-04-28 05:57:52,882 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_user_group.py' 2023-04-28 05:57:52,882 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_user_info.py' 2023-04-28 05:57:52,882 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_user_role.py' 2023-04-28 05:57:52,882 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_volume.py' 2023-04-28 05:57:52,883 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_volume_snapshot.py' 2023-04-28 05:57:52,883 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/os_zone.py' 2023-04-28 05:57:52,883 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/port.py' 2023-04-28 05:57:52,884 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/port_info.py' 2023-04-28 05:57:52,884 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/project.py' 2023-04-28 05:57:52,884 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/project_access.py' 2023-04-28 05:57:52,884 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/project_info.py' 2023-04-28 05:57:52,885 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/quota.py' 2023-04-28 05:57:52,885 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/recordset.py' 2023-04-28 05:57:52,885 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/role_assignment.py' 2023-04-28 05:57:52,885 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/router.py' 2023-04-28 05:57:52,886 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/routers_info.py' 2023-04-28 05:57:52,886 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/security_group.py' 2023-04-28 05:57:52,886 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/security_group_info.py' 2023-04-28 05:57:52,886 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/security_group_rule.py' 2023-04-28 05:57:52,887 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/security_group_rule_info.py' 2023-04-28 05:57:52,887 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/server.py' 2023-04-28 05:57:52,887 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/server_action.py' 2023-04-28 05:57:52,888 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/server_group.py' 2023-04-28 05:57:52,888 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/server_info.py' 2023-04-28 05:57:52,888 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/server_metadata.py' 2023-04-28 05:57:52,888 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/server_volume.py' 2023-04-28 05:57:52,889 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/stack.py' 2023-04-28 05:57:52,889 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/stack_info.py' 2023-04-28 05:57:52,889 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/subnet.py' 2023-04-28 05:57:52,889 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/subnet_pool.py' 2023-04-28 05:57:52,890 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/subnets_info.py' 2023-04-28 05:57:52,890 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/volume.py' 2023-04-28 05:57:52,890 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/volume_backup.py' 2023-04-28 05:57:52,890 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/volume_backup_info.py' 2023-04-28 05:57:52,891 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/volume_info.py' 2023-04-28 05:57:52,891 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/volume_snapshot.py' 2023-04-28 05:57:52,891 wheel INFO adding 'ansible_collections/openstack/cloud/plugins/modules/volume_snapshot_info.py' 2023-04-28 05:57:52,891 wheel INFO adding 'ansible_collections/openstack/cloud/scripts/inventory/openstack.yml' 2023-04-28 05:57:52,892 wheel INFO adding 'ansible_collections/openstack/cloud/scripts/inventory/openstack_inventory.py' 2023-04-28 05:57:52,892 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/CHANGELOG.rst' 2023-04-28 05:57:52,892 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/FILES.json' 2023-04-28 05:57:52,893 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/LICENSE' 2023-04-28 05:57:52,893 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/MANIFEST.json' 2023-04-28 05:57:52,893 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/README.md' 2023-04-28 05:57:52,893 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/bindep.txt' 2023-04-28 05:57:52,894 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/requirements.txt' 2023-04-28 05:57:52,894 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/test-requirements.txt' 2023-04-28 05:57:52,894 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/tox.ini' 2023-04-28 05:57:52,894 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,895 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/changelogs/changelog.yaml' 2023-04-28 05:57:52,895 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/changelogs/config.yaml' 2023-04-28 05:57:52,895 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/meta/runtime.yml' 2023-04-28 05:57:52,895 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/plugins/modules/__init__.py' 2023-04-28 05:57:52,895 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_bond.py' 2023-04-28 05:57:52,896 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_bridge.py' 2023-04-28 05:57:52,896 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_db.py' 2023-04-28 05:57:52,896 wheel INFO adding 'ansible_collections/openvswitch/openvswitch/plugins/modules/openvswitch_port.py' 2023-04-28 05:57:52,897 wheel INFO adding 'ansible_collections/ovirt/ovirt/CHANGELOG.rst' 2023-04-28 05:57:52,897 wheel INFO adding 'ansible_collections/ovirt/ovirt/FILES.json' 2023-04-28 05:57:52,898 wheel INFO adding 'ansible_collections/ovirt/ovirt/MANIFEST.json' 2023-04-28 05:57:52,898 wheel INFO adding 'ansible_collections/ovirt/ovirt/README-developers.md' 2023-04-28 05:57:52,898 wheel INFO adding 'ansible_collections/ovirt/ovirt/README.md' 2023-04-28 05:57:52,899 wheel INFO adding 'ansible_collections/ovirt/ovirt/README.md.in' 2023-04-28 05:57:52,899 wheel INFO adding 'ansible_collections/ovirt/ovirt/bindep.txt' 2023-04-28 05:57:52,899 wheel INFO adding 'ansible_collections/ovirt/ovirt/build.sh' 2023-04-28 05:57:52,900 wheel INFO adding 'ansible_collections/ovirt/ovirt/ovirt-ansible-collection-2.4.1.tar.gz' 2023-04-28 05:57:52,901 wheel INFO adding 'ansible_collections/ovirt/ovirt/ovirt-ansible-collection.spec' 2023-04-28 05:57:52,902 wheel INFO adding 'ansible_collections/ovirt/ovirt/ovirt-ansible-collection.spec.in' 2023-04-28 05:57:52,902 wheel INFO adding 'ansible_collections/ovirt/ovirt/requirements.txt' 2023-04-28 05:57:52,902 wheel INFO adding 'ansible_collections/ovirt/ovirt/automation/README.md' 2023-04-28 05:57:52,902 wheel INFO adding 'ansible_collections/ovirt/ovirt/automation/build.sh' 2023-04-28 05:57:52,903 wheel INFO adding 'ansible_collections/ovirt/ovirt/changelogs/README.md' 2023-04-28 05:57:52,903 wheel INFO adding 'ansible_collections/ovirt/ovirt/changelogs/changelog.yaml' 2023-04-28 05:57:52,904 wheel INFO adding 'ansible_collections/ovirt/ovirt/changelogs/config.yaml' 2023-04-28 05:57:52,904 wheel INFO adding 'ansible_collections/ovirt/ovirt/changelogs/fragments/.placeholder' 2023-04-28 05:57:52,904 wheel INFO adding 'ansible_collections/ovirt/ovirt/examples/ovirt_ansible_collections.yml' 2023-04-28 05:57:52,904 wheel INFO adding 'ansible_collections/ovirt/ovirt/examples/filters/ovirtdiff.yml' 2023-04-28 05:57:52,904 wheel INFO adding 'ansible_collections/ovirt/ovirt/examples/filters/vmips.yml' 2023-04-28 05:57:52,905 wheel INFO adding 'ansible_collections/ovirt/ovirt/licenses/Apache-license.txt' 2023-04-28 05:57:52,905 wheel INFO adding 'ansible_collections/ovirt/ovirt/licenses/GPL-license.txt' 2023-04-28 05:57:52,905 wheel INFO adding 'ansible_collections/ovirt/ovirt/meta/execution-environment.yml' 2023-04-28 05:57:52,906 wheel INFO adding 'ansible_collections/ovirt/ovirt/meta/requirements.yml' 2023-04-28 05:57:52,906 wheel INFO adding 'ansible_collections/ovirt/ovirt/meta/runtime.yml' 2023-04-28 05:57:52,906 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/callback/stdout.py' 2023-04-28 05:57:52,907 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/doc_fragments/ovirt.py' 2023-04-28 05:57:52,907 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/doc_fragments/ovirt_info.py' 2023-04-28 05:57:52,907 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/convert_to_bytes.py' 2023-04-28 05:57:52,907 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/convert_to_bytes.yml' 2023-04-28 05:57:52,907 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/filtervalue.yml' 2023-04-28 05:57:52,908 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/get_network_xml_to_dict.yml' 2023-04-28 05:57:52,908 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/get_ovf_disk_size.py' 2023-04-28 05:57:52,908 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/get_ovf_disk_size.yml' 2023-04-28 05:57:52,908 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/json_query.py' 2023-04-28 05:57:52,908 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/json_query.yml' 2023-04-28 05:57:52,909 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtdiff.yml' 2023-04-28 05:57:52,909 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmip.py' 2023-04-28 05:57:52,909 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmip.yml' 2023-04-28 05:57:52,909 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmips.yml' 2023-04-28 05:57:52,910 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipsv4.yml' 2023-04-28 05:57:52,910 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipsv6.yml' 2023-04-28 05:57:52,910 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipv4.yml' 2023-04-28 05:57:52,910 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/ovirtvmipv6.yml' 2023-04-28 05:57:52,910 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/filter/removesensitivevmdata.yml' 2023-04-28 05:57:52,911 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/inventory/ovirt.py' 2023-04-28 05:57:52,911 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/module_utils/__init__.py' 2023-04-28 05:57:52,911 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/module_utils/cloud.py' 2023-04-28 05:57:52,911 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/module_utils/ovirt.py' 2023-04-28 05:57:52,912 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/module_utils/version.py' 2023-04-28 05:57:52,912 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/__init__.py' 2023-04-28 05:57:52,912 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_group.py' 2023-04-28 05:57:52,913 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_label.py' 2023-04-28 05:57:52,913 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_affinity_label_info.py' 2023-04-28 05:57:52,913 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_api_info.py' 2023-04-28 05:57:52,913 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_auth.py' 2023-04-28 05:57:52,914 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_cluster.py' 2023-04-28 05:57:52,914 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_cluster_info.py' 2023-04-28 05:57:52,914 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_datacenter.py' 2023-04-28 05:57:52,915 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_datacenter_info.py' 2023-04-28 05:57:52,915 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk.py' 2023-04-28 05:57:52,915 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk_info.py' 2023-04-28 05:57:52,916 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_disk_profile.py' 2023-04-28 05:57:52,916 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_event.py' 2023-04-28 05:57:52,916 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_event_info.py' 2023-04-28 05:57:52,916 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_external_provider.py' 2023-04-28 05:57:52,917 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_external_provider_info.py' 2023-04-28 05:57:52,917 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_group.py' 2023-04-28 05:57:52,917 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_group_info.py' 2023-04-28 05:57:52,918 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host.py' 2023-04-28 05:57:52,918 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_info.py' 2023-04-28 05:57:52,918 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_network.py' 2023-04-28 05:57:52,918 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_pm.py' 2023-04-28 05:57:52,919 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_host_storage_info.py' 2023-04-28 05:57:52,919 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_instance_type.py' 2023-04-28 05:57:52,919 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_job.py' 2023-04-28 05:57:52,920 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_mac_pool.py' 2023-04-28 05:57:52,920 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_network.py' 2023-04-28 05:57:52,920 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_network_info.py' 2023-04-28 05:57:52,920 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_nic.py' 2023-04-28 05:57:52,921 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_nic_info.py' 2023-04-28 05:57:52,921 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_permission.py' 2023-04-28 05:57:52,921 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_permission_info.py' 2023-04-28 05:57:52,921 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_qos.py' 2023-04-28 05:57:52,922 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_quota.py' 2023-04-28 05:57:52,922 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_quota_info.py' 2023-04-28 05:57:52,922 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_role.py' 2023-04-28 05:57:52,923 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_scheduling_policy_info.py' 2023-04-28 05:57:52,923 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_snapshot.py' 2023-04-28 05:57:52,923 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_snapshot_info.py' 2023-04-28 05:57:52,923 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_connection.py' 2023-04-28 05:57:52,924 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain.py' 2023-04-28 05:57:52,924 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_domain_info.py' 2023-04-28 05:57:52,924 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_template_info.py' 2023-04-28 05:57:52,925 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_storage_vm_info.py' 2023-04-28 05:57:52,925 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_system_option_info.py' 2023-04-28 05:57:52,925 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_tag.py' 2023-04-28 05:57:52,925 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_tag_info.py' 2023-04-28 05:57:52,926 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_template.py' 2023-04-28 05:57:52,926 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_template_info.py' 2023-04-28 05:57:52,926 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_user.py' 2023-04-28 05:57:52,927 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_user_info.py' 2023-04-28 05:57:52,927 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm.py' 2023-04-28 05:57:52,928 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm_info.py' 2023-04-28 05:57:52,928 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vm_os_info.py' 2023-04-28 05:57:52,928 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vmpool.py' 2023-04-28 05:57:52,929 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vmpool_info.py' 2023-04-28 05:57:52,929 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vnic_profile.py' 2023-04-28 05:57:52,929 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/modules/ovirt_vnic_profile_info.py' 2023-04-28 05:57:52,929 wheel INFO adding 'ansible_collections/ovirt/ovirt/plugins/test/ovirt_proxied_check.py' 2023-04-28 05:57:52,930 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/README.md' 2023-04-28 05:57:52,930 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/defaults/main.yml' 2023-04-28 05:57:52,930 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples/cluster_upgrade.yml' 2023-04-28 05:57:52,930 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/examples/passwords.yml' 2023-04-28 05:57:52,931 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/cluster_policy.yml' 2023-04-28 05:57:52,931 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/log_progress.yml' 2023-04-28 05:57:52,931 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/main.yml' 2023-04-28 05:57:52,931 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/pinned_vms.yml' 2023-04-28 05:57:52,932 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/cluster_upgrade/tasks/upgrade.yml' 2023-04-28 05:57:52,932 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/README.md' 2023-04-28 05:57:52,932 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/defaults/main.yml' 2023-04-28 05:57:52,932 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/disaster_recovery_vars.yml' 2023-04-28 05:57:52,933 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/dr_ovirt_setup.yml' 2023-04-28 05:57:52,933 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/dr_play.yml' 2023-04-28 05:57:52,933 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/examples/ovirt_passwords.yml' 2023-04-28 05:57:52,933 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/bcolors.py' 2023-04-28 05:57:52,934 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/dr.conf' 2023-04-28 05:57:52,934 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/fail_back.py' 2023-04-28 05:57:52,934 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/fail_over.py' 2023-04-28 05:57:52,934 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_mapping.py' 2023-04-28 05:57:52,935 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_vars.py' 2023-04-28 05:57:52,935 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_vars_test.py' 2023-04-28 05:57:52,935 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/ovirt-dr' 2023-04-28 05:57:52,936 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/validator.py' 2023-04-28 05:57:52,936 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/vault_secret.sh' 2023-04-28 05:57:52,936 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean_engine.yml' 2023-04-28 05:57:52,936 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/generate_mapping.yml' 2023-04-28 05:57:52,937 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/main.yml' 2023-04-28 05:57:52,937 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover_engine.yml' 2023-04-28 05:57:52,937 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/run_unregistered_entities.yml' 2023-04-28 05:57:52,937 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/unregister_entities.yml' 2023-04-28 05:57:52,938 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_disks.yml' 2023-04-28 05:57:52,938 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_domain.yml' 2023-04-28 05:57:52,938 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_domain_process.yml' 2023-04-28 05:57:52,938 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_invalid_filtered_master_domains.yml' 2023-04-28 05:57:52,938 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_valid_filtered_master_domains.yml' 2023-04-28 05:57:52,939 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/remove_vms.yml' 2023-04-28 05:57:52,939 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/shutdown_vm.yml' 2023-04-28 05:57:52,939 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/shutdown_vms.yml' 2023-04-28 05:57:52,939 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/clean/update_ovf_store.yml' 2023-04-28 05:57:52,939 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_domain.yml' 2023-04-28 05:57:52,940 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_fcp_domain.yml' 2023-04-28 05:57:52,940 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_glusterfs_domain.yml' 2023-04-28 05:57:52,940 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_iscsi_domain.yml' 2023-04-28 05:57:52,940 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_nfs_domain.yml' 2023-04-28 05:57:52,941 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/add_posixfs_domain.yml' 2023-04-28 05:57:52,941 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/print_info.yml' 2023-04-28 05:57:52,941 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_template.yml' 2023-04-28 05:57:52,941 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_templates.yml' 2023-04-28 05:57:52,941 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_vm.yml' 2023-04-28 05:57:52,942 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/register_vms.yml' 2023-04-28 05:57:52,942 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/report_log_template.j2' 2023-04-28 05:57:52,942 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/recover/run_vms.yml' 2023-04-28 05:57:52,942 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/README.md' 2023-04-28 05:57:52,943 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/defaults/main.yml' 2023-04-28 05:57:52,943 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/examples/engine-deploy.yml' 2023-04-28 05:57:52,943 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/examples/engine-upgrade.yml' 2023-04-28 05:57:52,943 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/examples/passwords.yml' 2023-04-28 05:57:52,944 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/engine_setup.yml' 2023-04-28 05:57:52,944 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/install_packages.yml' 2023-04-28 05:57:52,944 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/main.yml' 2023-04-28 05:57:52,944 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/pre_install_checks.yml' 2023-04-28 05:57:52,944 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tasks/restore_engine_from_file.yml' 2023-04-28 05:57:52,945 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.1_basic.txt.j2' 2023-04-28 05:57:52,945 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.1_upgrade.txt.j2' 2023-04-28 05:57:52,945 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.2_basic.txt.j2' 2023-04-28 05:57:52,945 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.2_upgrade.txt.j2' 2023-04-28 05:57:52,946 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.3_basic.txt.j2' 2023-04-28 05:57:52,946 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.3_upgrade.txt.j2' 2023-04-28 05:57:52,946 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.4_basic.txt.j2' 2023-04-28 05:57:52,946 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.4_upgrade.txt.j2' 2023-04-28 05:57:52,946 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.5_basic.txt.j2' 2023-04-28 05:57:52,947 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/answerfile_4.5_upgrade.txt.j2' 2023-04-28 05:57:52,947 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/templates/basic_answerfile.txt.j2' 2023-04-28 05:57:52,947 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/containers-deploy.yml' 2023-04-28 05:57:52,947 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/engine-deploy.yml' 2023-04-28 05:57:52,947 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/engine-upgrade.yml' 2023-04-28 05:57:52,948 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/inventory' 2023-04-28 05:57:52,948 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/passwords.yml' 2023-04-28 05:57:52,948 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/requirements.yml' 2023-04-28 05:57:52,948 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-4.2.yml' 2023-04-28 05:57:52,949 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-master.yml' 2023-04-28 05:57:52,949 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/tests/test-upgrade-4.2-to-master.yml' 2023-04-28 05:57:52,949 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/engine_setup/vars/main.yml' 2023-04-28 05:57:52,949 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/README.md' 2023-04-28 05:57:52,950 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/defaults/main.yml' 2023-04-28 05:57:52,950 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/hosted_engine_deploy_localhost.yml' 2023-04-28 05:57:52,950 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/hosted_engine_deploy_remotehost.yml' 2023-04-28 05:57:52,950 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/iscsi_deployment_remote.json' 2023-04-28 05:57:52,951 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/nfs_deployment.json' 2023-04-28 05:57:52,951 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/passwords.yml' 2023-04-28 05:57:52,951 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/examples/required_networks_fix.yml' 2023-04-28 05:57:52,951 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/files/35-allow-ansible-for-vdsm.rules' 2023-04-28 05:57:52,951 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_add_host/README.md' 2023-04-28 05:57:52,952 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup/README.md' 2023-04-28 05:57:52,952 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/after_setup/add_host_storage_domain.yml' 2023-04-28 05:57:52,952 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_after_engine_setup/README.md' 2023-04-28 05:57:52,952 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/hooks/enginevm_before_engine_setup/README.md' 2023-04-28 05:57:52,953 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/add_engine_as_ansible_host.yml' 2023-04-28 05:57:52,953 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/alter_libvirt_default_net_configuration.yml' 2023-04-28 05:57:52,953 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/apply_openscap_profile.yml' 2023-04-28 05:57:52,953 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_revoke.yml' 2023-04-28 05:57:52,954 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/auth_sso.yml' 2023-04-28 05:57:52,954 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_cloud_init_config.yml' 2023-04-28 05:57:52,954 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_local_storage_pools.yml' 2023-04-28 05:57:52,954 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/clean_localvm_dir.yml' 2023-04-28 05:57:52,954 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_storage_domain.yml' 2023-04-28 05:57:52,955 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fc_getdevices.yml' 2023-04-28 05:57:52,955 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_engine_logs.yml' 2023-04-28 05:57:52,955 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/fetch_host_ip.yml' 2023-04-28 05:57:52,955 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/filter_team_devices.yml' 2023-04-28 05:57:52,955 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/filter_unsupported_vlan_devices.yml' 2023-04-28 05:57:52,956 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/final_clean.yml' 2023-04-28 05:57:52,956 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/full_execution.yml' 2023-04-28 05:57:52,956 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/get_appliance_dist.yml' 2023-04-28 05:57:52,956 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/get_local_vm_disk_path.yml' 2023-04-28 05:57:52,957 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/initial_clean.yml' 2023-04-28 05:57:52,957 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/install_appliance.yml' 2023-04-28 05:57:52,957 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/install_packages.yml' 2023-04-28 05:57:52,957 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/ipv_switch.yml' 2023-04-28 05:57:52,957 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/iscsi_discover.yml' 2023-04-28 05:57:52,958 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/iscsi_getdevices.yml' 2023-04-28 05:57:52,958 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/main.yml' 2023-04-28 05:57:52,958 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/partial_execution.yml' 2023-04-28 05:57:52,958 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pause_execution.yml' 2023-04-28 05:57:52,959 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/restore_backup.yml' 2023-04-28 05:57:52,959 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/restore_host_redeploy.yml' 2023-04-28 05:57:52,959 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/search_available_network_subnet.yaml' 2023-04-28 05:57:52,959 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/sync_on_engine_machine.yml' 2023-04-28 05:57:52,959 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_ip_prefix.yml' 2023-04-28 05:57:52,960 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_vlan_bond_mode.yml' 2023-04-28 05:57:52,960 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/validate_vlan_name.yml' 2023-04-28 05:57:52,960 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/01_prepare_routing_rules.yml' 2023-04-28 05:57:52,960 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/02_create_local_vm.yml' 2023-04-28 05:57:52,961 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/03_engine_initial_tasks.yml' 2023-04-28 05:57:52,961 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/04_engine_final_tasks.yml' 2023-04-28 05:57:52,961 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/bootstrap_local_vm/05_add_host.yml' 2023-04-28 05:57:52,961 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/01_create_target_hosted_engine_vm.yml' 2023-04-28 05:57:52,962 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/02_engine_vm_configuration.yml' 2023-04-28 05:57:52,962 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/create_target_vm/03_hosted_engine_final_tasks.yml' 2023-04-28 05:57:52,962 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/001_validate_network_interfaces.yml' 2023-04-28 05:57:52,962 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/002_validate_hostname_tasks.yml' 2023-04-28 05:57:52,963 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/define_variables.yml' 2023-04-28 05:57:52,963 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_data_center_name.yml' 2023-04-28 05:57:52,963 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_firewalld.yml' 2023-04-28 05:57:52,963 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_gateway.yml' 2023-04-28 05:57:52,964 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_mac_address.yml' 2023-04-28 05:57:52,964 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_memory_size.yml' 2023-04-28 05:57:52,964 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_network_test.yml' 2023-04-28 05:57:52,964 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_services_status.yml' 2023-04-28 05:57:52,964 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/tasks/pre_checks/validate_vcpus_count.yml' 2023-04-28 05:57:52,965 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/broker.conf.j2' 2023-04-28 05:57:52,965 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/fhanswers.conf.j2' 2023-04-28 05:57:52,965 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/hosted-engine.conf.j2' 2023-04-28 05:57:52,965 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-dhcp.j2' 2023-04-28 05:57:52,966 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-static-ipv6.j2' 2023-04-28 05:57:52,966 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/ifcfg-eth0-static.j2' 2023-04-28 05:57:52,966 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/meta-data.j2' 2023-04-28 05:57:52,966 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/network-config-dhcp.j2' 2023-04-28 05:57:52,966 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/network-config.j2' 2023-04-28 05:57:52,967 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/user-data.j2' 2023-04-28 05:57:52,967 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/version.j2' 2023-04-28 05:57:52,967 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/hosted_engine_setup/templates/vm.conf.j2' 2023-04-28 05:57:52,967 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/README.md' 2023-04-28 05:57:52,968 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/defaults/main.yml' 2023-04-28 05:57:52,968 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/examples/ovirt_image_template.yml' 2023-04-28 05:57:52,968 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/examples/passwords.yml' 2023-04-28 05:57:52,968 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/tasks/empty.yml' 2023-04-28 05:57:52,969 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/tasks/glance_image.yml' 2023-04-28 05:57:52,969 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/tasks/main.yml' 2023-04-28 05:57:52,969 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/tasks/qcow2_image.yml' 2023-04-28 05:57:52,969 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/image_template/vars/main.yml' 2023-04-28 05:57:52,970 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/README.md' 2023-04-28 05:57:52,970 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/defaults/main.yml' 2023-04-28 05:57:52,970 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/examples/ovirt_infra.yml' 2023-04-28 05:57:52,970 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/examples/ovirt_infra_destroy.yml' 2023-04-28 05:57:52,971 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/examples/vars/ovirt_infra_vars.yml' 2023-04-28 05:57:52,971 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/examples/vars/passwords.yml' 2023-04-28 05:57:52,971 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/README.md' 2023-04-28 05:57:52,971 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/defaults/main.yml' 2023-04-28 05:57:52,972 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/aaa_jdbc/tasks/main.yml' 2023-04-28 05:57:52,972 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/README.md' 2023-04-28 05:57:52,972 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/tasks/main.yml' 2023-04-28 05:57:52,973 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/clusters/vars/main.yml' 2023-04-28 05:57:52,973 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/README.md' 2023-04-28 05:57:52,973 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/defaults/main.yml' 2023-04-28 05:57:52,973 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/cluster_and_hosts.yml' 2023-04-28 05:57:52,974 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/datacenter.yml' 2023-04-28 05:57:52,974 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/disks.yml' 2023-04-28 05:57:52,974 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/main.yml' 2023-04-28 05:57:52,974 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/storages_last.yml' 2023-04-28 05:57:52,974 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/storages_pre.yml' 2023-04-28 05:57:52,975 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/templates.yml' 2023-04-28 05:57:52,975 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/vm_pools.yml' 2023-04-28 05:57:52,975 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenter_cleanup/tasks/vms.yml' 2023-04-28 05:57:52,975 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/README.md' 2023-04-28 05:57:52,976 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/defaults/main.yml' 2023-04-28 05:57:52,976 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/datacenters/tasks/main.yml' 2023-04-28 05:57:52,976 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/README.md' 2023-04-28 05:57:52,976 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/external_providers/tasks/main.yml' 2023-04-28 05:57:52,977 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/README.md' 2023-04-28 05:57:52,977 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/defaults/main.yml' 2023-04-28 05:57:52,977 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/hosts/tasks/main.yml' 2023-04-28 05:57:52,977 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/README.md' 2023-04-28 05:57:52,978 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/mac_pools/tasks/main.yml' 2023-04-28 05:57:52,978 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/networks/README.md' 2023-04-28 05:57:52,978 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/networks/tasks/main.yml' 2023-04-28 05:57:52,978 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/README.md' 2023-04-28 05:57:52,979 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/permissions/tasks/main.yml' 2023-04-28 05:57:52,979 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/storages/README.md' 2023-04-28 05:57:52,979 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/roles/storages/tasks/main.yml' 2023-04-28 05:57:52,979 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/tasks/create_infra.yml' 2023-04-28 05:57:52,980 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/tasks/main.yml' 2023-04-28 05:57:52,980 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/infra/tasks/remove_infra.yml' 2023-04-28 05:57:52,980 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/remove_stale_lun/README.md' 2023-04-28 05:57:52,980 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/remove_stale_lun/defaults/main.yml' 2023-04-28 05:57:52,981 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples/passwords.yml' 2023-04-28 05:57:52,981 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/remove_stale_lun/examples/remove_stale_lun.yml' 2023-04-28 05:57:52,981 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/fetch_hosts.yml' 2023-04-28 05:57:52,981 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/main.yml' 2023-04-28 05:57:52,981 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/remove_stale_lun/tasks/remove_mpath_device.yml' 2023-04-28 05:57:52,982 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/README.md' 2023-04-28 05:57:52,982 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/defaults/main.yml' 2023-04-28 05:57:52,982 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/examples/ovirt_repositories_release_rpm.yml' 2023-04-28 05:57:52,982 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/examples/ovirt_repositories_subscription_manager.yml' 2023-04-28 05:57:52,983 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/examples/passwords.yml' 2023-04-28 05:57:52,983 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/tasks/backup-repos.yml' 2023-04-28 05:57:52,983 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/tasks/install-satellite-ca.yml' 2023-04-28 05:57:52,983 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/tasks/main.yml' 2023-04-28 05:57:52,984 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/tasks/rh-subscription.yml' 2023-04-28 05:57:52,984 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/tasks/rpm.yml' 2023-04-28 05:57:52,984 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/tasks/satellite-subscription.yml' 2023-04-28 05:57:52,984 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/tasks/search-pool-id.yml' 2023-04-28 05:57:52,984 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/default.yml' 2023-04-28 05:57:52,985 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.1.yml' 2023-04-28 05:57:52,985 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.2.yml' 2023-04-28 05:57:52,985 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.3.yml' 2023-04-28 05:57:52,985 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_4.4.yml' 2023-04-28 05:57:52,985 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/engine_eus_4.4.yml' 2023-04-28 05:57:52,986 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.1.yml' 2023-04-28 05:57:52,986 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.2.yml' 2023-04-28 05:57:52,986 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.3.yml' 2023-04-28 05:57:52,986 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/host_4.4.yml' 2023-04-28 05:57:52,987 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/host_eus_4.4.yml' 2023-04-28 05:57:52,987 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/host_ppc_4.4.yml' 2023-04-28 05:57:52,987 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/host_ppc_eus_4.4.yml' 2023-04-28 05:57:52,987 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.1.yml' 2023-04-28 05:57:52,987 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.2.yml' 2023-04-28 05:57:52,988 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.3.yml' 2023-04-28 05:57:52,988 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/repositories/vars/rhvh_4.4.yml' 2023-04-28 05:57:52,988 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/shutdown_env/README.md' 2023-04-28 05:57:52,988 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/shutdown_env/defaults/main.yml' 2023-04-28 05:57:52,989 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/shutdown_env/examples/passwords.yml' 2023-04-28 05:57:52,989 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/shutdown_env/examples/shutdown_env.yml' 2023-04-28 05:57:52,989 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/shutdown_env/tasks/main.yml' 2023-04-28 05:57:52,989 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/README.md' 2023-04-28 05:57:52,990 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/defaults/main.yml' 2023-04-28 05:57:52,990 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/examples/ovirt_vm_infra.yml' 2023-04-28 05:57:52,990 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/examples/ovirt_vm_infra_inv.yml' 2023-04-28 05:57:52,990 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/examples/passwords.yml' 2023-04-28 05:57:52,991 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/affinity_groups.yml' 2023-04-28 05:57:52,991 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/affinity_labels.yml' 2023-04-28 05:57:52,991 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/create_inventory.yml' 2023-04-28 05:57:52,991 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/create_vms.yml' 2023-04-28 05:57:52,992 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/main.yml' 2023-04-28 05:57:52,992 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/manage_state.yml' 2023-04-28 05:57:52,992 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/vm_state_absent.yml' 2023-04-28 05:57:52,992 wheel INFO adding 'ansible_collections/ovirt/ovirt/roles/vm_infra/tasks/vm_state_present.yml' 2023-04-28 05:57:52,993 wheel INFO adding 'ansible_collections/purestorage/flasharray/CHANGELOG.rst' 2023-04-28 05:57:52,993 wheel INFO adding 'ansible_collections/purestorage/flasharray/COPYING.GPLv3' 2023-04-28 05:57:52,993 wheel INFO adding 'ansible_collections/purestorage/flasharray/FILES.json' 2023-04-28 05:57:52,994 wheel INFO adding 'ansible_collections/purestorage/flasharray/LICENSE' 2023-04-28 05:57:52,994 wheel INFO adding 'ansible_collections/purestorage/flasharray/MANIFEST.json' 2023-04-28 05:57:52,995 wheel INFO adding 'ansible_collections/purestorage/flasharray/README.md' 2023-04-28 05:57:52,995 wheel INFO adding 'ansible_collections/purestorage/flasharray/README.rst' 2023-04-28 05:57:52,995 wheel INFO adding 'ansible_collections/purestorage/flasharray/requirements.txt' 2023-04-28 05:57:52,995 wheel INFO adding 'ansible_collections/purestorage/flasharray/settings.json' 2023-04-28 05:57:52,995 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:52,996 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/210_add_rename_hgroup.yaml' 2023-04-28 05:57:52,996 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/211_fix_clearing_host_inititators.yaml' 2023-04-28 05:57:52,996 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/changelog.yaml' 2023-04-28 05:57:52,996 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/config.yaml' 2023-04-28 05:57:52,997 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/107_host_case_clarity.yaml' 2023-04-28 05:57:52,997 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/108_fix_eradicate_idempotency.yaml' 2023-04-28 05:57:52,997 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/109_fa_files_support_purefa_info.yaml' 2023-04-28 05:57:52,998 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/110_add_apiclient_support.yaml' 2023-04-28 05:57:52,998 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/111_add_filesystem_support.yaml' 2023-04-28 05:57:52,998 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/112_add_directory_support.yaml' 2023-04-28 05:57:52,998 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/113_add_exports_support.yaml' 2023-04-28 05:57:52,998 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/115_add_gcp_offload.yaml' 2023-04-28 05:57:52,999 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/116_add_policies.yaml' 2023-04-28 05:57:52,999 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/118_rename_host.yaml' 2023-04-28 05:57:52,999 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/121_add_multi_volume_creation.yaml' 2023-04-28 05:57:52,999 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/122_add_multi_host_creation.yaml' 2023-04-28 05:57:52,999 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/123_add_multi_vgroup_creation.yaml' 2023-04-28 05:57:53,000 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/124_sdk_handshake.yaml' 2023-04-28 05:57:53,000 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/125_dns_idempotency.yaml' 2023-04-28 05:57:53,000 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/126_fix_volume_move.yaml' 2023-04-28 05:57:53,000 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/130_info_ds_update.yaml' 2023-04-28 05:57:53,000 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/131_add_v6_ds_update.yaml' 2023-04-28 05:57:53,001 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/132_fc_replication.yaml' 2023-04-28 05:57:53,001 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/133_purefa_info_v6_replication.yaml' 2023-04-28 05:57:53,001 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/134_ac_pg_support.yaml' 2023-04-28 05:57:53,001 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/135_no_cbs_ntp.yaml' 2023-04-28 05:57:53,001 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/136_add_vol_get_send_info.yaml' 2023-04-28 05:57:53,002 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/137_pgsnap_regex.yaml' 2023-04-28 05:57:53,002 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/139_pgsnap_ac_support.yaml' 2023-04-28 05:57:53,002 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/140_pod_case.yaml' 2023-04-28 05:57:53,002 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/141_add_remote_snapshot.yaml' 2023-04-28 05:57:53,002 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/145_fix_missing_move_variable.yaml' 2023-04-28 05:57:53,003 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/149_volumes_demoted_pods_fix.yaml' 2023-04-28 05:57:53,003 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/152_fix_user.yaml' 2023-04-28 05:57:53,003 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/153_syslog_update.yaml' 2023-04-28 05:57:53,003 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/156_snap_suffix_fix.yaml' 2023-04-28 05:57:53,003 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/160_rename_pg.yaml' 2023-04-28 05:57:53,004 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/161_offline_offload_fix.yaml' 2023-04-28 05:57:53,004 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/162_pgsnap_info_fix.yaml' 2023-04-28 05:57:53,004 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/163_add_maintenance_windows.yaml' 2023-04-28 05:57:53,005 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/168_dsrole_fix.yaml' 2023-04-28 05:57:53,005 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/169_add_certs.yaml' 2023-04-28 05:57:53,005 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/170_pgsnap_stretch_pod_fail.yaml' 2023-04-28 05:57:53,005 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/174_null_gateway.yaml' 2023-04-28 05:57:53,005 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/175_check_pgname.yaml' 2023-04-28 05:57:53,006 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/176_fix_promote_api_issue.yaml' 2023-04-28 05:57:53,006 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/182_allow_pgroup_with_create.yaml' 2023-04-28 05:57:53,006 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/187_add_ad.yaml' 2023-04-28 05:57:53,006 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/188_add_dirsnap.yaml' 2023-04-28 05:57:53,006 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/193_duplicate_initiators.yaml' 2023-04-28 05:57:53,007 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/194_vg_qos.yaml' 2023-04-28 05:57:53,007 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/196_fix_activedr_api_version.yaml' 2023-04-28 05:57:53,007 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/199_add_fc_port_enable.yaml' 2023-04-28 05:57:53,007 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/200_add_DAR_info.yaml' 2023-04-28 05:57:53,007 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/201_increase_krb_count.yaml' 2023-04-28 05:57:53,008 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/202_add_sso.yaml' 2023-04-28 05:57:53,008 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/203_add_eradication_timer.yaml' 2023-04-28 05:57:53,008 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/205_policy_protocl.yaml' 2023-04-28 05:57:53,008 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/206_add_naa_info.yaml' 2023-04-28 05:57:53,008 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/207_fix_disable_for_remote_assist.yaml' 2023-04-28 05:57:53,009 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/208_add_directory_quota_support.yaml' 2023-04-28 05:57:53,009 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/213_add_kmip.yaml' 2023-04-28 05:57:53,009 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/214_join_ou.yaml' 2023-04-28 05:57:53,009 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/220_capacity_info.yaml' 2023-04-28 05:57:53,009 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/224_add_nguid_info.yaml' 2023-04-28 05:57:53,010 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/226_deprecate_protocol.yaml' 2023-04-28 05:57:53,010 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/227_missing_regex.yaml' 2023-04-28 05:57:53,010 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/228_nguid_to_volfact.yaml' 2023-04-28 05:57:53,010 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/229_snapsuffix.yaml' 2023-04-28 05:57:53,010 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/230_add_pg_deleted_vols.yaml' 2023-04-28 05:57:53,011 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/231_syslog_settings.yaml' 2023-04-28 05:57:53,011 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/234_add_vol_info_on_nochange.yaml' 2023-04-28 05:57:53,011 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/235_eula.yaml' 2023-04-28 05:57:53,011 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/237_fix_network.yaml' 2023-04-28 05:57:53,011 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/238_add_dirsnap_rename.yaml' 2023-04-28 05:57:53,012 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/239_safe_mode.yaml' 2023-04-28 05:57:53,012 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/242_multi_offload.yaml' 2023-04-28 05:57:53,012 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/243_sso_to_admin.yaml' 2023-04-28 05:57:53,012 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/246_python_precedence.yaml' 2023-04-28 05:57:53,012 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/247_fix_smb_policy_rules.yaml' 2023-04-28 05:57:53,013 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/249_allow_cert_reimport.yaml' 2023-04-28 05:57:53,013 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/252_add_saml2.yaml' 2023-04-28 05:57:53,013 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/254_sam2_info.yaml' 2023-04-28 05:57:53,013 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/257_fqcn.yaml' 2023-04-28 05:57:53,013 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/259_fix_gateway_check.yaml' 2023-04-28 05:57:53,014 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/261_fix_bad_arrays.yaml' 2023-04-28 05:57:53,014 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/265_fix_multiple_nfs_rules.yaml' 2023-04-28 05:57:53,014 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/268_fix_quotas_issues.yaml' 2023-04-28 05:57:53,014 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/270_add_priority_info.yaml' 2023-04-28 05:57:53,014 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/271_vgroup_prio.yaml' 2023-04-28 05:57:53,015 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/272_volume_prio.yaml' 2023-04-28 05:57:53,015 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/277_add_fs_repl.yaml' 2023-04-28 05:57:53,015 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/278_pgsnap_info.yaml' 2023-04-28 05:57:53,015 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/279_pg_safemode.yaml' 2023-04-28 05:57:53,015 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/280_multihost_no_suffix.yaml' 2023-04-28 05:57:53,016 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/284_volfact_for_recover.yaml' 2023-04-28 05:57:53,016 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/288_zero_params.yaml' 2023-04-28 05:57:53,016 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/292_fix_ds_password.yaml' 2023-04-28 05:57:53,016 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/293_add_chassis_inventory.yaml' 2023-04-28 05:57:53,016 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/294_dns_ntp_idempotency_absent.yaml' 2023-04-28 05:57:53,017 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/294_user_map_support.yaml' 2023-04-28 05:57:53,017 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/296_ad_tls.yaml' 2023-04-28 05:57:53,017 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/299_fix_pgsched_zero_support.yaml' 2023-04-28 05:57:53,017 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/302_fix_pg_recover_and_target_update.yaml' 2023-04-28 05:57:53,017 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/304_host_vlan.yaml' 2023-04-28 05:57:53,018 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/305_fix_target_dempo.yaml' 2023-04-28 05:57:53,018 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/307_multiple_dns.yaml' 2023-04-28 05:57:53,018 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/308_add_vm.yaml' 2023-04-28 05:57:53,018 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/310_hg_vol_idempotency.yaml' 2023-04-28 05:57:53,018 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/312_pg_alias.yaml' 2023-04-28 05:57:53,019 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/315_spf_details.yaml' 2023-04-28 05:57:53,019 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/317_add_all_squash.yaml' 2023-04-28 05:57:53,019 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/318_vol_defaults.yaml' 2023-04-28 05:57:53,019 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/319_lockout.yaml' 2023-04-28 05:57:53,019 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/320_completed_snaps.yaml' 2023-04-28 05:57:53,020 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/328_policy_fix.yaml' 2023-04-28 05:57:53,020 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/330_extend_vlan.yaml' 2023-04-28 05:57:53,020 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/334_fix_vg_qos.yaml' 2023-04-28 05:57:53,020 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/336_add_servicelist.yaml' 2023-04-28 05:57:53,021 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/337_fix_non-prod_versions.yml' 2023-04-28 05:57:53,021 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/341_pg_400s.yaml' 2023-04-28 05:57:53,021 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/342_add_vol_promotion.yaml' 2023-04-28 05:57:53,021 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/343_fix_ds.yaml' 2023-04-28 05:57:53,021 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/344_fix_smtp.yaml' 2023-04-28 05:57:53,022 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/345_user_map.yaml' 2023-04-28 05:57:53,022 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/347_dns_fix.yaml' 2023-04-28 05:57:53,022 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/348_add_default_prot.yaml' 2023-04-28 05:57:53,022 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/349_add_alerts.yaml' 2023-04-28 05:57:53,022 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/351_fix_rest_check.yaml' 2023-04-28 05:57:53,023 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/354_fix_promotion.yaml' 2023-04-28 05:57:53,023 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/360_fix_volume.yaml' 2023-04-28 05:57:53,023 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/363_overwrite_combo.yaml' 2023-04-28 05:57:53,023 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/364_fc_targets.yaml' 2023-04-28 05:57:53,023 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/365_pod_pgsched.yaml' 2023-04-28 05:57:53,024 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/366_add_nvme_types.yaml' 2023-04-28 05:57:53,024 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/367_fix_vg.yaml' 2023-04-28 05:57:53,024 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/369_fix_host.yaml' 2023-04-28 05:57:53,024 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/370_add_user_role.yaml' 2023-04-28 05:57:53,024 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/374_offload_pgsnap.yaml' 2023-04-28 05:57:53,025 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/375_fix_remote_hosts.yaml' 2023-04-28 05:57:53,025 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/379_cap_compat.yaml' 2023-04-28 05:57:53,026 wheel INFO adding 'ansible_collections/purestorage/flasharray/changelogs/fragments/v1.4.0_summary.yaml' 2023-04-28 05:57:53,026 wheel INFO adding 'ansible_collections/purestorage/flasharray/meta/execution-environment.yml' 2023-04-28 05:57:53,026 wheel INFO adding 'ansible_collections/purestorage/flasharray/meta/runtime.yml' 2023-04-28 05:57:53,026 wheel INFO adding 'ansible_collections/purestorage/flasharray/playbooks/.keep' 2023-04-28 05:57:53,027 wheel INFO adding 'ansible_collections/purestorage/flasharray/playbooks/files/.keep' 2023-04-28 05:57:53,027 wheel INFO adding 'ansible_collections/purestorage/flasharray/playbooks/roles/.keep' 2023-04-28 05:57:53,027 wheel INFO adding 'ansible_collections/purestorage/flasharray/playbooks/tasks/.keep' 2023-04-28 05:57:53,027 wheel INFO adding 'ansible_collections/purestorage/flasharray/playbooks/templates/.keep' 2023-04-28 05:57:53,028 wheel INFO adding 'ansible_collections/purestorage/flasharray/playbooks/vars/.keep' 2023-04-28 05:57:53,028 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/doc_fragments/purestorage.py' 2023-04-28 05:57:53,028 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/module_utils/purefa.py' 2023-04-28 05:57:53,029 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_ad.py' 2023-04-28 05:57:53,029 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_admin.py' 2023-04-28 05:57:53,029 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_alert.py' 2023-04-28 05:57:53,029 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_apiclient.py' 2023-04-28 05:57:53,030 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_arrayname.py' 2023-04-28 05:57:53,030 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_banner.py' 2023-04-28 05:57:53,030 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_certs.py' 2023-04-28 05:57:53,030 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_connect.py' 2023-04-28 05:57:53,031 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_console.py' 2023-04-28 05:57:53,031 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_default_protection.py' 2023-04-28 05:57:53,031 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_directory.py' 2023-04-28 05:57:53,031 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_dirsnap.py' 2023-04-28 05:57:53,032 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_dns.py' 2023-04-28 05:57:53,032 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_ds.py' 2023-04-28 05:57:53,032 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_dsrole.py' 2023-04-28 05:57:53,033 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_endpoint.py' 2023-04-28 05:57:53,033 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_eradication.py' 2023-04-28 05:57:53,033 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_eula.py' 2023-04-28 05:57:53,033 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_export.py' 2023-04-28 05:57:53,034 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_fs.py' 2023-04-28 05:57:53,034 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_hg.py' 2023-04-28 05:57:53,034 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_host.py' 2023-04-28 05:57:53,035 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_info.py' 2023-04-28 05:57:53,036 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_inventory.py' 2023-04-28 05:57:53,036 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_kmip.py' 2023-04-28 05:57:53,036 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_maintenance.py' 2023-04-28 05:57:53,036 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_messages.py' 2023-04-28 05:57:53,037 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_network.py' 2023-04-28 05:57:53,037 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_ntp.py' 2023-04-28 05:57:53,037 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_offload.py' 2023-04-28 05:57:53,038 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_pg.py' 2023-04-28 05:57:53,038 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_pgsched.py' 2023-04-28 05:57:53,038 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_pgsnap.py' 2023-04-28 05:57:53,039 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_phonehome.py' 2023-04-28 05:57:53,039 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_pod.py' 2023-04-28 05:57:53,039 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_pod_replica.py' 2023-04-28 05:57:53,040 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_policy.py' 2023-04-28 05:57:53,040 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_proxy.py' 2023-04-28 05:57:53,040 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_ra.py' 2023-04-28 05:57:53,041 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_saml.py' 2023-04-28 05:57:53,041 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_smis.py' 2023-04-28 05:57:53,041 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_smtp.py' 2023-04-28 05:57:53,041 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_snap.py' 2023-04-28 05:57:53,042 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_snmp.py' 2023-04-28 05:57:53,042 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_snmp_agent.py' 2023-04-28 05:57:53,042 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_sso.py' 2023-04-28 05:57:53,043 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_subnet.py' 2023-04-28 05:57:53,043 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_syslog.py' 2023-04-28 05:57:53,043 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_syslog_settings.py' 2023-04-28 05:57:53,043 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_timeout.py' 2023-04-28 05:57:53,044 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_user.py' 2023-04-28 05:57:53,044 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_vg.py' 2023-04-28 05:57:53,044 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_vlan.py' 2023-04-28 05:57:53,044 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_vnc.py' 2023-04-28 05:57:53,045 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_volume.py' 2023-04-28 05:57:53,045 wheel INFO adding 'ansible_collections/purestorage/flasharray/plugins/modules/purefa_volume_tags.py' 2023-04-28 05:57:53,046 wheel INFO adding 'ansible_collections/purestorage/flasharray/roles/.keep' 2023-04-28 05:57:53,046 wheel INFO adding 'ansible_collections/purestorage/flashblade/CHANGELOG.rst' 2023-04-28 05:57:53,046 wheel INFO adding 'ansible_collections/purestorage/flashblade/COPYING.GPLv3' 2023-04-28 05:57:53,047 wheel INFO adding 'ansible_collections/purestorage/flashblade/FILES.json' 2023-04-28 05:57:53,047 wheel INFO adding 'ansible_collections/purestorage/flashblade/LICENSE' 2023-04-28 05:57:53,047 wheel INFO adding 'ansible_collections/purestorage/flashblade/MANIFEST.json' 2023-04-28 05:57:53,048 wheel INFO adding 'ansible_collections/purestorage/flashblade/README.md' 2023-04-28 05:57:53,048 wheel INFO adding 'ansible_collections/purestorage/flashblade/README.rst' 2023-04-28 05:57:53,048 wheel INFO adding 'ansible_collections/purestorage/flashblade/requirements.txt' 2023-04-28 05:57:53,048 wheel INFO adding 'ansible_collections/purestorage/flashblade/settings.json' 2023-04-28 05:57:53,049 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:53,049 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/changelog.yaml' 2023-04-28 05:57:53,049 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/config.yaml' 2023-04-28 05:57:53,050 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/101_fix_policy_and_timezone_error.yaml' 2023-04-28 05:57:53,050 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/105_max_access_key.yaml' 2023-04-28 05:57:53,050 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/107_add_remove_s3user_key.yaml' 2023-04-28 05:57:53,050 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/108_dns_search_fix.yaml' 2023-04-28 05:57:53,050 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/109_update_info.yaml' 2023-04-28 05:57:53,051 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/111_dsrole_update_idempotency.yaml' 2023-04-28 05:57:53,051 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/112_fix_check_mode.yaml' 2023-04-28 05:57:53,051 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/113_policy_cleanup.yaml' 2023-04-28 05:57:53,051 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/114_certificate_update.yaml' 2023-04-28 05:57:53,051 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/115_multiprotocol.yaml' 2023-04-28 05:57:53,052 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/121_replication_perf.yaml' 2023-04-28 05:57:53,052 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/123_lifecycle_rule_fix.yaml' 2023-04-28 05:57:53,052 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/127_add_eula.yaml' 2023-04-28 05:57:53,052 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/128_add_32_to_info.yaml' 2023-04-28 05:57:53,052 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/129-virtualhost.yaml' 2023-04-28 05:57:53,053 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/131-apiclient.yaml' 2023-04-28 05:57:53,053 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/132_add_timeout.yaml' 2023-04-28 05:57:53,053 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/135_add_user_policies.yaml' 2023-04-28 05:57:53,053 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/136_add_s3user_policy.yaml' 2023-04-28 05:57:53,053 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/138_add_ad_module.yaml' 2023-04-28 05:57:53,054 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/139_add_keytabs.yaml' 2023-04-28 05:57:53,054 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/140_more_32_info.yaml' 2023-04-28 05:57:53,054 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/147_no_gateway.yaml' 2023-04-28 05:57:53,054 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/150_fix_joint_nfs_version_change.yaml' 2023-04-28 05:57:53,055 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/152_s3acc_lowercase.yaml' 2023-04-28 05:57:53,055 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/153_add_quota.yaml' 2023-04-28 05:57:53,055 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/154_add_snap_now.yaml' 2023-04-28 05:57:53,055 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/158_support_lags.yaml' 2023-04-28 05:57:53,055 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/159_add_lag.yaml' 2023-04-28 05:57:53,056 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/161_add_lifecycle_info.yaml' 2023-04-28 05:57:53,056 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/162_new_lifecycle.yaml' 2023-04-28 05:57:53,056 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/163_admin_key.yaml' 2023-04-28 05:57:53,056 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/164_add_admin.yaml' 2023-04-28 05:57:53,056 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/166_lag_mac_note.yaml' 2023-04-28 05:57:53,057 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/167_fix_logins.yaml' 2023-04-28 05:57:53,057 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/169_pypureclient_fix.yaml' 2023-04-28 05:57:53,057 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/174_access_policies.yaml' 2023-04-28 05:57:53,057 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/175_throttle_support.yaml' 2023-04-28 05:57:53,057 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/176_nfs_export_policies.yaml' 2023-04-28 05:57:53,058 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/179_fqcn.yaml' 2023-04-28 05:57:53,058 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/183_v2_connections.yaml' 2023-04-28 05:57:53,058 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/184_certificate_typos.yaml' 2023-04-28 05:57:53,058 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/185_nfs_export_rule.yaml' 2023-04-28 05:57:53,058 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/186_add_tz.yaml' 2023-04-28 05:57:53,059 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/187_rename_nfs_policy.yaml' 2023-04-28 05:57:53,059 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/188_bucket_type.yaml' 2023-04-28 05:57:53,059 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/191_add_quota_info.yaml' 2023-04-28 05:57:53,059 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/194_lists_for_service.yaml' 2023-04-28 05:57:53,059 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/200_proxy.yaml' 2023-04-28 05:57:53,060 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/202_multiple_snap_rules.yaml' 2023-04-28 05:57:53,060 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/205_fix_multi_lifecycle.yaml' 2023-04-28 05:57:53,060 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/211_change_booleans.yaml' 2023-04-28 05:57:53,060 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/212_object_account_quota.yaml' 2023-04-28 05:57:53,060 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/213_sec_update.yaml' 2023-04-28 05:57:53,061 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/215_encrypt_sec_info.yaml' 2023-04-28 05:57:53,061 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/216_extra_bucket_info.yaml' 2023-04-28 05:57:53,061 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/217_inventory.yaml' 2023-04-28 05:57:53,061 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/218_object_account_info.yaml' 2023-04-28 05:57:53,061 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/220_s3user_key_fix.yaml' 2023-04-28 05:57:53,062 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/76_default_fs_size.yaml' 2023-04-28 05:57:53,062 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/77_filesystem_policies_info.yaml' 2023-04-28 05:57:53,062 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/78_update_filesystem_replica_link.yaml' 2023-04-28 05:57:53,062 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/79_hide_connect_api.yaml' 2023-04-28 05:57:53,062 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/80_support_reverse_replica_link.yaml' 2023-04-28 05:57:53,063 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/81_purefb_fs_new_options.yaml' 2023-04-28 05:57:53,063 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/83_add_certgrp.yml' 2023-04-28 05:57:53,063 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/84_add_cert.yaml' 2023-04-28 05:57:53,063 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/85_add_banner.yaml' 2023-04-28 05:57:53,063 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/86_add_syslog.yaml' 2023-04-28 05:57:53,064 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/88_add_lifecycle.yml' 2023-04-28 05:57:53,064 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/90_delete_conn_fix.yaml' 2023-04-28 05:57:53,064 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/90_imported_keys.yaml' 2023-04-28 05:57:53,064 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/92_fix_ds_update.yaml' 2023-04-28 05:57:53,064 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/96_fix_update_connection.yaml' 2023-04-28 05:57:53,065 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/97_fix_encrpyted_array_connection_info.yaml' 2023-04-28 05:57:53,065 wheel INFO adding 'ansible_collections/purestorage/flashblade/changelogs/fragments/v1.3.0_summary.yaml' 2023-04-28 05:57:53,065 wheel INFO adding 'ansible_collections/purestorage/flashblade/meta/runtime.yml' 2023-04-28 05:57:53,065 wheel INFO adding 'ansible_collections/purestorage/flashblade/playbooks/.keep' 2023-04-28 05:57:53,066 wheel INFO adding 'ansible_collections/purestorage/flashblade/playbooks/files/.keep' 2023-04-28 05:57:53,066 wheel INFO adding 'ansible_collections/purestorage/flashblade/playbooks/roles/.keep' 2023-04-28 05:57:53,066 wheel INFO adding 'ansible_collections/purestorage/flashblade/playbooks/tasks/.keep' 2023-04-28 05:57:53,066 wheel INFO adding 'ansible_collections/purestorage/flashblade/playbooks/templates/.keep' 2023-04-28 05:57:53,067 wheel INFO adding 'ansible_collections/purestorage/flashblade/playbooks/vars/.keep' 2023-04-28 05:57:53,067 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/doc_fragments/purestorage.py' 2023-04-28 05:57:53,067 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/module_utils/purefb.py' 2023-04-28 05:57:53,067 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_ad.py' 2023-04-28 05:57:53,068 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_admin.py' 2023-04-28 05:57:53,068 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_alert.py' 2023-04-28 05:57:53,068 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_apiclient.py' 2023-04-28 05:57:53,068 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_banner.py' 2023-04-28 05:57:53,069 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_bladename.py' 2023-04-28 05:57:53,069 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_bucket.py' 2023-04-28 05:57:53,069 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_bucket_replica.py' 2023-04-28 05:57:53,069 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_certgrp.py' 2023-04-28 05:57:53,070 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_certs.py' 2023-04-28 05:57:53,070 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_connect.py' 2023-04-28 05:57:53,070 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_dns.py' 2023-04-28 05:57:53,071 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_ds.py' 2023-04-28 05:57:53,071 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_dsrole.py' 2023-04-28 05:57:53,071 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_eula.py' 2023-04-28 05:57:53,072 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_fs.py' 2023-04-28 05:57:53,072 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_fs_replica.py' 2023-04-28 05:57:53,072 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_groupquota.py' 2023-04-28 05:57:53,073 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_info.py' 2023-04-28 05:57:53,073 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_inventory.py' 2023-04-28 05:57:53,073 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_keytabs.py' 2023-04-28 05:57:53,074 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_lag.py' 2023-04-28 05:57:53,074 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_lifecycle.py' 2023-04-28 05:57:53,074 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_messages.py' 2023-04-28 05:57:53,074 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_network.py' 2023-04-28 05:57:53,075 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_ntp.py' 2023-04-28 05:57:53,075 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_phonehome.py' 2023-04-28 05:57:53,075 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_pingtrace.py' 2023-04-28 05:57:53,076 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py' 2023-04-28 05:57:53,076 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_proxy.py' 2023-04-28 05:57:53,076 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_ra.py' 2023-04-28 05:57:53,077 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_remote_cred.py' 2023-04-28 05:57:53,077 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_s3acc.py' 2023-04-28 05:57:53,077 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_s3user.py' 2023-04-28 05:57:53,077 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_smtp.py' 2023-04-28 05:57:53,078 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_snap.py' 2023-04-28 05:57:53,078 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_snmp_agent.py' 2023-04-28 05:57:53,078 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_snmp_mgr.py' 2023-04-28 05:57:53,079 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_subnet.py' 2023-04-28 05:57:53,079 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_syslog.py' 2023-04-28 05:57:53,079 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_target.py' 2023-04-28 05:57:53,079 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_timeout.py' 2023-04-28 05:57:53,080 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_tz.py' 2023-04-28 05:57:53,080 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_user.py' 2023-04-28 05:57:53,080 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_userpolicy.py' 2023-04-28 05:57:53,080 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_userquota.py' 2023-04-28 05:57:53,081 wheel INFO adding 'ansible_collections/purestorage/flashblade/plugins/modules/purefb_virtualhost.py' 2023-04-28 05:57:53,081 wheel INFO adding 'ansible_collections/purestorage/flashblade/roles/.keep' 2023-04-28 05:57:53,081 wheel INFO adding 'ansible_collections/purestorage/fusion/CHANGELOG.rst' 2023-04-28 05:57:53,081 wheel INFO adding 'ansible_collections/purestorage/fusion/COPYING.GPLv3' 2023-04-28 05:57:53,082 wheel INFO adding 'ansible_collections/purestorage/fusion/FILES.json' 2023-04-28 05:57:53,082 wheel INFO adding 'ansible_collections/purestorage/fusion/MANIFEST.json' 2023-04-28 05:57:53,082 wheel INFO adding 'ansible_collections/purestorage/fusion/README.md' 2023-04-28 05:57:53,083 wheel INFO adding 'ansible_collections/purestorage/fusion/changelogs/101_improve_duration_parsing.yml' 2023-04-28 05:57:53,083 wheel INFO adding 'ansible_collections/purestorage/fusion/changelogs/109_unify_storage_classes_key_in_fusion_info.yml' 2023-04-28 05:57:53,083 wheel INFO adding 'ansible_collections/purestorage/fusion/changelogs/112_unify_hardware_types_key_in_fusion_info.yml' 2023-04-28 05:57:53,083 wheel INFO adding 'ansible_collections/purestorage/fusion/changelogs/99_update_protection_policy_retention_description.yaml' 2023-04-28 05:57:53,084 wheel INFO adding 'ansible_collections/purestorage/fusion/changelogs/changelog.yaml' 2023-04-28 05:57:53,084 wheel INFO adding 'ansible_collections/purestorage/fusion/changelogs/config.yaml' 2023-04-28 05:57:53,084 wheel INFO adding 'ansible_collections/purestorage/fusion/meta/runtime.yml' 2023-04-28 05:57:53,084 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/create_array.yml' 2023-04-28 05:57:53,085 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/create_availability_zone.yml' 2023-04-28 05:57:53,085 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/create_tenant_space.yml' 2023-04-28 05:57:53,085 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_all.yml' 2023-04-28 05:57:53,085 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_api_clients.yml' 2023-04-28 05:57:53,085 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_arrays.yml' 2023-04-28 05:57:53,086 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_availability_zones.yml' 2023-04-28 05:57:53,086 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_hardware_types.yml' 2023-04-28 05:57:53,086 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_hosts.yml' 2023-04-28 05:57:53,086 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_interfaces.yml' 2023-04-28 05:57:53,086 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_network_interface_groups.yml' 2023-04-28 05:57:53,087 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_placement_groups.yml' 2023-04-28 05:57:53,087 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_protection_policies.yml' 2023-04-28 05:57:53,087 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_roles.yml' 2023-04-28 05:57:53,087 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_snapshots.yml' 2023-04-28 05:57:53,088 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_storage_classes.yml' 2023-04-28 05:57:53,088 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_storage_endpoints.yml' 2023-04-28 05:57:53,088 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_storage_services.yml' 2023-04-28 05:57:53,088 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_tenant_spaces.yml' 2023-04-28 05:57:53,088 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_tenants.yml' 2023-04-28 05:57:53,089 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_users.yml' 2023-04-28 05:57:53,089 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/list_volumes.yml' 2023-04-28 05:57:53,089 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/make_tenant_admin.yml' 2023-04-28 05:57:53,089 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/remove_array.yml' 2023-04-28 05:57:53,089 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/setup_infrastructure.yml' 2023-04-28 05:57:53,090 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/setup_protection_policies.yml' 2023-04-28 05:57:53,090 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/setup_storage_service_class.yml' 2023-04-28 05:57:53,090 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/simple/setup_workloads.yml' 2023-04-28 05:57:53,090 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/tasks/.keep' 2023-04-28 05:57:53,090 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/templates/.keep' 2023-04-28 05:57:53,091 wheel INFO adding 'ansible_collections/purestorage/fusion/playbooks/vars/.keep' 2023-04-28 05:57:53,091 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/doc_fragments/purestorage.py' 2023-04-28 05:57:53,091 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/inventory/__init__.py' 2023-04-28 05:57:53,092 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/errors.py' 2023-04-28 05:57:53,092 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/fusion.py' 2023-04-28 05:57:53,092 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/getters.py' 2023-04-28 05:57:53,092 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/networking.py' 2023-04-28 05:57:53,092 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/operations.py' 2023-04-28 05:57:53,093 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/parsing.py' 2023-04-28 05:57:53,093 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/prerequisites.py' 2023-04-28 05:57:53,093 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/module_utils/startup.py' 2023-04-28 05:57:53,093 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_api_client.py' 2023-04-28 05:57:53,094 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_array.py' 2023-04-28 05:57:53,094 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_az.py' 2023-04-28 05:57:53,094 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_hap.py' 2023-04-28 05:57:53,094 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_hw.py' 2023-04-28 05:57:53,095 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_info.py' 2023-04-28 05:57:53,095 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_ni.py' 2023-04-28 05:57:53,095 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_nig.py' 2023-04-28 05:57:53,096 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_pg.py' 2023-04-28 05:57:53,096 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_pp.py' 2023-04-28 05:57:53,096 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_ra.py' 2023-04-28 05:57:53,096 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_region.py' 2023-04-28 05:57:53,097 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_sc.py' 2023-04-28 05:57:53,097 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_se.py' 2023-04-28 05:57:53,097 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_ss.py' 2023-04-28 05:57:53,097 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_tenant.py' 2023-04-28 05:57:53,098 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_tn.py' 2023-04-28 05:57:53,098 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_ts.py' 2023-04-28 05:57:53,098 wheel INFO adding 'ansible_collections/purestorage/fusion/plugins/modules/fusion_volume.py' 2023-04-28 05:57:53,099 wheel INFO adding 'ansible_collections/sensu/sensu_go/CODE_OF_CONDUCT.md' 2023-04-28 05:57:53,099 wheel INFO adding 'ansible_collections/sensu/sensu_go/COPYING' 2023-04-28 05:57:53,099 wheel INFO adding 'ansible_collections/sensu/sensu_go/FILES.json' 2023-04-28 05:57:53,100 wheel INFO adding 'ansible_collections/sensu/sensu_go/MANIFEST.json' 2023-04-28 05:57:53,100 wheel INFO adding 'ansible_collections/sensu/sensu_go/Makefile' 2023-04-28 05:57:53,101 wheel INFO adding 'ansible_collections/sensu/sensu_go/README.md' 2023-04-28 05:57:53,101 wheel INFO adding 'ansible_collections/sensu/sensu_go/collection.requirements' 2023-04-28 05:57:53,101 wheel INFO adding 'ansible_collections/sensu/sensu_go/docs.requirements' 2023-04-28 05:57:53,101 wheel INFO adding 'ansible_collections/sensu/sensu_go/integration.requirements' 2023-04-28 05:57:53,101 wheel INFO adding 'ansible_collections/sensu/sensu_go/pytest.ini' 2023-04-28 05:57:53,102 wheel INFO adding 'ansible_collections/sensu/sensu_go/sanity.requirements' 2023-04-28 05:57:53,102 wheel INFO adding 'ansible_collections/sensu/sensu_go/changelogs/changelog.yaml' 2023-04-28 05:57:53,102 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/alma-8.docker' 2023-04-28 05:57:53,102 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/amazon-1.docker' 2023-04-28 05:57:53,103 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/amazon-2.docker' 2023-04-28 05:57:53,103 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/build-all.sh' 2023-04-28 05:57:53,103 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/build.sh' 2023-04-28 05:57:53,103 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/centos-6.docker' 2023-04-28 05:57:53,103 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/centos-7.docker' 2023-04-28 05:57:53,104 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/centos-8.docker' 2023-04-28 05:57:53,104 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/debian-10.docker' 2023-04-28 05:57:53,104 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/debian-9.docker' 2023-04-28 05:57:53,104 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/oracle-8.docker' 2023-04-28 05:57:53,104 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/redhat-7.docker' 2023-04-28 05:57:53,105 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/rocky-8.docker' 2023-04-28 05:57:53,105 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-5.14.2.docker' 2023-04-28 05:57:53,105 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-5.21.3.docker' 2023-04-28 05:57:53,105 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.2.5.docker' 2023-04-28 05:57:53,105 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.3.0.docker' 2023-04-28 05:57:53,106 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.4.3.docker' 2023-04-28 05:57:53,106 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.5.5.docker' 2023-04-28 05:57:53,106 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.6.2.docker' 2023-04-28 05:57:53,106 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.7.5.docker' 2023-04-28 05:57:53,106 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.8.2.docker' 2023-04-28 05:57:53,107 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/sensu-6.9.0.docker' 2023-04-28 05:57:53,107 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/ubuntu-14.04.docker' 2023-04-28 05:57:53,107 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/ubuntu-16.04.docker' 2023-04-28 05:57:53,107 wheel INFO adding 'ansible_collections/sensu/sensu_go/docker/ubuntu-18.04.docker' 2023-04-28 05:57:53,107 wheel INFO adding 'ansible_collections/sensu/sensu_go/meta/execution-environment.yml' 2023-04-28 05:57:53,108 wheel INFO adding 'ansible_collections/sensu/sensu_go/meta/runtime.yml' 2023-04-28 05:57:53,108 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/action/bonsai_asset.py' 2023-04-28 05:57:53,108 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/annotations.py' 2023-04-28 05:57:53,108 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/auth.py' 2023-04-28 05:57:53,109 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/info.py' 2023-04-28 05:57:53,109 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/labels.py' 2023-04-28 05:57:53,109 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/name.py' 2023-04-28 05:57:53,109 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/namespace.py' 2023-04-28 05:57:53,110 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/requirements.py' 2023-04-28 05:57:53,110 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/secrets.py' 2023-04-28 05:57:53,110 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/doc_fragments/state.py' 2023-04-28 05:57:53,110 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/filter/backends.py' 2023-04-28 05:57:53,110 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/filter/package_name.py' 2023-04-28 05:57:53,111 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/arguments.py' 2023-04-28 05:57:53,111 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/bonsai.py' 2023-04-28 05:57:53,111 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/client.py' 2023-04-28 05:57:53,111 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/debug.py' 2023-04-28 05:57:53,112 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/errors.py' 2023-04-28 05:57:53,112 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/http.py' 2023-04-28 05:57:53,112 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/role_utils.py' 2023-04-28 05:57:53,112 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/module_utils/utils.py' 2023-04-28 05:57:53,113 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/ad_auth_provider.py' 2023-04-28 05:57:53,113 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/asset.py' 2023-04-28 05:57:53,113 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/asset_info.py' 2023-04-28 05:57:53,113 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/auth_provider_info.py' 2023-04-28 05:57:53,114 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/bonsai_asset.py' 2023-04-28 05:57:53,114 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/check.py' 2023-04-28 05:57:53,114 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/check_info.py' 2023-04-28 05:57:53,114 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/cluster.py' 2023-04-28 05:57:53,114 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/cluster_info.py' 2023-04-28 05:57:53,115 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/cluster_role.py' 2023-04-28 05:57:53,115 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_binding.py' 2023-04-28 05:57:53,115 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_binding_info.py' 2023-04-28 05:57:53,115 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/cluster_role_info.py' 2023-04-28 05:57:53,116 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/datastore.py' 2023-04-28 05:57:53,116 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/datastore_info.py' 2023-04-28 05:57:53,116 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/entity.py' 2023-04-28 05:57:53,116 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/entity_info.py' 2023-04-28 05:57:53,117 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/etcd_replicator.py' 2023-04-28 05:57:53,117 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/etcd_replicator_info.py' 2023-04-28 05:57:53,117 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/event.py' 2023-04-28 05:57:53,117 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/event_info.py' 2023-04-28 05:57:53,117 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/filter.py' 2023-04-28 05:57:53,118 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/filter_info.py' 2023-04-28 05:57:53,118 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/handler_info.py' 2023-04-28 05:57:53,118 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/handler_set.py' 2023-04-28 05:57:53,118 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/hook.py' 2023-04-28 05:57:53,119 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/hook_info.py' 2023-04-28 05:57:53,119 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/ldap_auth_provider.py' 2023-04-28 05:57:53,119 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/mutator.py' 2023-04-28 05:57:53,119 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/mutator_info.py' 2023-04-28 05:57:53,120 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/namespace.py' 2023-04-28 05:57:53,120 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/namespace_info.py' 2023-04-28 05:57:53,120 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/oidc_auth_provider.py' 2023-04-28 05:57:53,120 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/pipe_handler.py' 2023-04-28 05:57:53,120 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/role.py' 2023-04-28 05:57:53,121 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/role_binding.py' 2023-04-28 05:57:53,121 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/role_binding_info.py' 2023-04-28 05:57:53,121 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/role_info.py' 2023-04-28 05:57:53,121 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/secret.py' 2023-04-28 05:57:53,122 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/secret_info.py' 2023-04-28 05:57:53,122 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_env.py' 2023-04-28 05:57:53,122 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_info.py' 2023-04-28 05:57:53,122 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/secrets_provider_vault.py' 2023-04-28 05:57:53,122 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/silence.py' 2023-04-28 05:57:53,123 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/silence_info.py' 2023-04-28 05:57:53,123 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/socket_handler.py' 2023-04-28 05:57:53,123 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/tessen.py' 2023-04-28 05:57:53,123 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/user.py' 2023-04-28 05:57:53,124 wheel INFO adding 'ansible_collections/sensu/sensu_go/plugins/modules/user_info.py' 2023-04-28 05:57:53,124 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/README.md' 2023-04-28 05:57:53,124 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/defaults/main.yml' 2023-04-28 05:57:53,124 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/handlers/main.yml' 2023-04-28 05:57:53,125 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/meta/argument_specs.yml' 2023-04-28 05:57:53,125 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/meta/main.yml' 2023-04-28 05:57:53,125 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/tasks/configure.yml' 2023-04-28 05:57:53,125 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/tasks/main.yml' 2023-04-28 05:57:53,126 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/tasks/start.yml' 2023-04-28 05:57:53,126 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/tasks/linux/configure.yml' 2023-04-28 05:57:53,126 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/tasks/windows/configure.yml' 2023-04-28 05:57:53,126 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/templates/agent.yml.j2' 2023-04-28 05:57:53,127 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/vars/linux.yml' 2023-04-28 05:57:53,127 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/vars/main.yml' 2023-04-28 05:57:53,127 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/agent/vars/windows.yml' 2023-04-28 05:57:53,127 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/README.md' 2023-04-28 05:57:53,127 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/defaults/main.yml' 2023-04-28 05:57:53,128 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/handlers/main.yml' 2023-04-28 05:57:53,128 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/meta/argument_specs.yml' 2023-04-28 05:57:53,128 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/meta/main.yml' 2023-04-28 05:57:53,128 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/tasks/configure.yml' 2023-04-28 05:57:53,129 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/tasks/main.yml' 2023-04-28 05:57:53,129 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/tasks/start.yml' 2023-04-28 05:57:53,130 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/templates/backend.yml.j2' 2023-04-28 05:57:53,130 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/backend/vars/main.yml' 2023-04-28 05:57:53,130 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/README.md' 2023-04-28 05:57:53,130 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/defaults/main.yml' 2023-04-28 05:57:53,131 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/meta/argument_specs.yml' 2023-04-28 05:57:53,131 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/meta/main.yml' 2023-04-28 05:57:53,131 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/main.yml' 2023-04-28 05:57:53,131 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/packages.yml' 2023-04-28 05:57:53,131 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/repositories.yml' 2023-04-28 05:57:53,132 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/apt/install.yml' 2023-04-28 05:57:53,132 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/apt/prepare.yml' 2023-04-28 05:57:53,132 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/dnf/install.yml' 2023-04-28 05:57:53,132 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/dnf/prepare.yml' 2023-04-28 05:57:53,133 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/msi/install.yml' 2023-04-28 05:57:53,133 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/yum/install.yml' 2023-04-28 05:57:53,133 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/tasks/yum/prepare.yml' 2023-04-28 05:57:53,133 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/Alma.yml' 2023-04-28 05:57:53,133 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/Amazon.yml' 2023-04-28 05:57:53,134 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/CentOS.yml' 2023-04-28 05:57:53,134 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/Debian.yml' 2023-04-28 05:57:53,134 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/OracleLinux.yml' 2023-04-28 05:57:53,134 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/RedHat.yml' 2023-04-28 05:57:53,135 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/Rocky.yml' 2023-04-28 05:57:53,135 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/Ubuntu.yml' 2023-04-28 05:57:53,135 wheel INFO adding 'ansible_collections/sensu/sensu_go/roles/install/vars/Windows.yml' 2023-04-28 05:57:53,135 wheel INFO adding 'ansible_collections/sensu/sensu_go/tools/windows-versions.py' 2023-04-28 05:57:53,136 wheel INFO adding 'ansible_collections/sensu/sensu_go/vagrant/windows/Vagrantfile' 2023-04-28 05:57:53,136 wheel INFO adding 'ansible_collections/sensu/sensu_go/vagrant/windows/back.yaml' 2023-04-28 05:57:53,136 wheel INFO adding 'ansible_collections/sensu/sensu_go/vagrant/windows/inventory.yaml' 2023-04-28 05:57:53,136 wheel INFO adding 'ansible_collections/sensu/sensu_go/vagrant/windows/play.yaml' 2023-04-28 05:57:53,136 wheel INFO adding 'ansible_collections/splunk/es/CHANGELOG.rst' 2023-04-28 05:57:53,137 wheel INFO adding 'ansible_collections/splunk/es/FILES.json' 2023-04-28 05:57:53,137 wheel INFO adding 'ansible_collections/splunk/es/LICENSE' 2023-04-28 05:57:53,138 wheel INFO adding 'ansible_collections/splunk/es/MANIFEST.json' 2023-04-28 05:57:53,138 wheel INFO adding 'ansible_collections/splunk/es/README.md' 2023-04-28 05:57:53,138 wheel INFO adding 'ansible_collections/splunk/es/bindep.txt' 2023-04-28 05:57:53,138 wheel INFO adding 'ansible_collections/splunk/es/pyproject.toml' 2023-04-28 05:57:53,139 wheel INFO adding 'ansible_collections/splunk/es/requirements.txt' 2023-04-28 05:57:53,139 wheel INFO adding 'ansible_collections/splunk/es/test-requirements.txt' 2023-04-28 05:57:53,139 wheel INFO adding 'ansible_collections/splunk/es/tox.ini' 2023-04-28 05:57:53,139 wheel INFO adding 'ansible_collections/splunk/es/changelogs/changelog.yaml' 2023-04-28 05:57:53,139 wheel INFO adding 'ansible_collections/splunk/es/changelogs/config.yaml' 2023-04-28 05:57:53,140 wheel INFO adding 'ansible_collections/splunk/es/changelogs/fragments/.keep' 2023-04-28 05:57:53,140 wheel INFO adding 'ansible_collections/splunk/es/meta/runtime.yml' 2023-04-28 05:57:53,140 wheel INFO adding 'ansible_collections/splunk/es/plugins/action/splunk_adaptive_response_notable_events.py' 2023-04-28 05:57:53,141 wheel INFO adding 'ansible_collections/splunk/es/plugins/action/splunk_correlation_searches.py' 2023-04-28 05:57:53,141 wheel INFO adding 'ansible_collections/splunk/es/plugins/action/splunk_data_inputs_monitor.py' 2023-04-28 05:57:53,141 wheel INFO adding 'ansible_collections/splunk/es/plugins/action/splunk_data_inputs_network.py' 2023-04-28 05:57:53,142 wheel INFO adding 'ansible_collections/splunk/es/plugins/httpapi/splunk.py' 2023-04-28 05:57:53,142 wheel INFO adding 'ansible_collections/splunk/es/plugins/module_utils/splunk.py' 2023-04-28 05:57:53,142 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/adaptive_response_notable_event.py' 2023-04-28 05:57:53,142 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/correlation_search.py' 2023-04-28 05:57:53,143 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/correlation_search_info.py' 2023-04-28 05:57:53,143 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/data_input_monitor.py' 2023-04-28 05:57:53,143 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/data_input_network.py' 2023-04-28 05:57:53,143 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_adaptive_response_notable_event.py' 2023-04-28 05:57:53,144 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_adaptive_response_notable_events.py' 2023-04-28 05:57:53,144 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_correlation_search.py' 2023-04-28 05:57:53,144 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_correlation_search_info.py' 2023-04-28 05:57:53,145 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_correlation_searches.py' 2023-04-28 05:57:53,145 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_data_input_monitor.py' 2023-04-28 05:57:53,145 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_data_input_network.py' 2023-04-28 05:57:53,145 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_data_inputs_monitor.py' 2023-04-28 05:57:53,146 wheel INFO adding 'ansible_collections/splunk/es/plugins/modules/splunk_data_inputs_network.py' 2023-04-28 05:57:53,146 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/CHANGELOG.md' 2023-04-28 05:57:53,147 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/CHANGELOG.rst' 2023-04-28 05:57:53,147 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/CODE_OF_CONDUCT.md' 2023-04-28 05:57:53,147 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/CONTRIBUTING.md' 2023-04-28 05:57:53,147 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/FILES.json' 2023-04-28 05:57:53,148 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/LICENSE' 2023-04-28 05:57:53,148 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/MANIFEST.json' 2023-04-28 05:57:53,148 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/README.md' 2023-04-28 05:57:53,148 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/renovate.json' 2023-04-28 05:57:53,149 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/changelogs/.plugin-cache.yaml' 2023-04-28 05:57:53,149 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/changelogs/changelog.yaml' 2023-04-28 05:57:53,149 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/changelogs/config.yaml' 2023-04-28 05:57:53,150 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_command.yml' 2023-04-28 05:57:53,150 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_info.yml' 2023-04-28 05:57:53,150 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_template.yml' 2023-04-28 05:57:53,150 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_command_template_info.yml' 2023-04-28 05:57:53,150 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_endpoint.yml' 2023-04-28 05:57:53,151 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_endpoint_info.yml' 2023-04-28 05:57:53,151 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_host.yml' 2023-04-28 05:57:53,151 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_info.yml' 2023-04-28 05:57:53,151 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_template.yml' 2023-04-28 05:57:53,151 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_host_template_info.yml' 2023-04-28 05:57:53,152 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_hostgroup.yml' 2023-04-28 05:57:53,152 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_hostgroup_info.yml' 2023-04-28 05:57:53,152 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification.yml' 2023-04-28 05:57:53,152 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_info.yml' 2023-04-28 05:57:53,153 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_template.yml' 2023-04-28 05:57:53,153 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_notification_template_info.yml' 2023-04-28 05:57:53,153 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_scheduled_downtime.yml' 2023-04-28 05:57:53,153 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_service.yml' 2023-04-28 05:57:53,153 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_apply.yml' 2023-04-28 05:57:53,154 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_apply_info.yml' 2023-04-28 05:57:53,154 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_info.yml' 2023-04-28 05:57:53,154 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_template.yml' 2023-04-28 05:57:53,154 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_service_template_info.yml' 2023-04-28 05:57:53,154 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_servicegroup.yml' 2023-04-28 05:57:53,155 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_servicegroup_info.yml' 2023-04-28 05:57:53,155 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_serviceset.yml' 2023-04-28 05:57:53,155 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod.yml' 2023-04-28 05:57:53,155 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_info.yml' 2023-04-28 05:57:53,155 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_template.yml' 2023-04-28 05:57:53,156 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_timeperiod_template_info.yml' 2023-04-28 05:57:53,156 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_user.yml' 2023-04-28 05:57:53,156 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_group.yml' 2023-04-28 05:57:53,156 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_group_info.yml' 2023-04-28 05:57:53,156 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_info.yml' 2023-04-28 05:57:53,157 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_template.yml' 2023-04-28 05:57:53,157 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_user_template_info.yml' 2023-04-28 05:57:53,157 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_zone.yml' 2023-04-28 05:57:53,157 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/examples/icinga_zone_info.yml' 2023-04-28 05:57:53,157 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/meta/runtime.yml' 2023-04-28 05:57:53,158 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments/common_options.py' 2023-04-28 05:57:53,158 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/inventory/icinga_director_inventory.py' 2023-04-28 05:57:53,158 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/module_utils/icinga.py' 2023-04-28 05:57:53,159 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command.py' 2023-04-28 05:57:53,159 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_info.py' 2023-04-28 05:57:53,159 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_template.py' 2023-04-28 05:57:53,159 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_command_template_info.py' 2023-04-28 05:57:53,160 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_endpoint.py' 2023-04-28 05:57:53,160 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_endpoint_info.py' 2023-04-28 05:57:53,160 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host.py' 2023-04-28 05:57:53,160 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_info.py' 2023-04-28 05:57:53,161 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_template.py' 2023-04-28 05:57:53,161 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_host_template_info.py' 2023-04-28 05:57:53,161 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_hostgroup.py' 2023-04-28 05:57:53,161 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_hostgroup_info.py' 2023-04-28 05:57:53,162 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification.py' 2023-04-28 05:57:53,162 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_info.py' 2023-04-28 05:57:53,162 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_template.py' 2023-04-28 05:57:53,162 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_notification_template_info.py' 2023-04-28 05:57:53,163 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_scheduled_downtime.py' 2023-04-28 05:57:53,163 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service.py' 2023-04-28 05:57:53,163 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_apply.py' 2023-04-28 05:57:53,163 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_apply_info.py' 2023-04-28 05:57:53,164 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_info.py' 2023-04-28 05:57:53,164 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_template.py' 2023-04-28 05:57:53,164 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_service_template_info.py' 2023-04-28 05:57:53,164 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_servicegroup.py' 2023-04-28 05:57:53,165 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_servicegroup_info.py' 2023-04-28 05:57:53,165 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_serviceset.py' 2023-04-28 05:57:53,165 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod.py' 2023-04-28 05:57:53,165 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_info.py' 2023-04-28 05:57:53,166 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_template.py' 2023-04-28 05:57:53,166 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_timeperiod_template_info.py' 2023-04-28 05:57:53,166 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user.py' 2023-04-28 05:57:53,166 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_group.py' 2023-04-28 05:57:53,167 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_group_info.py' 2023-04-28 05:57:53,167 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_info.py' 2023-04-28 05:57:53,167 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_template.py' 2023-04-28 05:57:53,167 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_user_template_info.py' 2023-04-28 05:57:53,167 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_zone.py' 2023-04-28 05:57:53,168 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/plugins/modules/icinga_zone_info.py' 2023-04-28 05:57:53,168 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/README.md' 2023-04-28 05:57:53,168 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/defaults/main.yml' 2023-04-28 05:57:53,169 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/meta/main.yml' 2023-04-28 05:57:53,169 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_command.yml' 2023-04-28 05:57:53,169 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_command_template.yml' 2023-04-28 05:57:53,169 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_endpoint.yml' 2023-04-28 05:57:53,169 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_host.yml' 2023-04-28 05:57:53,170 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_host_template.yml' 2023-04-28 05:57:53,170 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_hostgroup.yml' 2023-04-28 05:57:53,170 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_notification.yml' 2023-04-28 05:57:53,170 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_notification_template.yml' 2023-04-28 05:57:53,171 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_scheduled_downtime.yml' 2023-04-28 05:57:53,171 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service.yml' 2023-04-28 05:57:53,171 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service_apply.yml' 2023-04-28 05:57:53,171 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_service_template.yml' 2023-04-28 05:57:53,171 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_servicegroup.yml' 2023-04-28 05:57:53,172 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_serviceset.yml' 2023-04-28 05:57:53,172 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_timeperiod.yml' 2023-04-28 05:57:53,172 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_user.yml' 2023-04-28 05:57:53,172 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_user_template.yml' 2023-04-28 05:57:53,172 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/icinga_zone.yml' 2023-04-28 05:57:53,173 wheel INFO adding 'ansible_collections/t_systems_mms/icinga_director/roles/ansible_icinga/tasks/main.yml' 2023-04-28 05:57:53,173 wheel INFO adding 'ansible_collections/theforeman/foreman/CHANGELOG.rst' 2023-04-28 05:57:53,173 wheel INFO adding 'ansible_collections/theforeman/foreman/FILES.json' 2023-04-28 05:57:53,174 wheel INFO adding 'ansible_collections/theforeman/foreman/LICENSE' 2023-04-28 05:57:53,174 wheel INFO adding 'ansible_collections/theforeman/foreman/MANIFEST.json' 2023-04-28 05:57:53,174 wheel INFO adding 'ansible_collections/theforeman/foreman/PSF-license.txt' 2023-04-28 05:57:53,175 wheel INFO adding 'ansible_collections/theforeman/foreman/README.md' 2023-04-28 05:57:53,175 wheel INFO adding 'ansible_collections/theforeman/foreman/bindep.txt' 2023-04-28 05:57:53,175 wheel INFO adding 'ansible_collections/theforeman/foreman/requirements.txt' 2023-04-28 05:57:53,175 wheel INFO adding 'ansible_collections/theforeman/foreman/changelogs/changelog.yaml' 2023-04-28 05:57:53,176 wheel INFO adding 'ansible_collections/theforeman/foreman/meta/execution-environment.yml' 2023-04-28 05:57:53,176 wheel INFO adding 'ansible_collections/theforeman/foreman/meta/runtime.yml' 2023-04-28 05:57:53,176 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/callback/foreman.py' 2023-04-28 05:57:53,177 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/doc_fragments/foreman.py' 2023-04-28 05:57:53,177 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/filter/cp_label.yml' 2023-04-28 05:57:53,177 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/filter/foreman.py' 2023-04-28 05:57:53,178 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/inventory/foreman.py' 2023-04-28 05:57:53,178 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/module_utils/_apypie.py' 2023-04-28 05:57:53,178 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/module_utils/_version.py' 2023-04-28 05:57:53,179 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/module_utils/foreman_helper.py' 2023-04-28 05:57:53,180 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/activation_key.py' 2023-04-28 05:57:53,180 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/architecture.py' 2023-04-28 05:57:53,180 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/auth_source_ldap.py' 2023-04-28 05:57:53,180 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/bookmark.py' 2023-04-28 05:57:53,181 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/compute_attribute.py' 2023-04-28 05:57:53,181 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/compute_profile.py' 2023-04-28 05:57:53,181 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/compute_resource.py' 2023-04-28 05:57:53,181 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/config_group.py' 2023-04-28 05:57:53,182 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_credential.py' 2023-04-28 05:57:53,182 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_export_info.py' 2023-04-28 05:57:53,182 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_export_library.py' 2023-04-28 05:57:53,182 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_export_repository.py' 2023-04-28 05:57:53,183 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_export_version.py' 2023-04-28 05:57:53,183 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_upload.py' 2023-04-28 05:57:53,183 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view.py' 2023-04-28 05:57:53,183 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view_filter.py' 2023-04-28 05:57:53,184 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_info.py' 2023-04-28 05:57:53,184 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_rule.py' 2023-04-28 05:57:53,184 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view_filter_rule_info.py' 2023-04-28 05:57:53,184 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view_info.py' 2023-04-28 05:57:53,185 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view_version.py' 2023-04-28 05:57:53,185 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/content_view_version_info.py' 2023-04-28 05:57:53,185 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/discovery_rule.py' 2023-04-28 05:57:53,185 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/domain.py' 2023-04-28 05:57:53,185 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/domain_info.py' 2023-04-28 05:57:53,186 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/external_usergroup.py' 2023-04-28 05:57:53,186 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/global_parameter.py' 2023-04-28 05:57:53,186 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/hardware_model.py' 2023-04-28 05:57:53,186 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/host.py' 2023-04-28 05:57:53,187 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/host_collection.py' 2023-04-28 05:57:53,187 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/host_errata_info.py' 2023-04-28 05:57:53,187 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/host_info.py' 2023-04-28 05:57:53,187 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/host_power.py' 2023-04-28 05:57:53,188 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/hostgroup.py' 2023-04-28 05:57:53,188 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/hostgroup_info.py' 2023-04-28 05:57:53,188 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/http_proxy.py' 2023-04-28 05:57:53,188 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/image.py' 2023-04-28 05:57:53,189 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/installation_medium.py' 2023-04-28 05:57:53,189 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/job_invocation.py' 2023-04-28 05:57:53,189 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/job_template.py' 2023-04-28 05:57:53,189 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/lifecycle_environment.py' 2023-04-28 05:57:53,190 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/location.py' 2023-04-28 05:57:53,190 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/operatingsystem.py' 2023-04-28 05:57:53,190 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/organization.py' 2023-04-28 05:57:53,190 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/organization_info.py' 2023-04-28 05:57:53,191 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/os_default_template.py' 2023-04-28 05:57:53,191 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/partition_table.py' 2023-04-28 05:57:53,191 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/product.py' 2023-04-28 05:57:53,191 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/provisioning_template.py' 2023-04-28 05:57:53,192 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/puppet_environment.py' 2023-04-28 05:57:53,192 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/puppetclasses_import.py' 2023-04-28 05:57:53,192 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/realm.py' 2023-04-28 05:57:53,192 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/redhat_manifest.py' 2023-04-28 05:57:53,192 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/repository.py' 2023-04-28 05:57:53,193 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/repository_info.py' 2023-04-28 05:57:53,193 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/repository_set.py' 2023-04-28 05:57:53,193 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/repository_set_info.py' 2023-04-28 05:57:53,193 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/repository_sync.py' 2023-04-28 05:57:53,194 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/resource_info.py' 2023-04-28 05:57:53,194 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/role.py' 2023-04-28 05:57:53,194 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/scap_content.py' 2023-04-28 05:57:53,194 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/scap_tailoring_file.py' 2023-04-28 05:57:53,195 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/scc_account.py' 2023-04-28 05:57:53,195 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/scc_product.py' 2023-04-28 05:57:53,195 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/setting.py' 2023-04-28 05:57:53,195 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/setting_info.py' 2023-04-28 05:57:53,196 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/smart_class_parameter.py' 2023-04-28 05:57:53,196 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/smart_proxy.py' 2023-04-28 05:57:53,196 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/snapshot.py' 2023-04-28 05:57:53,196 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/snapshot_info.py' 2023-04-28 05:57:53,197 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/status_info.py' 2023-04-28 05:57:53,197 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/subnet.py' 2023-04-28 05:57:53,197 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/subnet_info.py' 2023-04-28 05:57:53,197 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/subscription_info.py' 2023-04-28 05:57:53,198 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/subscription_manifest.py' 2023-04-28 05:57:53,198 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/sync_plan.py' 2023-04-28 05:57:53,198 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/templates_import.py' 2023-04-28 05:57:53,198 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/user.py' 2023-04-28 05:57:53,199 wheel INFO adding 'ansible_collections/theforeman/foreman/plugins/modules/usergroup.py' 2023-04-28 05:57:53,199 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/activation_keys/README.md' 2023-04-28 05:57:53,199 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/activation_keys/tasks/main.yml' 2023-04-28 05:57:53,199 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/auth_sources_ldap/README.md' 2023-04-28 05:57:53,200 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/auth_sources_ldap/tasks/main.yml' 2023-04-28 05:57:53,200 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/compute_profiles/README.md' 2023-04-28 05:57:53,200 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/compute_profiles/tasks/main.yml' 2023-04-28 05:57:53,200 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/compute_resources/README.md' 2023-04-28 05:57:53,201 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/compute_resources/tasks/main.yml' 2023-04-28 05:57:53,201 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_credentials/README.md' 2023-04-28 05:57:53,201 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_credentials/tasks/main.yml' 2023-04-28 05:57:53,201 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_rhel/README.md' 2023-04-28 05:57:53,202 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_rhel/defaults/main.yml' 2023-04-28 05:57:53,202 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_rhel/tasks/main.yml' 2023-04-28 05:57:53,202 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_view_publish/README.md' 2023-04-28 05:57:53,203 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_view_publish/tasks/main.yml' 2023-04-28 05:57:53,203 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/README.md' 2023-04-28 05:57:53,203 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/delete_cv_versions.yml' 2023-04-28 05:57:53,203 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/find_and_delete_unused_cv_versions.yml' 2023-04-28 05:57:53,203 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_view_version_cleanup/tasks/main.yml' 2023-04-28 05:57:53,204 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_views/README.md' 2023-04-28 05:57:53,204 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_views/tasks/_create_content_view.yml' 2023-04-28 05:57:53,204 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/content_views/tasks/main.yml' 2023-04-28 05:57:53,204 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/README.md' 2023-04-28 05:57:53,205 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/defaults/main.yml' 2023-04-28 05:57:53,205 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/activation_keys.yml' 2023-04-28 05:57:53,205 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/content_views.yml' 2023-04-28 05:57:53,205 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/host_groups.yml' 2023-04-28 05:57:53,206 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/main.yml' 2023-04-28 05:57:53,206 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/products_and_repos.yml' 2023-04-28 05:57:53,206 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/convert2rhel/tasks/sync.yml' 2023-04-28 05:57:53,206 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/domains/README.md' 2023-04-28 05:57:53,207 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/domains/tasks/main.yml' 2023-04-28 05:57:53,207 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/hostgroups/README.md' 2023-04-28 05:57:53,207 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/hostgroups/tasks/main.yml' 2023-04-28 05:57:53,207 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/lifecycle_environments/README.md' 2023-04-28 05:57:53,208 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/lifecycle_environments/tasks/main.yml' 2023-04-28 05:57:53,208 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/manifest/README.md' 2023-04-28 05:57:53,208 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/manifest/defaults/main.yml' 2023-04-28 05:57:53,208 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/manifest/tasks/main.yml' 2023-04-28 05:57:53,209 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/operatingsystems/README.md' 2023-04-28 05:57:53,209 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/operatingsystems/tasks/main.yml' 2023-04-28 05:57:53,209 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/organizations/README.md' 2023-04-28 05:57:53,209 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/organizations/tasks/main.yml' 2023-04-28 05:57:53,210 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/provisioning_templates/README.md' 2023-04-28 05:57:53,210 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/provisioning_templates/tasks/main.yml' 2023-04-28 05:57:53,210 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/repositories/README.md' 2023-04-28 05:57:53,210 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/repositories/tasks/main.yml' 2023-04-28 05:57:53,211 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/settings/README.md' 2023-04-28 05:57:53,211 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/settings/tasks/main.yml' 2023-04-28 05:57:53,211 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/subnets/README.md' 2023-04-28 05:57:53,211 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/subnets/tasks/main.yml' 2023-04-28 05:57:53,212 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/sync_plans/README.md' 2023-04-28 05:57:53,212 wheel INFO adding 'ansible_collections/theforeman/foreman/roles/sync_plans/tasks/main.yml' 2023-04-28 05:57:53,212 wheel INFO adding 'ansible_collections/vmware/vmware_rest/CHANGELOG.rst' 2023-04-28 05:57:53,213 wheel INFO adding 'ansible_collections/vmware/vmware_rest/FILES.json' 2023-04-28 05:57:53,214 wheel INFO adding 'ansible_collections/vmware/vmware_rest/LICENSE' 2023-04-28 05:57:53,214 wheel INFO adding 'ansible_collections/vmware/vmware_rest/MANIFEST.json' 2023-04-28 05:57:53,214 wheel INFO adding 'ansible_collections/vmware/vmware_rest/README.md' 2023-04-28 05:57:53,215 wheel INFO adding 'ansible_collections/vmware/vmware_rest/bindep.txt' 2023-04-28 05:57:53,215 wheel INFO adding 'ansible_collections/vmware/vmware_rest/dev.md' 2023-04-28 05:57:53,215 wheel INFO adding 'ansible_collections/vmware/vmware_rest/docs-requirements.txt' 2023-04-28 05:57:53,215 wheel INFO adding 'ansible_collections/vmware/vmware_rest/modules.yaml' 2023-04-28 05:57:53,216 wheel INFO adding 'ansible_collections/vmware/vmware_rest/requirements.txt' 2023-04-28 05:57:53,216 wheel INFO adding 'ansible_collections/vmware/vmware_rest/test-requirements.txt' 2023-04-28 05:57:53,216 wheel INFO adding 'ansible_collections/vmware/vmware_rest/tox.ini' 2023-04-28 05:57:53,216 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/changelog.yaml' 2023-04-28 05:57:53,217 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/config.yaml' 2023-04-28 05:57:53,217 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/2.1.3-changelog.yaml' 2023-04-28 05:57:53,217 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/2.1.3-module_utils.yaml' 2023-04-28 05:57:53,217 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/allow_space_in_search_filters.yaml' 2023-04-28 05:57:53,217 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/cloud.common-bump.yaml' 2023-04-28 05:57:53,218 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/lookup-handle-special-chars.yml' 2023-04-28 05:57:53,218 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/set_default_galaxy_version.yaml' 2023-04-28 05:57:53,218 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/use-FQCN-in-create_vm.yaml.yaml' 2023-04-28 05:57:53,218 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/vcenter_network_info-dvs-example.yaml' 2023-04-28 05:57:53,218 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/version_added.yaml' 2023-04-28 05:57:53,219 wheel INFO adding 'ansible_collections/vmware/vmware_rest/changelogs/fragments/vm_template_library.yaml' 2023-04-28 05:57:53,219 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/.rstcheck.cfg' 2023-04-28 05:57:53,219 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/Makefile' 2023-04-28 05:57:53,219 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/conf.py' 2023-04-28 05:57:53,220 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/export_to_ansible_ansible.sh' 2023-04-28 05:57:53,220 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/guide_vmware_rest.rst' 2023-04-28 05:57:53,220 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/index.rst' 2023-04-28 05:57:53,220 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/appliance_access.rst' 2023-04-28 05:57:53,221 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/health.rst' 2023-04-28 05:57:53,221 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/network.rst' 2023-04-28 05:57:53,221 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/services.rst' 2023-04-28 05:57:53,221 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/appliance/system_managment.rst' 2023-04-28 05:57:53,222 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/1_authentication.rst' 2023-04-28 05:57:53,222 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/1_installation.rst' 2023-04-28 05:57:53,222 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/2_collect_information.rst' 2023-04-28 05:57:53,222 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/3_create_vm.rst' 2023-04-28 05:57:53,222 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/4_vm_info.rst' 2023-04-28 05:57:53,223 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/5_vm_hardware_tuning.rst' 2023-04-28 05:57:53,223 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/6_run_a_vm.rst' 2023-04-28 05:57:53,223 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/7_vm_tool_information.rst' 2023-04-28 05:57:53,223 wheel INFO adding 'ansible_collections/vmware/vmware_rest/manual/source/vmware_rest_scenarios/vcenter/8_vm_tool_configuration.rst' 2023-04-28 05:57:53,224 wheel INFO adding 'ansible_collections/vmware/vmware_rest/meta/runtime.yml' 2023-04-28 05:57:53,224 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:53,224 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/doc_fragments/moid.py' 2023-04-28 05:57:53,224 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/cluster_moid.py' 2023-04-28 05:57:53,225 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/datacenter_moid.py' 2023-04-28 05:57:53,225 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/datastore_moid.py' 2023-04-28 05:57:53,225 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/folder_moid.py' 2023-04-28 05:57:53,225 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/host_moid.py' 2023-04-28 05:57:53,225 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/network_moid.py' 2023-04-28 05:57:53,226 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/resource_pool_moid.py' 2023-04-28 05:57:53,226 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/lookup/vm_moid.py' 2023-04-28 05:57:53,226 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/module_utils/vmware_rest.py' 2023-04-28 05:57:53,227 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_consolecli.py' 2023-04-28 05:57:53,227 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_consolecli_info.py' 2023-04-28 05:57:53,227 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_dcui.py' 2023-04-28 05:57:53,227 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_dcui_info.py' 2023-04-28 05:57:53,228 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_shell.py' 2023-04-28 05:57:53,228 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_shell_info.py' 2023-04-28 05:57:53,228 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_ssh.py' 2023-04-28 05:57:53,228 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_access_ssh_info.py' 2023-04-28 05:57:53,229 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_applmgmt_info.py' 2023-04-28 05:57:53,229 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_database_info.py' 2023-04-28 05:57:53,229 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_databasestorage_info.py' 2023-04-28 05:57:53,229 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_load_info.py' 2023-04-28 05:57:53,230 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_mem_info.py' 2023-04-28 05:57:53,230 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_softwarepackages_info.py' 2023-04-28 05:57:53,230 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_storage_info.py' 2023-04-28 05:57:53,231 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_swap_info.py' 2023-04-28 05:57:53,231 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_health_system_info.py' 2023-04-28 05:57:53,231 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_infraprofile_configs.py' 2023-04-28 05:57:53,231 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_infraprofile_configs_info.py' 2023-04-28 05:57:53,232 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_globalpolicy.py' 2023-04-28 05:57:53,232 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_globalpolicy_info.py' 2023-04-28 05:57:53,232 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_localaccounts_info.py' 2023-04-28 05:57:53,232 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_monitoring_info.py' 2023-04-28 05:57:53,233 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_monitoring_query.py' 2023-04-28 05:57:53,233 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking.py' 2023-04-28 05:57:53,233 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_domains.py' 2023-04-28 05:57:53,234 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_domains_info.py' 2023-04-28 05:57:53,234 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_hostname.py' 2023-04-28 05:57:53,234 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_hostname_info.py' 2023-04-28 05:57:53,234 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_servers.py' 2023-04-28 05:57:53,235 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_dns_servers_info.py' 2023-04-28 05:57:53,235 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_firewall_inbound.py' 2023-04-28 05:57:53,235 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_firewall_inbound_info.py' 2023-04-28 05:57:53,236 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_info.py' 2023-04-28 05:57:53,236 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_info.py' 2023-04-28 05:57:53,236 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv4.py' 2023-04-28 05:57:53,236 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv4_info.py' 2023-04-28 05:57:53,237 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv6.py' 2023-04-28 05:57:53,237 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_interfaces_ipv6_info.py' 2023-04-28 05:57:53,237 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_noproxy.py' 2023-04-28 05:57:53,237 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_noproxy_info.py' 2023-04-28 05:57:53,238 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_proxy.py' 2023-04-28 05:57:53,238 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_networking_proxy_info.py' 2023-04-28 05:57:53,238 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_ntp.py' 2023-04-28 05:57:53,238 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_ntp_info.py' 2023-04-28 05:57:53,239 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_services.py' 2023-04-28 05:57:53,239 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_services_info.py' 2023-04-28 05:57:53,239 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_shutdown.py' 2023-04-28 05:57:53,240 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_shutdown_info.py' 2023-04-28 05:57:53,240 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_globalfips.py' 2023-04-28 05:57:53,240 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_globalfips_info.py' 2023-04-28 05:57:53,240 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_storage.py' 2023-04-28 05:57:53,241 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_storage_info.py' 2023-04-28 05:57:53,241 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_info.py' 2023-04-28 05:57:53,241 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_timezone.py' 2023-04-28 05:57:53,241 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_time_timezone_info.py' 2023-04-28 05:57:53,242 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_system_version_info.py' 2023-04-28 05:57:53,242 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_timesync.py' 2023-04-28 05:57:53,242 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_timesync_info.py' 2023-04-28 05:57:53,242 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_update_info.py' 2023-04-28 05:57:53,243 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_vmon_service.py' 2023-04-28 05:57:53,243 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/appliance_vmon_service_info.py' 2023-04-28 05:57:53,243 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/content_configuration.py' 2023-04-28 05:57:53,244 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/content_configuration_info.py' 2023-04-28 05:57:53,244 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/content_library_item_info.py' 2023-04-28 05:57:53,244 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/content_locallibrary.py' 2023-04-28 05:57:53,245 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/content_locallibrary_info.py' 2023-04-28 05:57:53,245 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/content_subscribedlibrary.py' 2023-04-28 05:57:53,245 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/content_subscribedlibrary_info.py' 2023-04-28 05:57:53,246 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_cluster_info.py' 2023-04-28 05:57:53,246 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datacenter.py' 2023-04-28 05:57:53,246 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datacenter_info.py' 2023-04-28 05:57:53,247 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_datastore_info.py' 2023-04-28 05:57:53,247 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_folder_info.py' 2023-04-28 05:57:53,247 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_host.py' 2023-04-28 05:57:53,247 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_host_info.py' 2023-04-28 05:57:53,248 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_network_info.py' 2023-04-28 05:57:53,248 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_ovf_libraryitem.py' 2023-04-28 05:57:53,248 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_resourcepool.py' 2023-04-28 05:57:53,249 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_resourcepool_info.py' 2023-04-28 05:57:53,249 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_storage_policies_info.py' 2023-04-28 05:57:53,249 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm.py' 2023-04-28 05:57:53,250 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_customization.py' 2023-04-28 05:57:53,250 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_filesystem_directories.py' 2023-04-28 05:57:53,250 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_identity_info.py' 2023-04-28 05:57:53,251 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_localfilesystem_info.py' 2023-04-28 05:57:53,251 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_info.py' 2023-04-28 05:57:53,251 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_interfaces_info.py' 2023-04-28 05:57:53,251 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_networking_routes_info.py' 2023-04-28 05:57:53,252 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_operations_info.py' 2023-04-28 05:57:53,252 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_power.py' 2023-04-28 05:57:53,252 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_guest_power_info.py' 2023-04-28 05:57:53,253 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware.py' 2023-04-28 05:57:53,253 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_sata.py' 2023-04-28 05:57:53,253 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_sata_info.py' 2023-04-28 05:57:53,253 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_scsi.py' 2023-04-28 05:57:53,254 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_adapter_scsi_info.py' 2023-04-28 05:57:53,254 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot.py' 2023-04-28 05:57:53,255 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_device.py' 2023-04-28 05:57:53,255 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_device_info.py' 2023-04-28 05:57:53,255 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_boot_info.py' 2023-04-28 05:57:53,255 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cdrom.py' 2023-04-28 05:57:53,256 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cdrom_info.py' 2023-04-28 05:57:53,256 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cpu.py' 2023-04-28 05:57:53,256 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_cpu_info.py' 2023-04-28 05:57:53,257 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_disk.py' 2023-04-28 05:57:53,257 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_disk_info.py' 2023-04-28 05:57:53,257 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_ethernet.py' 2023-04-28 05:57:53,257 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_ethernet_info.py' 2023-04-28 05:57:53,258 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_floppy.py' 2023-04-28 05:57:53,258 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_floppy_info.py' 2023-04-28 05:57:53,258 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_info.py' 2023-04-28 05:57:53,259 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_memory.py' 2023-04-28 05:57:53,259 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_memory_info.py' 2023-04-28 05:57:53,259 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_parallel.py' 2023-04-28 05:57:53,259 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_parallel_info.py' 2023-04-28 05:57:53,260 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_serial.py' 2023-04-28 05:57:53,260 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_hardware_serial_info.py' 2023-04-28 05:57:53,260 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_info.py' 2023-04-28 05:57:53,261 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_libraryitem_info.py' 2023-04-28 05:57:53,261 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_power.py' 2023-04-28 05:57:53,261 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_power_info.py' 2023-04-28 05:57:53,261 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy.py' 2023-04-28 05:57:53,262 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_compliance.py' 2023-04-28 05:57:53,262 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_compliance_info.py' 2023-04-28 05:57:53,262 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_storage_policy_info.py' 2023-04-28 05:57:53,262 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools.py' 2023-04-28 05:57:53,263 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_info.py' 2023-04-28 05:57:53,263 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_installer.py' 2023-04-28 05:57:53,263 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vm_tools_installer_info.py' 2023-04-28 05:57:53,264 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vmtemplate_libraryitems.py' 2023-04-28 05:57:53,264 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/modules/vcenter_vmtemplate_libraryitems_info.py' 2023-04-28 05:57:53,264 wheel INFO adding 'ansible_collections/vmware/vmware_rest/plugins/plugin_utils/lookup.py' 2023-04-28 05:57:53,265 wheel INFO adding 'ansible_collections/vultr/cloud/CHANGELOG.rst' 2023-04-28 05:57:53,265 wheel INFO adding 'ansible_collections/vultr/cloud/CONTRIBUTING.md' 2023-04-28 05:57:53,265 wheel INFO adding 'ansible_collections/vultr/cloud/COPYING' 2023-04-28 05:57:53,266 wheel INFO adding 'ansible_collections/vultr/cloud/FILES.json' 2023-04-28 05:57:53,266 wheel INFO adding 'ansible_collections/vultr/cloud/MANIFEST.json' 2023-04-28 05:57:53,266 wheel INFO adding 'ansible_collections/vultr/cloud/README.md' 2023-04-28 05:57:53,267 wheel INFO adding 'ansible_collections/vultr/cloud/codecov.yml' 2023-04-28 05:57:53,267 wheel INFO adding 'ansible_collections/vultr/cloud/changelogs/.gitignore' 2023-04-28 05:57:53,267 wheel INFO adding 'ansible_collections/vultr/cloud/changelogs/changelog.yaml' 2023-04-28 05:57:53,267 wheel INFO adding 'ansible_collections/vultr/cloud/changelogs/config.yaml' 2023-04-28 05:57:53,267 wheel INFO adding 'ansible_collections/vultr/cloud/changelogs/fragments/.keep' 2023-04-28 05:57:53,268 wheel INFO adding 'ansible_collections/vultr/cloud/meta/runtime.yml' 2023-04-28 05:57:53,268 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:53,268 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/doc_fragments/vultr_v2.py' 2023-04-28 05:57:53,269 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/inventory/vultr.py' 2023-04-28 05:57:53,269 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/module_utils/vultr_v2.py' 2023-04-28 05:57:53,269 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/__init__.py' 2023-04-28 05:57:53,269 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/account_info.py' 2023-04-28 05:57:53,270 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/block_storage.py' 2023-04-28 05:57:53,270 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/block_storage_info.py' 2023-04-28 05:57:53,270 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/dns_domain.py' 2023-04-28 05:57:53,270 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/dns_domain_info.py' 2023-04-28 05:57:53,271 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/dns_record.py' 2023-04-28 05:57:53,271 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/firewall_group.py' 2023-04-28 05:57:53,271 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/firewall_group_info.py' 2023-04-28 05:57:53,271 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/firewall_rule.py' 2023-04-28 05:57:53,271 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/firewall_rule_info.py' 2023-04-28 05:57:53,272 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/instance.py' 2023-04-28 05:57:53,272 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/instance_info.py' 2023-04-28 05:57:53,272 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/os_info.py' 2023-04-28 05:57:53,272 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/plan_info.py' 2023-04-28 05:57:53,273 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/plan_metal_info.py' 2023-04-28 05:57:53,273 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/region_info.py' 2023-04-28 05:57:53,273 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/reserved_ip.py' 2023-04-28 05:57:53,273 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/snapshot.py' 2023-04-28 05:57:53,274 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/snapshot_info.py' 2023-04-28 05:57:53,274 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/ssh_key.py' 2023-04-28 05:57:53,274 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/ssh_key_info.py' 2023-04-28 05:57:53,274 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/startup_script.py' 2023-04-28 05:57:53,275 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/startup_script_info.py' 2023-04-28 05:57:53,275 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/user.py' 2023-04-28 05:57:53,275 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/user_info.py' 2023-04-28 05:57:53,275 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/vpc.py' 2023-04-28 05:57:53,275 wheel INFO adding 'ansible_collections/vultr/cloud/plugins/modules/vpc_info.py' 2023-04-28 05:57:53,276 wheel INFO adding 'ansible_collections/vyos/vyos/CHANGELOG.rst' 2023-04-28 05:57:53,277 wheel INFO adding 'ansible_collections/vyos/vyos/FILES.json' 2023-04-28 05:57:53,278 wheel INFO adding 'ansible_collections/vyos/vyos/LICENSE' 2023-04-28 05:57:53,278 wheel INFO adding 'ansible_collections/vyos/vyos/MANIFEST.json' 2023-04-28 05:57:53,278 wheel INFO adding 'ansible_collections/vyos/vyos/README.md' 2023-04-28 05:57:53,279 wheel INFO adding 'ansible_collections/vyos/vyos/bindep.txt' 2023-04-28 05:57:53,279 wheel INFO adding 'ansible_collections/vyos/vyos/codecov.yml' 2023-04-28 05:57:53,279 wheel INFO adding 'ansible_collections/vyos/vyos/pyproject.toml' 2023-04-28 05:57:53,279 wheel INFO adding 'ansible_collections/vyos/vyos/requirements.txt' 2023-04-28 05:57:53,279 wheel INFO adding 'ansible_collections/vyos/vyos/test-requirements.txt' 2023-04-28 05:57:53,280 wheel INFO adding 'ansible_collections/vyos/vyos/tox.ini' 2023-04-28 05:57:53,280 wheel INFO adding 'ansible_collections/vyos/vyos/changelogs/changelog.yaml' 2023-04-28 05:57:53,280 wheel INFO adding 'ansible_collections/vyos/vyos/changelogs/config.yaml' 2023-04-28 05:57:53,280 wheel INFO adding 'ansible_collections/vyos/vyos/changelogs/fragments/.keep' 2023-04-28 05:57:53,281 wheel INFO adding 'ansible_collections/vyos/vyos/meta/runtime.yml' 2023-04-28 05:57:53,281 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/__init__.py' 2023-04-28 05:57:53,281 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/banner.py' 2023-04-28 05:57:53,281 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/bgp_address_family.py' 2023-04-28 05:57:53,282 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/bgp_global.py' 2023-04-28 05:57:53,282 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/command.py' 2023-04-28 05:57:53,282 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/config.py' 2023-04-28 05:57:53,282 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/facts.py' 2023-04-28 05:57:53,283 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/firewall_global.py' 2023-04-28 05:57:53,283 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/firewall_interfaces.py' 2023-04-28 05:57:53,283 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/firewall_rules.py' 2023-04-28 05:57:53,283 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/hostname.py' 2023-04-28 05:57:53,283 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/interface.py' 2023-04-28 05:57:53,284 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/interfaces.py' 2023-04-28 05:57:53,284 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/l3_interface.py' 2023-04-28 05:57:53,284 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/l3_interfaces.py' 2023-04-28 05:57:53,284 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/lag_interfaces.py' 2023-04-28 05:57:53,285 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/linkagg.py' 2023-04-28 05:57:53,285 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/lldp.py' 2023-04-28 05:57:53,285 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/lldp_global.py' 2023-04-28 05:57:53,285 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/lldp_interface.py' 2023-04-28 05:57:53,285 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/lldp_interfaces.py' 2023-04-28 05:57:53,286 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/logging.py' 2023-04-28 05:57:53,286 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/logging_global.py' 2023-04-28 05:57:53,286 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/ntp_global.py' 2023-04-28 05:57:53,286 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/ospf_interfaces.py' 2023-04-28 05:57:53,286 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/ospfv2.py' 2023-04-28 05:57:53,287 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/ospfv3.py' 2023-04-28 05:57:53,287 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/ping.py' 2023-04-28 05:57:53,287 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/prefix_lists.py' 2023-04-28 05:57:53,287 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/route_maps.py' 2023-04-28 05:57:53,288 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/snmp_server.py' 2023-04-28 05:57:53,288 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/static_route.py' 2023-04-28 05:57:53,288 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/static_routes.py' 2023-04-28 05:57:53,288 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/system.py' 2023-04-28 05:57:53,288 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/user.py' 2023-04-28 05:57:53,289 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/vlan.py' 2023-04-28 05:57:53,289 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/action/vyos.py' 2023-04-28 05:57:53,289 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/cliconf/__init__.py' 2023-04-28 05:57:53,289 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/cliconf/vyos.py' 2023-04-28 05:57:53,290 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/doc_fragments/__init__.py' 2023-04-28 05:57:53,290 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/doc_fragments/vyos.py' 2023-04-28 05:57:53,290 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/filter/__init__.py' 2023-04-28 05:57:53,290 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/inventory/__init__.py' 2023-04-28 05:57:53,291 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/__init__.py' 2023-04-28 05:57:53,291 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/__init__.py' 2023-04-28 05:57:53,291 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/__init__.py' 2023-04-28 05:57:53,291 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/vyos.py' 2023-04-28 05:57:53,292 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/__init__.py' 2023-04-28 05:57:53,292 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/__init__.py' 2023-04-28 05:57:53,292 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:53,292 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/__init__.py' 2023-04-28 05:57:53,293 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/bgp_global.py' 2023-04-28 05:57:53,293 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/__init__.py' 2023-04-28 05:57:53,293 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/facts.py' 2023-04-28 05:57:53,293 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/__init__.py' 2023-04-28 05:57:53,294 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/firewall_global.py' 2023-04-28 05:57:53,294 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/__init__.py' 2023-04-28 05:57:53,294 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/firewall_interfaces.py' 2023-04-28 05:57:53,294 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/__init__.py' 2023-04-28 05:57:53,295 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/firewall_rules.py' 2023-04-28 05:57:53,295 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/__init__.py' 2023-04-28 05:57:53,295 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/hostname.py' 2023-04-28 05:57:53,295 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/__init__.py' 2023-04-28 05:57:53,296 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/interfaces.py' 2023-04-28 05:57:53,296 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/__init__.py' 2023-04-28 05:57:53,296 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:53,296 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/__init__.py' 2023-04-28 05:57:53,296 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:53,297 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/__init__.py' 2023-04-28 05:57:53,297 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/lldp_global.py' 2023-04-28 05:57:53,297 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/__init__.py' 2023-04-28 05:57:53,297 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:53,298 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/__init__.py' 2023-04-28 05:57:53,298 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/logging_global.py' 2023-04-28 05:57:53,298 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/__init__.py' 2023-04-28 05:57:53,298 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/ntp_global.py' 2023-04-28 05:57:53,299 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/__init__.py' 2023-04-28 05:57:53,299 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:53,299 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/__init__.py' 2023-04-28 05:57:53,299 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/ospfv2.py' 2023-04-28 05:57:53,300 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/__init__.py' 2023-04-28 05:57:53,300 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/ospfv3.py' 2023-04-28 05:57:53,300 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/__init__.py' 2023-04-28 05:57:53,300 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/prefix_lists.py' 2023-04-28 05:57:53,301 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/__init__.py' 2023-04-28 05:57:53,301 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/route_maps.py' 2023-04-28 05:57:53,301 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/__init__.py' 2023-04-28 05:57:53,301 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/snmp_server.py' 2023-04-28 05:57:53,302 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/__init__.py' 2023-04-28 05:57:53,302 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/static_routes.py' 2023-04-28 05:57:53,302 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/__init__.py' 2023-04-28 05:57:53,302 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/__init__.py' 2023-04-28 05:57:53,303 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:53,303 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/__init__.py' 2023-04-28 05:57:53,303 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/bgp_global.py' 2023-04-28 05:57:53,304 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/__init__.py' 2023-04-28 05:57:53,304 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/firewall_global.py' 2023-04-28 05:57:53,304 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/__init__.py' 2023-04-28 05:57:53,304 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/firewall_interfaces.py' 2023-04-28 05:57:53,305 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/__init__.py' 2023-04-28 05:57:53,305 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/firewall_rules.py' 2023-04-28 05:57:53,305 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/__init__.py' 2023-04-28 05:57:53,306 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/hostname.py' 2023-04-28 05:57:53,306 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/__init__.py' 2023-04-28 05:57:53,306 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/interfaces.py' 2023-04-28 05:57:53,306 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/__init__.py' 2023-04-28 05:57:53,307 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:53,307 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/__init__.py' 2023-04-28 05:57:53,307 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:53,308 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/__init__.py' 2023-04-28 05:57:53,308 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/lldp_global.py' 2023-04-28 05:57:53,308 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/__init__.py' 2023-04-28 05:57:53,308 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:53,309 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/__init__.py' 2023-04-28 05:57:53,309 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/logging_global.py' 2023-04-28 05:57:53,309 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/__init__.py' 2023-04-28 05:57:53,309 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/ntp_global.py' 2023-04-28 05:57:53,310 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/__init__.py' 2023-04-28 05:57:53,310 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:53,310 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/__init__.py' 2023-04-28 05:57:53,310 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/ospfv2.py' 2023-04-28 05:57:53,311 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/__init__.py' 2023-04-28 05:57:53,311 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/ospfv3.py' 2023-04-28 05:57:53,311 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/__init__.py' 2023-04-28 05:57:53,312 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/prefix_lists.py' 2023-04-28 05:57:53,312 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/__init__.py' 2023-04-28 05:57:53,312 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/route_maps.py' 2023-04-28 05:57:53,312 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/__init__.py' 2023-04-28 05:57:53,313 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/snmp_server.py' 2023-04-28 05:57:53,313 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/__init__.py' 2023-04-28 05:57:53,313 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/static_routes.py' 2023-04-28 05:57:53,313 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/__init__.py' 2023-04-28 05:57:53,314 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/facts.py' 2023-04-28 05:57:53,314 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/__init__.py' 2023-04-28 05:57:53,314 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/bgp_address_family.py' 2023-04-28 05:57:53,314 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/__init__.py' 2023-04-28 05:57:53,315 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/bgp_global.py' 2023-04-28 05:57:53,315 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/__init__.py' 2023-04-28 05:57:53,315 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/firewall_global.py' 2023-04-28 05:57:53,316 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/__init__.py' 2023-04-28 05:57:53,316 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/firewall_interfaces.py' 2023-04-28 05:57:53,316 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/__init__.py' 2023-04-28 05:57:53,316 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/firewall_rules.py' 2023-04-28 05:57:53,317 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/__init__.py' 2023-04-28 05:57:53,317 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/hostname.py' 2023-04-28 05:57:53,317 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/__init__.py' 2023-04-28 05:57:53,317 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/interfaces.py' 2023-04-28 05:57:53,318 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/__init__.py' 2023-04-28 05:57:53,318 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/l3_interfaces.py' 2023-04-28 05:57:53,318 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/__init__.py' 2023-04-28 05:57:53,318 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/lag_interfaces.py' 2023-04-28 05:57:53,319 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/__init__.py' 2023-04-28 05:57:53,319 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/base.py' 2023-04-28 05:57:53,319 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/__init__.py' 2023-04-28 05:57:53,319 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/lldp_global.py' 2023-04-28 05:57:53,320 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/__init__.py' 2023-04-28 05:57:53,320 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/lldp_interfaces.py' 2023-04-28 05:57:53,320 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/__init__.py' 2023-04-28 05:57:53,320 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/logging_global.py' 2023-04-28 05:57:53,321 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/__init__.py' 2023-04-28 05:57:53,321 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/ntp_global.py' 2023-04-28 05:57:53,321 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/__init__.py' 2023-04-28 05:57:53,321 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/ospf_interfaces.py' 2023-04-28 05:57:53,322 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/__init__.py' 2023-04-28 05:57:53,322 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/ospfv2.py' 2023-04-28 05:57:53,322 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/__init__.py' 2023-04-28 05:57:53,322 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/ospfv3.py' 2023-04-28 05:57:53,323 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/__init__.py' 2023-04-28 05:57:53,323 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/prefix_lists.py' 2023-04-28 05:57:53,323 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/__init__.py' 2023-04-28 05:57:53,323 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/route_maps.py' 2023-04-28 05:57:53,324 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/__init__.py' 2023-04-28 05:57:53,324 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/snmp_server.py' 2023-04-28 05:57:53,324 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/__init__.py' 2023-04-28 05:57:53,324 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/static_routes.py' 2023-04-28 05:57:53,325 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/__init__.py' 2023-04-28 05:57:53,325 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/bgp_address_family.py' 2023-04-28 05:57:53,325 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/bgp_global.py' 2023-04-28 05:57:53,326 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/hostname.py' 2023-04-28 05:57:53,326 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/logging_global.py' 2023-04-28 05:57:53,326 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/ntp_global.py' 2023-04-28 05:57:53,327 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/ospf_interfaces.py' 2023-04-28 05:57:53,327 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/prefix_lists.py' 2023-04-28 05:57:53,327 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/route_maps.py' 2023-04-28 05:57:53,328 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/snmp_server.py' 2023-04-28 05:57:53,328 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/__init__.py' 2023-04-28 05:57:53,328 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/utils.py' 2023-04-28 05:57:53,329 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/__init__.py' 2023-04-28 05:57:53,329 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_banner.py' 2023-04-28 05:57:53,329 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_bgp_address_family.py' 2023-04-28 05:57:53,330 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_bgp_global.py' 2023-04-28 05:57:53,330 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_command.py' 2023-04-28 05:57:53,331 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_config.py' 2023-04-28 05:57:53,331 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_facts.py' 2023-04-28 05:57:53,331 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_global.py' 2023-04-28 05:57:53,332 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_interfaces.py' 2023-04-28 05:57:53,332 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_firewall_rules.py' 2023-04-28 05:57:53,333 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_hostname.py' 2023-04-28 05:57:53,333 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_interfaces.py' 2023-04-28 05:57:53,333 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_l3_interfaces.py' 2023-04-28 05:57:53,334 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_lag_interfaces.py' 2023-04-28 05:57:53,334 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_lldp_global.py' 2023-04-28 05:57:53,334 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_lldp_interfaces.py' 2023-04-28 05:57:53,335 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_logging.py' 2023-04-28 05:57:53,335 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_logging_global.py' 2023-04-28 05:57:53,335 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_ntp_global.py' 2023-04-28 05:57:53,336 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_ospf_interfaces.py' 2023-04-28 05:57:53,336 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_ospfv2.py' 2023-04-28 05:57:53,337 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_ospfv3.py' 2023-04-28 05:57:53,337 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_ping.py' 2023-04-28 05:57:53,337 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_prefix_lists.py' 2023-04-28 05:57:53,338 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_route_maps.py' 2023-04-28 05:57:53,338 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_snmp_server.py' 2023-04-28 05:57:53,339 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_static_routes.py' 2023-04-28 05:57:53,339 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_system.py' 2023-04-28 05:57:53,339 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_user.py' 2023-04-28 05:57:53,340 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/modules/vyos_vlan.py' 2023-04-28 05:57:53,340 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/terminal/__init__.py' 2023-04-28 05:57:53,340 wheel INFO adding 'ansible_collections/vyos/vyos/plugins/terminal/vyos.py' 2023-04-28 05:57:53,340 wheel INFO adding 'ansible_collections/wti/remote/CHANGELOG.rst' 2023-04-28 05:57:53,341 wheel INFO adding 'ansible_collections/wti/remote/FILES.json' 2023-04-28 05:57:53,341 wheel INFO adding 'ansible_collections/wti/remote/MANIFEST.json' 2023-04-28 05:57:53,341 wheel INFO adding 'ansible_collections/wti/remote/README.md' 2023-04-28 05:57:53,342 wheel INFO adding 'ansible_collections/wti/remote/requirements-wti.txt' 2023-04-28 05:57:53,342 wheel INFO adding 'ansible_collections/wti/remote/meta/execution-environment.yml' 2023-04-28 05:57:53,342 wheel INFO adding 'ansible_collections/wti/remote/meta/runtime.yml' 2023-04-28 05:57:53,342 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_config/cpm_config_backup.yml' 2023-04-28 05:57:53,342 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_config/cpm_config_restore.yml' 2023-04-28 05:57:53,343 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_firmwareupdate/firmware_upgrade.yml' 2023-04-28 05:57:53,343 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_hostname/hostname_config.yml' 2023-04-28 05:57:53,343 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_hostname/hostname_info.yml' 2023-04-28 05:57:53,343 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_interface/interface_config.yml' 2023-04-28 05:57:53,344 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_interface/interface_info.yml' 2023-04-28 05:57:53,344 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_iptables/iptables_config.yml' 2023-04-28 05:57:53,344 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_iptables/iptables_info.yml' 2023-04-28 05:57:53,344 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_plugconfig/plug_config.yml' 2023-04-28 05:57:53,345 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_plugconfig/plug_info.yml' 2023-04-28 05:57:53,345 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_plugcontrol/plug_control.yml' 2023-04-28 05:57:53,345 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_plugcontrol/plug_control_info.yml' 2023-04-28 05:57:53,345 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_action_info.yml' 2023-04-28 05:57:53,346 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_action_set.yml' 2023-04-28 05:57:53,346 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_config.yml' 2023-04-28 05:57:53,346 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_serial_ports/serial_ports_info.yml' 2023-04-28 05:57:53,346 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_snmp/snmp_config.yml' 2023-04-28 05:57:53,346 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_snmp/snmp_info.yml' 2023-04-28 05:57:53,347 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_status/alarm_info.yml' 2023-04-28 05:57:53,347 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_status/current_info.yml' 2023-04-28 05:57:53,347 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_status/firmware_info.yml' 2023-04-28 05:57:53,347 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_status/power_info.yml' 2023-04-28 05:57:53,348 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_status/status_info.yml' 2023-04-28 05:57:53,348 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_status/temp_info.yml' 2023-04-28 05:57:53,348 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_syslog_client/syslog_client_config.yml' 2023-04-28 05:57:53,348 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_syslog_client/syslog_client_info.yml' 2023-04-28 05:57:53,348 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_syslog_server/syslog_server_config.yml' 2023-04-28 05:57:53,349 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_syslog_server/syslog_server_info.yml' 2023-04-28 05:57:53,349 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_time_date/time_config.yml' 2023-04-28 05:57:53,349 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_time_date/time_info.yml' 2023-04-28 05:57:53,349 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_user/user_add.yml' 2023-04-28 05:57:53,350 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_user/user_delete.yml' 2023-04-28 05:57:53,350 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_user/user_edit.yml' 2023-04-28 05:57:53,350 wheel INFO adding 'ansible_collections/wti/remote/playbooks/cpm_user/user_get.yml' 2023-04-28 05:57:53,350 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_alarm_info.py' 2023-04-28 05:57:53,351 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_config_backup.py' 2023-04-28 05:57:53,351 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_config_restore.py' 2023-04-28 05:57:53,351 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_current_info.py' 2023-04-28 05:57:53,351 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_firmware_info.py' 2023-04-28 05:57:53,352 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_firmware_update.py' 2023-04-28 05:57:53,352 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_hostname_config.py' 2023-04-28 05:57:53,352 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_hostname_info.py' 2023-04-28 05:57:53,352 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_interface_config.py' 2023-04-28 05:57:53,353 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_interface_info.py' 2023-04-28 05:57:53,353 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_iptables_config.py' 2023-04-28 05:57:53,353 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_iptables_info.py' 2023-04-28 05:57:53,354 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_metering.py' 2023-04-28 05:57:53,354 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_plugconfig.py' 2023-04-28 05:57:53,354 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_plugcontrol.py' 2023-04-28 05:57:53,354 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_power_info.py' 2023-04-28 05:57:53,355 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_action_info.py' 2023-04-28 05:57:53,355 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_action_set.py' 2023-04-28 05:57:53,355 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_config.py' 2023-04-28 05:57:53,355 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_serial_port_info.py' 2023-04-28 05:57:53,356 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_snmp_config.py' 2023-04-28 05:57:53,356 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_snmp_info.py' 2023-04-28 05:57:53,356 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_status.py' 2023-04-28 05:57:53,357 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_status_info.py' 2023-04-28 05:57:53,357 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_syslog_client_config.py' 2023-04-28 05:57:53,357 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_syslog_client_info.py' 2023-04-28 05:57:53,357 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_syslog_server_config.py' 2023-04-28 05:57:53,358 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_syslog_server_info.py' 2023-04-28 05:57:53,358 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_temp_info.py' 2023-04-28 05:57:53,358 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_time_config.py' 2023-04-28 05:57:53,358 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_time_info.py' 2023-04-28 05:57:53,359 wheel INFO adding 'ansible_collections/wti/remote/plugins/lookup/cpm_user.py' 2023-04-28 05:57:53,359 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_alarm_info.py' 2023-04-28 05:57:53,359 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_config_backup.py' 2023-04-28 05:57:53,360 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_config_restore.py' 2023-04-28 05:57:53,360 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_current_info.py' 2023-04-28 05:57:53,360 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_firmware_info.py' 2023-04-28 05:57:53,360 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_firmware_update.py' 2023-04-28 05:57:53,361 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_hostname_config.py' 2023-04-28 05:57:53,361 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_hostname_info.py' 2023-04-28 05:57:53,361 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_interface_config.py' 2023-04-28 05:57:53,361 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_interface_info.py' 2023-04-28 05:57:53,362 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_iptables_config.py' 2023-04-28 05:57:53,362 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_iptables_info.py' 2023-04-28 05:57:53,362 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_plugconfig.py' 2023-04-28 05:57:53,363 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_plugcontrol.py' 2023-04-28 05:57:53,363 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_power_info.py' 2023-04-28 05:57:53,363 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_serial_port_action_info.py' 2023-04-28 05:57:53,363 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_serial_port_action_set.py' 2023-04-28 05:57:53,364 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_serial_port_config.py' 2023-04-28 05:57:53,364 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_serial_port_info.py' 2023-04-28 05:57:53,364 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_snmp_config.py' 2023-04-28 05:57:53,364 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_snmp_info.py' 2023-04-28 05:57:53,365 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_status_info.py' 2023-04-28 05:57:53,365 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_syslog_client_config.py' 2023-04-28 05:57:53,365 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_syslog_client_info.py' 2023-04-28 05:57:53,366 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_syslog_server_config.py' 2023-04-28 05:57:53,366 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_syslog_server_info.py' 2023-04-28 05:57:53,366 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_temp_info.py' 2023-04-28 05:57:53,366 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_time_config.py' 2023-04-28 05:57:53,367 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_time_info.py' 2023-04-28 05:57:53,367 wheel INFO adding 'ansible_collections/wti/remote/plugins/modules/cpm_user.py' 2023-04-28 05:57:53,367 wheel INFO adding 'ansible-7.5.0.dist-info/COPYING' 2023-04-28 05:57:53,368 wheel INFO adding 'ansible-7.5.0.dist-info/METADATA' 2023-04-28 05:57:53,368 wheel INFO adding 'ansible-7.5.0.dist-info/WHEEL' 2023-04-28 05:57:53,368 wheel INFO adding 'ansible-7.5.0.dist-info/entry_points.txt' 2023-04-28 05:57:53,368 wheel INFO adding 'ansible-7.5.0.dist-info/top_level.txt' 2023-04-28 05:57:53,442 wheel INFO adding 'ansible-7.5.0.dist-info/RECORD' 2023-04-28 05:57:53,497 wheel INFO removing build/bdist.linux-x86_64/wheel 2023-04-28 05:57:54,016 gpep517 INFO The backend produced dist/ansible-7.5.0-py3-none-any.whl ansible-7.5.0-py3-none-any.whl >>> ansible: Entering fakeroot... >>> ansible-pyc*: Running split function pyc... '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/netconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/netconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_options/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_policies_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/routing_instances/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/security_zones/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/facts/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_options/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_policies_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/routing_instances/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/security_zones/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/config/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_options/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_policies_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/routing_instances/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/security_zones/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/argspec/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/junos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/junipernetworks/junos/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/azure/azcollection/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/bgp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/cli/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/providers/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/network/frr/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/frr/frr/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/gluster/gluster/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/gluster/gluster/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/sub_plugins/validate/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/sub_plugins/validate/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/sub_plugins/fact_diff/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/sub_plugins/cli_parser/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/test/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/test/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/plugin_utils/base/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/plugin_utils/base/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/module_utils/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/module_utils/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/utils/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/callback/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/callback/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/shell/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/shell/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/hacking/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/posix/hacking/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/sub_plugins/grpc/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/sub_plugins/cli_parser/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/netconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/netconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/cli_parser/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/grpc/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/restconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/netconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/rm_base/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/module_utils/network/common/cfg/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/become/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/become/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/cache/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/netcommon/plugins/cache/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ansible/windows/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/grafana/grafana/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/grafana/grafana/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/module_utils/client/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/module_utils/client/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/module_utils/k8s/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/module_utils/k8s/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/kubernetes/core/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloudscale_ch/cloud/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/manual/source/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vmware/vmware_rest/manual/source/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp_eseries/santricity/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infoblox/nios_modules/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/chocolatey/chocolatey/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/chocolatey/chocolatey/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/microsoft/ad/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/callback/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/callback/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/amazon/aws/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/test/awx/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/test/awx/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/awx/awx/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/f5networks/f5_modules/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/wti/remote/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/wti/remote/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/wti/remote/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/wti/remote/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/azure/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/azure/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/azure/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/azure/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/azure/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/azure/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/elementsw/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/elementsw/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/elementsw/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/elementsw/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/elementsw/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/elementsw/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/cloudmanager/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/cloudmanager/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/cloudmanager/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/cloudmanager/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/cloudmanager/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/cloudmanager/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/ontap/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/storagegrid/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/storagegrid/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/storagegrid/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/storagegrid/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/storagegrid/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/storagegrid/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/um_info/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/um_info/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/um_info/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/um_info/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/um_info/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/um_info/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/aws/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/aws/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/aws/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/aws/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netapp/aws/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netapp/aws/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/module_utils/network/onyx/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/mellanox/onyx/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/rabbitmq/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/scripts/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/digitalocean/scripts/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/callback/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/callback/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/hacking/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/grafana/hacking/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hrobot/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/scripts/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/vmware/scripts/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/autopsk/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/agent2_common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2autopsk/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/no_auto_psk/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/autopsk/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/autopsk/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/no_auto_psk/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/agent2_common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/molecule/agent2/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/no_auto_psk/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/autopsk/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/agent2_common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_agent_tests/common/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_javagateway/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_server/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_server/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_proxy/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_proxy/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_web/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/molecule/zabbix_web/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/scripts/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/scripts/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/zabbix/roles/zabbix_agent/molecule/with-server/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/okd/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/okd/molecule/default/roles/openshift_adm_groups/library/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/okd/ci/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/okd/ci/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/test/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/test/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/callback/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/callback/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/oracle/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/oracle/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/mh/mixins/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/mh/mixins/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/mh/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/mh/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/remote_management/lxca/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/remote_management/lxca/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/source_control/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/source_control/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/net_tools/pritunl/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/net_tools/pritunl/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/identity/keycloak/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/identity/keycloak/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/storage/emc/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/storage/emc/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/storage/hpe3par/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/storage/hpe3par/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/become/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/become/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/cache/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/general/plugins/cache/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/proxysql/roles/proxysql/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/plugin_utils/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/plugin_utils/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/hosttech/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/hosttech/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/module/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/module/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/conversion/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/conversion/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/hetzner/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/plugins/module_utils/hetzner/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/dns/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/dns/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/module_utils/implementations/mysql/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/module_utils/implementations/mariadb/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mysql/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/vars/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/vars/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sops/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/fortios/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/fortios/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/fortios/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/fortios/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/fortios/plugins/module_utils/fortianalyzer/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/database/saphana/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/database/saphana/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/identity/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/identity/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/files/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/files/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/system/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/system/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/ecs/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/ecs/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/openssh/backends/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/openssh/backends/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/openssh/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/openssh/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/acme/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/acme/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/crypto/module_backends/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/crypto/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/crypto/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/crypto/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/postgresql/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/postgresql/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/postgresql/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/postgresql/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/postgresql/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/postgresql/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/aws/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/aws/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/aws/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/aws/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/aws/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/aws/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/types/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/types/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/api/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/api/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/credentials/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/credentials/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/transport/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/_api/transport/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/module_container/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/module_container/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/docker/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/module_utils/network/skydive/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/module_utils/network/skydive/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/skydive/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap_libs/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap_libs/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap_libs/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap_libs/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/sap_libs/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/sap_libs/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/libvirt/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/hashi_vault/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/google/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/google/scripts/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/google/scripts/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/cache/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/plugins/cache/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_repository/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/multiple_bind_ip/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongod/molecule/custom_db_path/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_config/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_config/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_config/molecule/custom_db_path/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_auth/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_mongos/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_linux/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_nohold_packages/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/mongodb_hold_packages/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/specific_mongodb_version/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_install/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/default/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/mongodb/roles/mongodb_selinux/molecule/virtualbox/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/ciscosmb/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/windows/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/windows/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/windows/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/windows/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/windows/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/windows/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/netconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/netconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/callback/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/callback/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/netvisor/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/netvisor/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ftd/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ftd/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/aos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/aos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ironware/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ironware/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/avi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/avi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/aruba/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/aruba/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/slxos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/slxos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/edgeswitch/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/edgeswitch/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ingate/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ingate/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/cloudengine/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/cloudengine/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/nos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/nos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/bigswitch/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/bigswitch/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/voss/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/voss/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/eric_eccli/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/eric_eccli/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/netscaler/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/netscaler/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ordnance/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/ordnance/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/icx/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/icx/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/exos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/a10/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/a10/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/apconos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/apconos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/enos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/enos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/aireos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/aireos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/sros/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/sros/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/cnos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/cnos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/edgeos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/edgeos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/become/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/become/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/cache/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/network/plugins/cache/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/community/routeros/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/plugin_utils/turbo/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/plugin_utils/turbo/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/module_utils/turbo/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/module_utils/turbo/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cloud/common/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/tools/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/sensu/sensu_go/tools/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/infinidat/infinibox/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortimanager/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortimanager/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortimanager/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortimanager/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortimanager/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortimanager/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortimanager/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/system/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/system/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/fortios/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/common/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/fortinet/fortios/plugins/module_utils/common/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/sm/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/inspur/ispim/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/splunk/es/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/openvswitch/openvswitch/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/openvswitch/openvswitch/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cyberark/conjur/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cyberark/conjur/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/cleanup-conjur-identity/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cyberark/conjur/roles/conjur_host_identity/tests/test_cases/configure-conjur-identity/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cyberark/pas/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cyberark/pas/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ucs/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ucs/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ucs/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ucs/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ucs/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ucs/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/aci/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nso/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nso/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nso/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nso/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nso/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nso/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/providers/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/ogs/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/facts/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/rm_templates/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/ogs/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/config/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/ogs/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/argspec/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/network/asa/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/asa/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/plugins/module_utils/network/meraki/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/scripts/sublime-build/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/meraki/scripts/sublime-build/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/mso/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/netconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/netconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/modules/storage/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/modules/storage/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bfd_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/telemetry/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/bgp_neighbor_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/hsrp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/facts/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/rm_templates/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/telemetry/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/cmdref/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/telemetry/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bfd_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/telemetry/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/bgp_neighbor_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/hsrp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/config/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bfd_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/telemetry/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/bgp_neighbor_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/hsrp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/argspec/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/nxos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/nxos/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/bgp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/cli/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/providers/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/facts/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/rm_templates/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/ping/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/config/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/ping/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/argspec/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/ios/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ios/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/pb/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/sub_plugins/grpc/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/netconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/netconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/bgp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/cli/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/providers/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/bgp_neighbor_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/facts/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/rm_templates/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/bgp_neighbor_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/ping/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/config/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/bgp_neighbor_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/ping/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/argspec/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/iosxr/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/iosxr/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/intersight/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/intersight/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/intersight/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/intersight/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/intersight/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/intersight/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/dnac/plugins/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/plugin_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/plugin_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/cisco/ise/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/t_systems_mms/icinga_director/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/check_point/mgmt/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/hpe/nimble/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/hpe/nimble/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/hpe/nimble/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/hpe/nimble/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/hpe/nimble/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/hpe/nimble/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_rules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/firewall_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/facts/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/rm_templates/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_rules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/firewall_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/config/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_rules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/firewall_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/argspec/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/vyos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vyos/vyos/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/callback/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/callback/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/theforeman/foreman/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/lookup/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/netbox/netbox/plugins/lookup/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/test/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/test/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/callback/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/callback/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/scripts/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/scripts/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/openstack/cloud/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ibm/qradar/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ibm/spectrum_virtualize/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ibm/spectrum_virtualize/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ibm/spectrum_virtualize/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/lowlydba/sqlserver/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/lowlydba/sqlserver/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/lowlydba/sqlserver/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/vultr/cloud/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/bgp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/cli/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/providers/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/legacy/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/facts/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/rm_templates/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/config/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv2/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_address_family/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lldp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/route_maps/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/hostname/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/snmp_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ntp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acl_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/bgp_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/logging_global/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospf_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/lacp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/ospfv3/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/argspec/acls/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/eos/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/arista/eos/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/filter/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/filter/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/molecule/gcsfuse/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/molecule/gcsfuse/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/molecule/gcloud/tests/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/molecule/gcloud/tests/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/test-fixtures/cloud-function-source/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/google/cloud/test-fixtures/cloud-function-source/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/fusion/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flasharray/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flasharray/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flasharray/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flasharray/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flasharray/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flasharray/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flashblade/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flashblade/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flashblade/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flashblade/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flashblade/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/purestorage/flashblade/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/httpapi/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_ext_communities/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/users/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_af/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/radius_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/tacacs_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vxlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/mclag/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/system/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_as_paths/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_neighbors_af/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/vrfs/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/aaa/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/port_breakout/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/bgp_communities/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/facts/ntp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_ext_communities/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/users/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_af/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/radius_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/tacacs_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vxlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/mclag/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/system/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_as_paths/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_neighbors_af/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/vrfs/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/aaa/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/port_breakout/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/bgp_communities/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/config/ntp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_ext_communities/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/users/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/static_routes/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/facts/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l3_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_af/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/radius_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/lag_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/prefix_lists/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/tacacs_server/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vxlans/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/mclag/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/l2_interfaces/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/system/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_as_paths/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_neighbors_af/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/vrfs/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/aaa/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/port_breakout/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/bgp_communities/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/argspec/ntp/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/sonic/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/enterprise_sonic/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/powerflex/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/powerflex/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/powerflex/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/powerflex/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/powerflex/plugins/module_utils/storage/dell/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/openmanage/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/openmanage/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/openmanage/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/openmanage/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/openmanage/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/openmanage/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os10/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os9/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/unity/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/unity/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/unity/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/unity/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/unity/plugins/module_utils/storage/dell/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/terminal/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/terminal/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/cliconf/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/cliconf/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/action/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/action/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/module_utils/network/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/dellemc/os6/plugins/module_utils/network/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/exoscale/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/exoscale/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/exoscale/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/exoscale/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/exoscale/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/exoscale/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/scripts/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/cloudstack/scripts/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/ngine_io/vultr/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/connection/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/connection/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/module_utils/podman/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/module_utils/podman/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/module_utils/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/become/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/plugins/become/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/containers/podman/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/doc_fragments/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/doc_fragments/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/inventory/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/inventory/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/modules/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/modules/__pycache__' '/home/buildozer/aports/community/ansible/pkg/ansible/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/module_utils/__pycache__' -> '/home/buildozer/aports/community/ansible/pkg/ansible-pyc/usr/lib/python3.11/site-packages/ansible_collections/hetzner/hcloud/plugins/module_utils/__pycache__' >>> ansible-pyc*: Preparing subpackage ansible-pyc... >>> ansible-pyc*: Running postcheck for ansible-pyc >>> ansible*: Running postcheck for ansible >>> ansible*: Preparing package ansible... >>> ansible-pyc*: Tracing dependencies... python3 ansible-core python3~3.11 >>> ansible-pyc*: Package size: 181.5 MB >>> ansible-pyc*: Compressing data... >>> ansible-pyc*: Create checksum... >>> ansible-pyc*: Create ansible-pyc-7.5.0-r0.apk >>> ansible*: Tracing dependencies... python3 ansible-core python3~3.11 >>> ansible*: Package size: 237.6 MB >>> ansible*: Compressing data... >>> ansible*: Create checksum... >>> ansible*: Create ansible-7.5.0-r0.apk >>> ansible: Build complete at Fri, 28 Apr 2023 05:59:21 +0000 elapsed time 0h 2m 9s >>> ansible: Cleaning up srcdir >>> ansible: Cleaning up pkgdir >>> ansible: Uninstalling dependencies... (1/48) Purging .makedepends-ansible (20230428.055714) (2/48) Purging ansible-core-pyc (2.14.5-r0) (3/48) Purging ansible-core (2.14.5-r0) (4/48) Purging py3-jinja2-pyc (3.1.2-r2) (5/48) Purging py3-jinja2 (3.1.2-r2) (6/48) Purging py3-markupsafe-pyc (2.1.2-r1) (7/48) Purging py3-markupsafe (2.1.2-r1) (8/48) Purging py3-paramiko-pyc (3.1.0-r1) (9/48) Purging py3-paramiko (3.1.0-r1) (10/48) Purging py3-bcrypt-pyc (4.0.1-r2) (11/48) Purging py3-bcrypt (4.0.1-r2) (12/48) Purging py3-cryptography-pyc (40.0.2-r1) (13/48) Purging py3-cryptography (40.0.2-r1) (14/48) Purging py3-pynacl-pyc (1.5.0-r4) (15/48) Purging py3-pynacl (1.5.0-r4) (16/48) Purging py3-cffi-pyc (1.15.1-r3) (17/48) Purging py3-cffi (1.15.1-r3) (18/48) Purging py3-cparser-pyc (2.21-r2) (19/48) Purging py3-cparser (2.21-r2) (20/48) Purging py3-resolvelib-pyc (0.9.0-r1) (21/48) Purging py3-resolvelib (0.9.0-r1) (22/48) Purging py3-yaml-pyc (6.0-r3) (23/48) Purging py3-yaml (6.0-r3) (24/48) Purging py3-gpep517-pyc (13-r2) (25/48) Purging py3-gpep517 (13-r2) (26/48) Purging py3-installer-pyc (0.7.0-r1) (27/48) Purging py3-installer (0.7.0-r1) (28/48) Purging py3-setuptools-pyc (67.7.2-r0) (29/48) Purging py3-setuptools (67.7.2-r0) (30/48) Purging py3-wheel-pyc (0.40.0-r1) (31/48) Purging py3-wheel (0.40.0-r1) (32/48) Purging py3-packaging-pyc (23.1-r1) (33/48) Purging py3-packaging (23.1-r1) (34/48) Purging py3-parsing-pyc (3.0.9-r2) (35/48) Purging py3-parsing (3.0.9-r2) (36/48) Purging python3-pyc (3.11.3-r10) (37/48) Purging python3-pycache-pyc0 (3.11.3-r10) (38/48) Purging pyc (0.1-r0) (39/48) Purging yaml (0.2.5-r1) (40/48) Purging python3 (3.11.3-r10) (41/48) Purging gdbm (1.23-r1) (42/48) Purging libbz2 (1.0.8-r5) (43/48) Purging libffi (3.4.4-r2) (44/48) Purging libpanelw (6.4_p20230401-r6) (45/48) Purging mpdecimal (2.5.1-r2) (46/48) Purging readline (8.2.1-r1) (47/48) Purging sqlite-libs (3.41.2-r2) (48/48) Purging xz-libs (5.4.2-r1) Executing busybox-1.36.0-r8.trigger OK: 392 MiB in 98 packages >>> ansible: Updating the community/x86_64 repository index... >>> ansible: Signing the index...